Bug 12678 – After updating plugin settings Squeezebox Server fails to restart with error "Can't write restart flag"

Bug 12678 - After updating plugin settings Squeezebox Server fails to restart with error "Can't write restart flag"

Summary:

After updating plugin settings Squeezebox Server fails to restart with error ...

Status:	CLOSED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Plugins
Version:	7.4.0
Platform:	PC Windows 7

Importance:	-- normal (vote)
Target Milestone:	7.4.0
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-07-05 04:48 UTC by Chris Tashjian
Modified:	2009-10-05 14:25 UTC (History)
CC List:	0 users

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 Chris Tashjian 2009-07-05 04:48:51 UTC

I just updated the plugin settings and when prompted to restart I said ok... I then checked the logs and noticed that the server would not restart:

[09-07-05 07:41:00.4286] Slim::Utils::OS::Win32::restartServer (777) Can't write restart flag (Slim::Utils::Prefs::Namespace=HASH(0xbb06e34)) - don't shut down

I tried 3 times...

Exact version: Squeezebox Server (v7.4, r27423, Sun Jul  5 04:02:13 PDT 2009)

Comment 1 Michael Herger 2009-07-06 00:57:35 UTC

change 27425 - should be fixed in tomorrow's build. Thanks!

Comment 2 James Richardson 2009-10-05 14:25:44 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.