On 25/08/06, Heimiko <[EMAIL PROTECTED]> wrote:
Dr Lovegrove;130897 Wrote: > On 25/08/06, Michael Herger <slim (AT) herger (DOT) net> wrote: > Also worth checking the Moose logfile - this'll show what messages > Moose is firing at the server.. > Moose generated a load of text rather quickly. While moose was logging, I reproduced the error. Log file was too big to attach it here, so you can view it from here: http://www.heimiko.com/downloads/moose_log.txt Hope this will be of some help
Thanks for that.. Nothing too obvious there.. Moose is just building up the playlist (which has 108 songs).. It requests it in chunks of 3 songs at a time and gets the first 96 song details ok, but then SS dies when Moose asks for the next 3 songs: 00:04:20:06:38:14 status 96 3 tags%3Ajalydestru My guess is the server's doing something fairly cpu/disk intensive and the extra flood of CLI's is just pushing it a bit too far and <pop>.. -- - Dr Lovegrove http://www.rusticrhino.com/drlovegrove _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/plugins
