[irc.git] / software / !RELEASES / ircservices / achurch.org / services / lists / ircservices / 2003 / 003547.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] unhappy restart quirks with 5.0.9
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20unhappy%20restart%20quirks%20with%205.0.9&In-Reply-To=">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="003545.html">
   <LINK REL="Next"  HREF="003552.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] unhappy restart quirks with 5.0.9</H1>
    <B>Arathorn</B> 
    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20unhappy%20restart%20quirks%20with%205.0.9&In-Reply-To="
       TITLE="[IRCServices] unhappy restart quirks with 5.0.9">arathorn at theonering.net
       </A><BR>
    <I>Wed Feb  5 09:12:11 PST 2003</I>
    <P><UL>
        <LI>Previous message: <A HREF="003545.html">[IRCServices] hide chanserv's kick
</A></li>
        <LI>Next message: <A HREF="003552.html">[IRCServices] unhappy restart quirks with 5.0.9
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#3547">[ date ]</a>
              <a href="thread.html#3547">[ thread ]</a>
              <a href="subject.html#3547">[ subject ]</a>
              <a href="author.html#3547">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Hi,

I just upgraded from 4.5.43 to 5.0.9 (at last!) for use with unreal 3.2b14
and have so far been very pleased with the transition.  After a few days
of use I've found a few unexpected pieces of behaviour which I'm confused
about:

Firstly, on an /msg operserv shutdown, services SQUITs from the ircd - but
then on almost all occasions the binary continues to run, and will not be
killed by any signal short of a KILL (-9).

On a related note, /msg operserv restart normally fails in precisely the
same manner - but on the one occasion that it came straight back up, all
registered channels with a +k mode in their modelock had mysteriously lost
their +k and key.  Which was a bit of a pain ;)

Moreover, whilst users in the channel access lists were correctly reopped
on reidentifying on the server coming back up - in every channel a random
user also acquired an @.  On being deopped, Chanserv once again enforced
the secureops correctly and refused to let them be reopped. Almost all the
channels have Options: Topic Retention, Secure Ops.  Even more
disturbingly, not all users on the channel were able to see the @ that the
mysteriously-opped user had acquired. (Either in the form of a channel
mode +o event or similar).

Finally, in the WhatsNew for services v5, I was overjoyed to see:

  + The Services stamp of the last user to identify for a nick is now
        recorded on disk, removing the necessity to re-identify when
        Services is restarted.

But so far, when /msg operserv restart works at all - everyone is forced
to reidentify nonetheless (combined with the quirks listed above).  So I'm
guessing that there's something going wrong here.

On a final possibly unrelated note, I've also been getting

[Mon Feb  3 23:23:24 2003] - select irc.theonering.net[127.0.0.1]:Bad file descriptor

error messages popping up in Unreal's ircd.log every 2-16 hours or so.
As services is the only thing connected to a fd on 127.0.0.1, I'm
wondering if there's a connection here to the above problem.

This is all happening on a dual PIII 1.26GHz box running Debian Woody with
a 2.4.18 kernel; everything compiled with gcc 2.95.4 (unreal compiled with
not default linux threads, fwiw).  It's all worked perfectly with
IRCServices 4.3.x, 4.5.x coupled with df467 and unreal 3.1.x on precisely
the same hardware.

Any help would be very much appreciated;

cheers,

A.

_________________________________________
Matthew Hodgson   <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">arathorn at theonering.net</A>
  Arathorn: Co-Sysadmin, TheOneRing.net&#174;

</PRE>

