PDA

View Full Version : Problem with Slimserver 6.1 crashing



awshirley
2005-10-02, 22:14
I've got Slimserver 6.1 running on a Mandrake 10.2 PC. Slimserver intermittently crashes and I have to restart it. Sometimes it will crash after I've told it to clear the database and rescan all my files. Other times it just dies when I've done nothing to it.

I'm tempted to write a script and put it on the cron to check Slimserver every minute. If Slimserver is not running, restart it, otherwise exit. I don't really want to do this because it's like putting a band-aid on the problem and not really fixing it.

Does anyone have any ideas of things I should look at?

All help is greatly appreciated.

Thanks,
Andy

Dan Sully
2005-10-03, 10:33
* awshirley shaped the electrons to say...

>I've got Slimserver 6.1 running on a Mandrake 10.2 PC. Slimserver
>intermittently crashes and I have to restart it. Sometimes it will
>crash after I've told it to clear the database and rescan all my files.
>Other times it just dies when I've done nothing to it.
>
>I'm tempted to write a script and put it on the cron to check
>Slimserver every minute. If Slimserver is not running, restart it,
>otherwise exit. I don't really want to do this because it's like
>putting a band-aid on the problem and not really fixing it.

Do you get any sort of error message when it crashes?

What version of perl are you using? perl -V will tell you.

-D
--
<iNoah> you know, most free operating systems come preinstalled with their own high horse.

awshirley
2005-10-03, 11:06
I upgraded to the latest build for 6.2 (dated Oct 3). I just checked it and the server had died. Log file showed:

2005-10-03 10:17:43.7950 DBD::SQLite::db do failed: no such table: contributor_album(1)
at dbdimp.c line 268 at /usr/local/slimserver/Slim/DataStores/DBI/DataModel.pm line 76, <$fh> line 23.
2005-10-03 10:17:43.7954 Couldn't execute SQL statement: [DROP TABLE contributor_album;] : [DBD::SQLite::db do failed: no such table: contributor_album(1) at dbdimp.c line 268 at /usr/local/slimserver/Slim/DataStores/DBI/DataModel.pm line 76, <$fh> line 23.
]

Version of perl I'm running is v5.8.6...

Dan Sully
2005-10-03, 11:22
* awshirley shaped the electrons to say...

>I upgraded to the latest build for 6.2 (dated Oct 3). I just checked it
>and the server had died. Log file showed:

Remove your slimserversql.db file. It's probably in /usr/local/slimserver/Cache/.slimserversql.db

-D
--
<dr.pox> what're the units of the coefficient of agnosticity? I don't knows per hour?

awshirley
2005-10-03, 12:55
I found the file in /usr/local/slimserver. I deleted it, but the server still crashes. I'm not finding any entries in the log. I've remove the RPM and reinstalled it. Slimserver is crashing when it goes to scan the my music library.

The library is on a share pointed to a Win2k3 server. I'm using the CIFS to access the windows share...

Dan Sully
2005-10-03, 13:01
* awshirley shaped the electrons to say...

>I found the file in /usr/local/slimserver. I deleted it, but the server
>still crashes. I'm not finding any entries in the log. I've remove the
>RPM and reinstalled it. Slimserver is crashing when it goes to scan the
>my music library.
>
>The library is on a share pointed to a Win2k3 server. I'm using the
>CIFS to access the windows share...

Can you run slimserver.pl manually, with a few debug options?

perl slimserver.pl --d_import --d_scan

Thanks.

-D
--
It does not do to leave a live Dragon out of your calculations..

awshirley
2005-10-03, 14:12
It died twice during a library scan. Nothing showed up on the screen indicating an error message, just a segmentation fault.

I restarted the scan from the GUI and told it to clear the DB before the scan and it got all the way through.

awshirley
2005-10-03, 14:18
I've tried to restart it from the slimserver script in the /etc/init.d directory, but won't stay running. I'm trying perl slimserver.pl --d_import --d_scan from the command line and it stays up...I just don't get it...

kdf
2005-10-03, 14:26
Quoting awshirley <awshirley.1wchnb (AT) no-mx (DOT) forums.slimdevices.com>:

>
> I've trying to restart it from the slimserver script in the /etc/init.d
> directory, but won't stay running. I'm trying perl slimserver.pl
> --d_import --d_scan from the command line and it stays up...I just
> don't get it...

the init.d script runs under a different user, and has the prefs file in
/etc/slimserver.conf. If you run slimserver.pl as a user, with a pref file in
the user's home directory.

try:
slimserver.pl --d_import --d_scan --prefsfile /etc/slimserver.conf

and see if that makes a difference. It may also be a permissions issue if the
slimserver user can't access something.

-kdf

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

snarlydwarf
2005-10-03, 14:38
It died twice during a library scan. Nothing showed up on the screen indicating an error message, just a segmentation fault.

It said 'segmentation fault'?

That specific string is coming from the kernel when a process misbehaves itself and tries to get to memory it hasn't asked nicely for.

Ie, a pointer points to '0xf9f89f99' or somesuch and the kernel, keeper of memory, knows that the application didn't ask for that.

Now, in Perl, you can't do that. 'Real' pointers just aren't used by programmers: there is a layer of abstraction and you can't get past it that I know of. So that would imply a bug in Perl.... but Perl is very well-studied by lots of projects, and though it almost certainly will always have bugs, such bugs should be easy to reproduce, not rarities like yours.

So what this sounds like to me is the classic, "when i try to build a new kernel, gcc segfaults!" problem, which isn't gcc or linux at all: it's almost always a bad memory simm.

http://www.bitwizard.nl/sig11/ has more details on this.

Robin Bowes
2005-10-03, 22:37
awshirley said the following on 03/10/2005 22:18:
> I've trying to restart it from the slimserver script in the /etc/init.d
> directory, but won't stay running. I'm trying perl slimserver.pl
> --d_import --d_scan from the command line and it stays up...I just
> don't get it...

If you're running from the command-line aqs root then slimserver will
not be able to write to the prefs file when you run it from the init
script as it runs as user "slimserver".

R.

--
http://robinbowes.com

If a man speaks in a forest,
and his wife's not there,
is he still wrong?

awshirley
2005-10-05, 14:05
It said 'segmentation fault'?

That specific string is coming from the kernel when a process misbehaves itself and tries to get to memory it hasn't asked nicely for.

http://www.bitwizard.nl/sig11/ has more details on this.

That gave me the clue I needed. Previously I had use WinXP on this PC. I went into the BIOS and turned off the agressive memory settings (that worked under WinXP). Now the SlimServer is rock solid. I also tried to compile some programs that previously took more than one attempt to get them to compile...

Thanks for the help! This stabilized my PC overall!!