[opensuse] is there a bug here?
in /etc/crontab, I read: # check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 I'm not good enough to understand what mean the end of the line:
/dev/null 2>&1
but my logs are full of déc. 07 18:15:01 linux-uegt CRON[6561]: pam_unix(crond:session): session closed for user root déc. 07 18:30:01 linux-uegt CRON[6776]: pam_unix(crond:session): session closed for user root déc. 07 18:45:01 linux-uegt CRON[7053]: pam_unix(crond:session): session closed for user root every 15 minutes that don't seems very usefull and that seems to come from the cron in question it's the first time I see this in the logs and the run-crons are very old files, so what? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/07/2014 06:48 PM, jdd wrote:
in /etc/crontab, I read:
# check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1
I'm not good enough to understand what mean the end of the line:
/dev/null 2>&1
but my logs are full of
déc. 07 18:15:01 linux-uegt CRON[6561]: pam_unix(crond:session): session closed for user root
prg > /dev/null means to redirect the 1st file descriptor to /dev/null, and a subsequent 2> &1 means to redirect the 2nd file descriptor to the same as the first one. While the regular program output (stdout, standard output, file descriptor 1) and the error diagnostics (stderr, standard error, file descriptor 2) are redirected to the null device, i.e., it's discarded, other components being used may still use other output channels. In this cases, the PAM authentication module is jumping into game when cron opens a "session". I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. Hints found via google either tried to avoid to open a session for cron (/etc/pam.d/cron), or tried to discard the output in the logger (whatever syslog program you are using: I personally installed good'ol rsyslog. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 07/12/2014 18:59, Bernhard Voelker a écrit :
I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. H
question is why is this now when the config is old? thanks your explanations where very good jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 07/12/2014 18:59, Bernhard Voelker a écrit :
I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. H
question is why is this now when the config is old?
Because cron is new(er). It's now cronie. -- Per Jessen, Zürich (4.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 07/12/2014 20:51, Per Jessen a écrit :
Because cron is new(er). It's now cronie.
afaik it's like that since ages :-)
It depends on how you define "ages", but on my 11.1 systems, I have no such messages. I don't see them on 11.4 nor on 12.3 (the latter does surprise me). It's clearly not about cron/cronie. -- Per Jessen, Zürich (4.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-07 20:51, Per Jessen wrote:
jdd wrote:
Le 07/12/2014 18:59, Bernhard Voelker a écrit :
I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. H
question is why is this now when the config is old?
Because cron is new(er). It's now cronie.
No, that's not the reason. It is related to pam reporting this, if I
remember correctly. I think I asked about this message some time ago. Yep:
+++—-—-—-—-—-—-—-—-
Date: Sun, 8 Sep 2013 02:30:11 +0200 (CEST)
From: Carlos E. R. <>
To: OS-EN
Carlos E. R. wrote:
On 2014-12-07 20:51, Per Jessen wrote:
jdd wrote:
Le 07/12/2014 18:59, Bernhard Voelker a écrit :
I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. H
question is why is this now when the config is old?
Because cron is new(er). It's now cronie.
No, that's not the reason.
You're right, it's something else. I think this one has a cure for it: http://askubuntu.com/questions/250105/thousands-of-pam-unix-log-entries-in-l... -- Per Jessen, Zürich (4.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2014 08:28 AM, Per Jessen wrote:
I think this one has a cure for it:
http://askubuntu.com/questions/250105/thousands-of-pam-unix-log-entries-in-l...
Hmm, there is already a similar line in /etc/pam.d/crond: account sufficient pam_listfile.so item=user sense=allow \ file=/etc/cron.allow onerr=succeed quiet ... but there is no '/etc/cron.allow'. I've created it with 'root' as content. I'm curious whether the logging will stop. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2014 09:00 AM, Bernhard Voelker wrote:
On 12/08/2014 08:28 AM, Per Jessen wrote:
I think this one has a cure for it:
http://askubuntu.com/questions/250105/thousands-of-pam-unix-log-entries-in-l...
Hmm, there is already a similar line in /etc/pam.d/crond:
account sufficient pam_listfile.so item=user sense=allow \ file=/etc/cron.allow onerr=succeed quiet
... but there is no '/etc/cron.allow'. I've created it with 'root' as content. I'm curious whether the logging will stop.
No, no change. ;-( Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 08/12/2014 12:47, Bernhard Voelker a écrit :
On 12/08/2014 09:00 AM, Bernhard Voelker wrote:
... but there is no '/etc/cron.allow'. I've created it with 'root' as content. I'm curious whether the logging will stop.
No, no change. ;-(
:-( thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 08/12/2014 08:28, Per Jessen a écrit :
I think this one has a cure for it:
http://askubuntu.com/questions/250105/thousands-of-pam-unix-log-entries-in-l...
Noted. if the logs are harmless (or do not denote any trouble) I can live with it and remove them if really annoying thanks, I wait to the Bernhard report about cron.allow thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Per Jessen
Carlos E. R. wrote:
On 2014-12-07 20:51, Per Jessen wrote:
jdd wrote:
Le 07/12/2014 18:59, Bernhard Voelker a écrit :
I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this. H
question is why is this now when the config is old?
Because cron is new(er). It's now cronie.
No, that's not the reason.
You're right, it's something else.
I think this one has a cure for it:
http://askubuntu.com/questions/250105/thousands-of-pam-unix-log-entries-in-l...
And my Tw has no common-session-noninteractive in /etc/pam.d/ -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Le 08/12/2014 05:17, Carlos E. R. a écrit :
I finished by removing pam-apparmor.
according to yast, pam_apparmor is not installed :-(
Weird. I have this moment three computers running, and one of them has this problem. All three have the same apparmor and pam packages. Looking at the link Per posted: http://askubuntu.com/questions/250105/thousands-of-pam-unix-log-entries-in-l... I see in /etc/pam.d/ a crond file, but all 3 are the same. However, the common-session, which in openSUSE is used for both interactive and non-interactive), is different. Working computers (64 bit both): session required pam_limits.so session required pam_unix2.so session optional pam_umask.so session optional pam_systemd.so session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm problematic computer (32 bit): session required pam_limits.so session required pam_unix.so try_first_pass session optional pam_umask.so session optional pam_systemd.so session optional pam_gnome_keyring.so auto_start only_if=gdm,gdm-password,lxdm,lightdm session optional pam_env.so So I'm thinking of applying those differences and see. [...] Progress! From two lines: 2014-12-20T04:30:01.725229+01:00 AmonLanc /USR/SBIN/CRON[16437]: (root) CMD ([ -x /usr/lib/sa/sa1 ] && exec /usr/lib/sa/sa1 -S ALL 1 1) 2014-12-20T04:30:01.853358+01:00 AmonLanc /USR/SBIN/CRON[16433]: pam_unix(crond:session): session closed for user root I'm now down to one: 2014-12-20T04:40:01.505841+01:00 AmonLanc /USR/SBIN/CRON[16823]: (root) CMD ([ -x /usr/lib/sa/sa1 ] && exec /usr/lib/sa/sa1 -S ALL 1 1) Ie, the "pam_unix" line is out. The second line I have is because "/etc/sysstat/sysstat.cron" lacks a "-": # Activity reports every 10 minutes everyday */10 * * * * root [ -x /usr/lib/sa/sa1 ] && exec /usr/lib/sa/sa1 -S ALL 1 1 changed to: # Activity reports every 10 minutes everyday - -*/10 * * * * root [ -x /usr/lib/sa/sa1 ] && exec /usr/lib/sa/sa1 -S ALL 1 1 [...] Yep: 2014-12-20T04:51:20.595517+01:00 AmonLanc systemd[1]: Started Command Scheduler. 2014-12-20T04:51:20.616274+01:00 AmonLanc /usr/sbin/cron[17161]: (CRON) INFO (running with inotify support) 2014-12-20T04:51:20.618062+01:00 AmonLanc /usr/sbin/cron[17161]: (CRON) INFO (@reboot jobs will be run at computer's startup.) 2014-12-20T05:00:01.644244+01:00 AmonLanc systemd[1]: Starting Session 1811 of user root. 2014-12-20T05:00:01.648345+01:00 AmonLanc systemd[1]: Started Session 1811 of user root. 2014-12-20T05:00:01.693319+01:00 AmonLanc systemd[1]: Starting Session 1812 of user root. 2014-12-20T05:00:01.695803+01:00 AmonLanc systemd[1]: Started Session 1812 of user root. However, the messages from systemd I can not get rid off. Not even by filtering with syslog. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlSU+40ACgkQtTMYHG2NR9WuRACeJYyjQpxPGdPOpM3U0cYG/0KX 5poAn3gwXpFSf7NOGH5tLdm2P16RwLtE =7Hse -----END PGP SIGNATURE-----
participants (5)
-
Bernhard Voelker -
Carlos E. R. -
jdd -
Patrick Shanahan -
Per Jessen