Sitescope 11.20 Monitor Process not starting

Hello,

 

I'm having trouble with a brand-new installation of SiteScope on a Redhat Linux server. When I run /opt/HP/SiteScope/start, it hangs for a long time, then gives the startup successful message. However, when I check the logs I see this:

 

error.log

2015-03-25 16:35:05,705 [main] (Service.java:194) INFO  - starting service process: 23264
2015-03-25 16:35:05,710 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:39:15,866 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:39:15,867 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:39:15,868 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:43:25,910 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:43:25,910 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:43:25,911 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:47:35,952 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:47:35,953 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:47:35,954 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:51:45,996 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:51:45,998 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:51:45,999 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x

 

RunMonitor.log

2015-03-25 16:35:05,705 [main] (Service.java:194) INFO  - starting service process: 23264
2015-03-25 16:35:05,710 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:39:15,866 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:39:15,867 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:39:15,868 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:43:25,910 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:43:25,910 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:43:25,911 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:47:35,952 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:47:35,953 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:47:35,954 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x
2015-03-25 16:51:45,996 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
2015-03-25 16:51:45,998 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
2015-03-25 16:51:45,999 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 23264 -x

 

Going to check SiteScope in my browser gets me an Apache Tomcat 404 page. If I check groups/ pid is created, but not monpid. The content of pid does match the results of ps -ef | grep SiteScope, reproduced below:

 

