INTERACT FORUM

More => Old Versions => JRiver Media Center 20 for Linux => Topic started by: posixx on December 03, 2014, 05:56:12 am

Title: License lost after server reboot
Post by: posixx on December 03, 2014, 05:56:12 am
Guys,

Running MC20 on ubuntu 64-bit. Everytime my server reboots i get the message 'The trial period has expired' on my screen. I have to restore the license through my registation code. But obvoisly i don't have much restores available this way.

How to prevent this fdrom happening everytime the serrver is rebooted? If i restart mediacenter without rebooting the server the license is still active.
Title: Re: License lost after server reboot
Post by: JimH on December 03, 2014, 07:16:17 am
Is the license you're installing for the correct version?
Title: Re: License lost after server reboot
Post by: posixx on December 03, 2014, 07:27:30 am
Yes of course. As i said when installing it it gives me the successfully installed message and i get a new email from jriver with a mjr file attached.
Title: Re: License lost after server reboot
Post by: posixx on December 03, 2014, 09:26:47 am
It seems the license file remains in the .jriver/Media Center 20/Temp directory. Could that be the problem?

Title: Re: License lost after server reboot
Post by: JimH on December 03, 2014, 10:03:26 am
Is your system date correct?
Title: Re: License lost after server reboot
Post by: posixx on December 04, 2014, 06:23:59 am
Syncing with pool.ntp.org so yes, the date and time are correct.

Currentlu the license is gone out of the Temp folder. On which location is the license stored so i can check if it's there?
Title: Re: License lost after server reboot
Post by: JimH on December 04, 2014, 06:41:27 am
Syncing with pool.ntp.org so yes, the date and time are correct.

Currentlu the license is gone out of the Temp folder. On which location is the license stored so i can check if it's there?
Bob should be able to help you later today.  We don't discuss details about the license mechanism.
Title: Re: License lost after server reboot
Post by: posixx on December 05, 2014, 04:44:43 am
@Jim: I didn't hear from Bob; did he try to contact me?

Title: Re: License lost after server reboot
Post by: JimH on December 05, 2014, 06:18:09 am
I'll ping him, but take a look at other threads here. 
Title: Re: License lost after server reboot
Post by: posixx on December 08, 2014, 05:09:40 am
An update about this problem, for future reference; we use a bonding interface on the server. It appears the MAC address can change according to the first initated NIC during boot. After adding a delay on bringing up eth1 we now get the same MAC address on the bond interface between reboots and the license is kept between reboots
Title: Re: License lost after server reboot
Post by: bob on December 11, 2014, 11:38:33 am
An update about this problem, for future reference; we use a bonding interface on the server. It appears the MAC address can change according to the first initated NIC during boot. After adding a delay on bringing up eth1 we now get the same MAC address on the bond interface between reboots and the license is kept between reboots
A good solution.
The indeterminate behavior seems a bit unusual. The NICs are usually entered in the /etc/udev/rules.d/*persistent-net.rules file when they are first seen and always come back in that order IIRC.
Title: Re: License lost after server reboot
Post by: mwillems on December 11, 2014, 12:52:03 pm
A good solution.
The indeterminate behavior seems a bit unusual. The NICs are usually entered in the /etc/udev/rules.d/*persistent-net.rules file when they are first seen and always come back in that order IIRC.


I think there were some issues with this kind of indeterminacy that led to some recent changes in the NIC naming convention in udev/systemd.  In recent versions systemd/udev assigns unique names to each NIC (analogous to using UUIDs for hard drives instead of /dev/sdx).  See this article for a discussion of some of the problems of the conventional naming system, including MAC address issues : http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

To my knowledge the new naming convention should solve boot order type issues, and has been implemented in Arch and a few other distros for a little while.  Debian Jessie adopted systemd, but seems to have retained the old naming convention (at least for now). Given that systemd adoption is almost universal at this point the new naming convention will probably be the new normal (eventually).