Network Crashing

[jojeaux22]

Problem Description: When Subsonic is accessed from browser, network seems to restart.
I only noticed it at first when outside my network trying to access. While at work, I use VNC to my Win7 machine and usually have SSH open to my Ubuntu server running all day. I first noticed that when I attempted to play anything from the Android app that VNC would disconnect as would Putty and the download on the phone app would halt. After about 30-45 secs, I could reconnect everything again and the app would start downloading again. This would cause everything to crash again.

At first i thought it was the Android app but I would access the subsonic link from my browser (IE, FF and Chrome) and the same thing would happen. I never really noticed it much at home but I use the IP address while there. I thought I would test that as well, using the IP address from my home browser through VNC. As soon as I load Subsonic, everything crashed and came back on its own.

This was working fine until I tried to update from 4.4 to 4.6 for the video stuff

TL;DR - Anything accessing any part of the subsonic application crashes my network.If the service sits there running, with nothing else trying to access, everything will be fine. As soon as you try to access via browser or mobile app, it crashes.

Troubleshooting Steps: I've been working on this for awhile now... The main windows machine has been reimaged to stock Win7. The Server running Subsonic has been replaced with much better hardware than before and also brand new clean build from scratch. I have also replaced the router to a new linksys as well.

I have tried both the stable 4.6 version (deb and standalone) and the 4.7beta3 (deb and standalone). Both occur. Read several various threads as well. even deleted jetty folder and rebuilt which I thought helped until I tried to access outside network.

Playback Application and version: Android app, IE, FF, Chrome
Subsonic Version: 4.7.beta3 (build 3060) August 2, 2012
Server Version: jetty-6.1.x, java 1.6.0_24, Linux (43.8 MB / 76.4 MB)
Hardware Platform: Ubuntu 12.04 Server
Java Memory Limit: Set to 1024

Last ten log file lines:
subsonic.log

Code: Select all

[2012-08-08 16:11:55,075] INFO DaoHelper - Checking database schema.
[2012-08-08 16:11:55,571] INFO DaoHelper - Done checking database schema.
[2012-08-08 16:11:55,935] INFO MediaScannerService - Automatic media library scanning scheduled to run every 1 day(s), starting at Thu Aug 09 03:00:00 EDT 2012
[2012-08-08 16:11:56,010] INFO PodcastService - Automatic Podcast update scheduled to run every 24 hour(s), starting at Wed Aug 08 16:16:56 EDT 2012
[2012-08-08 16:12:01,993] WARN NetworkService - No UPnP router found.
[2012-08-08 16:13:05,269] INFO VersionService - Resolved local Subsonic version to: 4.7.beta3
[2012-08-08 16:13:05,302] INFO PlayerDao - Created player 1.
[2012-08-08 16:13:05,429] INFO VersionService - Resolved latest Subsonic final version to: 4.6
[2012-08-08 16:13:05,430] INFO VersionService - Resolved latest Subsonic beta version to: 4.7.beta3
[2012-08-08 16:14:08,135] INFO MusicFolderDao - Created music folder /media/store/Pub/Music/Zune
[2012-08-08 16:14:08,136] INFO MediaScannerService - Automatic media library scanning scheduled to run every 1 day(s), starting at Thu Aug 09 03:00:00 EDT 2012
[2012-08-08 16:14:19,978] INFO MediaScannerService - Automatic media library scanning scheduled to run every 1 day(s), starting at Thu Aug 09 03:00:00 EDT 2012
[2012-08-08 16:14:39,037] INFO CoverArtController - Created thumbnail cache /var/subsonic/thumbs/200
[2012-08-08 16:16:14,965] INFO PlayQueueInputStream - admin listening to "A Day To Remember/01 - Intro.mp3"
[2012-08-08 16:16:20,233] INFO CoverArtController - Created thumbnail cache /var/subsonic/thumbs/48
[2012-08-08 16:16:56,011] INFO PodcastService - Starting scheduled Podcast refresh.
[2012-08-08 16:16:56,011] INFO PodcastService - Completed scheduled Podcast refresh.
[2012-08-08 16:16:57,304] INFO PlayQueueInputStream - admin listening to "A Day To Remember/02 - Heartless.mp3"


