System logs are empty (/var/log/messages; /var/log/secure; etc)logrotate does not compress /var/log/messagesLinux - martian source in /var/log/messageskill a hung mount processApache error logs are empty httpd.conf defines the error log file in /var/log/httpd/error_logPrevious Log Deleted /var/log/securegraylog not getting cents 7.1 syslog messages using the rsyslogd serviceHow can I pull data from journald and outputing it to logz via rsyslogRsyslog hangs after memory usage 456 MBClearing “/var/log/journal”where is rotation policy of logs under /var/log/messages-*

Domain expired, GoDaddy holds it and is asking more money

Are white and non-white police officers equally likely to kill black suspects?

Is Social Media Science Fiction?

How do I create uniquely male characters?

Could Giant Ground Sloths have been a good pack animal for the ancient Mayans?

What is GPS' 19 year rollover and does it present a cybersecurity issue?

Why is the design of haulage companies so “special”?

Unbreakable Formation vs. Cry of the Carnarium

Does the average primeness of natural numbers tend to zero?

What do you call something that goes against the spirit of the law, but is legal when interpreting the law to the letter?

What is the meaning of "of trouble" in the following sentence?

Add an angle to a sphere

Prime joint compound before latex paint?

Can I find out the caloric content of bread by dehydrating it?

Can a planet have a different gravitational pull depending on its location in orbit around its sun?

Is domain driven design an anti-SQL pattern?

What to wear for invited talk in Canada

Email Account under attack (really) - anything I can do?

When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?

Was there ever an axiom rendered a theorem?

Extreme, but not acceptable situation and I can't start the work tomorrow morning

Copycat chess is back

Is there a way to make member function NOT callable from constructor?

Is it wise to focus on putting odd beats on left when playing double bass drums?



System logs are empty (/var/log/messages; /var/log/secure; etc)


logrotate does not compress /var/log/messagesLinux - martian source in /var/log/messageskill a hung mount processApache error logs are empty httpd.conf defines the error log file in /var/log/httpd/error_logPrevious Log Deleted /var/log/securegraylog not getting cents 7.1 syslog messages using the rsyslogd serviceHow can I pull data from journald and outputing it to logz via rsyslogRsyslog hangs after memory usage 456 MBClearing “/var/log/journal”where is rotation policy of logs under /var/log/messages-*






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I found that rsyslog stopped writing on logs (messages; secure; cron;etc)



System information:
NAME="Red Hat Enterprise Linux Server"
VERSION="7.4 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.4"



already restarted rsyslog with no results. Other logs processed by rsyslogd are being writen without issues.



Also restarted systemd-journald.



rsyslog.conf (Omitting commented lines):



