Okay, looks like my box is much happier now that the clock is back to 366Mhz. Slimserver used to crash after about 5 minutes. Now onto a slightly different problem... with the same box.

On a library of 12,000 songs the first scan ended up taking 76M of memory at about 2 hours into the scan. Is this normal? After that 2 hours of scanning slimserver.pl exited and I had an entry in /emp/slimserver.log that said...

'Insane number of Timers 8857'

Any suggestions??

Mandrake 9.1
RPM Install
Perl 5.8.0
P-II 366
384M RAM

jess



Dan Sully wrote:

* Jess Askey shaped the electrons to say...

slimserver runs at about 85% cpu and 36Meg of memory on the machine until it crashes. It seems to crash in different places everytime too so Im wondering if the problem is something with my CPU overheating or something. The machine is a P-II 366 overclocked to a 533 but it has always run fine doing Apache, Postgresql and Bind. Apache isn't running on it anymore. I did used to have problems with my .shn to .mp3 conversion script (PERL) in that it would consistently crash this machine as well. So, I guess I will try dropping the CPU speed down to normal and see what happens.


Jess - you have kernel Ooopses, which are beyond our control.

SlimServer certainly might exercise your machine more, which exposes hardware issues.

The kernel trace you sent points in either a memory issue (which could be CPU
related) or a disk one (the llseek).


-D



_______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to