Mezzmo Media Server stopping

[mrgenie]

First of all: I'm using this software for a few years now and 100% content with it.
Lately, I upgraded my Server to a new CPU, more RAM, etc bla bla..

Runs 100% smooth, perfect, no issues.

And all of the sudden, it disappears from the network (the DLNA Mezzmo server)
I login to the PC with the mezzmo dlna server, and see that the media server simply stopped.

I switch it on, and everything runs smooth again, but all of the sudden (usually 1 or 2 days between this) it is stopped again..

and it keeps doing that every 1 or 2 days.

Not that it's a big issue, wrote myself a small script on the windows phone to simply click to switch it back on,
but it never did this on my old windows 2012 R2 server..

this is exactly the same configuration, only faster hardware, 8 core, etc..

no error message or anything, just as if I clicked manually on it to stop.

Any reason why it would do that?
Any log I can check what event happens to trigger this behavior?

like I said, no big issue, surely no high priority to handle this.

but why? i hate unanswered questions :)

[Paul]

Mezzmo server should not be stopping for no reason. My guess is that it may be crashing. If you run Mezzmo (Windows) app, then it will prompt you if there are any crash dump files for Mezzmo (Windows) app or Mezzmo server. When you see the Mezzmo crash window appear, click the 'Go To Folder' button and email the crash dump ZIP files to us at support [at] conceiva [dot] com. If they are larger that 10MB, then upload them to a filesharing site like Google Drive, OneDrive, Dropbox, mega.co.nz, etc. and email us the download link(s).

We also have a patch available that contains all the latest fixes for crashes, etc. so email us at support [at] conceiva [dot] com and we can provide that to you for testing.

[fletch]

That happens to me also, but only when I'm agressively playing videos. The solution below worked for me. When it crashes, I just wait a couple of minutes and it comes back up.

802

[xFallenAngelx]

I actually find Mezzmo disappearing off my network sometimes as well, except that my service doesn't stop, it actually hangs instead. So the process is running, but not responding to any requests, including requests to stop the service gracefully. I'm running the latest Mezzmo version. Killing the process with task manager, and starting the service again, brings the device back onto the network.

[Paul]

Please start logging in Mezzmo (see http://forum.conceiva.com/showthread.php/419-FAQ-How-to-turn-on-diagnostic-logging) and restart your Mezzmo server. The next time Mezzmo server server hangs as you describe, kill the Mezzmo server process again and exit Mezzmo app. Zip up all the logs and upload them to a filesharing site like Google Drive, Dropbox, OneDrive, mega.co.nz, etc. and email the download link to us at support [at] conceiva [dot] com.

[shutter]

i'm actually having a very similar problem. just recently rebuilt my media server (software only, same hardware) and switched from windows 8 to windows server 2012. Running the latest version of mezzmo. Have been running mezzmo very happily for several years. what happens is about once a day it stops showing up on the network and i get the following messages in the windows application event log. nothing else shows evident, except that when i open mezzmo it says in the bottom right corner "Media Server: Stopped". no crash dialog or other error messages. I click start media server and it starts back up just fine.

here are the event log messages:
808809810

error 2 and 3 are virtually identical except that the report status changes from 4 to 0.

I've enabled logging and will add those the next time it crashes.

[Paul]

Please do email us the logs when you have reproduced the problem. Email them to support [at] conceiva [dot] com, or upload them to a filesharing site like Google Drive, Dropbox, OneDrive, mega.co.nz, etc. and then email us the download link. We also have a patch available that contains all the latest fixes for v4.1.3.0 so you can email us to try this patch.