|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd: error in pam_systemd | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Vincent Untz <vuntz> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | bruno, fcrozat, gp |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Vincent Untz
2011-09-07 13:51:52 UTC
Same here with today's Factory: [ 259.102024] sudo[4405]: gp : TTY=pts/0 ; PWD=/suse/gp ; USER=root ; COMMAND=/bin/bash [ 259.105938] sudo[4407]: pam_systemd(sudo:session): Failed to parse message: Message has only 3 arguments, but more were expected seen that also on shutdown (which fail totally) on actual fresh factory on shutdown/reboot the last message on the screen (not in log) pam_systemd su-l:session failed to connect to system bus didn't get a reply or is blocked etc ... Then I've to poweroff the computer. fsck is running next reboot -> proof of non right shutdown. New information found today in dmesg
30.547182] type=1400 audit(1317753627.590:2): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=1599 comm="su"
which is strange as aa-status return
aa-status
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
systemctl status apparmor.service
apparmor.service - LSB: AppArmor initialization
Loaded: loaded (/etc/init.d/boot.apparmor)
Active: inactive (dead)
CGroup: name=systemd:/system/apparmor.service
systemctl restart apparmor.service
Job failed. See system logs and 'systemctl status' for details.
c-3po:~ # systemctl status apparmor.service
apparmor.service - LSB: AppArmor initialization
Loaded: loaded (/etc/init.d/boot.apparmor)
Active: failed since Tue, 04 Oct 2011 22:03:58 +0200; 6s ago
Process: 12975 ExecStart=/etc/init.d/boot.apparmor start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/apparmor.service
and there's a lot of them
Oct 4 19:41:18 localhost sudo: pam_apparmor(sudo:session): Unknown error occurred changing to root hat: Operation not permitted
Oct 4 19:41:18 localhost kernel: [36359.258045] type=1400 audit(1317750078.872:5): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=11549 comm="sudo"
Oct 4 20:40:27 localhost su: pam_apparmor(su-l:session): Unknown error occurred changing to postgres hat: Operation not permitted
Oct 4 20:40:27 localhost kernel: [ 30.547182] type=1400 audit(1317753627.590:2): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=1599 comm="su"
Oct 4 20:40:42 localhost kdm: :0[2506]: pam_apparmor(xdm:session): Unknown error occurred changing to ioda hat: Operation not permitted
Oct 4 20:40:42 localhost kernel: [ 45.871873] type=1400 audit(1317753642.922:3): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=2506 comm="kdm"
Oct 4 20:47:45 localhost kernel: [ 468.637067] type=1400 audit(1317754065.904:4): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=10108 comm="su"
seems there's a conflict or misconfiguration between apparmor and systemd
fixed in home:fcrozat:systemd/systemd This is an autogenerated message for OBS integration: This bug (716384) was mentioned in https://build.opensuse.org/request/show/87081 Factory / systemd |