Kills my network connection, seemingly at random

[exitwound]

I can't pinpoint the reason yet, but it seems that it's started upon the installation of the newest version 6.0.12.

SageTV will continue to work, but my network will stop working (mostly). The local network becomes unavailable, mapped network drives are unaccessible, and connections to the internet are not working either. The oddball thing is that connections through AIM to profiles and chats still work. But all other connections are severed.

The solution to the problem is not just to set SageTV into standby in the tray, but to kill the process altogether. Immediately, the network connections will be restored and I can reload SageTV.

Any idea what's going on? Any logs would show this error somewhere?

[Mark SS]

Submit a bug report and include the sagetv_x.txt logfiles which cover the time it occured.

[Narflex]

Quite bizarre....please do submit a bug report http://sagetv.com/bugs.html

[reggie14]

Wow, I've been complaining about this for a long time. I thought I was the only one. It only happens when Sage is open and running, but I'm not convinced its a Sage issue.

What components do you have in your computer?

[exitwound]

Oh I forgot to mention. Once I notice my network is down, SageTV will close itself completely after roughly 2-3 minutes. Sometimes I fall asleep at night with SageTV running and wake up and it's gone from the task manager and the system tray.

I will submit a bug report.

I'm running:
AMD 3200+
1GB Crucial RAM
nVidia 7600GT PCIe
ATI Wonder Elite (with remote)
aBit KN8-Ultra w/ onboard nForce4 sound
19" AGM 1440x900 LCD
19" Samsung 1600x1200 CRT (primary for SageTV)
Ultramon to handle the dual desktops

[dennyc]

I have the same problem and it started immediately after upgrading to the version 6 beta. Mine is in a client/server configuration and Sage is the only thing running on the server. Enable/Disable is the only way to get the network back (other than reboot). If you need any logs/debugging help let me know.

[Motofreak75]

Christ

and all this time, I thought it was me.....


I thought it was hardware, perhaps people should start listed hardware and and state if they use it as only as a HTPC ?

I have to disable/enable the network connection so I cna ping the my htpc again,and my MB has two different NICs (Nvidia & Marvel gbits conections) and has the same effect on both with nothing in the error logs.

I have tried XP & MCE 2005 (legit version) tried with all and no updates (doesnt make a difference)
2x Asus AMD ALI- Premium with 2 gigs ram (N-force4 chipset)
Nvidia 7600GS with the latest drivers


I shall be submitting a bugreport later on tonight

[Mahoney]

I don't know if it's related, but Eclipse (the java based IDE) can kill my workstation's network connection entirely when I do Eclipse updates (so when it is accessing the network for a reasonable period of time). This does not occur on my laptop, also using Eclipse. It may be some combination of JVM, hardware and operating system that is the problem? My motherboard is an Asus A8R-MVP, using an Athlon XP 2x4200 CPU.

[reggie14]

I have an Asus A8N-E, Athlon64 X2 3800, and a 6600GT. I'm running Java 1.5.0_06-b05 under WinXP. It is my main desktop, and I run the client software on it. My server does not experience problems.

I have always assumed it was some sort of problem with either the motherboard chipset or the drivers. At one point last year it got really bad, with the network problems starting soon after opening Sage. After a reformat, it seemed to get a lot better, but it still occurs.

One odd thing I noticed is that only new TCP connections seem to be killed. Open TCP connections seem to work for a couple minutes after problems start occuring, and I can still send and recieve UDP packets. Then after 2-3 minutes of that, everything comes down, Sage closes, then the network comes back up.

[GKusnick]

Originally Posted by reggie14

I'm running Java 1.5.0_06-b05 under WinXP.

There are well-known problems with Java 1.5, especially 1.5.0_06 and later. Use the version of Java (1.4.2) that ships with Sage, and don't allow it to automatically update itself.

[reggie14]

In general I think I've had better luck with Java 1.5 than 1.4, so I don't really want to downgrade unless there is reason to believe that it is the cause of my problems. Are you familiar with any known issues in Java 1.5 that would result in problems like these?

I remember my problems started occuring after I switched my recording quality from 2GB/hour to 3GB/hour. At first I assumed it was my router, but then I noticed that it was only my main desktop experiencing problems and that only TCP traffic wasn't working. Lately I've been assuming that its the on-board lan from the nforce4 chipset. Now that I know other people are having problems I don't know what to think.

