UnrealIRCd Forums

Hello,

I'm attempting to set up remote includes using curl on unrealircd3.2.8.

When i start unreal i get the following error:

[error] unrealircd.conf:76: include: error downloading 'http://******:*****@xtirc.scs.*********.com/remoteconfigs/_global/glob_help.conf': Could not resolve host: xtirc.scs.*******.com (Successful completion)


I can't figure out why. I've ran an IRCd successfully not to long ago (although on 3.2.7) and curl includes worked perfectly.


I am able to execute "curl my.url.here" successfully, and i'm also able to resolve the host via nslookup.

I found someone having the same issue here as well:
http://bugs.unrealircd.org/bug_view_adv ... ug_id=1827

I also noticed that the remote includes DO work if I use an ip address instead of a domain.

Any help on this?

I rolled back to 3.2.7 and everything works perfectly. This is a bug in 3.2.8.

DeMiNe0 wrote:I rolled back to 3.2.7 and everything works perfectly. This is a bug in 3.2.8.

Or your DNS settings in unrealircd.conf are wrong.

I was using the same config for both versions of UnrealIRCD

I upgraded a hub and a non-user server on my network to 3.2.8 as a trial before rolling out to the rest of the servers and the remote include system works fine, although it uses a different authentication system (non-http-auth). If there is a bug, it's either a curl-version or system-specific problem, or it's the difference between using http auth and not.

For reference, both servers on 3.2.8 are Debian, Unreal3.2.8, and libcurl 7.18.2.

DeMiNe0 wrote:I rolled back to 3.2.7 and everything works perfectly. This is a bug in 3.2.8.

In my understanding, this sounds like bug http://bugs.unrealircd.org/view.php?id=3847 . Why? Because UnrealIRCd-3.2.7 bundles, uses, and exports symbols from c-ares-1.4.0. UnrealIRCd-3.2.8{,.1} bundles, uses, and exports symbols from c-ares-1.6.0. c-ares's DNS resolving API ( & thus ABI ) changed between c-ares-1.4.0 and c-ares-1.5.*. You are asking a cURL that was designed and compiled against c-ares-1.4.0 with unrealircd's bundled c-ares-1.6.0.

The solution is to upgrade your OS's cURL installation to something compatible with c-ares-1.6.0. But, better yet, to have unrealircd use the same c-ares that libcURL is using. With unrealircd-3.2.9, you may specify this by passing --with-system-cares to ./configure (./Config will ask you for extra parameters). Now, if unrealircd-3.2.8 tried to compile against the system-installed c-ares and the system had c-ares-1.4.0, you'd be stopped at ./configure time because unrealircd asks for c-ares-1.6.0 (because of API changes). Then you'd ask your OS's package manager to upgrade your system overall and end up with compatible, system-installed versions of c-ares and libcurl. Then remote includes would work and not give strange undecipherable errors _and_ your OS would be kept more up-to-date .