Cant web to SMGR

[mickorourke]

i can ssh to the smgr but cant web to https://<ip>/SMGR

can see in the vsp that the domain is running, just cant web to it,

any idea's

[chrow]

A couple of things to check

There could be several things causing the web access to not work. Here are some things to try:

1) Check that the System Manager application is truely installed on the VSP slice:

A quick simple way is to ssh as root into the SMGR and run the "swversion" following command as shown below:

[root@SMGR ~]# swversion
Avaya System Manager Software Version Inventory
ASM Installer: 3.0.3.0 25-Dec-09 17:14
ASM Replication: 6.0.0.0.31001 - 01-26-2010
ASM Maintenance Agent: Not Found
ASM ElementManager: 6.0.0.0.31001 - 01-26-2010
Not installed
SIP AS 8.0 Management Cons:
System Manager: 3.0.3.0
IPTCM: 6.0.3.0
ElementManager: 6.0.0.0
OS: Red Hat Enterprise Linux Server release 5.3 (Tikanga) 5.3.0.3
Mgmt JBoss: 4.2.3.GA
ls: /opt/Avaya/apache*: No such file or directory
Apache:
SAL Agent: 3.0.3.0
PostgreSQL: 8.4.1-1PGDG.rhel5

System Manager Database Schema Versions
pan: 0.5.0
ipt: 6.0.3
asm: 6.1.6
nrp: 1.0.4
[root@SMGR ~]#


If the response to this command is some sort of error, then the System Manager installation did not complete sucessfully.

-------------------------------------------------------------

2) Insure all mounted partitions of the System Manager are not read-only. SSH as root into the SMGR and run the "touch" command as shown to try and create a test file:

[root@SMGR ~]# touch test
[root@SMGR ~]#

If an error comes back, the disk is likely read-only...which is causing your problem.
----------------------------------------

3) If nothing has alerted toward a problem in the first 2 checks, at least see if the SMGR is advertising HTTPS on 443 as shown with "netstat":

[root@SMGR ~]# netstat -an|grep 443
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN

This is a good response; if there is not a line showing "LISTEN", then there is an issue there.

4) Watch the boot process of the System Manager. Whether or not you've been able to narrow down cause of the issue from the troubleshooting steps listed above, watching the System Manager boot up will likley provide more detail into what's causing the inability to reach the webpage. Some process or service will likely fail during bootup, which is likley the cause of your outage.

You can do this from Dom-0 of the VSP. Get to root level of VSP and perform a restart on the System Manager Xen slice, then use the Xen utilities to console into the System Manager to watch it boot up.

[root@12LVSP ~]# xm reboot smgr

[root@12LVSP ~]# xm console smgr


-------------------------------------------

[theunisp]

How do i fix the port 443 error?

#3) If nothing has alerted toward a problem in the first 2 checks, at least see if the #SMGR is advertising HTTPS on 443 as shown with "netstat":
#
#[root@SMGR ~]# netstat -an|grep 443
#tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
#
#This is a good response; if there is not a line showing "LISTEN", then there is an #issue there.

I don't get any reply when I run the command. Where do I enable the ports?

[lawsd]

did you manage to resolve this as i am having the same issue

thanks

[hghatnekar]

Is this problem coming since first time(Installation / Upgrade) or was you able to login to SMGR at least once after the installation?

[mtorres]

I have the same issue, SMGR used to work fine but now I can´t access the webpage.

[mtorres]

Problem solved!

First I tried restarting the server several times with no success then I tried restarting the postgresql database service (service postgresql restart) after 5 minutes the website came back.

You could also try this:

service jboss restart
service spiritAgent restart

[jonakins]

I have this issue happen every several weeks with the web services. Did anyone find an answer?

[pappak]

Can't access SMGR 6.1 which is part of MES template

1. MES installed successfully. I can login into CM, SM and Utility server but not SMGR.
2. Tried default passwords for SMGR but they don't help.
3. I also cannot get SMGR web console page.
4. SMGR status on System platform shows it is running for both the application and template states.

I appreciate any inputs to solve this issue.

[dstaware]

We are not able to access ssh,webpage of SMGR 5.2.
Unable to ping SMGR ip address while console domain and domain 0 are accessible.
Kindly advice the procedure to resolve the issue.

xm list i can see smgr status is running.

[qlethinguyet]

Hi all,

I also have the same problem. After installing MES template, I can't login into SMGR 6.1.4 webpage with default password (admin/admin123). When I clicked "Change password", the page displayed a local-login page, not password change page. I tried to launch web with FQDN but it didn't help.

I also can't launch SMGR webpage with https://<IP>/SMGR or https://<FQDN>/SMGR. It only works with https://<IP>/network-login or https://<FQDN>/network-login. I don't know what's wrong.

Could you please consult me the way to solve this problem.

Thanks in advance,
Que

[agetor]

Have you applied the latest SMGR service packs - I resolved similar issues with SP application? Also SM and SMGR service packs should be at compatible levels. Lastly, SMGR service pack should be successfully applied before that of SM. (Sorry, this is a response to earlier posts)

[sadag2]

system manager outage

we are retriving the smgr in outage issue right now
before we cant able to acces the system manager web page