edit: We don't all have nforce4 boards after all.

[GKusnick]

The biggest issue with 1.5 is a resource leak that, if it goes on long enough, can cause various sorts of failures and lockups in the Java VM.

It's a fairly simple experiment to uninstall 1.5 and install 1.4 to see if that makes a difference. You can always put 1.5 back later if that's what you want to do. Plus it seems likely that SageTV Support will give you the same advice: try it with 1.4 and see if the problem goes away.

[Lucas]

I had this issue pre V6 beta when I was running Java 1.5. At the time I thought it was NIC driver related and the only way to fixit was to restart. A restart was needed every couple of days.

With the move to V6 beta, I also went back to Java 1.4 and the problem stopped.

[exitwound]

Just for the record, I am running Java 1.5.

[dennyc]

Some info. I started to play back the baseball game from last night and it happened almost immediately. Here's the log for that time period:

Wed 10/25 8:27:37.619 Opened MPEG-2 PS file: \\nas\array\video\recording\MLBBaseball-WorldSeriesGame3TeamsTBA-2759519-1.mpg firstPTS=36037 durationMsec=9035226
Wed 10/25 8:27:37.620 Mpeg2Reader seeking to pos=0
Wed 10/25 8:27:37.620 Setting audio stream for playback to be ID=0xc000
Wed 10/25 8:27:37.621 openURL0()
Wed 10/25 8:27:37.622 Sigma video dim=java.awt.Dimension[width=720,height=480]
Wed 10/25 8:27:37.622 pausePush0()
Wed 10/25 8:27:37.664 setMute0()
Wed 10/25 8:27:37.666 getDuration : 9035226
Wed 10/25 8:27:37.667 VideoFrame.timeSelected2(Tue 10/24 21:36:36.010, true) currFile=MediaFile[id=2807609 A[2759519,2759496,"MLB Baseball",11269@1024.20:00,180] host=pvr encodedBy=Hauppauge WinTV PVR PCI II Capture #6 DVD Standard Play format=MPEG2-PS 0:00:00 0 kbps [#0 Video[MPEG2-Video 29.97 fps 720x480 4:3 6400 kbps interlaced]#1 Audio[MP2 48000 Hz 2 channels 384 kbps]] \\nas\array\video\recording\MLBBaseball-WorldSeriesGame3TeamsTBA-2759519-0.mpg, Seg0[Tue 10/24 20:00:05.333-Tue 10/24 20:28:35.294], Seg1[Tue 10/24 20:28:35.304-Tue 10/24 23:00:00.020]] realDur=9035226
Wed 10/25 8:27:37.667 seeking numpushbuffers=0 seekTime=4058476
Wed 10/25 8:27:37.668 MPEG2 seek targetPts=365298877 length=8033091520 durationMsec=9035226 parsedPTS=-1 lastPos=0 firstPTS=36037 mux_rate=25312 estimBitrate=889082
Wed 10/25 8:27:37.668 Mpeg2Reader seeking to pos=3608332288 time=1:07:38.476
Wed 10/25 8:27:37.668 flushPush0()
Wed 10/25 8:27:37.672 Creating new push thread
Wed 10/25 8:27:37.673 VF processing job null nPlayin=true
Wed 10/25 8:27:37.673 Pusher thread is starting
Wed 10/25 8:27:37.677 isRec=false rd=9035226 base=4058476
Wed 10/25 8:27:37.677 VF thread is now waiting for 1:22:56.500
Wed 10/25 8:27:38.034 playPush0()
Wed 10/25 8:28:02.084 Error with MiniPlayer, closing UI: java.net.SocketTimeoutException: Read timed out
Wed 10/25 8:28:02.086 Killing UIMgr UIManager:localhost@@000dfe0004fb-111252f
Wed 10/25 8:28:02.086 Killed UI Timers
Wed 10/25 8:28:17.357 Ministry is waiting for 180 sec
Wed 10/25 8:28:18.876 Exception in the MiniUIClientReceiver of: java.net.SocketException: Connection reset
Wed 10/25 8:28:18.877 Exception in the MiniUIClientReceiver of: java.net.SocketException: Connection reset
Wed 10/25 8:28:18.878 Killing UIMgr UIManager:localhost@@000dfe00771f-1310c3b
Wed 10/25 8:28:18.878 Killed UI Timers
Wed 10/25 8:28:18.879 Seeker.finishWatch(UIManager:localhost@@000dfe00771f-1310c3b)
Wed 10/25 8:28:18.879 VF processing job null nPlayin=false
Wed 10/25 8:28:18.879 VideoFrame thread is now exiting
Wed 10/25 8:28:18.879 Killed VideoFrame
Wed 10/25 8:28:18.882 Killed EventRouter
Wed 10/25 8:28:20.001 Killed RootPanel
Wed 10/25 8:28:20.004 Saving properties file to clients\000dfe00771f.properties
Wed 10/25 8:28:20.058 Disposed Window
Wed 10/25 8:28:22.189 Dropping old MiniPlayer connection because it's old from:000dfe00771f
Wed 10/25 8:28:23.618 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.620 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.624 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.625 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.627 Updated:Watched[id=2811450 Airing=A[2759519,2759496,"MLB Baseball",11269@1024.20:00,180], WatchStart=Tue 10/24 20:00:05.333, WatchEnd=Tue 10/24 21:36:36.961, RealStart=Tue 10/24 22:13:41.824, RealEnd=Wed 10/25 8:28:23.623]
Wed 10/25 8:28:23.628 VF logFileWatch doneAir=A[2759519,2759496,"MLB Baseball",11269@1024.20:00,180] theTime=Tue 10/24 21:36:36.961 recTime=Tue 10/24 20:00:05.333
Wed 10/25 8:28:23.628 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.629 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.631 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.632 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.634 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.635 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.636 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.637 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.639 I/O error reading in push thread:java.io.IOException: The specified network name is no longer available
Wed 10/25 8:28:23.640 Error with MiniPlayer, closing UI: java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.642 stopPush0()
java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.643 Closing down MiniPlayer
Wed 10/25 8:28:23.643 closeDriver0()
java.net.SocketException: Connection reset by peer: socket write error
Wed 10/25 8:28:23.646 Seeker.finishWatch(UIManager:localhost@@000dfe0004fb-111252f)
Wed 10/25 8:28:23.647 Killed VideoFrame

[hechacker1]

this is a weird theory, but I have problems with my wireless network connection due to CPU usage.

Most of the NIC and wireless adapters today are software driven, and therefore CPU driven because of that. I've noticed that whenever my system is using 100% of CPU my wireless network will tend to lose quality and signal strength until the point where it just disconnects.

This happens for me while playing games because most of the CPU is dedicated to serving the game and graphics, not the internet connection.

Anyways, two things helped my problem.

My Computer->Properties->Advanced->Performance->Settings->Advanced:

1. I noticed that if I change Processor Scheduling to Background (which gives equal amount of CPU time to all processes) then my wireless connection seems to drop a whole lot less.

Negative: Because the cpu is equally sharing it's cycles, my Games tend to lag and slow down during critical moments (lots of action on screen) but at least the network connection stays up.

Memory usage: Set to Programs for the best system stability. A fact that a lot of people don't know is that setting this to "Sytem Cache" will often cause conflicts and driver errors (sometimes BSODs even).

My network connection did run better under "Programs" memory usage, but because I have a lot of ram (2GB) I prefer "System Cache" because it tends to use my RAM much more efficiently (by storing almost everything in cache).

Anyways, perhaps SageTV is taxing your system too much and as a side effect your network connection is dying? Just a theory.

[exitwound]

I run my SageTV process on Above Normal thread priority so that I don't get stuttering when the system is being used to do other things (not gaming). The CPU is never above 15% when I use the PureVideo decoder.

[krasev]

Originally Posted by exitwound

I can't pinpoint the reason yet, but it seems that it's started upon the installation of the newest version 6.0.12.

SageTV will continue to work, but my network will stop working (mostly). The local network becomes unavailable, mapped network drives are unaccessible, and connections to the internet are not working either. The oddball thing is that connections through AIM to profiles and chats still work. But all other connections are severed.

The solution to the problem is not just to set SageTV into standby in the tray, but to kill the process altogether. Immediately, the network connections will be restored and I can reload SageTV.

Any idea what's going on? Any logs would show this error somewhere?

do you still have the same proble? I do.
Tech. support is no help. I had a little bit improvement when I disabled any hard drives checkup as from unsupported features of SageTV and as from Dynamic Menus. Well... but for several months I do have this problem. Did you find any solution?