[root@c1t09003 groups]# ps -ef | grep SiteScope
root     23134     1  1 16:27 pts/0    00:00:10 ../java/bin/SiteScope -server -Xmx512m -Xms512m -Xmn160m -Xss256k -XX:MaxPermSize=240m -XX: UseParNewGC -XX: UseConcMarkSweepGC -XX:-DoEscapeAnalysis -Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -showversion -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -cp ../Tomcat/bin/bootstrap.jar -Dcatalina.base=../Tomcat -Dcatalina.home=../Tomcat -Djava.security.auth.login.config=../conf/jaas.config -Dtopaz.home=.. -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl -Djava.util.Arrays.useLegacyMergeSort=true -Djava.security.manager -Djava.security.policy=../conf/security/sitescope.policy -DMYPID=23134 -DPPID=23115 -Dfailover=false org.apache.catalina.startup.Bootstrap start
root     23262     1  0 16:35 pts/0    00:00:00 /bin/sh /opt/HP/SiteScope/start
root     23264 23262  0 16:35 pts/0    00:00:02 ../java/bin/java -Xmx256m -Dsun.net.inetaddr.ttl=0 -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -DSiteScope=true -Dfailover=false -cp ../WEB-INF/classes:../WEB-INF/lib/accore_api.jar:../WEB-INF/lib/actcommon.jar:../WEB-INF/lib/activation.jar:../WEB-INF/lib/acweb-appframework.jar:../WEB-INF/lib/acweb_site.jar:../WEB-INF/lib/amazon_api.jar:../WEB-INF/lib/antlr.jar:../WEB-INF/lib/app-infra.jar:../WEB-INF/lib/asresponse.jar:../WEB-INF/lib/authentication.jar:../WEB-INF/lib/autopassj-common-1.1.1.jar:../WEB-INF/lib/autopassj-core-1.1.1.jar:../WEB-INF/lib/autopassj-crypto-1.1.1.jar:../WEB-INF/lib/autopassj-saas-1.1.1.jar:../WEB-INF/lib/axis-ant.jar:../WEB-INF/lib/axis.jar:../WEB-INF/lib/bac-client.jar:../WEB-INF/lib/backport-util-concurrent.jar:../WEB-INF/lib/bac-shared.jar:../WEB-INF/lib/bcprov-jdk14-127.jar:../WEB-INF/lib/bsm-entity-utils.jar:../WEB-INF/lib/bsm-fx-common-js.jar:../WEB-INF/lib/bsm-fx-common-l10n.jar:../WEB-INF/lib/bsm-fx-css.jar:../WEB-INF/lib/bsm-sdk-utils.jar:../WEB-INF/lib/bvdmem.jar:../WEB-INF/lib/cmdbext.jar:../WEB-INF/lib/cmdb-framework.jar:../WEB-INF/lib/cmdb_history.jar:../WEB-INF/lib/cmdb_reconciliation.jar:../WEB-INF/lib/cmdb_shared.jar:../WEB-INF/lib/collectors.jar:../WEB-INF/lib/commons-beanutils.jar:../WEB-INF/lib/commons-codec.jar:../WEB-INF/lib/commons-collections.jar:../WEB-INF/lib/commons-digester.jar:../WEB-INF/lib/commons-discovery-0.2.jar:../WEB-INF/lib/commons-fileupload-1.2.jar:../WEB-INF/lib/commons-httpclient-2.0-final.jar:../WEB-INF/lib/commons-jexl-1.0.jar:../WEB-INF/lib/commons-lang-2.0.jar:../WEB-INF/lib/commons-logging.jar:../WEB-INF/lib/commons-pool.jar:../WEB-INF/lib/commons-validator.jar:../WEB-INF/lib/com.objectplanet.gui.Table.jar:../WEB-INF/lib/concurrent-utils.jar:../WEB-INF/lib/confidential-manager-facade.jar:../WEB-INF/lib/confUpgradeFramework.jar:../WEB-INF/lib/connpool.jar:../WEB-INF/lib/crimson.jar:../WEB-INF/lib/csrfguard_cust.jar:../WEB-INF/lib/datachannel.jar:../WEB-INF/lib/datacollect-client.jar:../WEB-INF/lib/datacollect-shared.jar:../WEB-INF/lib/datatypesifs.jar:../WEB-INF/lib/datatypes.jar:../WEB-INF/lib/dbLRDT.jar:../WEB-INF/lib/diagnostic.jar:../WEB-INF/lib/discovery-common.jar:../WEB-INF/lib/discovery-content.jar:../WEB-INF/lib/discovery.jar:../WEB-INF/lib/discovery-library.jar:../WEB-INF/lib/dnsjava-2.0.6.jar:../WEB-INF/lib/downtime-common.jar:../WEB-INF/lib/downtime-upgrade.jar:../WEB-INF/lib/ejb2.0.jar:../WEB-INF/lib/Encoders.jar:../WEB-INF/lib/epm.jar:../WEB-INF/lib/ezmorph.jar:../WEB-INF/lib/FastInfoset.jar:../WEB-INF/lib/federation-api.jar:../WEB-INF/lib/flex-messaging-common.jar:../WEB-INF/lib/flex-messaging-core.jar:../WEB-INF/lib/flex-messaging-opt.jar:../WEB-INF/lib/flex-messaging-proxy.jar:../WEB-INF/lib/flex-messaging-remoting.jar:../WEB-INF/lib/flex-tomcat-common.jar:../WEB-INF/lib/fnd-adapter.jar:../WEB-INF/lib/foundations-gwt-core.jar:../WEB-INF/lib/g11n4commoninfra.jar:../WEB-INF/lib/GaugeChart.jar:../WEB-INF/lib/genericHandlersFramework.jar:../WEB-INF/lib/gmbal-api-only.jar:../WEB-INF/lib/google-collections.jar:../WEB-INF/lib/GraphChart.jar:../WEB-INF/lib/gwt-log-2.6.2.jar:../WEB-INF/lib/gwt-servlet.jar:../WEB-INF/lib/ha-api.jar:../WEB-INF/lib/hac-msam.jar:../WEB-INF/lib/hellobean.jar:../WEB-INF/lib/hot-deploy-agent.jar:../WEB-INF/lib/hot-deploy.jar:../WEB-INF/lib/hsqldb.jar:../WEB-INF/lib/html2pdf.jar:../WEB-INF/lib/HTTPserver.jar:../WEB-INF/lib/ib6core.jar:../WEB-INF/lib/ib6extra.jar:../WEB-INF/lib/ib6http.jar:../WEB-INF/lib/ib6https.jar:../WEB-INF/lib/ib6js.jar:../WEB-INF/lib/ib6swing.jar:../WEB-INF/lib/ib6util.jar:../WEB-INF/lib/ib6xalan.jar:../WEB-INF/lib/imap.jar:../WEB-INF/lib/ini4j-0.5.2.jar:../WEB-INF/lib/installation-wizard.jar:../WEB-INF/lib/ireasoningsnmp.jar:../WEB-INF/lib/ismp5_ifs.jar:../WEB-INF/lib/isomorphic_applets.jar:../WEB-INF/lib/itext-1.3.jar:../WEB-INF/lib/itext-1.3-sources.jar:../WEB-INF/lib/iTextAsianCmaps.jar:../WEB-INF/lib/iTextAsian.jar:../WEB-INF/lib/jakarta-oro.jar:../WEB-INF/lib/jakarta-regexp-1.4.jar:../WEB-INF/lib/Java2.jar:../WEB-INF/lib/javacore.jar:../WEB-INF/lib/javax.annotation.j
root     23379 28753  0 16:44 pts/0    00:00:00 grep SiteScope

 

