Thread Info
  • State Not Answered
  • Replies 5 replies
  • Subscribers 0 subscribers
  • Views 1534 views
  • Users 0 members are here
Options
Suggested

[8.161][BUG][CLOSED] Log Management not forwarding logs

maygyver
Hi,

my system is still not forwarding any logs to Cloud-LM.
Is there still a problem?

My subscription lm-fa8a9941

Sven
  • 0 
    Astaro Beta Report
    --------------------------------
    Version: 8.161
    Type: BUG
    State: CLOSED
    Reporter: maygyver
    Contributor: 
    MantisID: 
    Target version: 
    Fixed in version: 
    --------------------------------

  • 0 in reply to Astaro Beta Bot
    Hi,
    the backend shows that the subscription is in a running state, but it shows that no logs have been entered.  Did it work at some point? Maybe some upstream firewall is blocking the data transfer?
    Can you check if both syslog servers are running on your ASG? (ps axuf|grep syslog)
    Can you please take a look into /var/log/system.log and look out for messages from syslog-ng?

    Cheers,
     andreas
  • 0 in reply to andreas
    Hi, there is no upstream firewall in front. I have had a running LG already, but after 8.161. update and tring to fix it, by getting a new subscription, it is not working.

    Here is the ps.

    root      6914  0.0  0.0   5280   564 ?        S    Mar17   0:00 supervising syslog-ng
    root      6916  0.0  0.1   7756  4092 ?        Ss   Mar17   2:52  \_ /usr/sbin/syslog-ng -f /etc/syslog-ng.conf
    root      3319  0.0  0.0   6256   984 ?        S    Mar22   0:01 supervising syslog-ng
    root       842  0.0  0.1   6552  2500 ?        Ss   16:03   0:00  \_ /opt/syslog-ng/sbin/syslog-ng --no-caps


    Some line from system.log 

    2011:03:28-15:27:42 betaasg01 syslog-ng[6916]: Syslog connection established; fd='101', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:31:26 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='101'
    2011:03:28-15:31:26 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='101', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-15:31:26 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-15:32:26 betaasg01 syslog-ng[6916]: Syslog connection established; fd='98', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:35:59 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='98'
    2011:03:28-15:35:59 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='98', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-15:35:59 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-15:36:59 betaasg01 syslog-ng[6916]: Syslog connection established; fd='98', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:40:42 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='98'
    2011:03:28-15:40:42 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='98', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-15:40:42 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-15:41:42 betaasg01 syslog-ng[6916]: Syslog connection established; fd='98', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:45:25 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='98'
    2011:03:28-15:45:25 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='98', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-15:45:25 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-15:46:25 betaasg01 syslog-ng[6916]: Syslog connection established; fd='98', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:50:09 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='98'
    2011:03:28-15:50:09 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='98', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-15:50:09 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-15:51:09 betaasg01 syslog-ng[6916]: Syslog connection established; fd='98', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:53:58 betaasg01 syslog-ng[6916]: Syslog connection established; fd='35', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-15:53:58 betaasg01 syslog-ng[6916]: Configuration reload request received, reloading configuration;
    2011:03:28-15:55:44 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='35'
    2011:03:28-15:55:44 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='35', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-15:55:44 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-15:56:44 betaasg01 syslog-ng[6916]: Syslog connection established; fd='35', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-16:03:27 betaasg01 syslog-ng[6916]: EOF occurred while idle; fd='35'
    2011:03:28-16:03:27 betaasg01 syslog-ng[6916]: Syslog connection broken; fd='35', server='AF_UNIX(/dev/lmlog)', time_reopen='60'
    2011:03:28-16:03:27 betaasg01 supervise/syslog-ng[3319]: Daemon exited due to a deadlock/signal/failure, restarting; exitcode='134'
    2011:03:28-16:04:27 betaasg01 syslog-ng[6916]: Syslog connection established; fd='101', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-16:07:05 betaasg01 syslog-ng[6916]: Syslog connection established; fd='36', server='AF_UNIX(/dev/lmlog)', local='AF_UNIX(anonymous)'
    2011:03:28-16:07:05 betaasg01 syslog-ng[6916]: Configuration reload request received, reloading configuration;

    Astaro user since 2001 - Astaro/Sophos Partner since 2008

  • 0 in reply to maygyver
    Since 29.03.2001 11:15PM it is working again. Don't now why.

    Sven

    Astaro user since 2001 - Astaro/Sophos Partner since 2008

  • 0 in reply to maygyver
    Maybe some breakage in the backend as we're still changing and fixing things there. Thanks for reporting anyway.
    Cheers,
     andreas
Cookie Information Banner