Anope IRC Services
Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Eliyah on August 26, 2012, 12:27:49 AM
-
The services shut down with this error message. I had to restart the service. I'm running a 64 bit CentOS with 4GB of RAM.
One day earlier I got the PANIC! buffer = :683AAKOLF QUIT :Connection closed error message.
Is this a memory error? What might be the cause?
Eliyah
-
Get a backtrace. There might be one in the log files.
-
Thanks. I'm not familiar with how to run backtrace. What would be the command?
-
gdb#: (1) From the directory that you would do ./services from, do the following instead: gdb ./services
(2) Do: r -support (3) Upon crash, do: bt full (4) Pastebin everything from step 1 to step 3. (Alternatively, if that output is too long, just
pastebin everything from when Anope crashed to the end of the output of bt full.)
Also get /os modlist
-
gdb ./services
-bash: gdb: command not found
I guess I don't have that. I even ran it as root but command not found
-
Unload any 3rd party modules you have, then
-
gdb ./services
-bash: gdb: command not found
I guess I don't have that. I even ran it as root but command not found
Install 'gdb'
I'm not familiar with CentOS, try 'yum install gdb'
-
http://pastebin.com/0rgdjruz
25[11:19:54pm] -OperServ- Current Module list:
-
25[11:19:54pm] -OperServ- Module: cs_appendtopic [1.8.6 (3072)] [Supported]
-
25[11:19:54pm] -OperServ- Module: cs_enforce [1.8.6 (3072)] [Supported]
-
25[11:19:55pm] -OperServ- Module: enc_none [1.8.6 (3072)] [Encryption]
-
25[11:19:55pm] -OperServ- Module: hs_request [1.8.6 (3072)] [Supported]
-
25[11:19:55pm] -OperServ- Module: inspircd20 [1.8.6 (3072)] [Protocol]
-
25[11:19:55pm] -OperServ- Module: ns_maxemail [1.8.6 (3072)] [Supported]
-
25[11:19:55pm] -OperServ- Module: ns_saregister [1.1] [3rd]
-
25[11:19:55pm] -OperServ- Module: os_info [1.8.6 (3072)] [Supported]
-
25[11:19:55pm] -OperServ- 8 Modules loaded.
-
Try running services when they arent already running
-
http://pastebin.com/4n9YS7p1
-
You have to wait for it to actually crash before typing 'bt full'... Note that starting with -support also doesn't load 3rd party modules which are likely the source of your problem, so use -debug -nofork instead.
-
This is something that doesn't crash right away.. maybe once every day or so.
-
Do you ever change the user modes of any of services clients? That will cause it to crash/do weird things
-
No, I just have a bot that handles all the nick registrations and password sends using the saregister module