Bug ID 924830
Summary Apparmor service fails to start on boot
Classification openSUSE
Product openSUSE Factory
Version 201503*
Hardware All
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter ushamim@linux.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

The apparmor service fails to start on boot but will work normally if I start
it manually afterwards (systemctl start apparmor).

----------------------------------------------------------------------------

linux-jyg:~ # systemctl status apparmor -l
��� apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/boot.apparmor)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)

Mar 29 12:22:46 linux-2jim systemd[1]: Job apparmor.service/start deleted to
break ordering cycle starting with sysinit.target/start
Mar 29 12:22:46 linux-2jim systemd[1]: Job apparmor.service/start deleted to
break ordering cycle starting with basic.target/start
Mar 29 12:22:46 linux-2jim systemd[1]: Job apparmor.service/start deleted to
break ordering cycle starting with sysinit.target/start
Mar 29 12:29:14 linux-jyg systemd[1]: Stopped LSB: AppArmor initialization.

----------------------------------------------------------------------------

linux-jyg:~ # systemctl show apparmor.service

Type=forking
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutStartUSec=5min
TimeoutStopUSec=5min
WatchdogUSec=0
WatchdogTimestampMonotonic=0
StartLimitInterval=10000000
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=yes
GuessMainPID=no
MainPID=0
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestampMonotonic=0
ExecMainExitTimestampMonotonic=0
ExecMainPID=0
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/etc/init.d/boot.apparmor ;
argv[]=/etc/init.d/boot.apparmor start ; ignore_errors=no ;
start_time=[Sun 2015-03-29 12:34:25 EDT] ; stop_time=[Sun 2015-03-29
12:34:26 EDT] ; pid=3876 ; code=exited ; status=0 }
ExecReload={ path=/etc/init.d/boot.apparmor ;
argv[]=/etc/init.d/boot.apparmor reload ; ignore_errors=no ;
start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
ExecStop={ path=/etc/init.d/boot.apparmor ;
argv[]=/etc/init.d/boot.apparmor stop ; ignore_errors=no ;
start_time=[Sun 2015-03-29 12:34:43 EDT] ; stop_time=[Sun 2015-03-29
12:34:43 EDT] ; pid=4084 ; code=exited ; status=0 }
Slice=system.slice
MemoryCurrent=18446744073709551615
Delegate=no
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=4096
LimitAS=18446744073709551615
LimitNPROC=31291
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=31291
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=no
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=apparmor.service
Names=apparmor.service
Requires=basic.target
Wants=system.slice
WantedBy=sysinit.target
Conflicts=shutdown.target
Before=shutdown.target libvirtd.service sysinit.target
YaST2-Second-Stage.service YaST2-Firstboot.service
After=cleanup.service basic.target system.slice systemd-journald.socket
Documentation=man:systemd-sysv-generator(8)
Description=LSB: AppArmor initialization
LoadState=loaded
ActiveState=inactive
SubState=dead
FragmentPath=/run/systemd/generator.late/apparmor.service
SourcePath=/etc/init.d/boot.apparmor
UnitFilePreset=disabled
InactiveExitTimestamp=Sun 2015-03-29 12:34:25 EDT
InactiveExitTimestampMonotonic=703223225
ActiveEnterTimestamp=Sun 2015-03-29 12:34:26 EDT
ActiveEnterTimestampMonotonic=704613755
ActiveExitTimestamp=Sun 2015-03-29 12:34:43 EDT
ActiveExitTimestampMonotonic=720971923
InactiveEnterTimestamp=Sun 2015-03-29 12:34:43 EDT
InactiveEnterTimestampMonotonic=721002152
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Sun 2015-03-29 12:34:25 EDT
ConditionTimestampMonotonic=703221450
AssertTimestamp=Sun 2015-03-29 12:34:25 EDT
AssertTimestampMonotonic=703221451
Transient=no

----------------------------------------------------------------------------

More info: http://lists.opensuse.org/opensuse-factory/2015-03/msg00390.html


You are receiving this mail because: