5
responses

Dear All,
I'm using this product for a months and it works fine, every windows PC (Win 7 and Win10) sent informations to central linux syslog server.
Now it doesn't work because I've changed network settings. All of my Windows computers have got 802.1x authentication so the networking
goes up after user login.

Maybe NXlog starts before user login and try to connect syslog server sending some messages, so it doesn't reach syslog remain in running status
and don't send any other informations.

Any ideas ?
Thanks a lot for you help !
Best Regards
Willy

AskedOctober 31, 2019 - 3:37pm

Comments (5)

  • willy70's picture

    Dear Manuel,
    I read delay autostart article but I think that my use case is a little bit different.

    Let me explain. I've got Windows 7 with some users without administrative privileges. Each user
    has got an own credentials to make login and another credentials to make network access
    (802.1x).

    So the problem is that NXLOG try to reach syslog server but without network it can't send
    anything and it don't send any other messages for all time !
    The NXLOG service appear to be in run a state.

    Are there any developer that can test this scenario and take some time to fix it ?

    Thanks a lot !
    Best Regards
    Willy

  • manuel.munoz's picture
    (NXLog)

    Willy,

    Unfortunately we cannot accept new feature requests for Community Edition at this moment.
    In the other hand, what about creating a script that start both the network access plus nxlog agent (in that order)?

  • willy70's picture

    Does NXLog run without administrator privileges ?

    How do I make to link networking and start other service ? For example ... from Task or from service network properties ?

    Greetings
    Willy

  • manuel.munoz's picture
    (NXLog)

    I was thinking in something like creating a batch file that your users can execute instead of just doing the network authentication...

    1. Starting your network authentication (your command here).
    2. sleep(x) wait a bit for previous step to be fully completed).
    3. Starting nxlog (your command here).

Answers (0)