Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1177184 - journald: Assertion 'n + 20 + (object_pid ? 11 : 0) <= m' failed at ../src/journal/journald-server.c:575, function dispatch_message_real(). Aborting
Summary: journald: Assertion 'n + 20 + (object_pid ? 11 : 0) <= m' failed at ../src/jo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1176007 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-24 22:12 UTC by Luke Macken
Modified: 2016-09-20 02:46 UTC (History)
10 users (show)

Fixed In Version: systemd-216-16.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-21 23:02:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Luke Macken 2014-12-24 22:12:06 UTC
Description of problem:

I'm hitting journald assertions using the Python API.


Version-Release number of selected component (if applicable):
systemd-216-13.fc21.x86_64

How reproducible:
always

Steps to Reproduce:

#!/usr/bin/python
# coding: utf-8

from systemd import journal

msg = "ansible-<stdin> Invoked with src=None directory_mode=None force=None remote_src=None dest=/var/tmp/foo selevel=None seuser=None serole=None replace=bar content=NOT_LOGGING_PARAMETER setype=None delimiter=None mode=None regexp=foo owner=None follow=False validate=None backup=False group=None"
args = {'SRC': 'None', 'GROUP': 'None', 'DIRECTORY_MODE': 'None', 'FORCE': 'None', 'REMOTE_SRC': 'None', 'DEST': '/var/tmp/foo', 'SELEVEL': 'None', 'SEUSER': 'None', 'SETYPE': 'None', 'MODULE': '<stdin>', 'REPLACE': 'bar', 'CONTENT': 'NOT_LOGGING_PARAMETER', 'SEROLE': 'None', 'DELIMITER': 'None', 'MODE': 'None', 'FOLLOW': 'False', 'OWNER': 'None', 'REGEXP': 'foo', 'VALIDATE': 'None', 'BACKUP': 'False'}

# This works.
journal.send(msg , **args)

# This however…
# From https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/basic.py#L1106
journal_args = ['MESSAGE=' + msg]
for k, v in args.items():
    journal_args.append(k + "=" + v)
journal.sendv(*journal_args)


Actual results:

systemd-journal[27213]: Permanent journal is using 3.0G (max allowed 4.0G, trying to leave 4.0G free of 38.7G available → current limit 4.0G).
systemd-journald[27141]: Assertion 'n + 20 + (object_pid ? 11 : 0) <= m' failed at ../src/journal/journald-server.c:575, function dispatch_message_real(). Aborting.
systemd-journal[27213]: Journal started


Additional info:

I hit this issue using ansible, and filed a pull request upstream to switch to using `send` instead of `sendv` on `systemd.journal` https://github.com/ansible/ansible/pull/9887

Comment 1 Lennart Poettering 2015-01-05 00:35:57 UTC
*** Bug 1176007 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Update System 2015-01-19 19:23:26 UTC
systemd-216-16.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/systemd-216-16.fc21

Comment 3 Fedora Update System 2015-01-20 21:02:30 UTC
Package systemd-216-16.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-216-16.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-0916/systemd-216-16.fc21
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2015-01-21 23:02:48 UTC
systemd-216-16.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.