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

Reply via email to