Anope IRC Services
Anope Support => 2.0.x/1.9.x Support => Topic started by: Manuel Garcia on January 08, 2010, 10:00:24 PM
-
Hi, this is my first post here.
I've configured Anope 1.91 to run with unreal32, but when i try to start the service with ./service or with ./services -debug -nofork it doesn't do a thing, and when i see the log (Or the debug in the console) it shows at the last lines:
[Jan 08 18:39:10.132833 2010] End config
[Jan 08 18:39:10.132863 2010] Done reading configuration file.
[Jan 08 18:39:10.133130 2010] Every UserKey must be different. It's for YOUR safety! Remember that!
[Jan 08 18:39:10.133154 2010] Loading IRCD Protocol Module: [unreal32]
[Jan 08 18:39:10.133179 2010] trying to load [unreal32]
And nothing else.
What could it be?
-
I cant replicate this result, is it a fresh install or upgrade? is the protocol module (unreal32.so) in /services/data/modules ?
-
I would also recommend trying to load Anope through gdb to see if it's crashing. Sometimes the crash won't be seen outside of GDB.
-
I cant replicate this result, is it a fresh install or upgrade? is the protocol module (unreal32.so) in /services/data/modules ?
Fresh install, both unreal and anope.
The protocol is in /modules/
For Naram:
How can i do that?
-
Ensure gdb is installed on the machine and, inside the service's bin directory, type: gdb services
You should get taken to a (gdb) prompt. Type r and hit enter. See what the output says.
Phil
-
This is the output of the gdb when r and enter:
Starting program: /Users/manu/services/bin/services
Reading symbols for shared libraries +++. done
Program exited with code 0377.
-
I fixed it!!!!!!!!!!!!!!!!!!!!
The problem was that for any reason, the "services" folder was read-only, so when i tried to load ANY protocol it stopped; the solution was to run the services in sudo mode and then voilâ! :D
Services running perfect in my server!!! Thanks to all for your help ;).
-
Err... I wouldn't recommend that since it's using root. If anything, you should save your DBs and config somewhere (assuming they are not owned by root, if they are, you'll have to make them owned by another user) and then remove the installed directory and reinstall as a normal user.