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 7C8E71393F1 for ; Thu, 17 Sep 2015 10:26:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 66C0A21C04C; Thu, 17 Sep 2015 10:26:22 +0000 (UTC) Received: from mailrelay103.isp.belgacom.be (mailrelay103.isp.belgacom.be [195.238.20.130]) by pigeon.gentoo.org (Postfix) with ESMTP id 2123621C005 for ; Thu, 17 Sep 2015 10:26:20 +0000 (UTC) X-Belgacom-Dynamic: yes X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.1 cv=gx4LFt9C7U8MVtlopYu6y61Gbp9nqOyhneTyg/i0HKM= c=1 sm=2 a=W_qYiKNrdsQnkQLBnJ0A:9 a=CjuIK1q_8ugA:10 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2BsBgColPpV/2inQ1degyPEKYJWAoE/PRABAQEBAQEBgQqEJAEBBCcTHDMLGC4QKR6ISwG8aI13LItwhFo6F4QVBYcxhnqEDoMoqB04K4IRHIFWPIpdAQEB Received: from 104.167-67-87.adsl-dyn.isp.belgacom.be (HELO numa-be.localdomain) ([87.67.167.104]) by relay.skynet.be with ESMTP; 17 Sep 2015 12:26:20 +0200 Received: from numa-be (localhost [127.0.0.1]) by numa-be.localdomain (Postfix) with ESMTP id D6B0F9C12B1 for ; Thu, 17 Sep 2015 12:26:19 +0200 (CEST) Date: Thu, 17 Sep 2015 12:26:19 +0200 From: Helmut Jarausch Subject: Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor" To: gentoo-user@lists.gentoo.org References: In-Reply-To: (from frodriguez.developer@outlook.com on Wed Sep 16 21:19:58 2015) X-Mailer: Balsa 2.5.2-3-g00031a6 Message-Id: <9drqqGyc66TA0/eP80FpSe@5/o9zF5Yg111g+bxB3fvM> 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-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 96a8b7e6-228c-49fe-8d15-8637d1ed92bb X-Archives-Hash: 987334e4b596949aba48763c81325ca1 On 09/16/2015 09:19:58 PM, Fernando Rodriguez wrote: > 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=3D'', error=3D'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 =3D > > > > persist_state_map_entry(self->persist_state, > self->persist_handle); > > > > gint rc =3D journald_seek_cursor(self->journal, state->cursor); > > > > persist_state_unmap_entry(self->persist_state, > > > > self->persist_handle); > > > > if (rc !=3D 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. >=20 > 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? >=20 Many thanks, Fernando,=20 the systemd use-flag of syslog-ng was the culprit. (no, I don't use a systemd profile) Helmut. =