From: <go...@bo...> - 2008-03-04 14:06:34
|
On Tue, 4 Mar 2008, Marc Grimme wrote: >>>> Does this have to be added to any lists (rpms or files) in >>>> /etc/comoonics/bootimage before it'll get bundled/started in the initrd? >>>> >>>> I have it in my cluster.conf, but there doesn't appear to be anything >>>> listening on port 12242. :-( >>> >>> What does /etc/init.d/fenceack stop and then /etc/init.d/fenceacksv start >>> tell you in the syslog and do you see a service like this: >>> >>> [marc@realserver9 ~]$ ps ax | grep fenceack >>> 12266 ? S >>> 0:36 /usr/bin/python /opt/atix/comoonics-fenceacksv/fenceacksv --xml >>> --xml-clusterconf --xml-novalidate --debug --nodename axqa01_1 >>> /etc/cluster/cluster.conf >>> 12267 ? S 0:08 /usr/bin/logger -t fenceacksv >>> 13119 pts/2 S+ 0:00 grep fenceack >> >> In a word - no. >> >> # /etc/init.d/fenceacksv stop >> Stopping fenceacksv: [ OK ] >> # /etc/init.d/fenceacksv start >> Starting fenceacksv: [ OK ] >> # ps axww | grep fenceack >> 28772 pts/0 S+ 0:00 grep fenceack >> >> Nothing about this gets logged in /var/log/messages. > strange. try starting it manually: > /usr/bin/python /opt/atix/comoonics-fenceacksv/fenceacksv --xml --xml-clusterconf --xml-novalidate --debug --nodename > <nodename> /etc/cluster/cluster.conf > > Where <nodename> is the clusternodename you are starting it on. > > What does it say? That seems to work: # /usr/bin/python /opt/atix/comoonics-fenceacksv/fenceacksv --xml --xml-clusterconf --xml-novalidate --debug --nodename sentinel1c /etc/cluster/cluster.conf DEBUG:comoonics.bootimage.fenceacksv:Parsing document /etc/cluster/cluster.conf DEBUG:comoonics.bootimage.fenceacksv:Nodename: sentinel1c, path: /cluster/clusternodes/clusternode[@name="sentinel1c"]/com_info/fenceackserver DEBUG:comoonics.bootimage.fenceacksv:Starting nonssl server So at a guess, it may be the init script choking on something in my setup. I'll take a closer look at it. Gordan |