Bug 5833 – log4perl error messages when scripts return to the console/shell

Bug 5833 - log4perl error messages when scripts return to the console/shell

Summary:

log4perl error messages when scripts return to the console/shell

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Windows Installer
Version:	7.0
Platform:	PC Windows XP

Importance:	P3 minor with 1 vote (vote)
Target Milestone:	7.x
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-10-18 02:43 UTC by Michael Herger
Modified:	2009-07-31 10:15 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Herger 2007-10-18 02:43:14 UTC

When un/installing squeezecenter.exe using the --remove/install parameters I'm getting the following message:

Log4perl: Seems like no initialization happened. Forgot to call init()?
Can't call method "warn" on an undefined value at /<c:\Program Files\SqueezeCenter\server\squeezecenter.exe>Slim/Utils/Log.pm line 241, <DATA> line 164.
END failed--call queue aborted, <DATA> line 164.

I wonder whether this is the reason why Windows seems to time out waiting for SC to be completely shut down.

Comment 1 Chris Owens 2007-11-05 10:55:57 UTC

Cosmetic issue only

Comment 2 Michael Herger 2008-01-18 12:54:37 UTC

*** Bug 6652 has been marked as a duplicate of this bug. ***

Comment 3 Michael Herger 2008-01-18 13:22:54 UTC

Both Windows executables return the same error message. Changing subject accordingly.

Comment 4 Michael Herger 2008-03-27 08:26:06 UTC


*** This bug has been marked as a duplicate of 5758 ***

Comment 5 Michael Herger 2008-04-01 22:14:34 UTC

Now that 5758 is closed I realise this isn't a dupe at all.

Comment 6 Michael Herger 2008-04-10 13:41:25 UTC

*** Bug 7793 has been marked as a duplicate of this bug. ***

Comment 7 Michael Herger 2008-04-10 13:55:10 UTC

kdf:

good spot.  yes, its the same basic issue.  The $rootlogger isn't getting
initialised when the full server isn't being run.  Need to either init the
logger always, or block logWarning et al when logging isn't enabled.
-k

will give this a try.

Comment 8 Michael Herger 2008-04-11 00:38:56 UTC

change 5833 - silence some warnings/errors when immediately returning the script with the usage screen
- initialize logging right after reading the options, but before shutting down
- don't try to close DB if it hasn't been initialized

Comment 9 Michael Herger 2008-04-11 00:40:23 UTC

sorry, that was change 18670

Comment 10 Michael Herger 2008-04-11 01:09:32 UTC

Change 18671 - silence the same warning when installing/removing the Window service

Comment 11 James Richardson 2008-05-06 11:32:49 UTC

(In reply to comment #10)
> Change 18671 - silence the same warning when installing/removing the Window
> service
> 

Closing bug

Comment 12 Chris Owens 2009-07-31 10:15:04 UTC

Reduce number of active targets for SC