Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12-05-2017, 12:07 PM
mcghe1 mcghe1 is offline
Member
 
Join Date: Dec 2015
Posts: 4
mcghe1 has 10 reputation points
Default WebLM 7.0 on ASBCE 7.2.x - Cannot License

I am having a showstopper problem in trying to upgrade to SBC 7.2.

This is a brand new Portwell CAD-0230 that we licensed for 7.x.

7.1 with WebLM 6.3 worked fine on this hardware, 7.2 includes WebLM 7.0, and it cannot be made to see a Host ID. When I click on Server Properties, Tomcat errors out to a HTTP 404 'Page cannot be found'. (See attachment) Attempting to load a license file fails with "A runtime error occurred while installing the license file."

I have tried every variation of upgrade path and fresh install, repeatedly, each time carefully following the Avaya documentation. The same result. I found one reference to permissions on /etc/hostname, but I applied the instructions and the result is the same.

Has anyone seen this? Have I made a stupid rookie mistake, or is this a bug I need to submit to Avaya?
Attached Images
File Type: png WebLMError.png (8.8 KB, 56 views)
Reply With Quote
  #2  
Old 12-05-2017, 02:50 PM
mcghe1 mcghe1 is offline
Member
 
Join Date: Dec 2015
Posts: 4
mcghe1 has 10 reputation points
Angry

Resolved this one myself.

It was the /etc/hosts file, but the version of the 7.2 Release Notes I originally had was incomplete. My version only instructed me to run "setfacl -m u:tomcat:rwx /etc/hosts"

An obviously later version was more complete:
Login to EMS as root user and run following :
1. setfacl -m u:tomcat:rwx /etc/hosts
2. cd /usr/local/weblm/server/scripts
3. Run below commands:
./manage-weblm.py -d
./manage-weblm.py –e
That got WebLM 7.0 able to see a Host ID. Except it picked the MAC of the M1 interface where the SBC 7.1/WebLM 6.3 used the MAC of the A1 interface. A PLDS regeneration later, and I have a functional SBC again.
Reply With Quote
  #3  
Old 01-08-2018, 11:22 AM
pbetteridge pbetteridge is offline
Aspiring Member
 
Join Date: Jan 2018
Posts: 1
pbetteridge has 10 reputation points
Default

Quote:
Originally Posted by mcghe1 View Post
Resolved this one myself.

It was the /etc/hosts file, but the version of the 7.2 Release Notes I originally had was incomplete. My version only instructed me to run "setfacl -m u:tomcat:rwx /etc/hosts"

An obviously later version was more complete:
Login to EMS as root user and run following :
1. setfacl -m u:tomcat:rwx /etc/hosts
2. cd /usr/local/weblm/server/scripts
3. Run below commands:
./manage-weblm.py -d
./manage-weblm.py –e
That got WebLM 7.0 able to see a Host ID. Except it picked the MAC of the M1 interface where the SBC 7.1/WebLM 6.3 used the MAC of the A1 interface. A PLDS regeneration later, and I have a functional SBC again.
Many thanks for the fix. All works now.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:58 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.