Beta 7.0.16 will not start - Resolved with updated file

[dvd_maniac]

I installed the newest beta and now Sage will not start.
I installed over the previous beta first.
Result was something like java.lang.NullException

I then uninstalled and removed the Sage folder, rebooted and tried installing it fresh.
Result was I could start Sage and go through the config wizard but towards the end it started getting sluggish and I recieved an out of memory system message in Sage. So I checked Task Manager and found a whole bunch of conhost.exe and sagetranscoder processes.

I uninstalled and I am going back to 7.0.15 until it gets figured out.

Anybody else having similair issues with 7.0.16?

[AlphaCrew]

Originally Posted by dvd_maniac

I installed the newest beta and now Sage will not start.
I installed over the previous beta first.
Result was something like java.lang.NullException

I then uninstalled and removed the Sage folder, rebooted and tried installing it fresh.
Result was I could start Sage and go through the config wizard but towards the end it started getting sluggish and I recieved an out of memory system message in Sage. So I checked Task Manager and found a whole bunch of conhost.exe and sagetranscoder processes.

I uninstalled and I am going back to 7.0.15 until it gets figured out.

Anybody else having similair issues with 7.0.16?

When I went from v6 to v7, about a month ago, I noticed if I didn't have the SageTV service runing before I started the GUI, It would load v6. However with the service running, v7 would load.. Strange Indeed..

Like you, I did the fresh install, and while the above problem went away, I have noticed SageTV seems sluggish in one area. When performing a manual recording, I noticed the "i" icon on the selected show would persist for a very long time before updating to the "m" icon.

Sorry, I could not be more help...

[redman]

I've got the same issue. first time in years an upgrade has stopped working.
I upgraded to .16 now my Sage service wont start (its all headless - no GUI at all.)
try to start the service and it goes straight back to stopped.
log files shows:
Seeker removing LiveStreamMF because the source is gone: MediaFile[id=1955093 FA[BAD AIRING] mask=V host=pvr encodedBy=Hauppauge HD PVR Capture Device S-Video format=MPEG2-TS 0:00:00 0 kbps []]


Last thing that shows, even after a reboot, same error message.

Weird.

[Narflex]

redman,

I know what your bug was; we hit that same one late Friday in some testing. I've uploaded a modified Sage.jar file that will fix the issue. It may be the same as the OP; because it would manifest itself as throwing up a dialog at startup that said "java.lang.NullPointerException". So it will likely fix both of your problems:

http://download.sage.tv/Sage.jar

[dvd_maniac]

The new Sage.jar worked for me...

[toricred]

Should everybody install this fix or only those that had the problem?

[cat6man]

i don't get the service fail but SRE plugin has been toast since 7.0.16, so i'm going to try the JAR and see if that fixes SRE's issue

[Olias]

Ahhh, that's what killed my system. I did the update late Friday night and got the NullExecption error. Tried to do a System Restore and Sage still wouldn't start. I'll revert back and try the .jar file.

[Narflex]

Originally Posted by toricred

Should everybody install this fix or only those that had the problem?

You only need it if you had that problem.

[MrD]

This is interesting.

I updated to .16 last night myself.... but at the same time (terrible I know) I updated the v4l / hdpvr drivers to the head from http://linuxtv.org/hg/v4l-dvb on a 2.6.32 Fedora 12 linux kernel.

This is supposed to fix a kernel oops on hd-pvr usb disconnects; a problem I am having if an HD-PVR needs to be cycled due to a hang.

Anyway I received a null pointer exception at startup and Sage would not start. I rolled back to the previous set of v4l / hd-pvr modules and I was able to start sage.

Is this problem related and fixed by the jar file or should I submit a bug report?

[MrD]

Well I tried the jar file. It allows Sage to start but it does not find the encoders anymore with the newer drivers.

I am wondering in there is an API change that is breaking compatibility. I will try a vanilla kernel next (i.e. 2.6.35) one for which the hd-pvr driver fix is in the mainline kernel source.

In the meantime here is the log:

