Description of problem: I've been testing some Ansible playbooks, running lineinfile tasks against the local host. All had been working well, but suddenly I was no longer able to execute the playbooks due to a "Connection refused" error. System logs showed Mar 21 11:32:23 peterj systemd[1]: systemd-journald.service: main process exited, code=dumped, status=6/ABRT Restarting the iptables service fixes the problem temporarily, but I often can't run the playbook to completion because systemd-journald will crash during execution. Version-Release number of selected component: systemd-197-1.fc18.2 Additional info: backtrace_rating: 4 cmdline: /usr/lib/systemd/systemd-journald crash_function: log_assert executable: /usr/lib/systemd/systemd-journald kernel: 3.7.9-205.fc18.x86_64 uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #2 log_assert at src/shared/log.c:702 #3 log_assert_failed at src/shared/log.c:707 #4 dispatch_message_real at src/journal/journald-server.c:538 #5 server_dispatch_message at src/journal/journald-server.c:795 #6 server_process_native_message at src/journal/journald-native.c:260 #7 process_event at src/journal/journald-server.c:1159
Created attachment 713940 [details] File: backtrace
Created attachment 713941 [details] File: cgroup
Created attachment 713942 [details] File: core_backtrace
Created attachment 713943 [details] File: dso_list
Created attachment 713944 [details] File: environ
Created attachment 713945 [details] File: limits
Created attachment 713946 [details] File: maps
Created attachment 713947 [details] File: open_fds
Created attachment 713948 [details] File: proc_pid_status
Created attachment 713949 [details] File: smolt_data
Created attachment 713950 [details] File: var_log_messages
This is the assertion that failed: assert(n + N_IOVEC_META_FIELDS <= m); n was 20 N_IOVEC_META_FIELDS is 17 m was 36
It also happened to me while testing some Ansible playbooks.
It would be nice if you could provide more exact steps to reproduce. I am not familiar with "Ansible playbooks", so going into details would be helpful.
Created attachment 736321 [details] Ansible playbook for crashing journal The playbook was tested with ansible-1.2-0.git201304142331.fc18.noarch and systemd-201-2.fc18.2.x86_64. It installs cobbler & koan and configures /etc/cobbler/settings (nothing is really changed). It uses the local connection, so there's no need to start the SSH server. To install ansible-1.2-0.git201304142331.fc18.noarch: % cd /tmp % git clone git://github.com/ansible/ansible.git % cd ansible % git checkout -b bug-924359 84fb92dac6bfd70b10fedf3f5a8758a684aa9dcb % make rpm # some packages might be required for this # yum install /tmp/ansible/rpm-build/ansible-1.2-0.git201304142331.fc18.noarch.rpm To run the playbook: % cd /tmp % tar xJf /tmp/bug-924359-ansible-playbook.tar.xz # cd /tmp/bug-924359-ansible-playbook # ansible-playbook -i hosts site.yml The journal should crash.
P.S. I'm sorry that I could make the playbook simpler, but the simpler versions didn't crash the journal.
Created attachment 736429 [details] Python script that crashes the journal The script for crashing the journal was tested with: systemd-201-2.fc18.2.x86_64.rpm systemd-libs-201-2.fc18.2.i686.rpm systemd-libs-201-2.fc18.2.x86_64.rpm systemd-python-201-2.fc18.2.x86_64.rpm systemd-sysv-201-2.fc18.2.x86_64.rpm python-2.7.3-13.fc18.x86_64.rpm
Thank you for the reproducer. I fixed the bug upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=f6422def2c10aa0dea1b872d2f187853e61bd015
systemd-201-2.fc18.5 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5
Package systemd-201-2.fc18.5: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.5 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6
Package systemd-201-2.fc18.6: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-201-2.fc18.6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 then log in and leave karma (feedback).
systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.