PDA

View Full Version : SlimServer 6.1.1. dies in call to time2str upon ALARM



Olaf
2005-09-12, 23:19
My SB failed to wake me this morning because the SlimServer had died on my XP
box, leaving the following msg in the event log

The description for Event ID ( 0 ) in Source ( Application ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: Undefined subroutine
&Slim::Web::HTTP::time2str called at /PerlApp/Slim/Web/HTTP.pm line 1163.

This happened exactly at the time that my alarm was scheduled to go off.
Please advise.

dean
2005-09-13, 11:17
Hi Olaf,

Does this happen every time that your alarm goes off? Looking at
that portion of SlimServer, I can't see why this error would be
triggered, so I'd need a way to reproduce this issue.

-dean

On Sep 12, 2005, at 11:19 PM, Olaf wrote:

> My SB failed to wake me this morning because the SlimServer had
> died on my XP
> box, leaving the following msg in the event log
>
> The description for Event ID ( 0 ) in Source ( Application ) cannot
> be found.
> The local computer may not have the necessary registry information
> or message
> DLL files to display messages from a remote computer. You may be
> able to use
> the /AUXSOURCE= flag to retrieve this description; see Help and
> Support for
> details. The following information is part of the event: Undefined
> subroutine
> &Slim::Web::HTTP::time2str called at /PerlApp/Slim/Web/HTTP.pm line
> 1163.
>
> This happened exactly at the time that my alarm was scheduled to go
> off.
> Please advise.
>
>
>

Olaf
2005-09-13, 13:03
dean blackketter <dean@...> writes:

> Does this happen every time that your alarm goes off?

I wish it was that simple, Dean. No, it does not happen every day. But I am
having no ends of trouble with SS since I installed the last MS security
updates. SS has since become notoriously unreliable to start on reboot. I'd
say that in about 50% of all start-ups (had such a case just now), I get

The description for Event ID ( 0 ) in Source ( Application ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: Perl interpreter
failed.

I know that other folks had this message before and I have not seen a solution
for this issue on this forum yet. These PERL errors are driving me barmy. SS
used to be fairly dependable but recently it's been all but wife-friendly :(

dean
2005-09-13, 13:45
Both of those errors imply some kind of corruption in the software or
memory.

First thing I'd do is run some diagnostics on your machine (memory
test, disk test), just to be on the safe side.

Then I'd try reinstalling SlimServer and see if it's better.

Olaf
2005-09-14, 13:02
dean blackketter <dean@...> writes:

>
> Both of those errors imply some kind of corruption in the software or
> memory.
>
> First thing I'd do is run some diagnostics on your machine (memory
> test, disk test), just to be on the safe side.
>
> Then I'd try reinstalling SlimServer and see if it's better.
>

Well, I only installed 6.1.1. because of the problems I have been encountering
of late. So I doubt it is the s/w. It might be h/w but then why would it
only affect Slim? With mem errors, I had expected the box to blue screen etc.

Olaf
2005-10-19, 13:26
dean blackketter <dean@...> writes:

>
> Both of those errors imply some kind of corruption in the software or
> memory.
>
> First thing I'd do is run some diagnostics on your machine (memory
> test, disk test), just to be on the safe side.
>

Just for the record, Dean: you were spot on; 1 of 4 memory clips was showing
early signs of Altzheimers... :(