[ngw] monitor/restart groupwise agents

James Taylor James.Taylor at eastcobbgroup.com
Thu Dec 27 18:03:23 UTC 2012


Also, there was an issue on one of the SLES version where the gwha port was already in use.
There was an issue with the gwha port (8400) being configured for another port, and another where the path to gwha was configured wrong in xinetd, but I don't believe those should be an issue with the current releases.

Here's a quick & dirty write-up in cool solutions, just in case you haven't seen it.
 
http://www.novell.com/communities/node/12596/configure-groupwise-high-availability-gwha-5-easy-steps

-jt



James Taylor
678-697-9420
james.taylor at eastcobbgroup.com



>>> "Alan Bens" <ABENS at go-metro.com> 12/27/2012   12:51 PM >>> 
Has the gwha user been configured as a local linux user (in /etc/passwd
not LUM), Yes

the GWHA service enabled in xinetd   Yes

credentials configured in the grpwise-mon startup script file to
include the gwha user  Yes

relevant agent http user ... ?   Don't understand this one.
 
Al B

>>> On 12/27/2012 at 12:48 PM, Lawrence Kearney
<lawrence.kearney at earthlink.net> wrote:

Has the gwha user been configured as a local linux user (in /etc/passwd
not LUM), the GWHA service enabled in xinetd and the credentials
configured in the grpwise-mon startup script file to include the gwha
user and the relevant agent http user ... ?


-- lawrence


-----Original Message-----
>From: Alan Bens <ABENS at go-metro.com>
>Sent: Dec 27, 2012 12:36 PM
>To: NGWList <ngw at ngwlist.com>
>Subject: Re: [ngw] monitor/restart groupwise agents
>
>Well I've been working on this since Dec 12th (off and on) and I have
>not been able to get the GWHA to work.  I read the Novell docs,
Danita's
>book, Everything is installed and monitoring.  I followed all the
steps
>in the cool solutions article (except my poor title of the comment,
to
>much holiday punch) and I'm still unable to the auto restart to work.
> 
>GW 2012 Sp1 SLES 10.3 OES 2.0.3  Head hurts and is getting flat.
> 
>But I hope everyone had a nice Christmas/Holiday.
> 
>Al B
>
>>>> On 12/12/2012 at 1:37 PM, "Kenneth Etter" <kle at msktd.com> wrote:
>
>I wasn't aware of that...missed that section in the docs.
>
>Ken
>
>>>> On 12/12/2012 at 11:22 AM, in message
><CAMYRAPMKo4n+8hY95pV2JGjSCMzqaUuP3W_fsRbW1tN1XPXsoA at mail.gmail.com>,
>Joseph Marton <jmmarton at gmail.com> wrote:
>
>Well by default GWIA binds to all IPs, so that makes sense.  All you
>should
>have to do is change GWIA to bind exclusively to the assigned IP as
>Morris
>suggested but you shouldn't have to do anything with postfix.
>
>You can do a quick test if you can schedule a couple of minutes of
>downtime.  Shutdown GWIA, startup postfix, then try to telnet both to
>localhost and the assigned IP on port 25.  If I was a betting man,
and
>I'm
>not because I'm a Cubs fan, I would bet that you'll only be able to
>connect
>on localhost.
>
>Joe
>
>
>On Wed, Dec 12, 2012 at 10:14 AM, Kenneth Etter <kle at msktd.com>
wrote:
>
>> Thanks Morris, I wasn't aware of that.
>>
>> Joe, when I initially installed GW 2012 on OES 11, my GWIA wasn't
>> sending/receiving.  I stopped postfix and the GWIA started working.