When I run /opt/HP/SiteScope/stop, it gives me this:

 

Stopped SiteScope process (23264)
/opt/HP/SiteScope/start: line 55: 23264 Killed                  ./start-service
SiteScope monitor process not running - monpid file not found

 

So clearly the monitor process isn't starting correctly, but I have no idea why. It's a new install on a clean box, the only things I've changed are 1) putting in a license file (directly from HP) in during installation and 2) changing logs/ to a symbolic link pointing to a different partition. I have to do that because the space given to /opt/ is very limited and if I keep the logs there SiteScope will quickly run out of space. (especially since I'll probably have to change to debug level when I get this working). The symbolic link works, I've tested it in the console, and SiteScope can clearly write to it properly, since it's updating the error and RunMonitor logs. I wouldn't think that's the problem.

 

Access can't be the problem, I'm running all commands as root.

 

Any ideas?

 

EDIT:

 

I forgot - running netstat -ln shows that something is listening on 8080 that wasn't listening there before I installed SiteScope, and it's listening even when SiteScope is stopped. Results of netstat -ln below.

 

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        0      0 127.0.0.1:28005             0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:46789             0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:28006               0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:46407             0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:28009               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:1002                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:5227                0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:10635             0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:38064             0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:59633             0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:5555                0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:631               0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:12409             0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:39930               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:54843               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:383                 0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:12228             0.0.0.0:*                   LISTEN
udp        0      0 0.0.0.0:46198               0.0.0.0:*
udp        0      0 0.0.0.0:631                 0.0.0.0:*
udp        0      0 15.56.4.214:123             0.0.0.0:*
udp        0      0 127.0.0.1:123               0.0.0.0:*
udp        0      0 0.0.0.0:123                 0.0.0.0:*
udp        0      0 0.0.0.0:68                  0.0.0.0:*
raw        0      0 0.0.0.0:1                   0.0.0.0:*                   7
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ACC ]     STREAM     LISTENING     289761 private/lmtp
unix  2      [ ACC ]     STREAM     LISTENING     289765 private/anvil
unix  2      [ ACC ]     STREAM     LISTENING     289769 private/scache
unix  2      [ ACC ]     STREAM     LISTENING     11392  /var/run/abrt/abrt.socket
unix  2      [ ACC ]     STREAM     LISTENING     7348   @/com/ubuntu/upstart
unix  2      [ ACC ]     STREAM     LISTENING     10901  /var/run/cups/cups.sock
unix  2      [ ACC ]     STREAM     LISTENING     10859  /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     10961  /var/run/acpid.socket
unix  2      [ ACC ]     STREAM     LISTENING     289680 public/cleanup
unix  2      [ ACC ]     STREAM     LISTENING     289687 private/tlsmgr
unix  2      [ ACC ]     STREAM     LISTENING     289691 private/rewrite
unix  2      [ ACC ]     STREAM     LISTENING     289695 private/bounce
unix  2      [ ACC ]     STREAM     LISTENING     289701 private/defer
unix  2      [ ACC ]     STREAM     LISTENING     289705 private/trace
unix  2      [ ACC ]     STREAM     LISTENING     289709 private/verify
unix  2      [ ACC ]     STREAM     LISTENING     289713 public/flush
unix  2      [ ACC ]     STREAM     LISTENING     289717 private/proxymap
unix  2      [ ACC ]     STREAM     LISTENING     289724 private/proxywrite
unix  2      [ ACC ]     STREAM     LISTENING     289728 private/smtp
unix  2      [ ACC ]     STREAM     LISTENING     289732 private/relay
unix  2      [ ACC ]     STREAM     LISTENING     289736 public/showq
unix  2      [ ACC ]     STREAM     LISTENING     289740 private/error
unix  2      [ ACC ]     STREAM     LISTENING     289744 private/retry
unix  2      [ ACC ]     STREAM     LISTENING     289748 private/discard
unix  2      [ ACC ]     STREAM     LISTENING     289752 private/local
unix  2      [ ACC ]     STREAM     LISTENING     289756 private/virtual

 

