media server running twice?

[syndy]

Hi,

I have mezzmo configured to run as a windows service. When I open task manager, I can see it is running twice as a process, I have two entries for mezzmo media server. One is identified as pugwash which is what I renamed it to when I installed, the other identified as Mezzmo. If I stop the server via mezzmo, pugwash disappears from the process list, which is correct. But Mezzmo media server is still running. Starting the media server starts pugwash again.

I can end task to Mezzmo media server via task manger, and all seems to still work ok. a reboot starts both back up again.

So, why is it running twice and how can I prevent two occurrences of Mezzmo media server from running on the same hardware? Its windows 10 build by the way.

Cheers,

Gavin.

[Paul]

Hi Gavin,

The other Mezzmo media server service is probably running under a different Windows login. If you installed and ran Mezzmo under a different Windows account, then that would explain it. In this case, log into your computer under that account and change the media server startup setting for Mezzmo media server in the Media Server Settings dialog.

[ftanner]

Hi Gavin,

The other Mezzmo media server service is probably running under a different Windows login. If you installed and ran Mezzmo under a different Windows account, then that would explain it. In this case, log into your computer under that account and change the media server startup setting for Mezzmo media server in the Media Server Settings dialog.

This happens to me all of the time too, and there's only one Windows login used on this machine. It's not, at least in my case, multiple accounts logged in.

In fact, the user context that the service is running under is the exact same user context that I am logging in under.


I have mentioned this in the past as happening and have never received a real answer as to why this happens or why you can't put some checks in place to ensure that this doesn't happen.

[Paul]

Interesting. Can you take a screenshot of Windows Task Manager (Processes tab) when this occurs and post it here or email it to us at support [at] conceiva [dot] com? That may help us better understand the problem.

[ftanner]

Interesting. Can you take a screenshot of Windows Task Manager (Processes tab) when this occurs and post it here or email it to us at support [at] conceiva [dot] com? That may help us better understand the problem.

One of the things that I have noticed is that there is two Mezzmo services in the Services MMC. One under the name that I named it "rhaevision" (because my daughter said so....hehehe) and another one under the default name of Mezzmo. Other than updates, Mezzmo has only ever been installed once on this machine, it is a dedicated machine that does nothing else, with only one user profile. The rhaevision named service instance is running under the svc-mezzmo account, the proper one, and the Mezzmo named service instance is running under System.

I am beginning to wonder if, when you're updating Mezzmo, it doesn't check to see if the service exists under a non-standard service name and when it doesn't see one called Mezzmo, it creates it. They are both pointing to the same directory.

[Paul]

Thanks for the information. We'll try to reproduce it here.

For the moment, I suggest you remove the unnecessary Mezzmo service. Open a Windows command line window and use the "sc delete" command. See http://technet.microsoft.com/en-us/library/cc742045%28v=ws.10%29.aspx.

[syndy]

many thanks to you both for looking into this. My setup is very similar, 1 windows user, 1 Mezzmo install. I can also see both services running ( the original Mezzmo and the re-named pugwash). I will follow the advice and delete the unwanted Mezzmo service and will check to see if it comes back next update. I have taken some screenshots, let me know if you need them or not as it sounds like you probably don't anymore.


Thanks again,

Cheers,

Gavin.

[Paul]

Hi Gavin,

If the problem persists, then please do email us the screenshots. They may help us understand what's happening.