Bug 17996 - Cannot stop server and process cannot be killed
: Cannot stop server and process cannot be killed
Status: UNCONFIRMED
Product: Logitech Media Server
Classification: Unclassified
Component: Platform Support
: 7.7.2
: PC Windows Server 2008
: -- major with 2 votes (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-03 06:35 UTC by rosabaer
Modified: 2013-02-11 11:53 UTC (History)
0 users

See Also:
Category: ---


Attachments
Cannot stop server with control panel (2.73 KB, image/png)
2012-08-03 06:35 UTC, rosabaer
Details
Mini dump (3.08 MB, application/octet-stream)
2012-08-03 06:36 UTC, rosabaer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rosabaer 2012-08-03 06:35:35 UTC
Created attachment 7675 [details]
Cannot stop server with control panel

I've got some problems with the Logitech media server 7.7.x. I had to replace my Windows Server 2003 (32-bit) machine with a Windows Server 2008 R2 (64-bit) machine. On Windows Server 2003 I had no problems with the Logitech media server 7.7.x. The installation on the Windows Server 2008 machine was fine but there is something like a infinite loop in the software. There are two issues:
- After the installation the media server is started but i can't stop the media server with the media server control panel. And there is no way to kill the process (squeezesvr.exe) with the task manager (or process explorer)
- After rebooting the server I can access the media server from my squeezebox-boom for about an hour, then it looses the connection

Version 7.6.x works fine.

I've already contacted the Logitech support team. On their suggestion I have 
uninstalled & reinstalled the version 7.7.x in clean boot. But the issue remains. There is no way to stop the server (see screenshot) or to kill the application.

I have attached a mini and a full dump as well.
Comment 1 rosabaer 2012-08-03 06:36:13 UTC
Created attachment 7676 [details]
Mini dump
Comment 2 rosabaer 2012-08-03 08:00:05 UTC
Full dump is too large to attach, I'm sorry.
Comment 3 rosabaer 2012-09-24 07:21:16 UTC
Please have a look at http://logitech-en-emea.custhelp.com/app/account/questions/detail/i_id/8216667

The most important points:

Well there is another bug producing the following error:

Slim::Networking::UDP::init (39) FATAL: There is already another copy of the Logitech Media Server running on this machine. (Only one usage of each socket address (protocol/network address/port) is normally permitted.)

You can reproduced it as follows:
- Start the logitech media server (in my case I've to do it in safe mode, because otherwise I cannot stop the server): The GUI freezes until the server is started
- Click quickly multiple times (2-3x) on the "Stop logitech media server"-button: The GUI does not wait until the server is stopped, so it probably tries to restart the server with the second or third click...

It would be nice if there would be a progress bar or a wait-cursor when the server is going to start or stop. Furthermore the start of logitech media server should not be done in the GUI-Thread (this is why the GUI freezes until the server is started). Sorry I'm a software engineer as well ;-)

But the main critical issues remain...
- The application works fine if I run it in safe mode (without user extensions)
- The server can be started and stopped
- The server can be killed with the process explorer or with the taskkill command
- When running the server with user extensions, the
- The squeezebox-boom loses the connection to the serer after an hour (that varies between some minutes or some hours...)
- The server cannot be stopped
- The server cannot be killed with the process explorer or with the taskkill command
- After trying to stop the server the squeezebox-boom loses the connection to the server

Some more informations when I try to kill the logitech media server (running with user extensions) with the taskkill command:
- I make a lookup for the PID with the tasklist-command
- I kill the logitech media server with the command "taskkill /f /pid 6488" (6488 as an example), this returns the following message:
"SUCCESS: The process with PID 6488 has been terminated."
- Then I list up all running processes again with the tasklist-command -> the process still exists!
- Trying to kill the process a second time ends up with the following messages:
"ERROR: The process with PID 6488 could not be terminated.
Reason: There is no running instance of the task."
- So the process is still somehow there (tasklist, process explorer and the logitech media server GUI recognize that ;-))
Comment 4 rosabaer 2012-09-24 07:21:27 UTC
As well as:

Maybe I did not respond in a proper way. I have uninstalled the LMS as well as anything related to it. But the issue "another copy is running on this machine" can be reproduced by
- Start the logitech media server (in my case I've to do it in safe mode, because otherwise I cannot stop the server): The GUI freezes until the server is started
- Click quickly multiple times (2-3x) on the "Stop logitech media server"-button: The GUI does not wait until the server is stopped, so it probably tries to restart the server with the second or third click...

Therefore this is another bug. And in my opinion this has nothing to do with the other issues.
Comment 5 Simon 2013-02-11 11:48:00 UTC
I'm experiencing the same problem with v7.7.1 on Windows Server 2012 Essentials.

The service seems to freeze after an hour or so (time's not predictable) and it's then impossible to kill the process without rebooting the server although I've not tried running without any extensions.

The service is set up to run at system start-up using the local system account.
Comment 6 Simon 2013-02-11 11:48:54 UTC
I'm experiencing the same problem with v7.7.1 on Windows Server 2012 Essentials.

The service seems to freeze after an hour or so (time's not predictable) and it's then impossible to kill the process without rebooting the server although I've not tried running without any extensions.

The service is set up to run at system start-up using the local system account.
Comment 7 Simon 2013-02-11 11:53:33 UTC
This should probably be re-categorised to Windows Service.