>So I'm
>> not sure when that became the default, but it didn't seem to be on
>my
>> install.
>>
>> Regards,
>> KEn
>>
>>
>> >>> On 12/12/2012 at 11:08 AM, in message <CAMYRAPMWp1t+ry3j+r3Ua==
>> 2qrrFb63PAL4AvbOefdxEpqiT2A at mail.gmail.com>, Joseph Marton <
>> jmmarton at gmail.com> wrote:
>>
>> That should actually be the default postfix setting.  Earlier
>versions of
>> SLES and OES had postfix bound to all IPs, but for quite some time
>now it
>> binds by default to just the loopback interface.
>>
>> Joe
>>
>>
>> On Wed, Dec 12, 2012 at 9:55 AM, Morris Blackham
><mblackham at gw.novell.com
>> >wrote:
>>
>> > You can have postfix and GWIA coexist.   Set GWIA to bind
exclusive
>to
>> the
>> > assigned IP.  Then make sure postfix is configured to only listen
>on
>> > localhost.  Edit /etc/postfix/main.cf and make sure
>inet_interfaces
>> > options is set like this:
>> >
>> > inet_interfaces = localhost
>> >
>> > --Morris
>> >
>> > >>> "Kenneth Etter" <kle at msktd.com> 12/11/2012 4:36 PM >>>
>> > That works nicely except that I disabled postfix since this
server
>also
>> > hosts my GWIA.  So I can't get an email notification from it.
>> >
>> > Ken
>> >
>> >
>> > >>> On 12/11/2012 at 5:24 PM, in message <
>> > 50C742100200008D00086BF7 at hermes.cwu.edu>, Greg DeLuca
><gdeluca at cwu.EDU>
>> > wrote:
>> >
>> >
>> > This basic check-up runs every 2 minutes and should work after
>creating
>> > the files and setting a few variables....  This setup can be
>easily
>> > modified for other agents too.  It also avoids using rcgrpwise
>status
>> which
>> > does not always return the proper status or return code.
>> >
>> >
>> > cat /usr/local/bin/check_po
>> > #!/bin/bash
>> >
>> > declare -i CNT=0
>> > #Modify the name of the GroupWise agent startup file to match the
>actual
>> > name.
>> > CNT=`ps -aef | grep -v grep | grep -c '@admin.poa'`
>> >
>> > if [ $CNT -eq 0 ]
>> > then
>> > echo "Restarting the Admin POA"
>> > echo "Restarted the Admin POA" `! date` >>
>/usr/local/bin/gwpoachk.log
>> > #Modify the name of the GW agent. Check the name by typing the
>command
>> > "rcgrpwise status". Set your email address too.
>> > /etc/init.d/grpwise start Admin.CWU &
>> > mail -s "GroupWise Admin POA restarted" user at domain <
>> > /usr/local/bin/smtpalertpoa.txt
>> > else
>> > echo "The GroupWise Admin POA is running"
>> > fi
>> >
>> > ----------------
>> > cat /usr/local/bin/smtpalertpoa.txt
>> > # set your po's name and the server's name
>> > {po} POA on {servername} restarted.
>> >
>> > ------------------
>> > crontab -e
>> >
>> > */2 * * * * /usr/local/bin/check_po
>> >
>> >
>> >
>> > >>> On 12/11/2012 at 01:33 PM, in message <
>> > 50C7606702000013000E74DA at mail.msktd.com>, Kenneth Etter
><kle at msktd.com>
>> > wrote:
>> >
>> >
>> > Sorry, I know this has been talked about plenty of times, but I
>can't
>> find
>> > what I need.  I am running GW 2012 SP1 on OES 11.  I have had a
>post
>> office
>> > go dead a couple of times now - just needed a restart.  I would
>really
>> like
>> > to have it monitored and auto-restarted in case I am not around
>when it
>> > goes down.  I was reading up on the Monitor Agent and GWHA.  Is
>that my
>> > only option?  Or are there other ways to monitor and restart a
>post
>> office
>> > agent?
>> >
>> > Thanks,
>> > Ken
>> > _______________________________________________
>> > ngw mailing list
>> > ngw at ngwlist.com
>> > http://ngwlist.com/mailman/listinfo/ngw
>> >
>> > Novell GroupWise 2012
>> > http://www.brainshare.com
>> > Follow us at twitter.com/brainshare
>> >
>> > _______________________________________________
>> > ngw mailing list
>> > ngw at ngwlist.com
>> > http://ngwlist.com/mailman/listinfo/ngw
>> >
>> >
>> _______________________________________________
>> ngw mailing list
>> ngw at ngwlist.com
>> http://ngwlist.com/mailman/listinfo/ngw
>>
>> _______________________________________________
>> ngw mailing list
>> ngw at ngwlist.com
>> http://ngwlist.com/mailman/listinfo/ngw
>>
>>
>_______________________________________________
>ngw mailing list
>ngw at ngwlist.com
>http://ngwlist.com/mailman/listinfo/ngw


Lawrence Kearney
Novell GroupWise Specialist
Novell Certified Engineer - Enterprise Services
Novell Certified Linux Administrator
lawrence.kearney at earthlink.net
http://www.lawrencekearney.com
_______________________________________________
ngw mailing list
ngw at ngwlist.com
http://ngwlist.com/mailman/listinfo/ngw



If this is an unsolicited spam message, please click this link to report it: http://control.eastcobbgroup.com:49285/contents/spamreport.shtml?rptid=19741&srvid=16vl15t



More information about the ngw mailing list