Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #183750

Re: systemd & postgresql - flooding system log

From Erwan David <erwan@rail.eu.org>
Newsgroups linux.debian.user
Subject Re: systemd & postgresql - flooding system log
Date 2017-07-16 19:10 +0200
Message-ID <u3Vdo-1Sn-9@gated-at.bofh.it> (permalink)
References (1 earlier) <u3hfY-1iw-5@gated-at.bofh.it> <u3E2S-7j3-19@gated-at.bofh.it> <u3OOB-65Y-1@gated-at.bofh.it> <u3PhD-6gu-1@gated-at.bofh.it> <u3UU1-1vy-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Le 07/16/17 à 18:32, Don Armstrong a écrit :
> On Sun, 16 Jul 2017, Václav Ovsík wrote:
>> On Sun, Jul 16, 2017 at 12:01:56PM +0200, Václav Ovsík wrote:
>>> OMG, I don't looked into /var/log/auth.log :(
>>>
>>> Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session closed for user postgres
>>> Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session opened for user postgres by (uid=0)
>>> Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session closed for user postgres
>>> Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session opened for user postgres by (uid=0)
>>> Jul 16 11:57:57 rt2 runuser: pam_unix(runuser:session): session closed for user postgres
>>>
>>> No, I'm going back to LogLevel notice setting of systemd. :(
> 
> This is not systemd logging this, but pam_unix.so.
> 
>> With su is /var/log/auth.log flooded too, I didn't noticed before :-/
>> (logcheck was filtering this).
> 
> If you don't care about this in your log, then you can either filter it,
> or comment out pam_unix in /etc/pam.d/common-session-noninteractive.
> 
> 
Commenting it will remove authentication methods ? Following that logic
you could also tell to just stop the machine...

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

systemd & postgresql - flooding system log Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-07 16:30 +0200
  Re: systemd & postgresql - flooding system log Michael Biebl <biebl@debian.org> - 2017-07-07 23:00 +0200
    Re: systemd & postgresql - flooding system log Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-08 09:40 +0200
      FYI: systemd session logging - no solution Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-10 17:10 +0200
        Re: FYI: systemd session logging - no solution Joel Rees <joel.rees@gmail.com> - 2017-07-11 15:30 +0200
        Re: FYI: systemd session logging - no solution Reco <recoverym4n@gmail.com> - 2017-07-12 13:00 +0200
      Re: systemd & postgresql - flooding system log Don Armstrong <don@debian.org> - 2017-07-15 00:30 +0200
        Re: systemd & postgresql - flooding system log Michael Biebl <biebl@debian.org> - 2017-07-15 00:50 +0200
          Re: systemd & postgresql - flooding system log Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-16 00:50 +0200
            Re: systemd & postgresql - flooding system log Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-16 12:20 +0200
              Re: systemd & postgresql - flooding system log Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-16 12:50 +0200
                Re: systemd & postgresql - flooding system log Don Armstrong <don@debian.org> - 2017-07-16 18:50 +0200
                Re: systemd & postgresql - flooding system log Erwan David <erwan@rail.eu.org> - 2017-07-16 19:10 +0200
                Re: systemd & postgresql - flooding system log Don Armstrong <don@debian.org> - 2017-07-17 21:50 +0200
                Re: systemd & postgresql - flooding system log - SOLUTION Václav Ovsík <vaclav.ovsik@gmail.com> - 2017-07-17 09:10 +0200

csiph-web