Anope IRC Services
Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: xristos on January 26, 2008, 04:18:57 PM
-
Hi. i have a problem linking anope with ircd witch are in different boxes ex:
services are in: box1.sh3lls.net
ircd is in box4.sh3lls.net
If i move the services to box4.sh3lls.net linking succesuful
with ircd.
If i live it to box1.sh3lls.net
and run services at log it load all modules bla bla ok with no errors and at the end i get this:
Read error from server: Unknown error: 0 (error num: 0)
services.conf:
RemoteServer ip-of-the-ircd-box 7023 "passhere"
ircd.conf:
connect {
name services.my.net;
host ip-of-the-services-box;
apasswd passhere;
cpasswd passhere;
class services;
};
Any idea or help will be usefull
Thanks a lot
-
run services in debug mode to get a more exact error:
./services -debug -nofork
-
and use a better subject in the future please other than general words like "help".
-
[Jan 26 12:36:00.576799 2008] debug: Loaded NickServ database (1/8)
[Jan 26 12:36:00.576977 2008] debug: Loaded HostServ database (2/8)
[Jan 26 12:36:00.577243 2008] debug: Loaded BotServ database (3/8)
[Jan 26 12:36:00.578326 2008] debug: Loaded ChanServ database (4/8)
[Jan 26 12:36:00.578632 2008] debug: Loaded OperServ database (5/8)
[Jan 26 12:36:00.578712 2008] debug: Loaded news database (6/8)
[Jan 26 12:36:00.578794 2008] debug: Loaded exception database (7/8)
[Jan 26 12:36:00.578900 2008] debug: Loaded PreNick database (8/8)
[Jan 26 12:36:00.578953 2008] Databases loaded
[Jan 26 12:36:00.579021 2008] Info: Reflecting database records.
[Jan 26 12:36:00.579076 2008] debug: Emitting event "db_saving" (1 args)
[Jan 26 12:36:00.579128 2008] debug: Saving FFF databases
[Jan 26 12:36:00.587963 2008] debug: Emitting event "db_saving" (1 args)
[Jan 26 12:36:00.588104 2008] debug: Emitting event "connect" (1 args)
[Jan 26 12:36:00.588492 2008] FATAL: Can't connect to server: Permission denied
[Jan 26 12:36:00.588573 2008] debug: Cleaning out Module run time directory (/home/hirc16/services/modules/runtime) - this may take a moment please wait
[Jan 26 12:36:00.667747 2008] debug: Module run time directory has been cleaned out
only in same box with the ip of the ircd in the connect block can connect no other way :/
like this works ok:
RemoteServer 204.88.218.160 7023 "passhere"
ircd
connect {
name services.hellasirc.net;
host 204.88.218.160;
apasswd passhere;
cpasswd passhere;
class services;
};
Please remember that the services ip is different than the ip in the connect block. if i put the default shell ip still cant connect even if he is in the same box ex:
ircd
connect {
name services.hellasirc.net;
host 204.88.218.168; <-- shell default ip of the services
apasswd passhere;
cpasswd passhere;
class services;
};
Note that this ip isn t the real ip.
Thanks.
-
"Please remember that the services ip is different than the ip in the connect block" <--- that's the problem.
you must put the IP services is connecting from in the connect block. and the IP services is to connect to in RemoteServer.
-
my connect block:
ircd ip : 204.8.218.160
ircd.conf:
connect {
name services.hellasirc.net;
host 204.8.218.168;
apasswd passhere;
cpasswd passhere;
class services;
};
services.conf"
RemoteServer 204.8.218.160 7023 "passhere"
services ip: 204.8.218.168
with this i gave u the debug example.
thanks
-
you pasted 2 connect blocks so I have no idea which you are trying to use.
What I do know is linking 2 servers together should take less than 5 minutes for any semi-experienced admin and is probably the easiest task for a netadmin. So if you are having difficulties with such an easy task, perhaps you should re-think being a netadmin and learn more about how IRC works before attempting to run your own network. Just some friendly advice.
-
hehe katsklaw
i know u from the bahamut community ;) i never notice how smart u are :P
also notice:
like this works ok:
RemoteServer 204.88.218.160 7023 "passhere"
ircd
connect {
name services.hellasirc.net;
host 204.88.218.160;
apasswd passhere;
cpasswd passhere;
class services;
};
with :
Please remember that the services ip is different than the ip in the connect block. if i put the default shell ip still cant connect even if he is in the same box ex: (look the example my friend here)
ircd
connect {
name services.hellasirc.net;
host 204.88.218.168; <-- shell default ip of the services
apasswd passhere;
cpasswd passhere;
class services;
};
my connect is this and works fine as i say:
ircd ip : 204.8.218.160
ircd.conf:
connect {
name services.hellasirc.net;
host 204.8.218.168;
apasswd passhere;
cpasswd passhere;
class services;
};
i only want to see why they cant connect from another box from the same company (probably ip problems)
-->
-------------> "Hi. i have a problem linking anope with ircd witch are in different boxes ex:" <--------------------------
services are in: box1.sh3lls.net
ircd is in box4.sh3lls.net
If i move the services to box4.sh3lls.net linking succesuful
with ircd.
so for the netadmin and the all experience u have my friend u better know who is the other guy u talk and i advise u to have some respect in ur posts. (friendly advise). Here and every like here is support forums, not "smart semi-experience" or "experience" or "n00bs" forum or any other u want say it.
----------------------------------------------------------------------------
I Hate smart people look fool and fool look smart.
[Edited on 27-1-2008 by xristos]
[Edited on 27-1-2008 by xristos]
-
ts ts ts
a little respect to users....
-
Hard to tell why they wouldn't be able to connect from a different box. My guess is they use their own ip as remote server, the box may be firewalled, not listening on ports, or i have even had experienced the problem being a routing problem in the DC...
Point is without logs or more concrete data there s only guessing. run services in debug for a more precise error: ./services -debug -nofork
btw services will by default use the boxes main IP which is what the LocalAddress directive is for, that s the most common mistake when remote linking. In most cases it will go bad even sooner with ip/port/connect probs though...