Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-20 Thread karlek
Enjoy! :) karlek's Profile: http://forums.slimdevices.com/member.php?userid=64321 View this thread: http://forums.slimdevices.com/showthread.php?t=107690 ___ Squeezecenter mail

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-20 Thread tv69
karlek wrote: > Malformed databases. > Please rename all database files (*.db) in > /opt/ssods4/var/home/SqueezeboxServer/Cache to *.db.old karlek, That was it! Thanks very much. I learned something new. The server is running and scanning the library as I type this. Cheers, T ---

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-19 Thread karlek
Malformed databases. Please rename all database files (*.db) in /opt/ssods4/var/home/SqueezeboxServer/Cache to *.db.old karlek's Profile: http://forums.slimdevices.com/member.php?userid=64321 View this thread: http://foru

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-19 Thread tv69
karlek wrote: > Delete the server.log, start LMS. When it's stopped again, post the Log > here. > Have you tried "/opt/ssods4/bin/ssctrl start"? Maybe we get some > messages from the console. Thanks for showing me how to reset and get info from the log file. Here it is... Looks like a problem w

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-19 Thread dergilb
tv69 wrote: > Is the cache stored in the 'tmp' folder? You can see which path is used for cache in Settings / Information in the Web UI. But if a system's restart doesn't do anything, then it's a different kind of problem. Never mind. I think I broke it. --

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-18 Thread karlek
Delete the server.log, start LMS. When it's stopped again, post the Log here. Have you tried "/opt/ssods4/bin/ssctrl start"? Maybe we get some messages from the console. karlek's Profile: http://forums.slimdevices.com/mem

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-18 Thread tv69
dergilb wrote: > Hi, try to restart the whole system, not only LMS. Did you delete the > cache by any chance? That's when I get this problem. I have tried it a few times and even removed LMS and reinstalled it. Is the cache stored in the 'tmp' folder? I deleted everything in the 'tmp' folder,

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-18 Thread tv69
karlek wrote: > More Info is required: > What QNAP running > Which Firmware (QTS?) > What Version of LMS? > What shows server.log? > Are there any error messages of SSOTS while starting LMS? > > Maybe you ssh in your QNAP and execute "ssctrl start" from command line. > I don't know exactly where

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-18 Thread dergilb
tv69 wrote: > When clicking the start button it tries to restart the server but it > fails and the same error is given with different PID#. Hi, try to restart the whole system, not only LMS. Did you delete the cache by any chance? That's when I get this problem. I think I broke it. --

Re: [SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-18 Thread karlek
More Info is required: What QNAP running Which Firmware (QTS?) What Version of LMS? What shows server.log? Are there any error messages of SSOTS while starting LMS? Maybe you ssh in your QNAP and execute "ssctrl start" from command line. I don't know exactly where to find ssctrl, maybe in /opt/ss

[SlimDevices: SqueezeCenter] Process status : not running (crashed as PID 19525)

2017-07-17 Thread tv69
Hello, Seems my LMS has a new problem and does not seem to run. I tried a new installation on QNAP and when checking status via SSOTS on port 9099, the server is not running. When clicking the start button it tries to restart the server but it fails and the same error is given with different PI