Services are currently down Error / Troubleshooting

These are old archives. They are kept for historic purposes only.
Post Reply
ACParson
Posts: 5
Joined: Mon Nov 17, 2008 5:32 am

Services are currently down Error / Troubleshooting

Post by ACParson »

Okay, I'm at the end of my rope here. I've troubleshot all configs, and they all seem to be correct.

Services speaks to the hub, but it doesn't speak to any of the linked servers. Here are the link blocks from the hub for the linked in servers:
/ns, /cs, /os, etc. all work on main.hub.ircu.org, but not on humility or hyrule, they get the "Services are currently down. Please try again later." error.

Code: Select all

link services.ircu.org {
        username *;
        hostname 69.164.207.121;
        port 7029;
        hub *;
        password-connect "omitted";
        password-receive "omitted";
        class servers;
};

link humility.us.ircu.org {
                username *;
                hostname 69.164.207.123;
                bind-ip *;
                port 7020;
                hub *;
                password-connect "omitted";
                password-receive "omitted";
                class servers;
};

link hyrule.ircu.org {
        username *;
        hostname 69.61.221.132;
        bind-ip *;
        port 7020;
        password-connect "omitted";
        password-receive "omitted";
        class servers;
        options {
        /*autoconnect;*/
        };
};
Humility's link block is:

Code: Select all

link main.hub.ircu.org {
                username *;
                hostname 69.164.207.121;
                bind-ip *;
                port 7020;
                hub *;
                password-connect "omitted";
                password-receive "omitted";
                class servers;
                options {
                        autoconnect;
                };
};
And hyrule's is:

Code: Select all

link main.hub.ircu.org
{
        username         *;
        hostname         69.164.207.121;
        bind-ip          *;
        port             7020;
        hub *;
        password-connect "omitted";
        password-receive "omitted";
        class            servers;
        options {
/*              autoconnect; */
        };
};
The ulines in place are:

Code: Select all

ulines {
services.ircu.org;
stats.ircu.org;
denora.ircu.org;
}
All have the same information in the set configuration for services server, namely:

Code: Select all

set {
        network-name            "IRCu";
        default-server          "irc.ircu.org";
        services-server         "Services.IRCu.org";
        stats-server            "stats.ircu.org";
What am I doing wrong? I've been asked to help fix this issue, but I've been trying all day and I'm still no closer.
katsklaw
Posts: 1124
Joined: Sun Apr 18, 2004 5:06 pm
Contact:

Re: Services are currently down Error / Troubleshooting

Post by katsklaw »

Usually it's because services-server is wrong but I see you have that correct other than the case but I don't think it matters in the set block. Another thing that can cause it is you either edited the wrong file for the other servers or didn't rehash them after you saved the changes. I do see there is no close brace in your paste, check that's actually there in unrealircd.conf

Steps to correct:

1> insure you are editing the correct copy of unrealircd.conf, should be in the same directory as the ircd binary. ie /home/user/Unreal32
2> rehash all the servers.

There is no reason it will work on 1 server and not the others without something being different or a rehash is needed.
Stealth
Head of Support
Posts: 2085
Joined: Tue Jun 15, 2004 8:50 pm
Location: Chino Hills, CA, US
Contact:

Re: Services are currently down Error / Troubleshooting

Post by Stealth »

Code: Select all

services-server         "Services.IRCu.org";
Server names are case-sensitive. Fix this, rehash, and everything should work fine.
ACParson
Posts: 5
Joined: Mon Nov 17, 2008 5:32 am

Re: Services are currently down Error / Troubleshooting

Post by ACParson »

I fixed it. It was the right info, but for whatever reason, the servers weren't seeing it until they were restarted. Once they were restarted, everything talked properly to each other. Thanks for the help.
Post Reply