but incense when system platform is running we cant able to recover the web page in system manager version 6.2

[mlombardi1]

we are retriving the smgr in outage issue right now
before we cant able to acces the system manager web page

but incense when system platform is running we cant able to recover the web page in system manager version 6.2

Have you tried a full server reboot initiated from the CDom web or Dom0 shell? Certificate expiration can also break the SMGR web service. The following PCN states 6.1 but also applies to 6.2: https://downloads.avaya.com/css/P8/documents/100159923

[edsplm]

There could be several things causing the web access to not work. Here are some things to try:

1) Check that the System Manager application is truely installed on the VSP slice:

A quick simple way is to ssh as root into the SMGR and run the "swversion" following command as shown below:

[root@SMGR ~]# swversion
Avaya System Manager Software Version Inventory
ASM Installer: 3.0.3.0 25-Dec-09 17:14
ASM Replication: 6.0.0.0.31001 - 01-26-2010
ASM Maintenance Agent: Not Found
ASM ElementManager: 6.0.0.0.31001 - 01-26-2010
Not installed
SIP AS 8.0 Management Cons:
System Manager: 3.0.3.0
IPTCM: 6.0.3.0
ElementManager: 6.0.0.0
OS: Red Hat Enterprise Linux Server release 5.3 (Tikanga) 5.3.0.3
Mgmt JBoss: 4.2.3.GA
ls: /opt/Avaya/apache*: No such file or directory
Apache:
SAL Agent: 3.0.3.0
PostgreSQL: 8.4.1-1PGDG.rhel5

System Manager Database Schema Versions
pan: 0.5.0
ipt: 6.0.3
asm: 6.1.6
nrp: 1.0.4
[root@SMGR ~]#


If the response to this command is some sort of error, then the System Manager installation did not complete sucessfully.

-------------------------------------------------------------


-------------------------------------------

Quick question. Should you be able to do the swversion command from the CLI of SMGR version 6.0? I have SP2 installed on this version. Anyway, I can do swversion from both of our session manager servers, but not system manager. If I go to the CLI of System Manager (logged in as root) and I type just swversion, it tells me the following:
[root@smgr ~]# swversion
-bash: swversion: command not found

Are you saying with absolute certainty that 'swversion' should work for SMGR 6.0 in the command line? Like I said, it works fine for our 6.0 Session Managers, but SMGR doesn't like that command.

Our SMGR web interface has worked fine in the past (but we did need to restart jboss once in awhile) but it just quit about a week ago but it came back sporadically with no pattern to when it would work or not. Mostly it's totally unresponsive now (web browser times out to completely dead page). Before it quit there had been no changes to SMGR, system platform or session manager other than running the certificate renewal utility about a month ago. A few weeks later the web page is pretty much consistently dead now. We always have access via the command line and system platform is ok. We just installed patch 1 for SP1 since SP1 was already installed from the start and then the System_Manager_06_00_SP1_SP2_Alarm_Patch.bin update, then the vsp-6.0.2.0.5 update for system platform before going to SMGR SP 2, then we did SP 2 for SMGR.

We're still stuck with the same problem...no web access. We've been through all the usual stuff like restarting jboss, postgresql, spiritAgent, deleting the file in the heapdump folder, rebooting the SMGR virtual machine, etc, etc. We used to be able ti get the web page back if it got a little screwy just by restarting jboss and waiting 15 minutes or so. But now, it's pretty much always dead. Not sure what's going on. Any ideas?

We've also verified again that the SMGR certificates are not expired. We just renewed them and they're good until 2018.

I checked the 'top' command and there's plenty of CPU. There's plenty of disk space (df -h).

One odd thing I've noticed is that spritiAgent is sometimes not running, but I don't know if that would affect the web interface or not. I start it and the page is still dead after awhile.

Regarding 'swversion', here's an example output from one of our session managers. I can't get this for the System Manager since it won't accept the command:

[craft@our-asm ~]$ swversion
Avaya Session Manager Software Version Inventory

ASM Release: 6.0.1.0.601009 30-Oct-14 18:51
SIP/AS ManagementServer: sipas8.1-sipas8.1.9_2-1 - 06-08-2010 13:20
SIP/AS ServiceDirector: sipas8.1-sipas8.1.9_2-1 - 06-08-2010 13:07
SIP/AS ServiceHost0: sipas8.1-sipas8.1.9_2-2 -
ASM Call Processing: 6.0.1.0.601009 - 07-22-2010
ASM Maintenance Agent: 6.0.1.0.601009 - 07-22-2010
ASM Management Agent: 6.0.1.0.601009 - 07-22-2010
OS: Red Hat Enterprise Linux Server release 5.4 (Tikanga) 5.4.0.3
ASM JBoss: 4.2.3.GA
SM-100: 6.0.1.0.382-1
PHP: Not Installed
Apache: 2.2.3-31.el5_4.2
SAL Agent: 30-Oct-14 18:43
PostgreSQL: 8.4.1-1PGDG.rhel5

Session Manager Database Schema Versions
nrp: 1.0.4
asm: 6.1.9
master: 0.0.6109
[craft@our-asm ~]$