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 C35351393F1 for ; Wed, 16 Sep 2015 19:20:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A44E721C037; Wed, 16 Sep 2015 19:20:42 +0000 (UTC) Received: from BLU004-OMC1S32.hotmail.com (blu004-omc1s32.hotmail.com [65.55.116.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 89DBA21C01B for ; Wed, 16 Sep 2015 19:20:41 +0000 (UTC) Received: from BLU436-SMTP45 ([65.55.116.7]) by BLU004-OMC1S32.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Wed, 16 Sep 2015 12:20:41 -0700 X-TMN: [1FgQaktELIGnsJls+KdSBNWfIohBY4mb] X-Originating-Email: [frodriguez.developer@outlook.com] Message-ID: From: Fernando Rodriguez To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor" Date: Wed, 16 Sep 2015 15:19:58 -0400 User-Agent: KMail/4.14.8 (Linux/3.18.21; KDE/4.14.8; x86_64; ; ) In-Reply-To: References: 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 16 Sep 2015 19:20:40.0543 (UTC) FILETIME=[C64C8EF0:01D0F0B4] X-Archives-Salt: d2dccfd4-f10a-4fef-8b56-a2c8636ad0a5 X-Archives-Hash: 9252342eacc2b390d90c2f6ffa6e4471 On Wednesday, September 16, 2015 3:05:55 PM Fernando Rodriguez wrote: > On Wednesday, September 16, 2015 8:52:21 PM Helmut Jarausch wrote: > > On 09/16/2015 06:55:00 PM, Alan McKinnon wrote: > > > On 16/09/2015 17:57, Helmut Jarausch wrote: > > > > I have syslog-ng-3.7.1 installed here. > > > > Syslog-ng fails to start with the message: > > > > Failed to seek to the Cursor cursor='', error='Success (0)' > > > > > > > > Does anybody know what's happening? > > > > > > > > Many thanks for a hint, > > > > Helmut > > > > > > > > > > > > > > > > > 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; > > > } > > > > > > > > > First step would appear to be to check systemd's built-in log thingy > > > > > > > Thanks Alan, > > > > but how to do that. I have systemd installed here but I haven't ever used it > since I'm using openrc. > > So, what can I do? > > > > Thanks, > > Helmut > > > > > > Look for file named syslog-ng.persist somewhere in /var and delete it, then try > restarting syslog-ng. > > I also recommend you start playing with journalctl. I hated it for a while but > mostly because I didn't knew how to use it. Now I love it and got rid of > syslog-ng. Ops, I missed the part about not using systemd. If deleting that file doesn't fix it check if you have the systemd use flag enabled for syslog-ng and disable it. Are you using a systemd profile? -- Fernando Rodriguez