[opensuse] 13.1 server semi-freeze, apparmor probs
This am my 13.1 server apparently ran out of tmp space, df gave no output for so long I killed it. My email client complained of "no tmp space available", and attempting to clear tmp space provided "read only file system". I rebooted the server which cleared tmp space but came up in "service" mode complaining of apparmor probs with dovecot. I disabled dovecot and restarted server and found same situation with apache2. I went no farther with apparmor but logged on and changed to runlevel 3. System appears to perform "normally". I cleared aged entries in /tmp and /var/tmp w/o incident. System appears working correctly but if I need to reboot, I can only do so locally as the box boot to service/recovery mode requiring action before achieving network. What can I do to correct my apparmor probs? tks, -- (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
Patrick Shanahan wrote:
This am my 13.1 server apparently ran out of tmp space, df gave no output for so long I killed it. My email client complained of "no tmp space available", and attempting to clear tmp space provided "read only file system".
I rebooted the server which cleared tmp space but came up in "service" mode complaining of apparmor probs with dovecot. I disabled dovecot and restarted server and found same situation with apache2. I went no farther with apparmor but logged on and changed to runlevel 3. System appears to perform "normally". I cleared aged entries in /tmp and /var/tmp w/o incident.
System appears working correctly but if I need to reboot, I can only do so locally as the box boot to service/recovery mode requiring action before achieving network.
What can I do to correct my apparmor probs?
TBH, it sounds pretty odd that apparmor would prevent a normal system start up. If you're certain, to start with, put apparmor in warning-only mode. (I'm sorry, I can't remember how to do that). Then you can proceed with a normal system and start investigating the apparmor issue in detail. -- Per Jessen, Zürich (2.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tuesday 17 of February 2015 10:04:44 Patrick Shanahan wrote:
This am my 13.1 server apparently ran out of tmp space, df gave no output for so long I killed it. My email client complained of "no tmp space available", and attempting to clear tmp space provided "read only file system".
I rebooted the server which cleared tmp space but came up in "service" mode complaining of apparmor probs with dovecot. I disabled dovecot and restarted server and found same situation with apache2. I went no farther with apparmor but logged on and changed to runlevel 3. System appears to perform "normally". I cleared aged entries in /tmp and /var/tmp w/o incident.
What can I do to correct my apparmor probs?
Perhaps some cache files in /etc/apparmor.d/cache are corrupted. Did you try removing them? The read-only filesystem suggests that it is corrupted. Did you check the disk? -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
auxsvr＠gmail.com -
Patrick Shanahan -
Per Jessen