Monitor want start after it died

GroupWise 2012 SP2
Server OS OES11
GroupWise Monitor 2012 SP2


Installed monitoring today and it was working, was looking and clicking around in the monitor and then it stopped (dead). When I start it back it failed and the message log said this (Dec 30 23:39:34 po startproc: startproc: exit status of parent of /opt/novell/groupwise/agents/bin/gwmon: 1).

So at a lost where to go from here, any ideals what to check?

Tags:

  • Hi,

    I would double check the process: ps -ef | grep gwmon

    If you see a line similar to this: root 16165 1 0 Nov21 ? 00:14:28 /opt/novell/groupwise/agents/bin/gwmon @/opt/novell/groupwise/agents/share/monitor.xml

    Then gwmon is still "loaded" and you will need to kill the process with the kill command.

    Let us know how it goes.

    Cheers,
  • When I run ps -ef | grep gwmon this is what it get below

    po:~ # ps -aef | grep gwmon
    root 12790 16353 0 14:39 pts/1 00:00:00 grep gwmon
    po:~ # ps -aef | grep gwmon
    root 12793 16353 0 14:39 pts/1 00:00:00 grep gwmon
    po:~ # ps -aef | grep gwmon
    root 12796 16353 0 14:39 pts/1 00:00:00 grep gwmon
    po:~ # ps -aef | grep gwmon
    root 12801 16353 0 14:39 pts/1 00:00:00 grep gwmon
    po:~ # ps -aef | grep gwmon
    root 12804 16353 0 14:39 pts/1 00:00:00 grep gwmon

    the first number keeps changing, so does this mean it is still running?
  • Hi,

    Nope, gwmon is not running on your system - the value being returned is just the grep command that you've just run.

    See if you can find anything in the gwmon log files: /var/log/novell/groupwise/gwmon/

    Let us know how it goes.

    Cheers,
  • Hi,

    One more thing...what happens if you start gwmon manually i.e. without using the rcgrpwise-ma script....

    Change to the GroupWise agent bin directory: cd /opt/novell/groupwise/agents/bin

    Use the following commands to start the Monitor Agent: ./gwmon --home /domain_directory
  • I try ./gwmon --home and the path to my wpdomain.db file and it started and has all the agent listed in it. So what is not setup right to have rcgrpwise-ma script start GroupWise monitoring. Also before it died I had only add the GWIA and the POA to the monitor, starting it with ./gwmom and the path to the wpdomain.db file it has all the agent listed and ignores what I had setup in it before it died. Should I try re-installing gwmon?
  • Hi

    Sounds like your monitor.xml file might be faulty. I think your best bet is running through the install again.

    Let us know how it goes.

    Cheers,
  • Did a re-instill of the monitor and that fixed it, and got GWHA working. Now tring to add messager to the monitor and it want take it. I have even tried adding it to the grpwise-ma scrept (--nmhome ou=DCBEMessengerService,ou=GrpWise,ou=ADMINISTRATION,o=DCBE ,--nmuser xxxxx ,--nmpassword xxxxxx, --nmaddress xxxxxx), with no luck. Any the docmantion is not that good for messager, any thoughts what might try next.
  • Hi,

    To be honest... I've not had success adding Messenger to Monitor on 2012!

    I suggest opening a SR with Novell in order to get this resolved.

    Let us know how it goes.

    Cheers,
  • Hi,

    I have found this: Bug 762686 - Messenger Agents don't show in GroupWise Monitor

    This is specific to GroupWise 2012 running on a SLES platform - that would include OES.

    Hopefully this will be resolved in GroupWise 2014 - I don't know if the fix will be ported back to 2012 :(

    Cheers,