Anope IRC Services
Anope Support => 1.8.x/1.7.x Support (Read Only) => Topic started by: Vunderik on January 13, 2007, 06:01:17 AM
-
I see services connected to my UnrealIRCD in status, but all my attemps to send them any command fail with such error. I don't know what to do. The same problems with register and identify commands and with all services.
WinXP, anope-1.7.9, Unreald 3.2.6
-
Firstly, services didn't need the autoconnect options on your services link block. And by looking at your config, i don't see anything wrong with it, except that on line no.1 on your unrealircd.conf you have
Fixedsys;Arial;Fixedsys;Arial;Fixedsys;Fixedsys;Arial;Fixedsys;Arial;Fixedsys;Arial;include "help.conf";
which can happen because of an improper editor or edit. that will give you an error on your unrealircd.cong when you do /rehash
line no. 4
include "aliases\anope.conf"
you have a missing semicolon at the end.
[Edited on 13-1-2007 by n00bie]
-
Originally posted by Vunderik
anope-1.7.9
you should really consider upgrading...
-
Originally posted by Viper
you should really consider upgrading...
Id personally say "consider" is an understatement and that "should" should have been emphasized. :P
-
well anope link block in conf dont need autoconnect 2nd you should update anope version in unreal config check this part below
include "aliases/anope.conf";<<<<<< that one hope your problem fix u need add this line in config.
-
Hassankhalid, you've just repeated whats been said already. Please check to make sure you're adding something useful to the topic, otherwise some may see it as spam or post-count-inflating.
-
Guys, If services is returning "-NickServ- unnkown command help" ,then services is already successfully connected so it's not a link issue.
Vunderik, upgrade to 1.7.18 and see if that fixes your problem.
-
I've updated and corrected mistake with semicolon, but Nickserv returns exactly the same mistake. Maybe something is wrong with services.conf? But when i start them they return no mistakes.
-
i suggest you do a backup of your databases and upgrade your services to 1.7.18
-
;( the same problem with 1.7.18... I have no idea why
-
do you have 'UseStrictPrivMsg' enabled on your services.conf