Anope IRC Services
Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Jeremified on December 01, 2008, 11:31:42 PM
-
I'm having a problem linking Anope/Unreal. The main error is "Missing password", although I'm sure the password is there. If I need to include any more info about this, let me know. I apologize if this issue has already been covered somewhere.
services.conf
IRCDModule "unreal32"
RemoteServer 127.0.0.1 6667 services
ServerName "irc-services.sector-five.net"
ServiceUser "services@sector-five.net"
unrealircd.conf
include "aliases/anope.conf";
me
{
name "irc.sector-five.net";
info "Sector Five";
numeric 1;
};
listen *:6660-6669;
link irc-services.sector-five.net {
username *;
hostname 127.0.0.1;
bind-ip *;
port 7029;
hub *;
password-connect "services";
password-receive "services";
class servers;
options { };
};
ulines {
irc-services.sector-five.net;
irc-stats.sector-five.net;
}
anope.bat -debug -nofork (last messages)
[Dec 01 15:59:03 2008] status: [0][Module, Okay - No Error]
[Dec 01 15:59:03 2008] debug: Received: :irc.sector-five.net NOTICE AUTH :*** Looking up your hostname...
[Dec 01 15:59:03 2008] debug: Received: :irc.sector-five.net NOTICE AUTH :*** Found your hostname
[Dec 01 15:59:03 2008] debug: Received: :irc.sector-five.net 461 PASS :Not enough parameters
[Dec 01 15:59:04 2008] debug: Received: ERROR :Missing password
[Dec 01 15:59:04 2008] debug: Missing password
[Dec 01 15:59:04 2008] debug: Received: ERROR :Closing Link: [127.0.0.1] (Missing password)
[Dec 01 15:59:04 2008] debug: Closing Link: [127.0.0.1] (Missing password)
[Dec 01 15:59:04 2008] debug: Emitting event "db_saving" (1 args)
[Dec 01 15:59:04 2008] [hs_request] Succesfully saved database
[Dec 01 15:59:04 2008] debug: Saving FFF databases
[Dec 01 15:59:04 2008] debug: Emitting event "db_saving" (1 args)
[Dec 01 15:59:04 2008] debug: Emitting event "shutdown" (1 args)
[Dec 01 15:59:04 2008] Read error from server: No such file or directory (errornum: 2)
[Dec 01 15:59:04 2008] debug: Sent: SQUIT irc-services.sector-five.net :Read error from server: No such file or directory (error num: 2)
[Dec 01 15:59:04 2008] debug: firstuser() returning NULL (end of list)
[Dec 01 15:59:04 2008] debug: Emitting event "shutdown" (1 args)
[Dec 01 15:59:04 2008] [cs_appendtopic] Unloaded successfully
[Dec 01 15:59:04 2008] [hs_request] Saving database...
[Dec 01 15:59:04 2008] [hs_request] Succesfully saved database
[Dec 01 15:59:04 2008] hs_request un-loaded
[Dec 01 15:59:04 2008] debug: Cleaning out Module run time directory (\modules/runtime) - this may take a moment please wait
[Dec 01 15:59:04 2008] debug: Module run time directory has been cleaned out
Press any key to continue . . .
-
As a first step try changing:
RemoteServer 127.0.0.1 6667 services
To:
RemoteServer 127.0.0.1 6667 "services"
If that doesnt work can you please give us a FULL debug log from Anope please, using ./services -support on *nix or anope.exe -support on windows.
-
The full record was too big to put here (50024 characters). Here's the log (I accidentally copied my entire post over, so it's enclosed in code brackets): http://pastebin.ca/1274547
-
I'm confused, you're telling anope to connect on port 6667 in services.conf but expecting the connection on 7029 in unrealircd.conf?
The missing password still suggests missing quotes around it and I'd be inclined to paste the whole of the two configs along with the output of /stats P, /stats U, & /stats C for good measure from your currently running ircd.
-
I'm confused, you're telling anope to connect on port 6667 in services.conf but expecting the connection on 7029 in unrealircd.conf?
That was an error that I fixed before making that log. I mentioned it because it was a part of the partial .conf record that I gave in the original post. I'll get the entire logs over soon, but right now I'm pressed for time and can't upload them.
-
Sorry for the double post... I found the error, it was a pretty obvious one too. I had been saving my services.conf file in the root Anope directory, not data/ or whatever. Needless to say, the problem is now resolved. Sorry for not catching that sooner...