ALiVE stat tracking not working [BUG]

  1. last year

    Hey all,

    I'm trying to run ALiVE on a Linux dedicated server with stat tracking enabled. I've followed the setup steps for adding a server and encounter an error in the output:
    Here's the output of ldd on the SO file:

    server@TehServer: ~/arma3: $ ldd @aliveserver/ => (0xf77a6000) => /usr/lib/i386-linux-gnu/ (0xf753e000) => /lib/i386-linux-gnu/ (0xf74f8000) => /lib/i386-linux-gnu/ (0xf7348000)
    /lib/ (0x565e5000) => /usr/lib/i386-linux-gnu/ (0xf7315000) => /usr/lib/i386-linux-gnu/ (0xf72fa000) => /lib/i386-linux-gnu/ (0xf72a1000) => /lib/i386-linux-gnu/ (0xf70f4000) => /usr/lib/i386-linux-gnu/ (0xf70ad000) => /usr/lib/i386-linux-gnu/ (0xf709e000) => /usr/lib/i386-linux-gnu/ (0xf704c000) => /lib/i386-linux-gnu/ (0xf7032000) => /lib/i386-linux-gnu/ (0xf7016000) => /usr/lib/i386-linux-gnu/ (0xf6f4f000) => /lib/i386-linux-gnu/ (0xf6ec8000) => /lib/i386-linux-gnu/ (0xf6ec3000) => /usr/lib/i386-linux-gnu/ (0xf6e05000) => /usr/lib/i386-linux-gnu/ (0xf6dd5000) => /lib/i386-linux-gnu/ (0xf6dcf000) => /usr/lib/i386-linux-gnu/ (0xf6dc3000) => /lib/i386-linux-gnu/ (0xf6dab000) => /usr/lib/i386-linux-gnu/ (0xf6d90000) => /usr/lib/i386-linux-gnu/ (0xf6d54000) => /usr/lib/i386-linux-gnu/ (0xf6d3f000) => /usr/lib/i386-linux-gnu/ (0xf6d03000) => /lib/i386-linux-gnu/ (0xf6cfe000) => /lib/i386-linux-gnu/ (0xf6cfa000) => /usr/lib/i386-linux-gnu/ (0xf6cf1000) => /usr/lib/i386-linux-gnu/ (0xf6c6a000) => /usr/lib/i386-linux-gnu/ (0xf6bc4000) => /usr/lib/i386-linux-gnu/ (0xf6b8f000) => /usr/lib/i386-linux-gnu/ (0xf6b79000) => /usr/lib/i386-linux-gnu/ (0xf6b72000) => /usr/lib/i386-linux-gnu/ (0xf6b48000) => /usr/lib/i386-linux-gnu/ (0xf6b39000) => /usr/lib/i386-linux-gnu/ (0xf6af2000) => /usr/lib/i386-linux-gnu/ (0xf6a35000) => /lib/i386-linux-gnu/ (0xf6a04000)

    Does anyone have any idea what's wrong?

  2. Tupolov

    12 Jan 2017 Administrator

    Did you get the latest plugin from the ALiVE War Room Server Setup page?

    Is there a plugin log file created in @aliveserver?


  3. Tupolov

    12 Jan 2017 Administrator

    Also check out the Linux guide here

  4. Try running ldconfig as root to reload the library cache. If that doesn't help try a reboot.

  5. Looks like ldconfig fixed the issue.

    Next question, while I already have a post open... is it possible to do stat tracking without loading the base @ALiVE mod, or is that only a thing when the core mod is loaded on the server and clients?

  6. Tupolov

    13 Jan 2017 Administrator

    Requires @ALiVE on all clients and server. You don't need to enable any modules other than data (which can be done automatically using the sys_data_auto.pbo in the optional folder)

  7. Awesome. I loaded sys_data_auto.pbo into the addons directory in @ALiVE and loaded @ALiVE followed by @aliveserver, but don't see the operation showing up in the war room. Have I done something wrong? The log shows a successful connection to the database.

     server@TehServer: ~/arma3/@ALiVE/ $ ls addons/ | grep data
  8. Tupolov

    14 Jan 2017 Administrator

    Post the server RPT

    Is there a conflicting data module in the mission?

  9. The mission doesn't have any ALiVE modules. I assume by RPT you mean log? Here's the server log:

    I'll try and grab the server output in a few hours.

  10. Tupolov

    14 Jan 2017 Administrator

    Hmmm, well we got an OperationStart event from your server, but not sure we're getting other data. Will look into it.

  11. Tupolov

    14 Jan 2017 Administrator

    Ok there's a bug with AAR where it is not initializing with sys_data_auto.pbo. Will be fixed in next release.

  12. Looks like a new build went out (139494), but I'm still not seeing the operation listed. As far as I can tell the logs and server output are the same as previously posted.

  13. Tupolov

    18 Jan 2017 Administrator

    Can you put on Data debug and send the RPT?

  14. Here's the log:

  15. Tupolov

    18 Jan 2017 Administrator

    Need the RPT

  16. I don't know what an RPT is.

  17. Google Arma rpt

  18. Thanks @SpyderBlack723.


  19. Tupolov

    18 Jan 2017 Administrator

    Ok, confirmed there is a bug. Will try to get a hotfix out over the next few days.

  20. Is that what ia wrong with my server as well

  21. Newer ›

or Sign Up to reply!