From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 733AE1393F1 for ; Wed, 16 Sep 2015 19:42:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FD6FE0839; Wed, 16 Sep 2015 19:42:20 +0000 (UTC) Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com [209.85.192.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0CAD821C014 for ; Wed, 16 Sep 2015 19:42:18 +0000 (UTC) Received: by qgev79 with SMTP id v79so180882559qge.0 for ; Wed, 16 Sep 2015 12:42:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=/USZdlI8/XkFAZgqU4AGArc9YV10wbfvd6ReqV8I+js=; b=SY1u1o+xR2G1UclqgZ3EOE+V+5V5yR0LMkjonkLmD7mHuywOTLu+KmgSLSPWli1f4c h21sghwnDecRgzEj0KlqmwxD9S/lolrZg54Gm6+WlmGPbSi2abcEnWVa1IXnIa/3LCzz 4RKDf6fGvw1RXoAf9a2txC+sU43Os90MGyjW7MTjQfJ6PFjiVbYkEfcKodsZnpOX3tnu 3F0i3LcMR+OoE8E7V9iMbL3HgfCVMsqblxGH5HfeRM3hdf2EI6lRQpO4xxUnSPpH8VBK SBjK10rT8pjQvuXfJmpACEWoU983uxDDm5EJ2PvhL+Mc44oU0okC1mkSJMpzvWlfXkHJ 3D8Q== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.140.235.142 with SMTP id g136mr47576977qhc.18.1442432537847; Wed, 16 Sep 2015 12:42:17 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.140.38.106 with HTTP; Wed, 16 Sep 2015 12:42:17 -0700 (PDT) In-Reply-To: <55F99EE4.6000902@gmail.com> References: <55F99EE4.6000902@gmail.com> Date: Wed, 16 Sep 2015 15:42:17 -0400 X-Google-Sender-Auth: qHi5AxJOnWj9idrLwLFFZDLzYB4 Message-ID: Subject: Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor" From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: d9c3c2db-b5d3-447d-a005-30a643a9cdfb X-Archives-Hash: 3b6b06fe9efd29fc539c52ecfc50a0a4 On Wed, Sep 16, 2015 at 12:55 PM, Alan McKinnon wrote: > > It has something to do with systemd's log thingy. > > The error only appears in one place in the syslog-ng source, > in modules/systemd-journal/journal-reader.c: > > static inline gboolean > __seek_to_saved_state(JournalReader *self) > { > JournalReaderState *state = > persist_state_map_entry(self->persist_state, self->persist_handle); > gint rc = journald_seek_cursor(self->journal, state->cursor); > persist_state_unmap_entry(self->persist_state, self->persist_handle); > if (rc != 0) > { > msg_warning("Failed to seek to the cursor", > evt_tag_str("cursor", state->cursor), > evt_tag_errno("error", errno), > NULL); > return __seek_to_head(self); > } > journald_next(self->journal); > return TRUE; > } > The other posts are getting at the solution - disable journal support if you're not actually using systemd. However, does syslog-ng actually READ logs? My understanding is that journal cursors are used to read logs, not to write them, and I associate syslog-ng more with writing logs. The concept is that when you query the journal every record gets returned with a cursor, which is just a guid of some sort. Then you can run a later query and pass the last cursor you saw back and just get a list of new records since the last one you read. The use case is for log monitors and such so that they can periodically poll the log without having to read the entire thing from the beginning each time. -- Rich