Anope Support > 2.0.x/1.9.x Support

Anope 2.0.7/IRCD-Hybrid - Raspberry Pi Jessie - Anope can't start

(1/2) > >>

Nick:
Hello, brand new to this, but thanks for a great bit of software that I hope to be able to use!

I'm quite confused right now, as I'm getting this on boot:


--- Code: ---Starting Anope
Anope 2.0.7, build #2, compiled 16:28:41 Apr 15 2020
Using configuration file conf/services.conf
Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1), port 6666
Successfully connected to uplink #1 127.0.0.1:6666
ERROR: Closing Link: localhost (Invalid password.)

Unfortunately it seems Anope did not start successfully
This error has been logged in your Anope Log file
Located in /home/pi/services/logs/
This may help you diagnose the problem
Further help may be available from https://www.anope.org/
--- End code ---

Seems simple enough, but the passwords are matching in both ircd.conf (hybrid) and services.conf (Anope)

Example: services.conf (


--- Code: ---uplink
{
        /*
         * The IP or hostname of the IRC server you wish to connect Services to.
         * Usually, you will want to connect Services over 127.0.0.1 (aka localhost).
         *
         * NOTE: On some shell providers, this will not be an option.
         */
        host = "127.0.0.1"

        /*
         * Enable if Services should connect using IPv6.
         */
        ipv6 = no

        /*
         * Enable if Services should connect using SSL.
         * You must have an SSL module loaded for this to work.
         */
        ssl = no

        /*
         * The port to connect to.
         * The IRCd *MUST* be configured to listen on this port, and to accept
         * server connections.
         *
         * Refer to your IRCd documentation for how this is to be done.
         */
        port = 6667

        /*
         * The password to send to the IRC server for authentication.
         * This must match the link block on your IRCd.
         *
         * Refer to your IRCd documentation for more information on link blocks.
         */
        password = "PASSWORD"

}

--- End code ---

Password fails whether you use the copy of the encrypted or decrypted password provided in ircd.conf below:


--- Code: ---connect {
        /* name: the name of the server. */
        name = "PiDiscordBot.irc";

        /*
         * host: the host or IP address to connect to. If a hostname is used it
         * must match the reverse DNS of the server.
         */
        host = "127.0.0.1";

        /*
         * vhost: the IP address to bind to when making outgoing connections to
         * servers.
         * serverinfo::vhost and serverinfo::vhost6 will be overridden
         * by this directive.
         */
#       vhost = "192.168.0.2";

        /*
         * send_password, accept_password: the passwords to send and accept.
         * The remote server will have these passwords swapped.
         */
        send_password = "ENCRYPTED_PASSWORD";
        accept_password = "ENCRYPTED_PASSWORD";

        /*
         * encrypted: controls whether the accept_password above has been
         * encrypted.
         */
        encrypted = yes;

        /* port: the port to connect to this server on. */
        port = 6667;

        /*
         * hub_mask: the mask of servers that this server may hub. Multiple
         * entries are permitted.
         */
        hub_mask = "*";

        /*
         * leaf_mask: the mask of servers this server may not hub. Multiple
         * entries are permitted. Useful for forbidding EU -> US -> EU routes.
         */
#       leaf_mask = "*.uk";

        /* class: the class this server is in */
        class = "server";

        /*
         * autoconn   - controls whether we autoconnect to this server or not,
         *              dependent on class limits. By default, this is disabled.
         */
#       flags = autoconn;

};

connect {
        name = "PiDiscordBot";
        host = "127.0.0.1";
        send_password = "ENCRYPTED_PASSWORD";
        accept_password = "ENCRYPTED_PASSWORD";
        encrypted = yes;
        port = 6667;

        /*
         * aftype: controls whether the connection uses "ipv4" or "ipv6".
         * Default is ipv4.
         */
        aftype = ipv6;
        class = "server";
};



--- End code ---

Finally, the log:


--- Code: ---[Apr 17 00:32:41 2020] SERVER: PiDiscordBot.irc (Services for IRC Networks) has connected to the network (uplinked to no uplink)
[Apr 17 00:32:41 2020] Anope 2.0.7 starting up
[Apr 17 00:32:41 2020] Unable to initialize languages, gettext is not installed
[Apr 17 00:32:41 2020] Loading modules...
[Apr 17 00:32:41 2020] Using IRCd protocol hybrid
[Apr 17 00:32:41 2020] Loading databases...
[Apr 17 00:32:41 2020] DB_FLATFILE: Unable to open data/anope.db for reading!
[Apr 17 00:32:41 2020] Databases loaded
[Apr 17 00:32:41 2020] Attempting to connect to uplink #1 127.0.0.1 (127.0.0.1), port 6666
[Apr 17 00:32:41 2020] Successfully connected to uplink #1 127.0.0.1:6666
[Apr 17 00:32:41 2020] ERROR: Closing Link: localhost (Invalid password.)
[Apr 17 00:32:41 2020] Received ERROR from uplink: Closing Link: localhost (Invalid password.)

--- End code ---

Any help you can offer is appreciated.

Thanks,

Nick

Lord255:
hello.
in services.conf you have "port = 6667", however your error msg for the uplink says 6666.
so which one true right now?

you should not link ircd and services on port 6667.
ircd's port 6667 is for users, not for server. although i didnt see your listen and link block, or at least i'm not familiar with whatever ircd is this. :|

anyway: if anope says, that the password is wrong, then the password is wrong.
i presume it comes from the fact, that you want to link the ircd and services on port 6667 which ..

todo:
- link ircd and anope on a diff port (like the example says in the doc: 7000)
- if it still fails, paste your ircd's listen and link block and also your anope's uplink block.
   (dont change it in between.. because if the uplink will say 6667 again and the error msg will contain 6666.. then we will no that the there is an inconsistency in your conf..)
- please state which ircd and anope version are trying to use.

thx.

Nick:
Thanks for the reply, and apologies for the delay. It seemed no matter what I set the port to in services.conf, it would always display 6666 when trying to connect...

I'm using Anope 2.0.7, and here is the full services.conf: https://pastebin.com/QmdTUefe

And here is the IRCD-Hybrid (ircd: version hybrid-1:8.2.0+dfsg.1-2+deb8u1(20140824_4566)): https://pastebin.com/5dWzgBzY

I apologise again for the code dump. Appreciate your help oh Lord255. :)

