1348328 - restarted anope

Status: RESOLVED DUPLICATE of bug 1272863

(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)

Description

[Ludovic Hirlimann [:Usul]]

[[e-mail]3 ~]$ sudo /etc/init.d/anope status
Anope is not currently running
[[e-mail]3 ~]$ sudo /etc/init.d/anope start
Starting Anope
Anope 2.0.3, build #6, compiled 11:09:53 Apr 15 2016
Using configuration file conf/services.conf
Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1), port 7000
Successfully connected to uplink #1 127.0.0.1:7000
Successfully linked, launching into background...
[[e-mail]3 ~]$ ps -efww | grep anope | grep -v grep
anope    17385     1 32 09:16 pts/0    00:00:05 /home/anope/services/bin/services
[[e-mail]3 ~]$ 


https://mana.mozilla.org/wiki/display/NAGIOS/IRC+ChanServ still lists lerxst as a contact can you update the escalation Ashish ?

Comment 1

[Ludovic Hirlimann [:Usul]]

Fri 16:51:30 UTC [5090] irc1.dmz.scl3.mozilla.com:IRC ChanServ is CRITICAL: NICK CRITICAL: ChanServ is not on irc (http://m.mozilla.org/IRC+ChanServ)
<nagios-scl3> Fri 16:51:31 UTC [5091] belew.mozilla.org:IRC ChanServ is CRITICAL: NICK CRITICAL: ChanServ is not on irc (http://m.mozilla.org/IRC+ChanServ)

[[e-mail]3 ~]$ ps -efww | grep anope | grep -v grep
[[e-mail]3 ~]$ sudo /etc/init.d/anope start
Starting Anope
Anope 2.0.3, build #6, compiled 11:09:53 Apr 15 2016
Using configuration file conf/services.conf
Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1), port 7000
Successfully connected to uplink #1 127.0.0.1:7000
Successfully linked, launching into background...
[[e-mail]3 ~]$ ps -efww | grep anope | grep -v grep
anope    19736     1 44 09:53 pts/0    00:00:05 /home/anope/services/bin/services

Comment 2

[Ludovic Hirlimann [:Usul]]

[[e-mail]3 ~]$ ps -efww | grep anope | grep -v grep
[[e-mail]3 ~]$ sudo /etc/init.d/anope start
Starting Anope
Anope 2.0.3, build #6, compiled 11:09:53 Apr 15 2016
Using configuration file conf/services.conf
Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1), port 7000
Successfully connected to uplink #1 127.0.0.1:7000
Successfully linked, launching into background...
[[e-mail]3 ~]$ ps -efww | grep anope | grep -v grep
anope    19736     1 44 09:53 pts/0    00:00:05 /home/anope/services/bin/services

Comment 3

[Keegan Ferrando [:fauweh]]

I had to fire up anope several more times. Absolutely nothing of note in the log /home/anope/services/logs/services.log.20170317.

Comment 4

[Keegan Ferrando [:fauweh]]

Ashish found that chanserv/anope was dying after trying to perform the regular expired user deletions on user 'Alexander'.

<NickServ> Expiring nickname Alexander (group: Alexander) (e-mail: [e-mail])
<ChanServ> Deleting channel #Bersal_Übersetzungen owned by deleted nick Alexander
<NickServ> Deleting nickname group Alexander

Curious, I joined the channel and found that ChanServ was the only sole member. Unfortunately, this seems to have stopped the bug from triggering again to capture a good gdb dump as ChanServ was able to remove the channel registration and leave without the channel being orphaned, since I was present.

* ChanServ sets mode -r on #Bersal_Übersetzungen

Anope did not crash afterwards and ChanServ was no longer in the channel. This does seem to confirm that there is a bug when the following conditions are met.

* User is expired and flagged for deletion
  AND
* Expired user is owner of a channel with no members (causing ChanServ to park itself to preserve the channel?)
  
  Triggered When
* Anope attempts to delete the channel with no members present other than itself