Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can;t OPen System Management Interface
- Thread starter dhalfin
- Start date
PhonesAllDay
Technical User
I have this same problem when trying to access SMGR Web:
"Maintenance is in progress. Please try to login at a later time. Need more help? Please contact support team."
This happened after an upgrade from 6.0 to 6.3
Going to try a fresh software install as we suspect corruption. The logs said "duplicate files" in the database.
Please update if you find a solution!
Thanks!
"Maintenance is in progress. Please try to login at a later time. Need more help? Please contact support team."
This happened after an upgrade from 6.0 to 6.3
Going to try a fresh software install as we suspect corruption. The logs said "duplicate files" in the database.
Please update if you find a solution!
Thanks!
jimbojimbo
Vendor
All right, I'm only going to post this one time.
When Upgrading the Kernel changes and the web container library dependencies won't allow the web services to start until the system is rebooted. This is a major FUBAR from Avaya. Once you do reboot there is a lock file which is causing you to get the maintenance screen (you'll also see a notice if you log into the CLI.
You'll need to check the logs to verify the upgrade completed. /opt/Avaya/install_logs/avaya_aura_install-log<date stamp>.txt. At the end of the file you should get INSTALLATION STATUS" success.
After the server reboot there are some additional "UPDATES" that need to complete. From the CLI run the command ps -ef and you will most likely see several postgres processes running and showing UPDATE waiting.
You then need to remove the lock file. Of course you won't find it in /var/lock. /opt/vsp/MaintainSMGR/.SMGR_Maintenance.lock.
Wait until the ps -ef doesn't show any UPDATE waiting messages. You should be okay to login.
When Upgrading the Kernel changes and the web container library dependencies won't allow the web services to start until the system is rebooted. This is a major FUBAR from Avaya. Once you do reboot there is a lock file which is causing you to get the maintenance screen (you'll also see a notice if you log into the CLI.
You'll need to check the logs to verify the upgrade completed. /opt/Avaya/install_logs/avaya_aura_install-log<date stamp>.txt. At the end of the file you should get INSTALLATION STATUS" success.
After the server reboot there are some additional "UPDATES" that need to complete. From the CLI run the command ps -ef and you will most likely see several postgres processes running and showing UPDATE waiting.
You then need to remove the lock file. Of course you won't find it in /var/lock. /opt/vsp/MaintainSMGR/.SMGR_Maintenance.lock.
Wait until the ps -ef doesn't show any UPDATE waiting messages. You should be okay to login.
PhonesAllDay
Technical User
Thanks jimbojimbo,
We did reboot last night and we knew to look for .SMGR_Maintenance.lock and the file was not there. Completed a fresh install of 6.1 on the System Manager, then rolling back Session Manager to 6.1 introduced an expired certificate "bug". After 30+ hours on this, team went to rest and re-group tomorrow morning.
Thank you for the information.
PhonesAllDay
We did reboot last night and we knew to look for .SMGR_Maintenance.lock and the file was not there. Completed a fresh install of 6.1 on the System Manager, then rolling back Session Manager to 6.1 introduced an expired certificate "bug". After 30+ hours on this, team went to rest and re-group tomorrow morning.
Thank you for the information.
PhonesAllDay
- Thread starter
- #5
jimbojimbo
Vendor
Make sure you use ls -al since .SMGR_Maintenance.lock is hidden.
- Status
Similar threads
