All of a sudden I can't keep Subsonic running.

[huff009]

So, I've been running SS for about two weeks and, for the most part, it has run flawlessly. However, yesterday I couldn't connect from my Evo 4g at all, although I was able to connect via the test connection. After about an hour, I could no longer connect via the test either. When I got home, I realized I also couldn't open the SS player in my browser. It just said it couldn't locate the site. A reboot of the computer seemed to solve this and everything was good for about 12 hours.

Now I'm experiencing the exact same problem again. Started fine, changed to not being able to connect, but good test connections, and now nothing. Also, I am no longer able to load SS in my browser. I just get the following message:

The webpage at http://localhost:8080/index.view might be temporarily down or it may have moved permanently to a new web address.

I also get this error:

Error 101 (net::ERR_CONNECTION_RESET): Unknown error.

From my Evo I get this message:

A network error occurred. Please check the server address or try again later.

Through all of this, the demo server works fine. Please understand it took me following the setup guide closely and s l o w l y in order to set this up in the first place. I am not very knowledgeable when it comes to networks, etc. so a lot of the conversations I read in the forums are over my head. . . . way over.

Any help would be great. I want to be able to donate, but I need to know this is going to work consistently first. Thanks!

Update: A restart of the computer fixed everything again, however, I still need help on why this is happening all of a sudden. Thanks.

[GJ51]

It's not possible to give you a specific answer on why the server stopped. There can be many causes for this to happen. Sometimes the cause is rooted in a problem with the Operating System, sometimes it can be an ill-behaved application, and then there are hardware issues that can cause problems, such as a bad memory chip. Don't panic, there's no way we can tell remotely what may have happened. I have 3 servers running SS 24/7 that have been up for months without failing and I did the last upgrade to 4.4 beta1 to all 3 in under 10 mins.

Althouhg Subsonic is a complex application that does require a bit of time and reading to set up properly, the effort is well worth it. Not only do you end up with a dynamite application, you also learn a great deal in the process.

If you continue to have a problem, there are many users here willing to help you solve any particular problem. In the meantime, here's some light reading that may be of interest to you.

First read: http://monroeworld.com/android/subsonic/

Never use port 80 - ISP's often use it or block it. 8080,8081, work fine.

In Subsonic Settings/Network - UNCHECK " Automatically configure your router to allow incoming connections to Subsonic (using UPnP or NAT-PMP port forwarding)." make sure to hit the SAVE button, you may have to scroll down to see it depending on your screen size. UPnP or Plug & Pray works sometimes, but not very often and you're better off learning what's going on anyway. You're dipping your toe into the network mgmt. thing anyway, might as well learn what's going on as home networks don't get simpler as time goes on. As your network gets more complex, you're going to have to learn this stuff! No time like the present.

Manually assign a fixed intenal IP and static route to your server at the upper end of the address range of the router, out of the way of DHCP, e.g. 192.168.1.254

Set up your router manually. uPNP might work, but most often it doesn't. Learing how to do it will be a skill you'll love having as your network grows.

Check the Subsonic Control Panel to make sure it's using the right port you're going to use. I typically use 8080, 8081, etc.

Set up port forwarding in your router to direct traffic on the selected port to your server.

Learn your external IP address assigned by your ISP.

Test your setup by entering your external IP:port# to see if it connects. e.g. http://24.88.76.61:8080/ If it works, you're good to go.

Default Transcoding for video:

ffmpeg -ss %o -i %s -async 1 -b %bk -s %wx%h -ar 44100 -ac 2 -v 0 -f flv -

[huff009]

I appreciate the response, unfortunately, this are all things I have already done. They were all part of the initial setup. I use port 8080 and, as I said, the problem seems to be resolved by rebooting my computer.

I haven't made any changes recently (e.g., no new programs, etc. on the computer). The problem seems to be with the computer end of things, and not my phone, since it also prevents me from launching SS in my browser.

Anyway, if anyone else out there has any ideas I'd love to hear them. If you need specific system info, please let me know what and I'll provide it.

Thanks.

[huff009]

bump

[GJ51]

If you followed ALL the steps outlined above for a Windows install, everything should be running fine. As much as it may sound a bit tedious, I would recommend an uninstall/reinstall of both the latest versions of Java and Subsonic. It really doesn't take all that long if you really understand the process, and if you do it carefully, you just may discover what caused the problem.

If after doing that you still have a problem, then it must be either an OS issue or a hardware problem. I have SS running without any issues on thre different versions of Windows. WHS, Server 08 R2, and the SBS7 preview. All instances are stable and work as advertised.

[mr3man]

I've been running subsonic for over a year standalone and on tomcat. After upgrading to 4.4 beta 1 (standalone), I'm having the same problem. I've had to restart the service 3 times in the last 2 days to restore subsonic. While the service is down, the subsonic control panel is still running but the service status, memory usage, etc are blank.

[mr3man]

I switched back to tomcat w/ ssl. seems to be stable again.

[OlYeller21]

When I first started using Subsonic, it worked perfectly. When I started adding massive amounts of files, Subsonic would shutdown unexpectedly and was next to impossible to keep up for more than a portion of a day.

I increased the "Memory limit" that the Subsonic is allowed to 512MB and the problem seems to be solved. I have never had to shutdown and restart the service again and it's never shutdown on its own since.

To increase the memory limit, open the control panel (double click the icon in your system tray), go to the Settings tab, increase the "Memory limit (MC)" to 512.

My Subsonic never gets close to using 512 but I've never cared to reduce the number.