PDA

View Full Version : 6.2.0 is throwing lots of errors and 100% load upon startup



dranch
2005-11-05, 23:53
Hello Everyone,

A while back I upgraded from a Slimp3 to a SB2 running a 6.2Beta with a few bumps in the road:

http://forums.slimdevices.com/showthread.php?t=15672


Anyway.. so here I am upgrading from a very slow 6.2Beta [v2005-08-21] to 6.2.0. (Just a FYI on that "slowness": just selecting the "browse music folder" would take the system ~30 seconds or more to show the first A's of my ~517 artist directories.)

Anyway.. 6.2.0 is running built from the tar.gz file but it initially threw these errors and then 10,000s of the last line:

--
/usr/local/slimserver/slimserver.pl --diag --prefsfile /etc/slimserver.pref


2005-11-05 22:06:55.6189 Odd number of elements in anonymous hash at /usr/local/slimserver/Slim/Web/Setup.pm line 2230.
2005-11-05 22:06:55.6303 Use of uninitialized value in anonymous hash ({}) at /usr/local/slimserver/Slim/Web/Setup.pm line 2230.
2005-11-05 22:06:58.4397 Using a hash as a reference is deprecated at /usr/local/slimserver/Plugins/MusicMagic/Plugin.pm line 1224.
2005-11-05 22:06:58.4434 Using a hash as a reference is deprecated at /usr/local/slimserver/Plugins/MusicMagic/Plugin.pm line 1239.
2005-11-05 22:06:59.1069 Parentheses missing around "my" list at /usr/local/slimserver/Plugins/RPC.pm line 42.
2005-11-05 22:06:59.1147 Useless use of a variable in void context at /usr/local/slimserver/Plugins/RPC.pm line 42.
2005-11-05 22:06:59.1160 Useless use of a variable in void context at /usr/local/slimserver/Plugins/RPC.pm line 42.
2005-11-05 22:06:59.1203 Unquoted string "true" may clash with future reserved word at /usr/local/slimserver/Plugins/RPC.pm line 109.
2005-11-05 22:06:59.1217 Unquoted string "false" may clash with future reserved word at /usr/local/slimserver/Plugins/RPC.pm line 110.

2005-11-05 22:33:04.6577 Use of uninitialized value in substitution (s///) at /usr/local/slimserver/Slim/DataStores/DBI/DBIStore.pm line 1353.

[That last line repeats forever]

At this point, the machine is at 100% CPU utilization and though
the SB2's display for the clock does update, it's only updating once every 10 seconds.


System details:
--
This is running on an OLD server but it's all I have for now
Linux kernel: 2.2.26
glibc-2.1.3
perl, v5.8.7
All other perl modules were installed fresh via the build-perl-modules.pl script


Any ideas on how to get this running?

--David

kdf
2005-11-06, 00:20
On 5-Nov-05, at 10:53 PM, dranch wrote:
>
> Anyway.. so here I am upgrading from a very slow 6.2Beta [v2005-08-21]
> to 6.2.0. (Just a FYI on that "slowness": just selecting the "browse
> music folder" would take the system ~30 seconds or more to show the
> first A's of my ~517 artist directories.)
>
That slownesss of an august build should be very different now. BMF is
a raw file listing in 6.2+ to allow it to be faster.

> Anyway.. 6.2.0 is running built from the tar.gz file but it initially
> threw these errors and then 10,000s of the last line:
>
With all of those errors, I'd almost say you have to have a corrupt
module in there somewhere.
However, --diag can be very hazardous for your server if you just run
with it for no reason. It gets VERY strict with perl; far more than
needed for operational use. Try taking that option out before you go
and erase everything. If that still gives you those syntax error
reports, then something got mixed up.

Also, 6.2.1 has had many fixes added (will be released soon) so
consider trying that as well.

-kdf

dranch
2005-11-06, 20:18
>With all of those errors, I'd almost say you have to have a >corrupt module in there somewhere.

All of the various DBI, zlib compres, etc. modules were just
installed for 6.2.0 cleanly. This machine is very stable so I
don't think these new Perl modules are corrupt. How can I
figure out which module is causing it?


>However, --diag can be very hazardous for your server if you
>just run with it for no reason. It gets VERY strict with
>perl; far more than needed for operational use.

Strict is a good thing here and it seems that unless my Perl
install is very screwed up, looks like 6.2.0 has some minor
errors in the initial startup (as I had indicated). So, instead of not having any logging at all, is there a recommended logging setting I should use to redirect various errors and warnings to a log file? I'd like to do something like:

slimserver.pl --some-log-setting >> /var/log/slimserver.log


Anyway, so I left --diag on overnight and the CPU utilization did come back to zero and the clock is now counting every second.

The issue is that if I run with the usual --daemon mode when I *first* install a new version from scratch, sometimes the slimserver will run for a bit an then silently crash (no errors seen). If I first run the new install in --diag mode, it seems to somehow slow things down enough that things survive over the initialization. Once this first run completes doing possibly things like file/DB initialization, things will then restart ok without the need for additional debugging (see below).

Any ideas on what might be causing this? Seems I have identified a work around which is a good thing and I've confirmed that 6.2.0 is *MUCH* faster than 6.2Beta.

--David