Hi Dave... There was a thread on the slimserver list about CLI crashing slimserver. Here's a bit of it:
> Followed the instructions from Browny, and I have used both Moose and > slimfx without crashing the server. Looks like perl 5.8.8 solves the > CLI problem. I am running PERL 5.8.8 on both of my machines which might explain why I don't have slimserver crashing here and there. Try upgrading your PERL to 5.8.8 and let us know what happens. ...thanks stuart wrote: > Update... > > I upgraded to slimserver 6.5.2 which now has a fairly complete version > information of all the important software: > ---- > VERSION INFO > > SlimServer Version: 6.5.2 - 12047 - RedHat - EN - utf8 > Server IP address: 0.0.0.0 > Perl Version: 5.8.8 i386-linux-thread-multi > MySQL Version: 5.0.21-standard > ---- > So far I have had no problems. Granted I am running something with bits > and pieces of what I am developing. But the communication between > MClient and Slimserver should be effectively the same. So far I have > had no problems. I have played several selections from two different > albums which both have art work available. Hum, let's try one that has > no art work... well that's no good... I didn't get a reset, but the > text is no longer updated. Not only that but the art work isn't either. > So, apparently, as soon as you hit a track with no art work, something > goes wrong. > > Well, this must be a Heisenberg thing, I started to monitor the CLI > interface from a telnet session and I can not repeat the problem. > > Let me know if you capture anything in the logs. I'll keep playing from > the 6.5.2 server to see if anything else looks funny... > > > stuart wrote: >> Hi Dave... >> >> [EMAIL PROTECTED] wrote: >>> My slimserver is crashing intermittently when I am navigating around >>> MClient. The typical scenario is that I'll be browsing around, >>> finally decide on something, select it, hit OK, and a few seconds >>> later get the "No communication to slimserver" display, which I must >>> say is definetly better than the nothing that I used to get. >> Yea, part of trying to clean up and getting to the bottom of any >> problems people have. >> >>> I don't see anything in the slimserver log, although I don't know how >>> to turn on any deugging in slimserver. >> Server Settings --> Debugging --> "click on stuff you think is important >> to log". >> >> Also, the latest log entries are here: >> http://<slimserver_ip>:9000/log.txt >> >>> I would refrain from posting >>> to the mvpmc group, but I have not seen the behavior when using a web >>> browser to navigate the slimserver stuff, only when using mvpmc. >>> I am running slimserver 6.5.2, and just upgraded to the latest nightly >>> build of mvpmc last night. >> Humm, I should probably upgrade my slimserver. I am running 6.3.1 on >> one machine and 6.5.0 on the other. >> >>> Any ideas as to why this might be happening, or as a temporary measure >>> what I could do to automatically restart the slimserver service when >>> it crashes? >>> >>> Thanks, >>> Dave Stenhouse >> Don't know what is going on. All the CLI communication is fairly >> straight forward. The http communications for the image is also on the >> simple side. >> >> On a linux machine you could write a script and / or cron job to check >> and restart slimserver. I don't know what you can do on a Windows machine. >> >> I'll upgrade one of my machines and test the set up. Do you know when >> the crash happened? Do you use album cover images? Were you moving >> around (i.e. fast forward, reverse) in the selection? >> >> ...thanks for the feed back ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
