[IRCServices Coding] problems with 5.0.9

[Arathorn]

I've had this problem too (although I cannot reproduce it at the moment) -
I've reported it on the non-coding list.  Andrew's suggestion there is to
attach to the hung process with gdb and see what's going on (which I'm going
to do when it next happens to me).

That said, I have a suspicion that I may have somehow prevented it; although
so many variables have been changed I'm not sure what may have helped.

Off the top of my head:

1) I changed services to connect to unreal 3.2 on localhost - explicitly
specifying the binding port (i.e. connecting from 127.0.0.1:7028 to
127.0.0.1:7029),

2) enabled a PingFrequency of 30s across the link to try to keep things
alive and healthy (i've also had problems with 3.2 complaining about Bad
File Descriptors on the Services socket when select()ing the FDLIST),

3) Tried running services 'plain' from the commandline rather than from a

start-stop-daemon --start --quiet --pidfile
/usr/local/lib/ircservices/ircservices.pid \
                  --chuid irc:irc --exec /usr/local/sbin/ircservices >
/dev/null 2>&1

in a Debian /etc/init.d script.

Somewhere along there, it's decided to start behaving absolutely fine (after
consistently hanging after the ircd closed its connection).  Services die
cleanly on a /restart and /die work fine - and for that matter, so does
/operserv restart, quit & shutdown.  With the proviso of some thoroughly
screwed up intermittent faults with +k modelocks disappearing on registered
channels after services restarts - and xml-export doing some very mangled
things. c.f. ircservices at ircservices.za.net.

________________________________________________________________
Matthew Hodgson   arathorn at theonering.net   Tel: +44 7968 722968
             Arathorn: Co-Sysadmin, TheOneRing.net®


----- Original Message -----
From: "Aragon Gouveia" <aragon at phat.za.net>
To: <ircservices-coding at ircservices.za.net>
Sent: Monday, February 10, 2003 9:22 PM
Subject: [IRCServices Coding] problems with 5.0.9


> Hi,
>
> The other day I reported the database save bug when ircservices looses its
> uplink.  Just upgraded to 5.0.9 and am having another problem...
>
> When the uplink server closes the connection ircservices does not exit.
> Neither is there any log of such activity.  Further more, issuing a
SIGTERM
> to the process after the uplink has died only results in "Received
SIGTERM,
> exiting." being logged, but the process does not die.  It takes a SIGKILL
to
> kill it off.  And of course a SIGKILL doesn't go down well with saving the
> database to disk! :)
>
> Running Unreal 3.2 btw.
>
>
> Regards,
> Aragon
> ------------------------------------------------------------------
> To unsubscribe or change your subscription options, visit:
> http://www.ircservices.za.net/mailman/listinfo/ircservices-coding