Cool Solutions

GWIA won’t start on OES after some changes to config



By:

May 27, 2008 11:46 pm

Reads: 6176

Comments:0

Score:5

One of our engineers called me tonight with a broken GroupWise 7.0.3 GWIA on OES1. he said they tried to add a second GWIA to the same machine and couldn’t get it going.

We looked at it for quite some time, tried loading it from the /etc/init.d/groupwise start OUR-DOM.GWIA command and got very little except it wouldn’t load. Loading it by hand with /opt/novell/groupwise/agents/bin/gwia @/opt/novel/groupwise/agents/share/gwia.cfg would work.

My solution was to modify the /etc/opt/novell/groupwise/gwha.conf file. This is the file that tells the /etc/init.d/grpwise script what to load and from where.

Normally it would have a section for each agent, the gwia one looks like this
[perfect_dom.GWIA]
server = /opt/novell/groupwise/agents/bin/gwia
command = /etc/init.d/grpwise
startup = gwia.cfg
delay = 2
wait = 10

I figured that I had to type the full path to the conf file when I did it manually, maybe it would help to tell the gwah.conf to do the same. My working gwha.conf file looks like this

[perfect_dom.GWIA]
server = /opt/novell/groupwise/agents/bin/gwia
command = /etc/init.d/grpwise
startup = /opt/novell/groupwise/agents/share/gwia.cfg
delay = 2
wait = 10

I don’t know why it’s working this way. Sometime, especially late at night, at the end of a long day, you just have to go with the flow :-))))

VN:F [1.9.22_1171]
Rating: 5.0/5 (1 vote cast)
GWIA won't start on OES after some changes to config, 5.0 out of 5 based on 1 rating

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS