GMS18 not opening port 443

I just built a new server for GMS18 because our GMS14 was SLES 11, and after installing the GMS18 services I found that my on-network devices are not able to connect to it. The local firewall is turned off, there are no other firewalls between devices, and when I do a port scan the server is not showing port 443 as being open. When I scan against my GMS14 server it does show that port 443 is open. I've compared their configurations and I'm not seeing anything aside from the local IP address and what they're using to authenticate to LDAP different between them, and none of that would be related to why port 443 isn't opening. Any suggestions? Thanks!
  • Hi,

    On the GMS server do the following: netstat -plan | grep 443

    Should show python listining on that port.

    Cheers,
  • laurabuckley;2474041 wrote:
    Hi,

    On the GMS server do the following: netstat -plan | grep 443

    Should show python listining on that port.

    Cheers,


    When I typed that in it came back with no results, just gave me another command line prompt
  • Hi,

    I would check to see if python is indeed running. When I do a: ps -ef | grep python I get the following:


    gms18:~ # ps -ef | grep python
    root 10163 10118 0 08:32 pts/0 00:00:00 grep --color=auto python
    root 16046 1 0 2017 ? 01:36:29 /usr/bin/python /opt/novell/datasync/monitorengine/sbin/monitorEngine.pyc
    root 16094 1 0 2017 ? 00:47:49 /usr/bin/python /opt/novell/datasync/configengine/sbin/configEngine.pyc
    root 16152 1 0 2017 ? 00:19:41 /usr/bin/python /opt/novell/datasync/syncengine/sbin/syncEngine.pyc
    root 16222 1 0 2017 ? 00:00:12 /usr/bin/python /opt/novell/datasync/webadmin/sbin/webadminServer.pyc
    root 16252 1 0 2017 ? 00:05:35 /usr/bin/python /opt/novell/datasync/syncengine/sbin/connectorManager.pyc
    root 16254 16252 0 2017 ? 01:54:50 /usr/bin/python /opt/novell/datasync/syncengine/sbin/connectorManager.pyc
    root 16255 16252 0 2017 ? 03:40:35 /usr/bin/python /opt/novell/datasync/syncengine/sbin/connectorManager.pyc
    gms18:~ #



    Cheers,
  • Hi,

    Further to my post above about python running... when you start GMS do you see a line like this in the mobility-agent.log file:


    2018-01-24 09:21:40.641 INFO [DeviceInterfaceMonitor_Thread] [DeviceInterface:185] [userID:] [eventID:] [objectID:] [Server] Mobility Device Interface Running... device.wsgiserver.CherryPyWSGIServer(('0.0.0.0', 443))



    Cheers,
  • laurabuckley;2474098 wrote:
    Hi,

    Further to my post above about python running... when you start GMS do you see a line like this in the mobility-agent.log file:


    2018-01-24 09:21:40.641 INFO [DeviceInterfaceMonitor_Thread] [DeviceInterface:185] [userID:] [eventID:] [objectID:] [Server] Mobility Device Interface Running... device.wsgiserver.CherryPyWSGIServer(('0.0.0.0', 443))



    Cheers,


    To answer both of your posts, yes I do see python running and I do see the line as you have indicated. When I do a port scan on the local server while GMS is running I only see ports 22, 25 and 5432 as active. I'm about to open a ticket on this since I wasn't sure if I messed something up on my first attempt at the server so I rebuilt it and this is a repeating issue.
  • Possible the install was bad, and the connectors didn't get set up properly?

    Check the path /etc/datasync/configengine/engine/pipeline1/connectors/ (I may have that path mistyped..)
    In that folder you should have two other folders. One called groupwise, and the other mobility. Make sure you have a connector.xml in the mobility folder.

    If that checks out.. possible the cert is bad? /var/lib/datasync/device/mobility.pem

    Good luck!