https://bugzilla.novell.com/show_bug.cgi?id=865188 https://bugzilla.novell.com/show_bug.cgi?id=865188#c2 Yarny Yarny <Yarny@public-files.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Yarny@public-files.de | --- Comment #2 from Yarny Yarny <Yarny@public-files.de> 2014-02-22 23:23:42 UTC --- Created an attachment (id=579654) --> (http://bugzilla.novell.com/attachment.cgi?id=579654) setup script which (occasionally) triggers the bug
What is the reason of using a `script' to `issues' some systemctl commands the most services ... ?! The script runs on a freshly installed openSUSE and installs/configures some services which I need on my machines. I'm using VirtualBox to test the script before using it on production systems.
Why do you not use the normal way that is you enable your required services and the set your default target like systemctl set-default graphical.target Hmm, what is "normal"? I'm mostly enabling my services with "systemctl enable whatever.service". But since there are so many, and since there are a lot of other things to do when perparing my machines for use (e.g. put some stuff in /etc/skel, ...), I assembled a script which does these things for me.
Beside: How stable your virtual system is? I'm mostly fine with it --- up to this bug ;-)
The case that the socket /run/systemd/private does not exists indicates that systemd has been crash. It still exists, but systemd doesn't react to connections anymore, since systemd was "freezing execution" (see logfile in original bug report).
Indeed I've several virtual and real systems with systemd running and *never* catched such a crash. And I'm really stress the virtual systems in a hard way. I wish I had better information on how to reproduce the bug, but I haven't. The only reason I can guess is that the bug is more likely to appear if several systemctl calls are issued in short order.
Please attach your crash script. That's not easy. The script grew for several years, is now about 18k lines of python code and contains lots of confidential stuff. I've now distilled the systemctl command lines and put them in script.sh (attached tar file). The tar file also contains the unit files that are referenced in the script. Most of these unit files shouldn't be relevant for the bug, however.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.