Lord255:
hi!
i have checked your configs and i see some errors in there for sure.

you need to know, that linking servers means, that in a network there will be more servers, which needs to be identified by an id (no need to take care if you use the defaults) and by a server name, which you completely ignored.
you have to have a network name and then a server name for ircd and a server name for your services.

look at your ircd's servername (line 46).
--- Code: ---// name = "PiDiscordBot.irc"; //
--- End code ---
now look at your services's servername (line 210).
--- Code: ---// name = "PiDiscordBot.irc" //
--- End code ---

those needs to be different.

next: check ircd's line 74. (hub?) read the hints in front of the line. i think that should be yes.
next: ircd's conf line 430-439.  i think this is needed.. because you want to have services. right? line 210 from services's conf should come be here. (which you have fixed previously i hope - see above)
next: ircd's conf line 441-517 - i see some redundancy. either comment out everything from the first one, or just fill out the 2nd one things into the 1st one. fix the servername, fix the ipv6/ipv4 and i would try to connect the two servers without encrypted password (later on your can try to enable that feature..)
next: services line 299 - should be equal to ircd's line 66.

-----

okay.. so. 1st: fix the things mentioned above, 2nd: read all of the hints in the given two example confs, because lots of info is in there.. 3rd: re-check everything and try to use the defaults 1st, later on max out security and etc..

Nick:
I'm very sorry, I presumed the defaults would work in a lot of cases. Guess I didn't read them thoroughly.

Many thanks for checking.

Nick

Navigation

[0] Message Index

[#] Next page

Go to full version