$ModLoad imuxsock
$ModLoad imjournal
$WorkDirectory /var/lib/rsyslog
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$IncludeConfig /etc/rsyslog.d/*.conf
$OmitLocalLogging on
$IMJournalStateFile imjournal.state
*.info;mail.none;authpriv.none;cron.none /var/log/messages
authpriv.* /var/log/secure
mail.* -/var/log/maillog
cron.* /var/log/cron
*.emerg :omusrmsg:*
uucp,news.crit /var/log/spooler
local7.* /var/log/boot.log
local3.* /var/log/sshd-second.log


Journald.conf (Omitting commented lines):



[Journal]


Already deleted /run/log/journal/* and restarted journald
Already deleted imjournal.state and restarted rsyslog



output of the command rsyslogd -N 1:



rsyslogd: version 8.24.0, config validation run (level 1), master config /etc/rsyslog.conf


rsyslogd: End of config validation run. Bye.



output of the command rsyslogd -N 6:



rsyslogd: version 8.24.0, config validation run (level 6), master config /etc/rsyslog.conf


rsyslogd: End of config validation run. Bye.



Already tried all the solutions described in https://unix.stackexchange.com/questions/124942/rsyslog-not-logging with no results



Output of lsof -p



COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
rsyslogd 5820 root cwd DIR 202,2 236 64 /
rsyslogd 5820 root rtd DIR 202,2 236 64 /
rsyslogd 5820 root txt REG 202,2 663872 552421 /usr/sbin/rsyslogd
rsyslogd 5820 root mem REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
rsyslogd 5820 root mem REG 202,2 29352 13067688 /usr/lib64/rsyslog/imudp.so
rsyslogd 5820 root mem REG 202,2 68192 34595 /usr/lib64/libbz2.so.1.0.6
rsyslogd 5820 root mem REG 202,2 99944 34673 /usr/lib64/libelf-0.168.so
rsyslogd 5820 root mem REG 202,2 402384 34477 /usr/lib64/libpcre.so.1.2.0
rsyslogd 5820 root mem REG 202,2 19888 34705 /usr/lib64/libattr.so.1.1.0
rsyslogd 5820 root mem REG 202,2 297328 45575 /usr/lib64/libdw-0.168.so
rsyslogd 5820 root mem REG 202,2 111080 1274500 /usr/lib64/libresolv-2.17.so
rsyslogd 5820 root mem REG 202,2 19384 34688 /usr/lib64/libgpg-error.so.0.10.0
rsyslogd 5820 root mem REG 202,2 535064 34703 /usr/lib64/libgcrypt.so.11.8.2
rsyslogd 5820 root mem REG 202,2 157400 34499 /usr/lib64/liblzma.so.5.2.2
rsyslogd 5820 root mem REG 202,2 155752 34476 /usr/lib64/libselinux.so.1
rsyslogd 5820 root mem REG 202,2 1139680 34473 /usr/lib64/libm-2.17.so
rsyslogd 5820 root mem REG 202,2 20032 34709 /usr/lib64/libcap.so.2.22
rsyslogd 5820 root mem REG 202,2 24928 13067682 /usr/lib64/rsyslog/imjournal.so
rsyslogd 5820 root mem REG 202,2 38032 13067689 /usr/lib64/rsyslog/imuxsock.so
rsyslogd 5820 root mem REG 202,2 24416 13067690 /usr/lib64/rsyslog/lmnet.so
rsyslogd 5820 root mem REG 202,2 2127336 23375 /usr/lib64/libc-2.17.so
rsyslogd 5820 root mem REG 202,2 88720 1233870 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
rsyslogd 5820 root mem REG 202,2 20040 35554 /usr/lib64/libuuid.so.1.3.0
rsyslogd 5820 root mem REG 202,2 40824 374355 /usr/lib64/libfastjson.so.4.0.0
rsyslogd 5820 root mem REG 202,2 15424 392270 /usr/lib64/libestr.so.0.0.0
rsyslogd 5820 root mem REG 202,2 44448 23398 /usr/lib64/librt-2.17.so
rsyslogd 5820 root mem REG 202,2 19776 34471 /usr/lib64/libdl-2.17.so
rsyslogd 5820 root mem REG 202,2 144792 1274481 /usr/lib64/libpthread-2.17.so
rsyslogd 5820 root mem REG 202,2 90632 34489 /usr/lib64/libz.so.1.2.7
rsyslogd 5820 root mem REG 202,2 164112 23368 /usr/lib64/ld-2.17.so
rsyslogd 5820 root mem REG 202,2 162560 3600 /usr/lib64/libsystemd.so.0.6.0
rsyslogd 5820 root 0r CHR 1,3 0t0 1041 /dev/null
rsyslogd 5820 root 1w CHR 1,3 0t0 1041 /dev/null
rsyslogd 5820 root 2w CHR 1,3 0t0 1041 /dev/null
rsyslogd 5820 root 3u IPv4 28378 0t0 UDP *:syslog
rsyslogd 5820 root 4u IPv6 28379 0t0 UDP *:syslog
rsyslogd 5820 root 5r a_inode 0,9 0 5987 inotify
rsyslogd 5820 root 6u unix 0xffff8800da61a400 0t0 28380 socket
rsyslogd 5820 root 7r REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
rsyslogd 5820 root 8u a_inode 0,9 0 5987 [eventpoll]
rsyslogd 5820 root 9w REG 202,2 193240 8457 /var/log/haproxy.log


Does anyone have any clues?










share|improve this question




























    1















    I found that rsyslog stopped writing on logs (messages; secure; cron;etc)



    System information:
    NAME="Red Hat Enterprise Linux Server"
    VERSION="7.4 (Maipo)"
    ID="rhel"
    ID_LIKE="fedora"
    VARIANT="Server"
    VARIANT_ID="server"
    VERSION_ID="7.4"



    already restarted rsyslog with no results. Other logs processed by rsyslogd are being writen without issues.



    Also restarted systemd-journald.



    rsyslog.conf (Omitting commented lines):



    $ModLoad imuxsock
    $ModLoad imjournal
    $WorkDirectory /var/lib/rsyslog
    $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
    $IncludeConfig /etc/rsyslog.d/*.conf
    $OmitLocalLogging on
    $IMJournalStateFile imjournal.state
    *.info;mail.none;authpriv.none;cron.none /var/log/messages
    authpriv.* /var/log/secure
    mail.* -/var/log/maillog
    cron.* /var/log/cron
    *.emerg :omusrmsg:*
    uucp,news.crit /var/log/spooler
    local7.* /var/log/boot.log
    local3.* /var/log/sshd-second.log


    Journald.conf (Omitting commented lines):



    [Journal]


    Already deleted /run/log/journal/* and restarted journald
    Already deleted imjournal.state and restarted rsyslog



    output of the command rsyslogd -N 1:



    rsyslogd: version 8.24.0, config validation run (level 1), master config /etc/rsyslog.conf


    rsyslogd: End of config validation run. Bye.



    output of the command rsyslogd -N 6:



    rsyslogd: version 8.24.0, config validation run (level 6), master config /etc/rsyslog.conf


    rsyslogd: End of config validation run. Bye.



    Already tried all the solutions described in https://unix.stackexchange.com/questions/124942/rsyslog-not-logging with no results



    Output of lsof -p



    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    rsyslogd 5820 root cwd DIR 202,2 236 64 /
    rsyslogd 5820 root rtd DIR 202,2 236 64 /
    rsyslogd 5820 root txt REG 202,2 663872 552421 /usr/sbin/rsyslogd
    rsyslogd 5820 root mem REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
    rsyslogd 5820 root mem REG 202,2 29352 13067688 /usr/lib64/rsyslog/imudp.so
    rsyslogd 5820 root mem REG 202,2 68192 34595 /usr/lib64/libbz2.so.1.0.6
    rsyslogd 5820 root mem REG 202,2 99944 34673 /usr/lib64/libelf-0.168.so
    rsyslogd 5820 root mem REG 202,2 402384 34477 /usr/lib64/libpcre.so.1.2.0
    rsyslogd 5820 root mem REG 202,2 19888 34705 /usr/lib64/libattr.so.1.1.0
    rsyslogd 5820 root mem REG 202,2 297328 45575 /usr/lib64/libdw-0.168.so
    rsyslogd 5820 root mem REG 202,2 111080 1274500 /usr/lib64/libresolv-2.17.so
    rsyslogd 5820 root mem REG 202,2 19384 34688 /usr/lib64/libgpg-error.so.0.10.0
    rsyslogd 5820 root mem REG 202,2 535064 34703 /usr/lib64/libgcrypt.so.11.8.2
    rsyslogd 5820 root mem REG 202,2 157400 34499 /usr/lib64/liblzma.so.5.2.2
    rsyslogd 5820 root mem REG 202,2 155752 34476 /usr/lib64/libselinux.so.1
    rsyslogd 5820 root mem REG 202,2 1139680 34473 /usr/lib64/libm-2.17.so
    rsyslogd 5820 root mem REG 202,2 20032 34709 /usr/lib64/libcap.so.2.22
    rsyslogd 5820 root mem REG 202,2 24928 13067682 /usr/lib64/rsyslog/imjournal.so
    rsyslogd 5820 root mem REG 202,2 38032 13067689 /usr/lib64/rsyslog/imuxsock.so
    rsyslogd 5820 root mem REG 202,2 24416 13067690 /usr/lib64/rsyslog/lmnet.so
    rsyslogd 5820 root mem REG 202,2 2127336 23375 /usr/lib64/libc-2.17.so
    rsyslogd 5820 root mem REG 202,2 88720 1233870 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
    rsyslogd 5820 root mem REG 202,2 20040 35554 /usr/lib64/libuuid.so.1.3.0
    rsyslogd 5820 root mem REG 202,2 40824 374355 /usr/lib64/libfastjson.so.4.0.0
    rsyslogd 5820 root mem REG 202,2 15424 392270 /usr/lib64/libestr.so.0.0.0
    rsyslogd 5820 root mem REG 202,2 44448 23398 /usr/lib64/librt-2.17.so
    rsyslogd 5820 root mem REG 202,2 19776 34471 /usr/lib64/libdl-2.17.so
    rsyslogd 5820 root mem REG 202,2 144792 1274481 /usr/lib64/libpthread-2.17.so
    rsyslogd 5820 root mem REG 202,2 90632 34489 /usr/lib64/libz.so.1.2.7
    rsyslogd 5820 root mem REG 202,2 164112 23368 /usr/lib64/ld-2.17.so
    rsyslogd 5820 root mem REG 202,2 162560 3600 /usr/lib64/libsystemd.so.0.6.0
    rsyslogd 5820 root 0r CHR 1,3 0t0 1041 /dev/null
    rsyslogd 5820 root 1w CHR 1,3 0t0 1041 /dev/null
    rsyslogd 5820 root 2w CHR 1,3 0t0 1041 /dev/null
    rsyslogd 5820 root 3u IPv4 28378 0t0 UDP *:syslog
    rsyslogd 5820 root 4u IPv6 28379 0t0 UDP *:syslog
    rsyslogd 5820 root 5r a_inode 0,9 0 5987 inotify
    rsyslogd 5820 root 6u unix 0xffff8800da61a400 0t0 28380 socket
    rsyslogd 5820 root 7r REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
    rsyslogd 5820 root 8u a_inode 0,9 0 5987 [eventpoll]
    rsyslogd 5820 root 9w REG 202,2 193240 8457 /var/log/haproxy.log


    Does anyone have any clues?










    share|improve this question
























      1












      1








      1


      1






      I found that rsyslog stopped writing on logs (messages; secure; cron;etc)



      System information:
      NAME="Red Hat Enterprise Linux Server"
      VERSION="7.4 (Maipo)"
      ID="rhel"
      ID_LIKE="fedora"
      VARIANT="Server"
      VARIANT_ID="server"
      VERSION_ID="7.4"



      already restarted rsyslog with no results. Other logs processed by rsyslogd are being writen without issues.



      Also restarted systemd-journald.



      rsyslog.conf (Omitting commented lines):



      $ModLoad imuxsock
      $ModLoad imjournal
      $WorkDirectory /var/lib/rsyslog
      $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
      $IncludeConfig /etc/rsyslog.d/*.conf
      $OmitLocalLogging on
      $IMJournalStateFile imjournal.state
      *.info;mail.none;authpriv.none;cron.none /var/log/messages
      authpriv.* /var/log/secure
      mail.* -/var/log/maillog
      cron.* /var/log/cron
      *.emerg :omusrmsg:*
      uucp,news.crit /var/log/spooler
      local7.* /var/log/boot.log
      local3.* /var/log/sshd-second.log


      Journald.conf (Omitting commented lines):



      [Journal]


      Already deleted /run/log/journal/* and restarted journald
      Already deleted imjournal.state and restarted rsyslog



      output of the command rsyslogd -N 1:



      rsyslogd: version 8.24.0, config validation run (level 1), master config /etc/rsyslog.conf


      rsyslogd: End of config validation run. Bye.



      output of the command rsyslogd -N 6:



      rsyslogd: version 8.24.0, config validation run (level 6), master config /etc/rsyslog.conf


      rsyslogd: End of config validation run. Bye.



      Already tried all the solutions described in https://unix.stackexchange.com/questions/124942/rsyslog-not-logging with no results



      Output of lsof -p



      COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
      rsyslogd 5820 root cwd DIR 202,2 236 64 /
      rsyslogd 5820 root rtd DIR 202,2 236 64 /
      rsyslogd 5820 root txt REG 202,2 663872 552421 /usr/sbin/rsyslogd
      rsyslogd 5820 root mem REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
      rsyslogd 5820 root mem REG 202,2 29352 13067688 /usr/lib64/rsyslog/imudp.so
      rsyslogd 5820 root mem REG 202,2 68192 34595 /usr/lib64/libbz2.so.1.0.6
      rsyslogd 5820 root mem REG 202,2 99944 34673 /usr/lib64/libelf-0.168.so
      rsyslogd 5820 root mem REG 202,2 402384 34477 /usr/lib64/libpcre.so.1.2.0
      rsyslogd 5820 root mem REG 202,2 19888 34705 /usr/lib64/libattr.so.1.1.0
      rsyslogd 5820 root mem REG 202,2 297328 45575 /usr/lib64/libdw-0.168.so
      rsyslogd 5820 root mem REG 202,2 111080 1274500 /usr/lib64/libresolv-2.17.so
      rsyslogd 5820 root mem REG 202,2 19384 34688 /usr/lib64/libgpg-error.so.0.10.0
      rsyslogd 5820 root mem REG 202,2 535064 34703 /usr/lib64/libgcrypt.so.11.8.2
      rsyslogd 5820 root mem REG 202,2 157400 34499 /usr/lib64/liblzma.so.5.2.2
      rsyslogd 5820 root mem REG 202,2 155752 34476 /usr/lib64/libselinux.so.1
      rsyslogd 5820 root mem REG 202,2 1139680 34473 /usr/lib64/libm-2.17.so
      rsyslogd 5820 root mem REG 202,2 20032 34709 /usr/lib64/libcap.so.2.22
      rsyslogd 5820 root mem REG 202,2 24928 13067682 /usr/lib64/rsyslog/imjournal.so
      rsyslogd 5820 root mem REG 202,2 38032 13067689 /usr/lib64/rsyslog/imuxsock.so
      rsyslogd 5820 root mem REG 202,2 24416 13067690 /usr/lib64/rsyslog/lmnet.so
      rsyslogd 5820 root mem REG 202,2 2127336 23375 /usr/lib64/libc-2.17.so
      rsyslogd 5820 root mem REG 202,2 88720 1233870 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
      rsyslogd 5820 root mem REG 202,2 20040 35554 /usr/lib64/libuuid.so.1.3.0
      rsyslogd 5820 root mem REG 202,2 40824 374355 /usr/lib64/libfastjson.so.4.0.0
      rsyslogd 5820 root mem REG 202,2 15424 392270 /usr/lib64/libestr.so.0.0.0
      rsyslogd 5820 root mem REG 202,2 44448 23398 /usr/lib64/librt-2.17.so
      rsyslogd 5820 root mem REG 202,2 19776 34471 /usr/lib64/libdl-2.17.so
      rsyslogd 5820 root mem REG 202,2 144792 1274481 /usr/lib64/libpthread-2.17.so
      rsyslogd 5820 root mem REG 202,2 90632 34489 /usr/lib64/libz.so.1.2.7
      rsyslogd 5820 root mem REG 202,2 164112 23368 /usr/lib64/ld-2.17.so
      rsyslogd 5820 root mem REG 202,2 162560 3600 /usr/lib64/libsystemd.so.0.6.0
      rsyslogd 5820 root 0r CHR 1,3 0t0 1041 /dev/null
      rsyslogd 5820 root 1w CHR 1,3 0t0 1041 /dev/null
      rsyslogd 5820 root 2w CHR 1,3 0t0 1041 /dev/null
      rsyslogd 5820 root 3u IPv4 28378 0t0 UDP *:syslog
      rsyslogd 5820 root 4u IPv6 28379 0t0 UDP *:syslog
      rsyslogd 5820 root 5r a_inode 0,9 0 5987 inotify
      rsyslogd 5820 root 6u unix 0xffff8800da61a400 0t0 28380 socket
      rsyslogd 5820 root 7r REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
      rsyslogd 5820 root 8u a_inode 0,9 0 5987 [eventpoll]
      rsyslogd 5820 root 9w REG 202,2 193240 8457 /var/log/haproxy.log


      Does anyone have any clues?










      share|improve this question














      I found that rsyslog stopped writing on logs (messages; secure; cron;etc)



      System information:
      NAME="Red Hat Enterprise Linux Server"
      VERSION="7.4 (Maipo)"
      ID="rhel"
      ID_LIKE="fedora"
      VARIANT="Server"
      VARIANT_ID="server"
      VERSION_ID="7.4"



      already restarted rsyslog with no results. Other logs processed by rsyslogd are being writen without issues.



      Also restarted systemd-journald.



      rsyslog.conf (Omitting commented lines):



      $ModLoad imuxsock
      $ModLoad imjournal
      $WorkDirectory /var/lib/rsyslog
      $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
      $IncludeConfig /etc/rsyslog.d/*.conf
      $OmitLocalLogging on
      $IMJournalStateFile imjournal.state
      *.info;mail.none;authpriv.none;cron.none /var/log/messages
      authpriv.* /var/log/secure
      mail.* -/var/log/maillog
      cron.* /var/log/cron
      *.emerg :omusrmsg:*
      uucp,news.crit /var/log/spooler
      local7.* /var/log/boot.log
      local3.* /var/log/sshd-second.log


      Journald.conf (Omitting commented lines):



      [Journal]


      Already deleted /run/log/journal/* and restarted journald
      Already deleted imjournal.state and restarted rsyslog



      output of the command rsyslogd -N 1:



      rsyslogd: version 8.24.0, config validation run (level 1), master config /etc/rsyslog.conf


      rsyslogd: End of config validation run. Bye.



      output of the command rsyslogd -N 6:



      rsyslogd: version 8.24.0, config validation run (level 6), master config /etc/rsyslog.conf


      rsyslogd: End of config validation run. Bye.



      Already tried all the solutions described in https://unix.stackexchange.com/questions/124942/rsyslog-not-logging with no results



      Output of lsof -p



      COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
      rsyslogd 5820 root cwd DIR 202,2 236 64 /
      rsyslogd 5820 root rtd DIR 202,2 236 64 /
      rsyslogd 5820 root txt REG 202,2 663872 552421 /usr/sbin/rsyslogd
      rsyslogd 5820 root mem REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
      rsyslogd 5820 root mem REG 202,2 29352 13067688 /usr/lib64/rsyslog/imudp.so
      rsyslogd 5820 root mem REG 202,2 68192 34595 /usr/lib64/libbz2.so.1.0.6
      rsyslogd 5820 root mem REG 202,2 99944 34673 /usr/lib64/libelf-0.168.so
      rsyslogd 5820 root mem REG 202,2 402384 34477 /usr/lib64/libpcre.so.1.2.0
      rsyslogd 5820 root mem REG 202,2 19888 34705 /usr/lib64/libattr.so.1.1.0
      rsyslogd 5820 root mem REG 202,2 297328 45575 /usr/lib64/libdw-0.168.so
      rsyslogd 5820 root mem REG 202,2 111080 1274500 /usr/lib64/libresolv-2.17.so
      rsyslogd 5820 root mem REG 202,2 19384 34688 /usr/lib64/libgpg-error.so.0.10.0
      rsyslogd 5820 root mem REG 202,2 535064 34703 /usr/lib64/libgcrypt.so.11.8.2
      rsyslogd 5820 root mem REG 202,2 157400 34499 /usr/lib64/liblzma.so.5.2.2
      rsyslogd 5820 root mem REG 202,2 155752 34476 /usr/lib64/libselinux.so.1
      rsyslogd 5820 root mem REG 202,2 1139680 34473 /usr/lib64/libm-2.17.so
      rsyslogd 5820 root mem REG 202,2 20032 34709 /usr/lib64/libcap.so.2.22
      rsyslogd 5820 root mem REG 202,2 24928 13067682 /usr/lib64/rsyslog/imjournal.so
      rsyslogd 5820 root mem REG 202,2 38032 13067689 /usr/lib64/rsyslog/imuxsock.so
      rsyslogd 5820 root mem REG 202,2 24416 13067690 /usr/lib64/rsyslog/lmnet.so
      rsyslogd 5820 root mem REG 202,2 2127336 23375 /usr/lib64/libc-2.17.so
      rsyslogd 5820 root mem REG 202,2 88720 1233870 /usr/lib64/libgcc_s-4.8.5-20150702.so.1
      rsyslogd 5820 root mem REG 202,2 20040 35554 /usr/lib64/libuuid.so.1.3.0
      rsyslogd 5820 root mem REG 202,2 40824 374355 /usr/lib64/libfastjson.so.4.0.0
      rsyslogd 5820 root mem REG 202,2 15424 392270 /usr/lib64/libestr.so.0.0.0
      rsyslogd 5820 root mem REG 202,2 44448 23398 /usr/lib64/librt-2.17.so
      rsyslogd 5820 root mem REG 202,2 19776 34471 /usr/lib64/libdl-2.17.so
      rsyslogd 5820 root mem REG 202,2 144792 1274481 /usr/lib64/libpthread-2.17.so
      rsyslogd 5820 root mem REG 202,2 90632 34489 /usr/lib64/libz.so.1.2.7
      rsyslogd 5820 root mem REG 202,2 164112 23368 /usr/lib64/ld-2.17.so
      rsyslogd 5820 root mem REG 202,2 162560 3600 /usr/lib64/libsystemd.so.0.6.0
      rsyslogd 5820 root 0r CHR 1,3 0t0 1041 /dev/null
      rsyslogd 5820 root 1w CHR 1,3 0t0 1041 /dev/null
      rsyslogd 5820 root 2w CHR 1,3 0t0 1041 /dev/null
      rsyslogd 5820 root 3u IPv4 28378 0t0 UDP *:syslog
      rsyslogd 5820 root 4u IPv6 28379 0t0 UDP *:syslog
      rsyslogd 5820 root 5r a_inode 0,9 0 5987 inotify
      rsyslogd 5820 root 6u unix 0xffff8800da61a400 0t0 28380 socket
      rsyslogd 5820 root 7r REG 0,18 8388608 27215 /run/log/journal/ca23e130dda846d5b2a30e4ab9461e43/system.journal
      rsyslogd 5820 root 8u a_inode 0,9 0 5987 [eventpoll]
      rsyslogd 5820 root 9w REG 202,2 193240 8457 /var/log/haproxy.log


      Does anyone have any clues?







      linux redhat log-files rsyslog journald






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 31 '18 at 9:57









      BANJOSABANJOSA

      63




      63




















          1 Answer
          1






          active

          oldest

          votes


















          0














          A bug fix for a problem where rsyslog would stop writing entries from the systemd journal was released in errata RHBA-2017:2306. Ensure that your system is up to date.






          share|improve this answer


















          • 1





            That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

            – BANJOSA
            Aug 31 '18 at 13:31












          • I have same issue and no solution found

            – Satish
            Oct 22 '18 at 2:09











          • I haven´t found a solution yet. if found I'll posted it here.

            – BANJOSA
            Oct 23 '18 at 14:28











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f928855%2fsystem-logs-are-empty-var-log-messages-var-log-secure-etc%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          A bug fix for a problem where rsyslog would stop writing entries from the systemd journal was released in errata RHBA-2017:2306. Ensure that your system is up to date.






          share|improve this answer


















          • 1





            That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

            – BANJOSA
            Aug 31 '18 at 13:31












          • I have same issue and no solution found

            – Satish
            Oct 22 '18 at 2:09











          • I haven´t found a solution yet. if found I'll posted it here.

            – BANJOSA
            Oct 23 '18 at 14:28















          0














          A bug fix for a problem where rsyslog would stop writing entries from the systemd journal was released in errata RHBA-2017:2306. Ensure that your system is up to date.






          share|improve this answer


















          • 1





            That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

            – BANJOSA
            Aug 31 '18 at 13:31












          • I have same issue and no solution found

            – Satish
            Oct 22 '18 at 2:09











          • I haven´t found a solution yet. if found I'll posted it here.

            – BANJOSA
            Oct 23 '18 at 14:28













          0












          0








          0







          A bug fix for a problem where rsyslog would stop writing entries from the systemd journal was released in errata RHBA-2017:2306. Ensure that your system is up to date.






          share|improve this answer













          A bug fix for a problem where rsyslog would stop writing entries from the systemd journal was released in errata RHBA-2017:2306. Ensure that your system is up to date.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 31 '18 at 12:17









          Michael HamptonMichael Hampton

          174k27319644




          174k27319644







          • 1





            That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

            – BANJOSA
            Aug 31 '18 at 13:31












          • I have same issue and no solution found

            – Satish
            Oct 22 '18 at 2:09











          • I haven´t found a solution yet. if found I'll posted it here.

            – BANJOSA
            Oct 23 '18 at 14:28












          • 1





            That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

            – BANJOSA
            Aug 31 '18 at 13:31












          • I have same issue and no solution found

            – Satish
            Oct 22 '18 at 2:09











          • I haven´t found a solution yet. if found I'll posted it here.

            – BANJOSA
            Oct 23 '18 at 14:28







          1




          1





          That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

          – BANJOSA
          Aug 31 '18 at 13:31






          That doesn't seem to be the issue. The version that is running is rsyslog.x86_64 0:8.24.0-12.el7 (the same one where you link points to). Nevertheless i upgraded to version rsyslog.x86_64 0:8.24.0-16.el7_5.4 witth no success in solving the issue.

          – BANJOSA
          Aug 31 '18 at 13:31














          I have same issue and no solution found

          – Satish
          Oct 22 '18 at 2:09





          I have same issue and no solution found

          – Satish
          Oct 22 '18 at 2:09













          I haven´t found a solution yet. if found I'll posted it here.

          – BANJOSA
          Oct 23 '18 at 14:28





          I haven´t found a solution yet. if found I'll posted it here.

          – BANJOSA
          Oct 23 '18 at 14:28

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f928855%2fsystem-logs-are-empty-var-log-messages-var-log-secure-etc%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

          Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

          Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020