Wiz.bin corruption with 2.6.24 kernel and Save 6.3.x

[svemuri]

Hello,
I just upgraded my kernel to 2.6.24 (Running on CentOS 5.1) and all of a sudden the Wiz.bin is corrupted. I have two ATSC tuners (Air2PC and A180, both DVB devices). I can tune to them fine. But there appears to be a problem with Sage trying to populate EPG data. If I delete all the adapters, the corruption does not happen. But If add the adapters back in, add the channels, and restart sage, the DB becomes corrupt.

I have done a number of things including starting fresh with a 6.3.9 beta, but nothing helped. Also, when starting fresh, if I scan channels, sage servers crashes.

Is any one else using 2.6.24 kernel successfully with 6.3.x Sage?

THanks
Sarat.

Here is a sample of sagetv_0.txt complaining about corruption

Tue 2/19 13:28:20.767 Changed default timezone to:Eastern Standard Time
Tue 2/19 13:28:20.791 user.dir2=/opt/sagetv/server
Tue 2/19 13:28:20.791 classpath=Sage.jar:.:/:JARs/commons-jxpath-1.1.jar:JARs/commons-logging-api.jar:JARs/commons-logging.jar:JARs/jcifs-1.1.6.jar:JARs/mx4j-impl.jar:JARs/mx4j-jmx.jar:JARs/mx4j-remote.jar:JARs/mx4j-tools.jar:JARs/sbbi-jmx-1.0.jar:JARs/sbbi-upnplib-1.0.3.jar
Tue 2/19 13:28:20.791 JVM version=1.6.0_04
Tue 2/19 13:28:20.792 OS=Linux 2.6.24.2sv1
Tue 2/19 13:28:20.799 SageTV V6.3.9.1
Tue 2/19 13:28:20.802 hostname=fatboy.svemuri.com
Tue 2/19 13:28:21.521 Wizard starting to load database info...
Tue 2/19 13:28:21.529 DBFile at version 65 FileSize=2022697
Tue 2/19 13:28:21.529 Wizard allocating table for Year of size 18
Tue 2/19 13:28:21.531 ERROR DB RECORD LENGTH VIOLATION was 10 should be 26378 fp=4 length=2022697 opcode=4 typecode=0
Tue 2/19 13:28:21.531 sage.ar.ci(Unknown Source)
Tue 2/19 13:28:21.531 sage.ar.f(Unknown Source)
Tue 2/19 13:28:21.531 sage.ar.a(Unknown Source)
Tue 2/19 13:28:21.531 sage.ar.ck(Unknown Source)
Tue 2/19 13:28:21.531 sage.SageTV.<init>(Unknown Source)
Tue 2/19 13:28:21.532 sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Tue 2/19 13:28:21.532 sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
Tue 2/19 13:28:21.532 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Tue 2/19 13:28:21.532 java.lang.reflect.Constructor.newInstance(Unknown Source)
Tue 2/19 13:28:21.532 java.lang.Class.newInstance0(Unknown Source)
Tue 2/19 13:28:21.532 java.lang.Class.newInstance(Unknown Source)
Tue 2/19 13:28:21.532 sage.Sage.void(Unknown Source)
Tue 2/19 13:28:21.532 sage.Sage.b(Unknown Source)
Tue 2/19 13:28:21.533 SecuredLoader.main(SecuredLoader.java:5)
Tue 2/19 13:28:21.537 Error with DB file:java.io.IOException: BOGUS command length, ending file load now. req=1729798158 atual=2022697, attempting to restore backup.
Tue 2/19 13:28:21.538 Wizard starting to load database info...
Tue 2/19 13:28:21.538 DBFile at version 65 FileSize=2673508
Tue 2/19 13:28:21.538 Wizard allocating table for Year of size 3

[svemuri]

Just downloaded and compiled 2.6.23-16. It appears to work fine without corruption. I think 2.6.24 included a lot of DVB/V4L patches and may have broken something in Sage.
Sarat.

[bcjenkins]

How many nics in the machine? I am using 2.6.24 on Arch with no issues.

B

[svemuri]

2 NICs. One Realtek 8111B and a D-Link.

I just got a reply from Sage support saying that I need to re-run keygen.sh and re-register. I'll try that when I get a chance

Sarat.

[kbyrd]

I moved my Sage/NAS Linux server to a new motherboard today. Because I'm an idiot, it didn't occur to me that I would need to re-keygen Sage on the new motherboard. It caused a small panic attack when restoring a Wiz.bin from a backup didn't work.

SageTV guys, would it be that hard to post something obvious in the debug log like: "Warning! No activation key!" instead of hoping that I found the right search terms?

For the record, "BOGUS command length" was what I searched for as that seemed the most unique thing in the log file.

[drewg]

Originally Posted by kbyrd

I moved my Sage/NAS Linux server to a new motherboard today. Because I'm an idiot, it didn't occur to me that I would need to re-keygen Sage on the new motherboard. It caused a small panic attack when restoring a Wiz.bin from a backup didn't work.

SageTV guys, would it be that hard to post something obvious in the debug log like: "Warning! No activation key!" instead of hoping that I found the right search terms?

Amen. I've been bitten by that as well.

Drew

[kbyrd]

....and a couple years later, this bit me again. I really wish someone at Sage would change the error message to something more like: "Hey your license key is invalid, did you steal this or did you just change your hardware recently?"

[razrsharpe]

Originally Posted by kbyrd

I really wish someone at Sage would change the error message to something more like: "Hey your license key is invalid, did you steal this or did you just change your hardware recently?"

ever submit an enhancement request?