PDA

View Full Version : CLI crashing SlimServer



mherger
2007-02-06, 10:45
The new SlimFX skin seems to expose some problems with the CLI (see
http://forums.slimdevices.com/showthread.php?t=32422). This thread is
intended to concentrate on these issues.

When you answer here, please ask the following questions and give some
details about your configuration:

- operating system, flavour, version
- hardware
- SlimServer version
- perl version ("perl -v")

Please start slimserver from the command line using the d_cli and
d_command parameters (or turn them on using the web interface). Connect to
slimserver using the CLI: "telnet yourserver 9090". Run the following
commands until your server crashes:

info total genres ?
info total artists ?
info total albums ?
<playerid> mode ? (where playerid is one of your players)
<playerid> play
<playerid> stop
albums 0 1
albums 0 10
albums 0 10000
genres 0 1
genres 0 10
genres 0 10000
artists 0 1
artists 0 10
artists 0 10000

If SlimServer crashes, please post the logfile here as well.

Last question: are you able to store playlists from within the web
interface?

Thanks for your help!

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

CCRDude
2007-02-06, 11:17
Hardware: Buffalo Kurobox
OS: Debian 4.0.3-3 (PPC... I know, but it was still officially supported when I bought them)
Slimserver: 6.5.1 & SlimServer_6.5_v2007-02-06, both from tarball
Perl: v5.8.4

When I start Slimserver from the command line, albums 0 10000 crashed again. Last lines from log, 2170 is the total album count, so I think it was finished sending this:


2007-02-06 18:02:55.3490 Result: 2169. [id] = [2170]
2007-02-06 18:02:55.3547 Result: 2169. [album] = [Люди инвалиды]
2007-02-06 18:18:35.6239 CLI: Now accepting connections on port 9090

Crash here, telnet client lost connection, nothing else following the enumeration (both parameters added to the init.d-script, since I wanted to avoid errors in using a different configuration (init.d-script specifies Debian-style cache folder, configuration folder, etc). Memory usage was not very high at this point.

Earlier in the log file (still 6.5.1), shortly before the out of memory and invalid pointer messages:

Use of uninitialized value in string eq at /usr/share/slimserver/Slim/Schema.pm line 2187.
Use of uninitialized value in string eq at /usr/share/slimserver/Slim/Schema.pm line 2187.
Use of uninitialized value in string ne at /usr/share/slimserver/Slim/Schema.pm line 2163.
Use of uninitialized value in string eq at /usr/share/slimserver/Slim/Schema.pm line 2187.
Use of uninitialized value in string eq at /usr/share/slimserver/Slim/Schema.pm line 2187.
Use of uninitialized value in string ne at /usr/share/slimserver/Slim/Schema.pm line 2163.
2007-01-26 18:13:33.6462 About to look for files in /mnt/media/Playlists
2007-01-26 18:13:33.8683 For files with extensions in: [(?i-xsm:\.(?:asf|wax|asx|lnk|wpl|m3u|pls|xspf|cue)$)]
Use of uninitialized value in string eq at /usr/share/slimserver/Slim/Music/TitleFormatter.pm line 57.
Use of uninitialized value in string eq at /usr/share/slimserver/Slim/Music/TitleFormatter.pm line 57.

Don't have any players attached while testing this, will do so later to tell you about being able to store playlists.

CCRDude
2007-02-06, 12:53
Update: did power on one SB; can store playlists through the official interface as well as through SlimFX.

mherger
2007-02-06, 14:11
> When I start Slimserver from the command line, albums 0 10000 crashed
> again.

What about the simpler commands (player control, counts etc.)?

> Last lines from log, 2170 is the total album count, so I think

Hmm... I think we need a little more than this. Rather looks like some
startup message than like a crash.

>> 2007-01-26 18:13:33.8683 For files with extensions in:
>> [(?i-xsm:\.(?:asf|wax|asx|lnk|wpl|m3u|pls|xspf|cue)$)]

This is the output you'll typically get when starting a scan?!? Was the
server scanning when you ran the test? Could you make sure the server is
rather idle when running the test?

> Update: did power on one SB; can store playlists through the official
> interface as well as through SlimFX.

Thanks. Don't know what to do with this information, but Fred asked for it
:-)

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

norman12
2007-02-06, 15:24
I've experienced slimserver crashes using SlimFX also.

I'm running Clarkconnect 4 on a Via MII1000 itx M/B 512mB RAM.
6.5.1 slimserver and Squeezebox3 cable connected via router.
Installed plugins - alien BBC and weathertime.
Perl ver 5.8.5 i386

I have run all the commands and the only one that crashes is albums 0 1.

As requested I've checked off the debug settings, but I can't find the log file - any ideas where to find it?

mherger
2007-02-06, 15:31
> I have run all the commands and the only one that crashes is albums 0
> 1.

albums 0 10000 wouldn't crash?

> As requested I've checked off the debug settings, but I can't find the
> log file - any ideas where to find it?

/tmp/slimserver.log or /var/log/slimserver.log?

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

norman12
2007-02-06, 15:48
Micheal,

Yes, albums 0 1 is the only command that causes the crash.
I started from the top of the list, got to albums 0 1 - crashed the instant I pressed return, then worked up from the bottom, again - crashed on albums 0 1. albums 0 10 and 0 10000 both okay.
I've found the log file (thanks), it's rather large so I'm going to run all the commands again

CCRDude
2007-02-06, 15:51
Those from the scanning I only mentioned because they looked like they might be related to the others above, which might be related to the memory leak.

Not sure if the memory leak is related to the crash, since the crash happens otherwise as well ;)

