Bug 2999 – Server stops running when you manually update your firmware...

Bug 2999 - Server stops running when you manually update your firmware...

Summary:

Server stops running when you manually update your firmware...

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	6.5b1
Platform:	PC Windows XP

Importance:	P2 minor (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-02-14 11:21 UTC by Joe Willis
Modified:	2008-09-15 14:38 UTC (History)
CC List:	2 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 Joe Willis 2006-02-14 11:21:28 UTC

If you try to update your SB2/SB3 while music is playing from the server, the server will stop running.

This is an issue because often tech support will recommend people to grab nightly revs when troubleshooting.

Comment 1 KDF 2006-02-14 14:56:35 UTC

What is the message in the event viewer at the time of the crash?

Comment 2 Joe Willis 2006-02-16 09:45:40 UTC

(In reply to comment #1)
> What is the message in the event viewer at the time of the crash?

It's not a crash. It literally stops the slimserver, and you have to reactivate it.

Comment 3 KDF 2006-02-16 21:20:16 UTC

stops as in locking up, and you have to kill slimserver and restart?
or stops as in the server goes offline and you have to restart?

If it is the latter, there should still (hopefully) be something in the event viewer that says something about why the service stopped.

Current rev of 6.5 under linux, seems to have no problem with a manual firmware update, so I don't have many other guesses.

Comment 4 Joe Willis 2006-02-17 10:38:00 UTC

stops as in locking up, and you have to kill slimserver and restart?
or stops as in the server goes offline and you have to restart?

If it is the latter, there should still (hopefully) be something in the event
viewer that says something about why the service stopped.

***I didn't know that. Well, it is definitely the latter, so as you suggest -- I'll reproduce it & check the event viewer to see if I can find anything.


-JW

Comment 5 Blackketter Dean 2006-04-21 15:47:09 UTC

I can't reproduce this in 6.2.2.