<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="003545.html">[IRCServices] hide chanserv's kick
</A></li>
	<LI>Next message: <A HREF="003552.html">[IRCServices] unhappy restart quirks with 5.0.9
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#3547">[ date ]</a>
              <a href="thread.html#3547">[ thread ]</a>
              <a href="subject.html#3547">[ subject ]</a>
              <a href="author.html#3547">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices] unhappy restart quirks with 5.0.9
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20unhappy%20restart%20quirks%20with%205.0.9&In-Reply-To=">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="003545.html">
	11	<LINK REL="Next" HREF="003552.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] unhappy restart quirks with 5.0.9</H1>
	15	<B>Arathorn</B>
	16	<A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20unhappy%20restart%20quirks%20with%205.0.9&In-Reply-To="
	17	TITLE="[IRCServices] unhappy restart quirks with 5.0.9">arathorn at theonering.net
	18	</A><BR>
	19	<I>Wed Feb 5 09:12:11 PST 2003</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="003545.html">[IRCServices] hide chanserv's kick
	22	</A></li>
	23	<LI>Next message: <A HREF="003552.html">[IRCServices] unhappy restart quirks with 5.0.9
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#3547">[ date ]</a>
	27	<a href="thread.html#3547">[ thread ]</a>
	28	<a href="subject.html#3547">[ subject ]</a>
	29	<a href="author.html#3547">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>Hi,
	35
	36	I just upgraded from 4.5.43 to 5.0.9 (at last!) for use with unreal 3.2b14
	37	and have so far been very pleased with the transition. After a few days
	38	of use I've found a few unexpected pieces of behaviour which I'm confused
	39	about:
	40
	41	Firstly, on an /msg operserv shutdown, services SQUITs from the ircd - but
	42	then on almost all occasions the binary continues to run, and will not be
	43	killed by any signal short of a KILL (-9).
	44
	45	On a related note, /msg operserv restart normally fails in precisely the
	46	same manner - but on the one occasion that it came straight back up, all
	47	registered channels with a +k mode in their modelock had mysteriously lost
	48	their +k and key. Which was a bit of a pain ;)
	49
	50	Moreover, whilst users in the channel access lists were correctly reopped
	51	on reidentifying on the server coming back up - in every channel a random
	52	user also acquired an @. On being deopped, Chanserv once again enforced
	53	the secureops correctly and refused to let them be reopped. Almost all the
	54	channels have Options: Topic Retention, Secure Ops. Even more
	55	disturbingly, not all users on the channel were able to see the @ that the
	56	mysteriously-opped user had acquired. (Either in the form of a channel
	57	mode +o event or similar).
	58
	59	Finally, in the WhatsNew for services v5, I was overjoyed to see:
	60
	61	+ The Services stamp of the last user to identify for a nick is now
	62	recorded on disk, removing the necessity to re-identify when
	63	Services is restarted.
	64
65	But so far, when /msg operserv restart works at all - everyone is forced
66	to reidentify nonetheless (combined with the quirks listed above). So I'm
67	guessing that there's something going wrong here.
68
69	On a final possibly unrelated note, I've also been getting
70
71	[Mon Feb 3 23:23:24 2003] - select irc.theonering.net[127.0.0.1]:Bad file descriptor
72
73	error messages popping up in Unreal's ircd.log every 2-16 hours or so.
74	As services is the only thing connected to a fd on 127.0.0.1, I'm
75	wondering if there's a connection here to the above problem.
76
77	This is all happening on a dual PIII 1.26GHz box running Debian Woody with
78	a 2.4.18 kernel; everything compiled with gcc 2.95.4 (unreal compiled with
79	not default linux threads, fwiw). It's all worked perfectly with
80	IRCServices 4.3.x, 4.5.x coupled with df467 and unreal 3.1.x on precisely
81	the same hardware.
82
83	Any help would be very much appreciated;
84
85	cheers,
86
87	A.
88
89	_________________________________________
90	Matthew Hodgson <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">arathorn at theonering.net</A>
91	Arathorn: Co-Sysadmin, TheOneRing.net®
92
93	</PRE>
94
95	<!--endarticle-->
96	<HR>
97	<P><UL>
98	<!--threads-->
99	<LI>Previous message: <A HREF="003545.html">[IRCServices] hide chanserv's kick
100	</A></li>
101	<LI>Next message: <A HREF="003552.html">[IRCServices] unhappy restart quirks with 5.0.9
102	</A></li>
103	<LI> <B>Messages sorted by:</B>
104	<a href="date.html#3547">[ date ]</a>
105	<a href="thread.html#3547">[ thread ]</a>
106	<a href="subject.html#3547">[ subject ]</a>
107	<a href="author.html#3547">[ author ]</a>
108	</LI>
109	</UL>
110
111	</body></html>