I think that simple player commands would crash as well since Moose in idle mode (background, without having used it) did seem to crash it after some time as well.
I extended my test application to run 100 times the player update function, which includes a full information query (count + name, id, ip, model, displaytype, signalstrength and connected for each player). Did run without problems.

I then extended my application to do a "genres 0 10" a few times... while debugging, the third or fourth time it did that small amount of genres, Slimserver crashed again.

norman12
2007-02-06, 16:04
Very strange.
I've managed to crash the server 4 times in a row with the command - albums 0 1. I've just re-run the tests and it crashed the second time I entered albums 0 1.
log file:
2007-02-06 22:54:22.1123 CLI: Processing request [albums]
2007-02-06 22:54:22.1140 CLI: Dispatching [albums]
2007-02-06 22:54:22.1156
2007-02-06 22:54:22.1802 Request: Query [albums] from CLI (Done)
2007-02-06 22:54:22.1823 Param: [_index] = [0]
2007-02-06 22:54:22.1840 Param: [_quantity] = [1]
2007-02-06 22:54:22.1858 Result: [count] = [418]
2007-02-06 22:54:22.1877 Result: [@albums] is loop with 1 elements:
2007-02-06 22:54:22.1914 Result: 0. [id] = [385]
2007-02-06 22:54:22.1932 Result: 0. [album] = [10 Track Collectors Album]
2007-02-06 22:54:22.1976 CLI: 192.168.0.10:33377 - Sending response [albums 0 1 count%3A418 id%3A385 album%3A10%20Track%20Collectors%20Album...]
2007-02-06 22:54:22.2001 CLI: Sent response to 192.168.0.10:33377
2007-02-06 22:54:36.2044 CLI: 192.168.0.10:33377 - Buffered [albums 0 1
]
2007-02-06 22:54:36.2079 CLI: Processing request [albums]
2007-02-06 22:54:36.2098 CLI: Dispatching [albums]
2007-02-06 22:54:36.2114
2007-02-06 22:54:36.2749 Request: Query [albums] from CLI (Done)
2007-02-06 22:54:36.2768 Param: [_index] = [0]
2007-02-06 22:54:36.2786 Param: [_quantity] = [1]
2007-02-06 22:54:36.2805 Result: [count] = [418]
2007-02-06 22:54:36.2824 Result: [@albums] is loop with 1 elements:
2007-02-06 22:54:36.2843 Result: 0. [id] = [385]
2007-02-06 22:54:36.2861 Result: 0. [album] = [10 Track Collectors Album]

Fred
2007-02-06, 17:26
Right.

Thanks a lot to Michael for investigating this. We're making progress.

This is not an out of memory issue. If anything, the problem with album 0 1 shows this. But it is a pointer issue, i.e. at some point something is referring to the wrong area of memory.

