Description of problem: pam_systemd is spewing the logs (with a for totally me unknown message). Version-Release number of selected component (if applicable): systemd-libs-208-14.fc20.x86_64 How reproducible: On 3 out of 3 systems. Steps to Reproduce: 1. grep pam_systemd /var/log/secure 2. 3. Actual results: # grep pam_systemd /var/log/secure|head Feb 24 18:03:01 gw crond[20839]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:04:01 gw crond[20885]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:05:01 gw crond[20937]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:05:01 gw crond[20938]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:05:01 gw crond[20936]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:06:01 gw crond[21036]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:07:01 gw crond[21068]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:08:01 gw crond[21091]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:09:01 gw crond[21114]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 Feb 24 18:10:01 gw crond[21121]: pam_systemd(crond:session): Ignoring vtnr 0 for which is not seat0 # grep pam_systemd /var/log/secure|wc 7000 98000 704627 # Expected results: Sufficiently clean logs (and/or a better explanation of "Ignoring vtnr 0 for which is not seat0") Additional info: Seem to have started with the systemd-libs-208-14.fc20.x86_64 update on Feb 24, se yum.log: # grep "Feb 24" /var/log/yum.log Feb 24 18:02:22 Updated: systemd-libs-208-14.fc20.x86_64 Feb 24 18:02:40 Updated: python-libs-2.7.5-11.fc20.x86_64 Feb 24 18:02:42 Updated: python-2.7.5-11.fc20.x86_64 Feb 24 18:02:52 Updated: systemd-208-14.fc20.x86_64 Feb 24 18:02:54 Updated: gssdp-0.14.7-1.fc20.x86_64 Feb 24 18:02:56 Updated: gupnp-0.20.10-1.fc20.x86_64 Feb 24 18:02:56 Updated: libreport-filesystem-2.1.12-3.fc20.x86_64 Feb 24 18:03:00 Updated: libreport-2.1.12-3.fc20.x86_64 Feb 24 18:03:01 Updated: libreport-python-2.1.12-3.fc20.x86_64
Same problem here with 2 computers running 32 bit systemd-libs-208-14.fc20.i686.
Same here on Linux localhost.home 3.12.10-300.fc20.x86_64 #1 SMP Thu Feb 6 22:11:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Yeah, the patch is already backported and will go out in the next update.
I note sshd causes this as well as cron: pam_systemd(sshd:session): Ignoring vtnr 0 for which is not seat0
systemd-208-15.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-15.fc20
Package systemd-208-15.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-208-15.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3522/systemd-208-15.fc20 then log in and leave karma (feedback).
systemd-208-15.fc20 seems to have solved the issue on the two systems I have tested. Good karma has been left.
systemd-208-15.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.