1 |
On 1/15/21 4:30 PM, Michael wrote: |
2 |
> On Friday, 15 January 2021 15:23:34 GMT Peter Humphrey wrote: |
3 |
>> On Friday, 15 January 2021 15:08:15 GMT n952162 wrote: |
4 |
>>> On 1/15/21 10:24 AM, Michael wrote: |
5 |
>>>> On Friday, 15 January 2021 08:47:18 GMT n952162 wrote: |
6 |
>>>>> Hello, |
7 |
>>>>> |
8 |
>>>>> can anyone explain this? |
9 |
>>>>> |
10 |
>>>>> I noticed today (15. January) that the |
11 |
>>>>> /var/log/{messages,kern.log,etc.} |
12 |
>>>>> files on a box were last touched on 22. November. |
13 |
>>>>> |
14 |
>>>>> sysklogd was in the rc-open /started/ state and was running. |
15 |
>>>>> |
16 |
>>>>> The configuration file, /etc/syslog.conf matches completely that file |
17 |
>>>>> on |
18 |
>>>>> another machine of mine, where the logs are properly updated. |
19 |
>>>>> |
20 |
>>>>> /etc/syslog.d/ was empty on both machines. |
21 |
>>>>> |
22 |
>>>>> I sent the process a HUP signal, as follows |
23 |
>>>>> |
24 |
>>>>> sudo kill -HUP $(cat /var/run/syslogd.pid ) |
25 |
>>>>> |
26 |
>>>>> and all the log files were immediately updated and reporting. |
27 |
>>>>> |
28 |
>>>>> I rebooted my machine, and the log files are untouched, it is again |
29 |
>>>>> hibernating. |
30 |
>>>> Do you get something like this on your system? |
31 |
>>>> |
32 |
>>>> $ rc-update -s -v | grep syslog |
33 |
>>>> |
34 |
>>>> syslog-ng | default |
35 |
>>>> |
36 |
>>>> and, |
37 |
>>>> |
38 |
>>>> $ rc-service -v syslog-ng status |
39 |
>>>> |
40 |
>>>> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh |
41 |
>>>> /etc/init.d/ |
42 |
>>>> |
43 |
>>>> syslog-ng status |
44 |
>>>> |
45 |
>>>> * status: started |
46 |
>>> $ rc-service -v syslog-ng status |
47 |
>>> |
48 |
>>> * rc-service: service `syslog-ng' does not exist |
49 |
>>> |
50 |
>>> $ rc-service -v syslog status |
51 |
>>> |
52 |
>>> * rc-service: service `syslog' does not exist |
53 |
>>> |
54 |
>>> $ rc-service -v syslogd status |
55 |
>>> |
56 |
>>> * rc-service: service `syslogd' does not exist |
57 |
>>> |
58 |
>>> $ rc-service -v sysklogd status |
59 |
>>> |
60 |
>>> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh |
61 |
>>> |
62 |
>>> /etc/init.d/sysklogd status |
63 |
>>> |
64 |
>>> * status: started |
65 |
>>> |
66 |
>>> $ rc-update -s -v | grep syslog |
67 |
>>> |
68 |
>>> $ rc-update -s -v | grep sysklog |
69 |
>>> |
70 |
>>> sysklogd | default sysinit |
71 |
>>> |
72 |
>>> I ran that as a script on a machine where the logs are properly updated: |
73 |
>>> |
74 |
>>> 01~>bash -x /tmp/test |
75 |
>>> + rc-service -v syslog-ng status |
76 |
>>> |
77 |
>>> * rc-service: service `syslog-ng' does not exist |
78 |
>>> |
79 |
>>> + rc-service -v syslog status |
80 |
>>> |
81 |
>>> * rc-service: service `syslog' does not exist |
82 |
>>> |
83 |
>>> + rc-service -v syslogd status |
84 |
>>> |
85 |
>>> * rc-service: service `syslogd' does not exist |
86 |
>>> |
87 |
>>> + rc-service -v sysklogd status |
88 |
>>> |
89 |
>>> * Executing: /lib/rc/sh/openrc-run.sh /lib/rc/sh/openrc-run.sh |
90 |
>>> |
91 |
>>> /etc/init.d/sysklogd status |
92 |
>>> |
93 |
>>> * status: started |
94 |
>>> |
95 |
>>> + rc-update -s -v |
96 |
>>> + grep syslog |
97 |
>>> + rc-update -s -v |
98 |
>>> + grep sysklog |
99 |
>>> |
100 |
>>> sysklogd | default |
101 |
>> Substitute your syslog program's name for syslog-ng. Michael did say |
102 |
>> "something like." |
103 |
> Yes, quite, other log daemons are available. :-) |
104 |
> |
105 |
> It seems your PC on which sysklogd works as expected has its rc script |
106 |
> only on |
107 |
> 'default' runlevel, rather than default +sysinit. I don't know if |
108 |
> sysinit is |
109 |
> required. If you remove sysinit and restart sysklogd from a terminal |
110 |
> does it |
111 |
> spew out any errors? |
112 |
|
113 |
|
114 |
Oh, I missed that sysinit way out there on the left ;-) |
115 |
|
116 |
It looks like that was it, no errors after removing runlevel sysinit, |
117 |
and /var/log/messages has like the current time. |
118 |
|
119 |
Thanks, that was great! |