From what I can gather, it only occurs on the more esoteric of OS (Clarkconnect?) and/or hardware platforms, those most likely to have a bug nobody else ever found :(

From the logs, it seems it crashes right when it should send results back, i.e. the query has been processed normally, but something is happening when sending data back to the client.

Keep the reports coming as Michael posted above for now, more data can't hurt in determining the best next step.

Fred

aubuti
2007-02-06, 20:56
OS: Debian (2.4.20_mv131-ppc_linkstation) (aka FreeLink v1.11)
Hardware: Buffalo LinkStation HD-HG250LAN (aka gigabit)
Slimserver: 6.5.1 - 11206 (offical 6.5.1 release)
Perl: 5.8.4

I followed Michael's instructions in post #1 and got it to crash on "genres 0 1". Here's the log excerpts:

2007-02-06 22:18:05.1739 CLI: Now accepting connections on port 9090
2007-02-06 22:18:08.0932
2007-02-06 22:18:08.1043 Request: Calling callback function
2007-02-06 22:18:08.1089 Request: Command [00:04:20:05:b9:61->playlist addtracks] cb+ (Done)
2007-02-06 22:18:08.1101 Param: [_what] = [listref]
2007-02-06 22:18:08.1113 Param: [_listref] = [ARRAY(0x11499250)]
2007-02-06 22:18:08.9041
2007-02-06 22:18:08.9143 Request: Calling callback function
2007-02-06 22:18:08.9188 Request: Command [00:04:20:05:c2:a3->playlist addtracks] cb+ (Done)
2007-02-06 22:18:08.9199 Param: [_what] = [listref]
2007-02-06 22:18:08.9211 Param: [_listref] = [ARRAY(0x1149e11c)]
2007-02-06 22:18:16.3694 Plugin WeatherTime: need to add condition |Snow Late| to translation STRINGS
2007-02-06 22:18:35.4829 Plugin WeatherTime: need to add condition |Snow Late| to translation STRINGS
2007-02-06 22:21:16.7956 CLI: Accepted connection from 192.168.0.5:1372 (1 active connections)
2007-02-06 22:21:23.2001 CLI: 192.168.0.5:1372 - Buffered [i]
2007-02-06 22:21:23.4406 CLI: 192.168.0.5:1372 - Buffered [n]

<snip -- assuming you don't want 800+ lines of log>
<jump to end of 'albums 0 10000' and all of 'genres 0 1'>

2007-02-06 22:23:24.0465 Result: 273. [id] = [90]
2007-02-06 22:23:24.0487 Result: 273. [album] = [Workbench Songs]
2007-02-06 22:23:24.0514 Result: 274. [id] = [242]
2007-02-06 22:23:24.0537 Result: 274. [album] = [World Moods]
2007-02-06 22:23:24.0564 Result: 275. [id] = [134]
2007-02-06 22:23:24.0587 Result: 275. [album] = [Yes]
2007-02-06 22:23:24.7373 CLI: 192.168.0.5:1372 - Sending response [albums 0 10000 count%3A276 id%3A11 album%3A11%2C000%20Virgins%20-%20Chants%20for%20the%20Feast%20o...]
2007-02-06 22:23:24.7415 CLI: Sent response to 192.168.0.5:1372
2007-02-06 22:23:31.9684 CLI: 192.168.0.5:1372 - Buffered [g]
2007-02-06 22:23:32.4565 CLI: 192.168.0.5:1372 - Buffered [e]
2007-02-06 22:23:32.8459 CLI: 192.168.0.5:1372 - Buffered [n]
2007-02-06 22:23:33.6650 CLI: 192.168.0.5:1372 - Buffered [r]
2007-02-06 22:23:33.7558 CLI: 192.168.0.5:1372 - Buffered [e]
2007-02-06 22:23:34.5310 CLI: 192.168.0.5:1372 - Buffered [s]
2007-02-06 22:23:36.6157 CLI: 192.168.0.5:1372 - Buffered [ ]
2007-02-06 22:23:37.1498 CLI: 192.168.0.5:1372 - Buffered [0]
2007-02-06 22:23:37.4365 CLI: 192.168.0.5:1372 - Buffered [ ]
2007-02-06 22:23:37.9703 CLI: 192.168.0.5:1372 - Buffered [1]
2007-02-06 22:23:39.0796 CLI: 192.168.0.5:1372 - Buffered [
]
2007-02-06 22:23:39.0892 CLI: Processing request [genres]
2007-02-06 22:23:39.0913 CLI: Dispatching [genres]
2007-02-06 22:23:39.0932
2007-02-06 22:23:39.1935 Request: Query [genres] from CLI (Done)
2007-02-06 22:23:39.1959 Param: [_index] = [0]
2007-02-06 22:23:39.1982 Param: [_quantity] = [1]
2007-02-06 22:23:39.2006 Result: [count] = [28]
2007-02-06 22:23:39.2033 Result: [@genres] is loop with 1 elements:
2007-02-06 22:23:39.2059 Result: 0. [id] = [3]
2007-02-06 22:23:39.2082 Result: 0. [genre] = [African]

Then it crashed with a segmentation fault.

Re saving playlists from within web interface, it works when I start slimserver the usual way via startup script. Forgot to try it when started via command line.

On a subsequent test it crashed on 'albums 0 10'.

Let me know if you want any of the logfile that I didn't post, and thanks for the work on debugging this.

ddewey
2007-02-06, 21:13
Quoting Fred (Fred.2llzrz1170808202 (AT) no-mx (DOT) forums.slimdevices.com):

>
> Right.
>
> Thanks a lot to Michael for investigating this. We're making progress.
>
> This is not an out of memory issue. If anything, the problem with album
> 0 1 shows this. But it is a pointer issue, i.e. at some point something
> is referring to the wrong area of memory.
>
> >From what I can gather, it only occurs on the more esoteric of OS
> (Clarkconnect?) and/or hardware platforms, those most likely to have a
> bug nobody else ever found :(

Well, I'm running Fedora Core 3, that's pretty mainstream. I only had a few
minutes to run tests today - running the exact same tests that reliably
crashed SS yesterday, without touching the server in between, executed
flawlessly. I was unable to get the server to crash, and slimfx worked
fine.

I'll have more time tomorrow, and see if I can't get it crashing again. :-)

mherger
2007-02-07, 01:29
> I'll have more time tomorrow, and see if I can't get it crashing again.

yeah, don't give up! :-)

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

mherger
2007-02-07, 01:33
> From what I can gather, it only occurs on the more esoteric of OS
> (Clarkconnect?)

ClarkConnect might be less esoteric than it seems: it's IMHO based on
CentOS 4.3, which is the free cousin of RedHat Enterprise Linux 4. I might
give it a test run today as I've just got a DVD on a computer magazine
which features ClarkConnect.

Interestingly I found a posting where some CentOS user complained about
that crash (not SlimServer related, but the same error message, which
seems to be related to glibc). He then was adviced to test with a less
esoteric distribution like RedHat or Fedora...

Did anyobody do the test with the MALLOC_CHECK_=1 parameter
(http://forums.slimdevices.com/showpost.php?p=178246&postcount=76)?

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

CCRDude
2007-02-07, 03:27
> Did anyobody do the test with the MALLOC_CHECK_=1 parameter

Yes, why did you think I mentioned those mem leak reports that weren't related to the crash directly? ;)
I'm not sure if they're the result of using the malloc check, but at least they're of a kind I haven't seen in the logs before.
There are so many of them though that I can't really say if this came only from the malloc check. Or if running it as a daemon would even honor this MALLOC_CHECK, I guess I would need to put it into some default environment for that :-/

Ramage
2007-02-07, 03:43
System tested:

P2 266MHz,192M of RAM, Linux ClarkConnect 3.2, SlimServer Version: 6.5.2 - 11354, Perl v5.8.5.

Ran tests with telnet as per Michael's post with mixed results. Slimserver crashed once every about 4 run-throughs with the request albums 0 10000. Log output was not helpful and just displayed the list of all the albums, just before the crash.

I added d_memory to the debugging and got the following message on the next crash:

*** glibc detected *** free(): invalid next size (fast): 0x0b551950 ***

This is the only error message produced.

Edit: Playlists saved OK.

Hope this helps.

mherger
2007-02-07, 05:55
ClarkConnect might be less esoteric than it seems: it's IMHO based on CentOS 4.3

Wow... I really didn't expect this to be so easily reproducable: I just started a CentOS 4.3 I had lying around, installed slimserver, ran a few CLI commands, then "artists 0 1" - and boom! SlimServer (perl?) died.

There must something be odd on this distro. It's the same collection of songs as I've been using with all my tests so far.

mherger
2007-02-07, 07:03
> Wow... I really didn't expect this to be so easily reproducable: I just
> started a CentOS 4.3 I had lying around, installed slimserver, ran a few
> CLI commands, then "artists 0 1" - and boom! SlimServer (perl?) died.

....and ClarkConnect 4.0 as well :-(

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

Ramage
2007-02-07, 07:45
Ran same series of tests on:

NSLU2 Unslung 6.8b SlimServer Version: 6.3.1 - 8476 - Linux, Perl v5.8.8.

No crashes, and both Moose and slimfx work without problem.

mherger
2007-02-07, 07:59
> NSLU2 Unslung 6.8b SlimServer Version: 6.3.1 - 8476 - Linux, Perl
> v5.8.8.

....and if there's an underpowered machine, then it's the NSLU2 :-). Thanks
for the feedback.

BTW: I've done a "yum update" on the CentOS, which updates some parts of
perl, and I haven't been able to make it crash yet. Unfortunately
ClarkConnect does not include any perl updates in its recently published
service pack :-(

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

aubuti
2007-02-07, 12:59
Just as another piece of info (although not that useful I imagine), I can *not* get it to crash running on:
Ubuntu 6.06
Dell 500MHz Pentium3 256MB RAM (accessing music library on the same LinkStation HAS that crashes when running slimserver with slimfx)
Slimserver 6.5.1
Perl 5.8.8

And hey, slimfx is really slick when it works!

mherger
2007-02-07, 13:57
> Just as another piece of info (although not that useful I imagine), I

Probably not as unnecessary as you think. If you had written success with
perl 5.8.5, this would have confused me. But I'm starting to believe that
perl <=5.8.5 has a problem with whatever is run in the CLI. All report so
far have been using these version.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

Fred
2007-02-07, 14:08
OK, I think this is clear: there is something wrong with perl? in the affected OS.

There is no trick in these commands: once execute finishes (after printing the results), control comes back the the CLI with serializes the results and sends it to TCP/IP.

Here's a CLI.pm file with all debug output enabled. Replace your file in server/Plugins with this one, restart SlimServer and try it again. Maybe we'll discover the problem.

Fred

ddewey
2007-02-07, 14:28
OK, I think this is clear: there is something wrong with perl? in the affected OS.

There is no trick in these commands: once execute finishes (after printing the results), control comes back the the CLI with serializes the results and sends it to TCP/IP.

Here's a CLI.pm file with all debug output enabled. Replace your file in server/Plugins with this one, restart SlimServer and try it again. Maybe we'll discover the problem.

Fred

Tried with this CLI.pm. Started from command line using
./slimserver.pl -d_cli -d_command
Fedora Core 3, perl v5.8.5 built for i386-linux-thread-multi

I can get some commands to return, but still crashes it pretty reliably.

Here's the last one (they all look the same).

Command sent:
artists 0 1000

Sent to stdout:
... <complete list of 645 artists>
2007-02-07 16:21:19.8461 Result: 645. [artist] = [Zuzu's Petals]
2007-02-07 16:21:19.8468 CLI: Back from dispatching [artists]
2007-02-07 16:21:19.8475 CLI: Checking for subscription
2007-02-07 16:21:19.8484 CLI: About to write results
2007-02-07 16:21:19.8492 CLI: cli_request_write(artists)
Segmentation fault

Another one:
Command sent:
albums 0 1000

Stdout:
... <list of 1000 albums>
2007-02-07 16:24:54.3489 Result: 835. [id] = [222]
2007-02-07 16:24:54.3497 Result: 835. [album] = [Zen Arcade]
2007-02-07 16:24:54.3507 Result: 836. [id] = [497]
2007-02-07 16:24:54.3514 Result: 836. [album] = [Zeno Beach]
2007-02-07 16:24:54.3524 CLI: Back from dispatching [albums]
2007-02-07 16:24:54.3532 CLI: Checking for subscription
2007-02-07 16:24:54.3540 CLI: About to write results
2007-02-07 16:24:54.3548 CLI: cli_request_write(albums)
Segmentation fault

mherger
2007-02-07, 14:55
> OK, I think this is clear: there is something wrong with perl? in the
> affected OS.

The fact that my CentOS 4.3 does work properly (it has been running for
several hours, used by SlimFX and SlimRemote) after Perl was updated in a
"yum update" seems to confirm that theory. Before that update it crashed
after only a couple of requests. SlimRemote is hitting it even harder than
SlimFX but it's still stable.

So... if you have the possibility to update your perl, give it a try.
ClarkConnect users seem a bit out of luck, though.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

norman12
2007-02-07, 14:59
OK, I think this is clear: there is something wrong with perl? in the affected OS.

There is no trick in these commands: once execute finishes (after printing the results), control comes back the the CLI with serializes the results and sends it to TCP/IP.

Here's a CLI.pm file with all debug output enabled. Replace your file in server/Plugins with this one, restart SlimServer and try it again. Maybe we'll discover the problem.

Fred

My CC box crashed on albums 0 1
Log file:
2007-02-07 21:51:11.2486 CLI: cli_socket_accept()
2007-02-07 21:51:11.2506 CLI: Accepted connection from 192.168.0.10:33462 (1 active connections)
2007-02-07 21:52:57.6124 CLI: client_socket_read()
2007-02-07 21:52:57.6129 CLI: 192.168.0.10:33462 - Buffered [albums 0 1
]
2007-02-07 21:52:57.6132 CLI: client_socket_buf_parse(192.168.0.10:33462)
2007-02-07 21:52:57.6136 CLI: Using terminator 13 10 for 192.168.0.10:33462
2007-02-07 21:52:57.6139 CLI: cli_process(albums 0 1)
2007-02-07 21:52:57.6156 CLI: Processing request [albums]
2007-02-07 21:52:57.6160 CLI: Dispatching [albums]
2007-02-07 21:52:57.6802 CLI: Back from dispatching [albums]
2007-02-07 21:52:57.6806 CLI: Checking for subscription
2007-02-07 21:52:57.6809 CLI: About to write results
2007-02-07 21:52:57.6811 CLI: cli_request_write(albums)

aubuti
2007-02-07, 15:46
> Just as another piece of info (although not that useful I imagine), I

Probably not as unnecessary as you think. If you had written success with perl 5.8.5, this would have confused me. But I'm starting to believe that perl <=5.8.5 has a problem with whatever is run in the CLI. All report so far have been using these version.


Yeah, I wouldn't have mentioned it at all if you hadn't noted your success after upgrading perl. I'll venture in to upgrading perl on the LS tonight.

aubuti
2007-02-07, 17:07
Upgraded to perl 5.8.8, and ran through Michael's test protocol once without crashing. A few minutes of normal use with slimfx has been smooth, without any crashes.

On a side note, after upgrading perl I re-ran the build-perl-modules.pl script, which generated a slew of errors. So far slimserver seems to be behaving though (fingers crossed...)

ddewey
2007-02-07, 20:58
Upgraded to perl v5.8.6 i386-linux-thread-multi, rebuilt from a src rpm.

Everything seems ducky so far, can't get SS to crash. Ran through the suite of tests successfully, slimfx seems to be fine.

Off to try Fat Gooey now too, see if that works.

Thanks for the help debugging this Michael!

dave

mherger
2007-02-08, 02:12
> Upgraded to perl 5.8.8, and ran through Michael's test protocol once
> without crashing. A few minutes of normal use with slimfx has been
> smooth, without any crashes.

And? Still running?

Thanks for the feedback! I'm glad we can blame it to someone else ;-)

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

mherger
2007-02-08, 02:12
> Upgraded to perl v5.8.6 i386-linux-thread-multi, rebuilt from a src
> rpm.
>
> Everything seems ducky so far, can't get SS to crash. Ran through the
> suite of tests successfully, slimfx seems to be fine.

Thanks for the feedback!

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

aubuti
2007-02-08, 04:38
> Upgraded to perl 5.8.8, and ran through Michael's test protocol once
> without crashing. A few minutes of normal use with slimfx has been
> smooth, without any crashes.

And? Still running?


Yes, I used slimfx for a while last night and no problemo. I didn't go through a second round of the test commands, because all seems good now.

CCRDude
2007-02-08, 10:13
I was hesitant to update to a newer Perl version than 5.8.4 than the one available through Debians stable packages, so I went ahead and tried something different first: I did a perl -MCPAN -e 'upgrade' (just updating the installed Perl modules). Took many hours on the Kurobox, but after doing that and restarting Slimserver, CLI seems more stable, I was able to query the list of genres a dozen times already.

For anyone not wanting to leave the distributions mechanism of updating Perl itself, I would recommend to try this way.

I'm going to implement Artist and Album CLI queries into my test app now and loop-query them a hundred times or so ;)

mick_w
2007-02-24, 02:05
I've just updated Perl in my ClarkConnect 4.0 server...

(Downloaded the latest sorce code (stable.tar.gz) from www.perl.com to the tmp directory, then on a command line entered:)

/etc/init.d/slimserver stop
tar -xzvf stable.tar.gx
cd perl-5.8.8
./Configure -d
make
make test
make install
/etc/init.d/slimserver start

It appears to have installed OK (perl -v reports that I'm now running 5.8.8) and SlimServer is running fine.

But I'm still having the same problem - the SlimFX skin randomly crashes SlimServer. - any ideas?

Mike

mherger
2007-02-24, 10:49
> But I'm still having the same problem - the SlimFX skin randomly
> crashes SlimServer. - any ideas?

No good :-(. Does slimserver (web interface -> Server Settings) confirm
the new perl version? Do you still see the same error messages as before
in the logs?

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

mick_w
2007-02-24, 11:45
It appears slimserver is still using 5.8.5 !!

I must have both versions installed - the problems of doing a default install of 5.8.8 - I'll try to find out whats happening

Thanks for the pointer

Mike

mherger
2007-02-24, 11:56
> I must have both versions installed - the problems of doing a default
> install of 5.8.8 - I'll try to find out whats happening

You can always "patch" slimserver.pl and have it point to your latest perl
version: just edit the top line (#!/usr/bin/perl or whatever) to use your
binary.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

mick_w
2007-02-24, 12:12
I've created a link from where SlimServer thinks Perl is located (/usr/bin/) to where 5.8.8 actually was installed (/usr/local/bin/).

But SlimServer doesn't like my new 5.8.8 Perl and refuses to start...

Looks like I'll have to wait for ClarkConnect to generate a proper package for Perl

Thanks for the help

Mike

Browny
2007-02-24, 12:39
Since I'm stuck with CC's version of Perl I have also had to resort to compiling my own new version of Perl (pretty much identical to your instructions).

The problem with the Perl you've compiled is that it is only the main Perl runtime. You now need to also install all the extra modules that Slimserver uses - I've done this and am now running Slimfx happily on CC 3.2 using Perl 5.8.8

To install the extra modules I needed to do the following (as root):

apt-get update
apt-get install mysql-devel
perl /usr/local/slimserver/Bin/build-perl-modules.pl DBD::mysql DBI XML::Parser::Expat HTML::Parser Compress::Zlib Digest::SHA1 YAML::Syck

For info I needed to install mysql-devel before DBD::mysql would install ok (although I spent a lot of time trying to install the modules from CPAN so I can't be sure on this!).

As Michael suggested I also had to update the first line of slimserver.pl to update the location of perl. An alternative to this would be to copy perl from /usr/local/bin to /usr/bin.

Hope this helps.

Browny

Ramage
2007-02-25, 01:25
Since I'm stuck with CC's version of Perl I have also had to resort to compiling my own new version of Perl (pretty much identical to your instructions).

The problem with the Perl you've compiled is that it is only the main Perl runtime. You now need to also install all the extra modules that Slimserver uses - I've done this and am now running Slimfx happily on CC 3.2 using Perl 5.8.8

To install the extra modules I needed to do the following (as root):

apt-get update
apt-get install mysql-devel
perl /usr/local/slimserver/Bin/build-perl-modules.pl DBD::mysql DBI XML::Parser::Expat HTML::Parser Compress::Zlib Digest::SHA1 YAML::Syck

For info I needed to install mysql-devel before DBD::mysql would install ok (although I spent a lot of time trying to install the modules from CPAN so I can't be sure on this!).

As Michael suggested I also had to update the first line of slimserver.pl to update the location of perl. An alternative to this would be to copy perl from /usr/local/bin to /usr/bin.

Hope this helps.

Browny

Followed the instructions from Browny, and I have used both Moose and slimfx without crashing the server. Looks like perl 5.8.8 solves the CLI problem.

This forum is superb. Great work

mick_w
2007-02-25, 01:39
wow!!!! it works!!!!

I also had to install MySQL 'client' as well as 'developer' with:

apt-get install mysql-client

(this is probably because I didn't select MySQL when I initially installed ClarkConnect)

I'm going to add a full set of instructions on my website for anyone who's interested...

Thanks for all the help

Mike