subsonic_sh.log - mostly ever filled with GC and Full GC

Code: Select all

4248 [main] INFO org.springframework.web.servlet.DispatcherServlet - FrameworkServlet 'subsonic': initialization completed in 780 ms
4266 [main] INFO org.mortbay.log - Started SelectChannelConnector@0.0.0.0:4090
Subsonic running on: http://localhost:4090/
4333 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Looking for RMI registry at port '9412'
4349 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Could not detect RMI registry - creating new one
4402 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Binding service 'SubsonicDeployerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[127.0.1.1:9412](local),objID:[0:0:0, 0]]]]
[GC 30904K->9362K(73856K), 0.0222540 secs]
[Full GC 9362K->9274K(73856K), 0.1043410 secs]
[GC 36218K->10228K(75200K), 0.0037200 secs]
[GC 38068K->11678K(69440K), 0.0045010 secs]
[GC 38622K->12471K(74112K), 0.0042970 secs]
[GC 39543K->13881K(73984K), 0.0050160 secs]
[GC 40953K->16375K(89728K), 0.0094810 secs]
73296 [btpool0-8] INFO org.directwebremoting.log.startup - Starting: DwrServlet v3.0.0.116.rc1 on jetty-6.1.x / JDK 1.6.0_24 from Sun Microsystems Inc. at
[GC 59549K->22618K(89856K), 0.0259010 secs]
[GC 65946K->33446K(113664K), 0.0587810 secs]
[GC 98342K->33548K(118144K), 0.0193240 secs]
[GC 98444K->34314K(132736K), 0.0170690 secs]
[GC 125194K->35888K(146048K), 0.0074120 secs]
[GC 129264K->36188K(131456K), 0.0074240 secs]
[Full GC 36188K->31493K(143552K), 0.1979230 secs]


[GJ51]

I don't use Linux so I can't help too much with your server setup, but we run several servers on Windows and use VNC to log onto our network from all over the country. Running Subsonic has never crashed the network for us so I would have to conclude that the source of your issue is most likely in your server setup and how it is interacting with your network.

I'm not too clear on what you mean by "crashing your network" does that mean that all network traffic ceases and you have to reboot the router to get internet connection and peer to peer communication restored?

I've never run into that scenario before. Can you describe what is actually happening in a bit more detail?

[jojeaux22]

I did a little more testing last night when I was actually home instead of trying to troubleshoot this at work.

That being said, my initial thought was I was overloading my router and the router was restarting (dropping connections for all the users on my network) and coming back online. It made sense at the time. Then I was home and had one of those dumb realizations. I noticed that network shares and any other remote management that I had opened were not closing when my 'network crashed'. Turns out that its not my router that is crashes, its my modem that is losing its internet connection.

New Scenario: I did some more testing. I closed everything on ever computer. I started the subsonic service on my server. Everything was good so far, nothing weird happening. Then I went into a browser and launched Subsonic from the ip address. Logged in fine and picked a handful of songs for a playlist. Pressed play and almost instantly, network lost internet but the songs were still downloading at good pace so I'm assuming my LAN was fine (checked some network shares as well). Tried the same thing from my phone (wifi, ipaddress for server, made playlist, lost internet).

I guess my main question is this; why would playing songs through my LAN, not routing through internet as far as I can tell, drop my internet connection? I can use subsonic all the live long day at home now, assuming I don't want to browse the web at the same time.

I'm going to try to install on a windows environment to see if it still happens. Hopefully it will narrow it down to the linux server itself and subsonic.

[GJ51]

Not enough information to be sure, but wireless routers are notorious for going belly up after about two years due to heat issues. If your router is doing all the DCHP for the network that would explain why everything dies under enough load to overheat and failthe router.