1 |
On 16/09/2015 20:52, Helmut Jarausch wrote: |
2 |
> On 09/16/2015 06:55:00 PM, Alan McKinnon wrote: |
3 |
>> On 16/09/2015 17:57, Helmut Jarausch wrote: |
4 |
>>> I have syslog-ng-3.7.1 installed here. |
5 |
>>> Syslog-ng fails to start with the message: |
6 |
>>> Failed to seek to the Cursor cursor='', error='Success (0)' |
7 |
>>> |
8 |
>>> Does anybody know what's happening? |
9 |
>>> |
10 |
>>> Many thanks for a hint, |
11 |
>>> Helmut |
12 |
>>> |
13 |
>>> |
14 |
>> |
15 |
>> |
16 |
>> It has something to do with systemd's log thingy. |
17 |
>> |
18 |
>> The error only appears in one place in the syslog-ng source, |
19 |
>> in modules/systemd-journal/journal-reader.c: |
20 |
>> |
21 |
>> static inline gboolean |
22 |
>> __seek_to_saved_state(JournalReader *self) |
23 |
>> { |
24 |
>> JournalReaderState *state = |
25 |
>> persist_state_map_entry(self->persist_state, self->persist_handle); |
26 |
>> gint rc = journald_seek_cursor(self->journal, state->cursor); |
27 |
>> persist_state_unmap_entry(self->persist_state, |
28 |
>> self->persist_handle); |
29 |
>> if (rc != 0) |
30 |
>> { |
31 |
>> msg_warning("Failed to seek to the cursor", |
32 |
>> evt_tag_str("cursor", state->cursor), |
33 |
>> evt_tag_errno("error", errno), |
34 |
>> NULL); |
35 |
>> return __seek_to_head(self); |
36 |
>> } |
37 |
>> journald_next(self->journal); |
38 |
>> return TRUE; |
39 |
>> } |
40 |
>> |
41 |
>> |
42 |
>> First step would appear to be to check systemd's built-in log thingy |
43 |
>> |
44 |
> |
45 |
> Thanks Alan, |
46 |
> |
47 |
> but how to do that. I have systemd installed here but I haven't ever used it since I'm using openrc. |
48 |
> So, what can I do? |
49 |
|
50 |
Well you are one better than me. |
51 |
I _don't_ have systemd installed here but I haven't ever used it since |
52 |
I'm using openrc :-) |
53 |
|
54 |
I haven't seen Canek for a few days, hopefully he'll drop by and help |
55 |
you out - he's usually the one with the most useful systemd answers |
56 |
|
57 |
-- |
58 |
Alan McKinnon |
59 |
alan.mckinnon@×××××.com |