"THERE IS A PROBLEM WITH THE ALIVE PLUGIN!" (SOLVED)

  1. ‹ Older
  2. 4 years ago

    It's now working! Thank's to secure, Tupolov, Friznit and SavageCDN for all your help and patience.

  3. Tupolov

    17 Oct 2015 Administrator

    Awesome! Thanks for your patience while we roll out this new feature!

  4. Another one here that had the same "THERE IS A PROBLEM WITH THE ALIVE PLUGIN!" problem and got it fixed.

    I'm using 64 bit Arch Linux and the problem was that using a 32 bit software in a 64 bit environment creates a situation where the ALiVEPlugIn is "unable to find" the suitable and needed file when it doesn't exist at all OR doesn't exist in the correct file path.

    So following the earlier discussion in this topic I began with checking

    ldd ALiVEPlugIn.so

    and got

    linux-gate.so.1 (0xf7714000)
    libcurl.so.4 => not found
    libm.so.6 => /usr/lib32/libm.so.6 (0xf74d9000)
    libc.so.6 => /usr/lib32/libc.so.6 (0xf731f000)
    /usr/lib/ld-linux.so.2 (0x5664b000)

    where libcurl.so.4 was not found.
    The missing of this file was causing a repeated spam of "THERE IS A PROBLEM WITH THE ALIVE PLUGIN!" in the dedicated server RPT log file and @aliveserver not connecting to the War Room.

    To cure this I had to install the lib32-curl package to get the sorts of cross-compatibility going for my 64 bit system.

    After I did that and checking with

    ldd ALiVEPlugIn.so

    I was shown this

    linux-gate.so.1 (0xf7739000)
    libcurl.so.4 => /usr/lib32/libcurl.so.4 (0xf74c8000)
    libm.so.6 => /usr/lib32/libm.so.6 (0xf747b000)
    libc.so.6 => /usr/lib32/libc.so.6 (0xf72c1000)
    /usr/lib/ld-linux.so.2 (0x5662b000)
    libidn.so.11 => /usr/lib32/libidn.so.11 (0xf728d000)
    libssh2.so.1 => /usr/lib32/libssh2.so.1 (0xf725a000)
    libssl.so.1.0.0 => /usr/lib32/libssl.so.1.0.0 (0xf71dd000)
    libcrypto.so.1.0.0 => /usr/lib32/libcrypto.so.1.0.0 (0xf6fc9000)
    libgssapi_krb5.so.2 => /usr/lib32/libgssapi_krb5.so.2 (0xf6f76000)
    libkrb5.so.3 => /usr/lib32/libkrb5.so.3 (0xf6e93000)
    libk5crypto.so.3 => /usr/lib32/libk5crypto.so.3 (0xf6e5f000)
    libcom_err.so.2 => /usr/lib32/libcom_err.so.2 (0xf6e5a000)
    libz.so.1 => /usr/lib32/libz.so.1 (0xf6e43000)
    libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf6e25000)
    libdl.so.2 => /usr/lib32/libdl.so.2 (0xf6e20000)
    libkrb5support.so.0 => /usr/lib32/libkrb5support.so.0 (0xf6e11000)
    libkeyutils.so.1 => /usr/lib32/libkeyutils.so.1 (0xf6e0c000)
    libresolv.so.2 => /usr/lib32/libresolv.so.2 (0xf6df3000)

    where we can see among few new additional lines also libcurl.so.4 => /usr/lib32/libcurl.so.4 (0xf74c8000)

    Bear in my mind dear reader that this fix was done with Arch Linux and might not directly apply to the Linux distro you are using. But you can still follow roughly the same principle.

    Also about another thing:

    I was skeptical that like secure asked from Feanix

    @secure
    @aliveServer or @aliveserver ?
    You should lowercase the foldername.

    case-sensitivity would play any role if you got it right on the -mod=@mod1 -line but apparently it did. The thing is even more funny that I could get away with using @AliveServer as the folder name (and in the -mod= -line) before fixing the main problem I was talking about earlier in this reply. But since I got that problem fixed I couldn't anymore use @AliveServer (as the folder name nor in the -mod= -line) because the server would crash during loading the game map always with the same "error message":

    Segmentation fault (core dumped)

    and nothing else. That is a Arch Linux message printed in the console right after the server crashed. There is nothing to be seen in the server RPT log, it just abruptly ends.

    So, if ALiVE devs know about this case-sensitivity maybe they could distribute the @aliveserver -folder written in lowercase?

  5. What is this aliveserver.so file? Do i need it? My dedi server wont accept it when i try to install it?
    Thanks

  6. Tupolov

    18 Feb 2016 Administrator

    Linux only

 

or Sign Up to reply!