Running gwadmin-console on a gw2014 cluster

we have use the gw2014 interoperability guide for Cluster Installation on oes11sp2
the Cluster works correctly and we can migrate on all Cluster nodes

we have run gwadminutil config -Cluster enable on all Cluster nodes and gwadminutil installcfg -m user -u admin -p Password (correct Password: is it gw-Password or edirectory Password?)

https://ip-adress-cluster:9710/gwadmin-console/login.jsp) don't work

before enabling Cluster, the gwadmin-console will work

who can help?

thanks
  • Cgreiner wrote:

    > we have run gwadminutil config -Cluster enable on all Cluster nodes and
    > gwadminutil installcfg -m user -u admin -p Password (correct Password: is it
    > gw-Password or edirectory Password?)


    Neither. The password is one you make up for a user specific to the
    installation user. But note this is NOT the user that logs in as admin for the
    system. It's only the installation user! The Admin user is the user you
    created when you defined the system during the original installation.

    > https://ip-adress-cluster:9710/gwadmin-console/login.jsp) don't work
    >
    > before enabling Cluster, the gwadmin-console will work
    >


    When you say it doesn't work, does it simply not seem to be listening? What
    happens when you run

    /opt/novell/groupwise/admin/gwadmin-ipc query


    --
    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...
  • the result of /opt/novell/groupwise/admin/gwadmin-ipc query is:

    10.1.0.61:9710=>rabenhdo(/media/nss/GWDATA/groupwise/rabenhdo)
    10.1.0.61:9711=>rabenhpo.rabenhdo(/media/nss/GWDATA/groupwise/rabenhpo)

    10.1.0.61 is the Cluster ip adress

    10.1.0.61:9710 will not be reached, Telnet can Access on port 9710
  • Cgreiner wrote:

    > 10.1.0.61:9710 will not be reached, Telnet can Access on port 9710


    Do you see anything in the gwadmin-service.log. This is typically on
    /var/log/novell/groupwise/gwadmin, but it's possible that it's out on the
    cluster resource volume 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...
  • Here the solution of 2 Cluster Problems:

    1. WebAdmin console

    The problem was caused by missing certificates (on the correct Folder). On non-cluster server, the certificates are in /opt/Novell/GroupWise in a directory called certificates.
    There are two subdirs - a system GUID folder and install one.

    When wanting to have a webadmin console enabled for a cluster, you need to create at the same level where are the domains and PO's dir structure a new directory called "GroupWise", then a sub-dir named "certificates". Please copy / paste all files that are located in the system GUID Folder directly in this Folder, don't use a other subdirectory

    After that re-run gwadminutil config -cluster enable

    and then restart gwadminservices. Then you can start webadmin console from the desktop icon that connects to a cluster IP address of the domain admin service.


    2. Webaccess problem.

    In the webacc.cf file located in /var/opt/Novell/GroupWise/webaccess there was a line about SOAP provider holding wrong IP address -> modified this parameter "Provider.SOAP.1.ip=<cluster IP of POA> and restarting tomcat helped to resolve the WA. In the GW2014-Installation there is no Point to install Software in a Cluster as in gw2012

    We have a separate stand alone Server for webaccess and this Server is not in the Cluster.

    Thank you to the novell Support, we had Need 5 hours to resolve this two Problems.
  • So, the docs may not be clear, but you should run gwadminutil config -cluster enable and restarting adminservice BEFORE you do anything else. That way the admin service knows to create the certificates directory on the cluster resource.

    --Morris
  • Hi there, yet another problem with groupwise 2014