Cannot 'monitor' webaccess

Just updated to the eval version on my lab GW system (had been running
it as part of the Tech Preview so was on beta 10 or 12).

Now, when I try to go to the url to monitor GW webaccess, I get:

Unable to connect to the GroupWise Admin Console
@https://<primary mta>:9710/gwadmin-service/system/whoami

Webaccess as well as calendar publishing both working on this server.

GW2014 build 115243 on sles11sp2.

Suggestions?

--
Stevo

Tags:

  • Ok, so I'm an idiot. Forgot the conditions I set up to access this and
    was trying an incorrect userid...............[THUD]


    --
    Stevo
  • "Stevo" wrote:

    > Ok, so I'm an idiot. Forgot the conditions I set up to access this and was
    > trying an incorrect userid...............[THUD]


    Oops! Well, thanks for getting back to us!

    --
    Danita
    Novell Knowledge Partner
    Upgrading to GroupWise 2014? We've got you covered
    http://www.caledonia.net/store

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • DZanre sounds like they 'said':

    > Oops! Well, thanks for getting back to us!


    So my response to DZanre's comment is...

    It does seem a bit weird that it gives some obscure web page error
    instead of a 'warning' or whatever about incorrect user / password used.

    --
    Stevo
  • Stevo wrote:

    > Just updated to the eval version on my lab GW system (had been running
    > it as part of the Tech Preview so was on beta 10 or 12).
    >
    > Now, when I try to go to the url to monitor GW webaccess, I get:
    >
    > Unable to connect to the GroupWise Admin Console
    > @https://<primary mta>:9710/gwadmin-service/system/whoami
    >
    > Webaccess as well as calendar publishing both working on this server.
    >
    > GW2014 build 115243 on sles11sp2.
    >
    > Suggestions?
    >


    I am seeing this same message and I am using the correct login info. Any
    ideas?


  • Rickb wrote:

    > I am seeing this same message and I am using the correct login info. Any
    > ideas?


    I am not seeing this on my system. This is the correct location for the primary
    domain's admin service? Did any firewalls get turned on anywhere?

    --
    Danita
    Novell Knowledge Partner
    Upgrading to GroupWise 2014? We've got you covered
    http://www.caledonia.net/store

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • DZanre wrote:

    > Rickb wrote:
    >
    >> I am seeing this same message and I am using the correct login info. Any
    >> ideas?

    >
    > I am not seeing this on my system. This is the correct location for the
    > primary
    > domain's admin service? Did any firewalls get turned on anywhere?
    >


    I know this is not supported, but I am clustering webacc. I had it clustered
    as well on 2012 and never had an issue with opening the monitor on any node.
    I realize this has all changed somewhat. Does there need to be an
    adminservice running on the clustered ip as well? I don't see a way to do
    that for a gateway service.
  • Rickb wrote:

    > Does there need to be an adminservice running on the clustered ip as well? I
    > don't see a way to do that for a gateway service.


    Is WebAccess running on the same cluster as the other GW agents?


    --
    Danita
    Novell Knowledge Partner
    Upgrading to GroupWise 2014? We've got you covered
    http://www.caledonia.net/store

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • DZanre wrote:

    > > Does there need to be an adminservice running on the clustered ip as well? I
    > > don't see a way to do that for a gateway service.

    >
    > Is WebAccess running on the same cluster as the other GW agents?


    By the way, I'll see if Morris will look in on this thread too - he's the
    clustering expert right now :-)

    --
    Danita
    Novell Knowledge Partner
    Upgrading to GroupWise 2014? We've got you covered
    http://www.caledonia.net/store

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...
  • DZanre wrote:

    > DZanre wrote:
    >
    >> > Does there need to be an adminservice running on the clustered ip as
    >> > well? I don't see a way to do that for a gateway service.

    >>
    >> Is WebAccess running on the same cluster as the other GW agents?

    >
    > By the way, I'll see if Morris will look in on this thread too - he's the
    > clustering expert right now :-)
    >


    Thanks Danita, Yes it is running in the same cluster. It does not matter
    whether or not if the service is running on the same node as the clustered
    po or not.

  • So, no clustering issue here methinks..



    Check your webacc.cfg and look for these lines:


    Admin.WebConsole.enable=true (make sure this is true)
    Admin.RestService.host=127.0.0.1
    Admin.RestService.port=9710



    If you see the .host as 127.0.0.1, you'll need to edit and supply IP of a admin service listener. By default, when a 2014 domain is created, the MTA is set to bind exclusive to the bound addr (or secondary addr on cluster, it's whatever you enter in the host field). And the admin service will listen only on that address.



    The webaccess install seems to have an issue with not picking this up. After editing the file, bounce tomcat6, and try again.



    --Morris








    >>> Rickb<rdb@rdbnetsolutions.com> 4/24/2014 5:46 AM >>>



    DZanre wrote:


    > DZanre wrote:
    >

    >> > Does there need to be an adminservice running on the clustered ip as
    >> > well? I don't see a way to do that for a gateway service.

    >>
    >> Is WebAccess running on the same cluster as the other GW agents?

    >
    > By the way, I'll see if Morris will look in on this thread too - he's the
    > clustering expert right now :-)
    >


    Thanks Danita, Yes it is running in the same cluster. It does not matter
    whether or not if the service is running on the same node as the clustered
    po or not.