When running the Media Server in a virtual machine (VM), the server process might terminate immediately after launching.
Most likely Cause
To calculate a unique Hardware ID, the VMS requires specific system details from the operating system (OS) API. In certain virtual environments, the OS API fails to return these system values. As a result, the VMS cannot generate a unique Globally Unique Identifier (GUID) and shuts down.
Identify the issue
If your server process terminates unexpectedly, check the Media Server Log files. The issue is present if you see the following log entry which contains:
ERROR: Can't save guid. Run once as administrator.Solution
To resolve this issue, manually generate a new GUID and add it to your server configuration.
Step 1: Generate a new GUID
Go to guidgenerator.com.
Assure UUID v4 is selected
Select the Hyphens option is selected.
Click Generate Some UUID v4s.
Copy the generated GUID to your clipboard.
Step 2: Apply the GUID to your operating system
Follow the instructions below for your specific operating system.
For Windows
Press
Windows Key + Rto open the Run dialog.Type
regeditand pressEnter.In the Registry Editor, navigate to the following path:
HKEY_LOCAL_MACHINE\SOFTWARE\Network Optix\Network Optix Media ServerLocate and double-click the
serverGuidattribute to edit the string.Paste the copied GUID into the Value data field and click OK.
Close the Registry Editor.
Restart the
mediaserverservice, by stopping and starting the Media Server application in the System Tray Overflow Menu
For Ubuntu
Open your terminal.
Navigate to the configuration directory:
cd /opt/networkoptix/mediaserver/etc/Open the configuration file in a text editor:
sudo nano mediaserver.confLocate the
serverGuidattribute and remove its existing value.Paste the new GUID as the value for
serverGuid.Save and close the file.
Restart the media server service:
sudo service networkoptix-mediaserver restart
Comments
0 comments
Article is closed for comments.