troubleshooting external license server issues

Post Reply
ssteiner

troubleshooting external license server issues

Post by ssteiner »

I'm having the weirdest issue. Keep getting a service not initialized error when creating new PBX objects (using the pbx management API). Reboots of OXE and O2G, deleting and re-creating the node didn't help. So in my desperation, I started the old VM hosting the official 1.0 release. Had to switch the license to the external license server since that's where my licenses are hosted... and from that point on, no HTTPS connection possible to the O2G anymore.
I finally gave up, and installed a brand new VM using the latest ISO, and installed the 1.01 snapshot. I initially configured the external license server, and then I couldn't access the web interface either. Eventually I switched to the internal license server, and lo behold, the webpage is accessible once again. Switch back to external, and nothing.

My Flexlm also hosts the licenses for my OTMS, and I can still create users and voicemail boxes, so at least that part is fine and I'm assuming the FLEXLM can't work properly for OTMS but not for O2G so I'm stumped.
yblanchard
Member
Posts: 27
Joined: 03 Dec 2018 06:32

Re: troubleshooting external license server issues

Post by yblanchard »

Just to close the topic, a response has been brought outside:

the issue initial reason seems to be a configuration problem:
even in case of remote license server, the license file must also be present on the local O2G server in order to check the systemId. (if a new license file is updated on the license server, the systemId keeps the same value, so it is not necessary to update the file on O2G).

The installation doc should be updated to mention this configuration requirement.
ssteiner

Re: troubleshooting external license server issues

Post by ssteiner »

That was indeed the issue. However I'm wondering if there's not some kind of log message that I should see and that tells me something is off.
Post Reply

Return to “O2G”