Parents
  • Verified Answer

    Hi,

     

    You need to check if that process running in 8080 is a defunct instance of monitoring process (use netstat -tulpn command).

     

    Also, there was an issue with monitoring process not writting the monpid file. Try these customized start and SiteScope/bin/start-monitor scripts (rename your own first). Notice start-monitor scripot is arelady sized for 32 bits (1GB heap space)

    scripts.zip
  • All right, I checked the results of netstat -tulpn while SiteScope was running and after I stopped it. I got the same result both times, reproduced below.

     

    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
    tcp        0      0 127.0.0.1:28005             0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 127.0.0.1:46789             0.0.0.0:*                   LISTEN      20571/opcmsga
    tcp        0      0 0.0.0.0:28006               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 127.0.0.1:46407             0.0.0.0:*                   LISTEN      20482/ovcd
    tcp        0      0 0.0.0.0:28009               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 0.0.0.0:1002                0.0.0.0:*                   LISTEN      6586/python
    tcp        0      0 0.0.0.0:5227                0.0.0.0:*                   LISTEN      19916/perfd
    tcp        0      0 127.0.0.1:10635             0.0.0.0:*                   LISTEN      15363/ttd
    tcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 127.0.0.1:38064             0.0.0.0:*                   LISTEN      20517/ovconfd
    tcp        0      0 127.0.0.1:59633             0.0.0.0:*                   LISTEN      20553/opcacta
    tcp        0      0 0.0.0.0:5555                0.0.0.0:*                   LISTEN      1913/xinetd
    tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      2108/sshd
    tcp        0      0 127.0.0.1:631               0.0.0.0:*                   LISTEN      1873/cupsd
    tcp        0      0 127.0.0.1:12409             0.0.0.0:*                   LISTEN      20482/ovcd
    tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      6932/master
    tcp        0      0 0.0.0.0:39930               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 0.0.0.0:54843               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 0.0.0.0:383                 0.0.0.0:*                   LISTEN      20492/ovbbccb
    tcp        0      0 127.0.0.1:12228             0.0.0.0:*                   LISTEN      20538/coda
    udp        0      0 0.0.0.0:46198               0.0.0.0:*                               20571/opcmsga
    udp        0      0 0.0.0.0:631                 0.0.0.0:*                               1873/cupsd
    udp        0      0 15.56.4.214:123             0.0.0.0:*                               1921/ntpd
    udp        0      0 127.0.0.1:123               0.0.0.0:*                               1921/ntpd
    udp        0      0 0.0.0.0:123                 0.0.0.0:*                               1921/ntpd
    udp        0      0 0.0.0.0:68                  0.0.0.0:*                               2409/dhclient

     

    I also put in the new scripts and used them. Results of new start script:

     

    Bootstrapping SiteScope...
    
    
    SiteScope monitor process failed to start or has wrong pid written.

     

    And checking the pid, it is different. The old one seems to be hanging around the ports, while the new one is 12019, seen when I ran ps -ef and checked groups/. error.log was written to, with these results:

     

    2015-03-26 20:07:39,878 [main] (Service.java:194) INFO  - starting service process: 12019
    2015-03-26 20:07:39,887 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x
    2015-03-26 20:11:50,040 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
    2015-03-26 20:11:50,041 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
    2015-03-26 20:11:50,042 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x
    2015-03-26 20:16:00,081 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
    2015-03-26 20:16:00,082 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
    2015-03-26 20:16:00,082 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x
    2015-03-26 20:20:10,133 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
    2015-03-26 20:20:10,134 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
    2015-03-26 20:20:10,135 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x

     

    So...clear out the old version of Sitescope hanging around the ports somehow?

     

