OTP issue after upgrading

136 views
Skip to first unread message

Steve MacDougall

unread,
Jul 30, 2015, 12:17:38 PM7/30/15
to RCDevs Security Solutions - Technical
I recently upgraded the backup OTP server to 1.4.0-1 of Webadm. After the upgrade I had to edit some of the configurations for new ports, encryption keys, etc. 

I can now logon to the system and view all the users and webadm data. All of the web applications and web services I want to use show as OK on the home page.

Everything looks ok when I restart webadm.

However, when I go to 'Test user login', server status shows as 'Not Available', and if I proceed to try a test anyway, I get:

Result: Failure
Message: Account currently in use


If I check status from the command line I get:

Server Status:

Steve MacDougall

unread,
Jul 30, 2015, 1:46:28 PM7/30/15
to RCDevs Security Solutions - Technical, smacd...@bluepay.com
I upgraded the primary node in the cluster and it works fine after the upgrade.

Steve MacDougall

unread,
Jul 30, 2015, 2:38:42 PM7/30/15
to RCDevs Security Solutions - Technical, smacd...@bluepay.com
I'm getting closer. I rebuilt the secondary node from scratch, everything is green. The 'Test user login' page 
now shows:

Server Status: Accepting Requests
Server: OTP & U2F Authentication Server 1.2.1-1 (WebADM 1.4.0-1)
System: Linux 3.5.0-43-generic x86_64 (64 bit)
Listener: 127.0.0.1:8080 (HTTP/1.1 SSL)
Uptime: 3614 (0 days)
Memory: 1.75M
Total Requests: 0
Active Requests: 0
Connectors: OK (4 alive & 0 down)

So all looks good, except when I enter my OTP, I get:

 
Result: Failure
Message: Server error
 
The log shows:

Could not get semaphore request


On Thursday, July 30, 2015 at 12:17:38 PM UTC-4, Steve MacDougall wrote:

Steve MacDougall

unread,
Jul 30, 2015, 2:51:13 PM7/30/15
to RCDevs Security Solutions - Technical, smacd...@bluepay.com
restarted entire server. All works fine now.


On Thursday, July 30, 2015 at 12:17:38 PM UTC-4, Steve MacDougall wrote:

Dave

unread,
Mar 23, 2018, 10:49:36 AM3/23/18
to RCDevs Security Solutions - Technical
Thanks for this posting!  It helped me as well, just a simple reboot when I have upgraded to 1.6.3-2-x64 today.


On Thursday, July 30, 2015 at 12:17:38 PM UTC-4, Steve MacDougall wrote:
Reply all
Reply to author
Forward
0 new messages