Sat 9/4 23:46:48.990 [main@87a5cc] Splash: Linux IVTV Capture Manager is initializing...
Sat 9/4 23:46:48.992 [main@87a5cc] videoDevices=[video0, video1]
Sat 9/4 23:46:48.992 [main@87a5cc] Checking encoder key:-84594568
Sat 9/4 23:46:48.994 [main@87a5cc] Capture device is not available, skipping: Haupauge HD PVR 00A1DC8C
Sat 9/4 23:46:48.994 [main@87a5cc] Checking encoder key:-84594677
Sat 9/4 23:46:48.994 [main@87a5cc] Capture device is not available, skipping: Haupauge HD PVR 00A1DC53
Sat 9/4 23:46:48.994 [main@87a5cc] EncoderMap1={}
Sat 9/4 23:46:48.994 [main@87a5cc] Processing new system dev:video0
Sat 9/4 23:46:48.996 [main@87a5cc] V4L: getV4LCardType /dev/null
Sat 9/4 23:46:48.996 [main@87a5cc] java.lang.NullPointerException
Sat 9/4 23:46:48.996 [main@87a5cc] V4L: Testing type for /dev/video0
Sat 9/4 23:46:48.996 [main@87a5cc] V4L: getV4LCardType /dev/video0
Sat 9/4 23:46:48.996 [main@87a5cc] V4L: getV4LInputName /dev/video0 0
Sat 9/4 23:46:49.001 [main@87a5cc] V4L: getV4LInputName /dev/video0 1
Sat 9/4 23:46:49.001 [main@87a5cc] V4L: getV4LInputName /dev/video0 2
Sat 9/4 23:46:49.001 [main@87a5cc] V4L: getV4LInputName /dev/video0 3
Sat 9/4 23:46:49.001 [main@87a5cc] Processing new system dev:video1
Sat 9/4 23:46:49.002 [main@87a5cc] V4L: getV4LCardType /dev/null
Sat 9/4 23:46:49.002 [main@87a5cc] java.lang.NullPointerException
Sat 9/4 23:46:49.002 [main@87a5cc] V4L: Testing type for /dev/video1
Sat 9/4 23:46:49.002 [main@87a5cc] V4L: getV4LCardType /dev/video1

[redman]

Thanks Narflex,
I have applied the jar, and seems ok for the moment.
Will monitor.

Cheers
Chris

[Olias]

Whew, the new jar worked for me!
And more importantly, the wife is happy again.

[Wirenut]

Wow... I was up til 3am this am.... I reverted back to 15..... I'll try the new jar file and the update....

[Bacon2002]

Hi,

The new JAR worked for me.

Thanks,

David

[Wirenut]

Yep. The jar works here as well.

[ranger]

Didn't run into the problem until I re-booted the system a second time. The updated JAR fixed it.

[kwallin]

Ran into problem after a reboot, the updated JAR did NOT fix the problem.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x02ba8123, pid=2548, tid=2552
#
# JRE version: 6.0_21-b07
# Java VM: Java HotSpot(TM) Client VM (17.0-b17 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [DShowCapture.dll+0x28123]
#

[Narflex]

Originally Posted by kwallin

Ran into problem after a reboot, the updated JAR did NOT fix the problem.

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x02ba8123, pid=2548, tid=2552
#
# JRE version: 6.0_21-b07
# Java VM: Java HotSpot(TM) Client VM (17.0-b17 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [DShowCapture.dll+0x28123]
#

This is a different issue I'd think. Please submit a bug report on it http://sagetv.com/bugs.html

[gizmo3141]

Well, I'm on my 5 th install of sage today. Suddenly died with a java exception this morning. Re-install went fine until I changed the recording directories.

CPU shot up to 100%, and stayed there. Can't use the user interface at all under those conditions. Now, Sage stays at User interface is Initializing...FOREVER!

The worst part is, I formatted my recording drive, and hadto lose everything, as this condition appeared to be previously attributed to a corrupt recording directory.

Grrrrr....