Reply
  • All right, I checked the results of netstat -tulpn while SiteScope was running and after I stopped it. I got the same result both times, reproduced below.

     

    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
    tcp        0      0 127.0.0.1:28005             0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 127.0.0.1:46789             0.0.0.0:*                   LISTEN      20571/opcmsga
    tcp        0      0 0.0.0.0:28006               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 127.0.0.1:46407             0.0.0.0:*                   LISTEN      20482/ovcd
    tcp        0      0 0.0.0.0:28009               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 0.0.0.0:1002                0.0.0.0:*                   LISTEN      6586/python
    tcp        0      0 0.0.0.0:5227                0.0.0.0:*                   LISTEN      19916/perfd
    tcp        0      0 127.0.0.1:10635             0.0.0.0:*                   LISTEN      15363/ttd
    tcp        0      0 0.0.0.0:8080                0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 127.0.0.1:38064             0.0.0.0:*                   LISTEN      20517/ovconfd
    tcp        0      0 127.0.0.1:59633             0.0.0.0:*                   LISTEN      20553/opcacta
    tcp        0      0 0.0.0.0:5555                0.0.0.0:*                   LISTEN      1913/xinetd
    tcp        0      0 0.0.0.0:22                  0.0.0.0:*                   LISTEN      2108/sshd
    tcp        0      0 127.0.0.1:631               0.0.0.0:*                   LISTEN      1873/cupsd
    tcp        0      0 127.0.0.1:12409             0.0.0.0:*                   LISTEN      20482/ovcd
    tcp        0      0 0.0.0.0:25                  0.0.0.0:*                   LISTEN      6932/master
    tcp        0      0 0.0.0.0:39930               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 0.0.0.0:54843               0.0.0.0:*                   LISTEN      23134/../java/bin/S
    tcp        0      0 0.0.0.0:383                 0.0.0.0:*                   LISTEN      20492/ovbbccb
    tcp        0      0 127.0.0.1:12228             0.0.0.0:*                   LISTEN      20538/coda
    udp        0      0 0.0.0.0:46198               0.0.0.0:*                               20571/opcmsga
    udp        0      0 0.0.0.0:631                 0.0.0.0:*                               1873/cupsd
    udp        0      0 15.56.4.214:123             0.0.0.0:*                               1921/ntpd
    udp        0      0 127.0.0.1:123               0.0.0.0:*                               1921/ntpd
    udp        0      0 0.0.0.0:123                 0.0.0.0:*                               1921/ntpd
    udp        0      0 0.0.0.0:68                  0.0.0.0:*                               2409/dhclient

     

    I also put in the new scripts and used them. Results of new start script:

     

    Bootstrapping SiteScope...
    
    
    SiteScope monitor process failed to start or has wrong pid written.

     

    And checking the pid, it is different. The old one seems to be hanging around the ports, while the new one is 12019, seen when I ran ps -ef and checked groups/. error.log was written to, with these results:

     

    2015-03-26 20:07:39,878 [main] (Service.java:194) INFO  - starting service process: 12019
    2015-03-26 20:07:39,887 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x
    2015-03-26 20:11:50,040 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
    2015-03-26 20:11:50,041 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
    2015-03-26 20:11:50,042 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x
    2015-03-26 20:16:00,081 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
    2015-03-26 20:16:00,082 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
    2015-03-26 20:16:00,082 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x
    2015-03-26 20:20:10,133 [main] (Service.java:357) INFO  - SiteScope monitor process: 0 is not running
    2015-03-26 20:20:10,134 [main] (Service.java:293) INFO  - SiteScope monitoring process restarted, process not running
    2015-03-26 20:20:10,135 [main] (Service.java:267) INFO  - starting monitor process: /opt/HP/SiteScope/bin/start-monitor 12019 -x

     

    So...clear out the old version of Sitescope hanging around the ports somehow?

     

Children