Scribe scribe 3.x_y - syslog-ng and logrotate installer

[SomeWhereOverTheRainBow]

@Martinski's always on top of things — more things than you realize!

oh no, i realize quite a lot of @Martinski exploits. He is a Legendary! Especially in these tough coding times!

 

[Davidncali001]

in my logs I see this popping up a couple times a day. I tried looking it up to see if I can fix it but came up with nothing.

Can anyone explain what this log means and how to resolve the problem?

logrotate: warning: state file/var/lib/logrotate.status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition...

 

[visortgw]

in my logs I see this popping up a couple times a day. I tried looking it up to see if I can fix it but came up with nothing.

Can anyone explain what this log means and how to resolve the problem?

logrotate: warning: state file/var/lib/logrotate.status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition...

Permissions on the lock file are wrong -- too wide open.

 

[Davidncali001]

Permissions on the lock file are wrong -- too wide open.

How do I fix it?

 

[visortgw]

How do I fix it?

chmod o-w <filename>

 

[Ripshod]

Permissions on the lock file are wrong -- too wide open.

Is it not a concern that, even on initial install, this file has the wrong permissions by default? I've had to fix the permissions on mine too, so it's not an individual event.

 

[bibikalka]

Had a strange issue. Scribe latest just stopped working on one of the days, while I was away. Then it just would not start - I tried manually several times. I had to re-install it, and it works now. Not the first time this happened to me.

Nothing in the log - but the issue occurred on Dec 24 08:09, since after that the filters stopped supressing kernel error messages. Anything else I should check?

Dec 24 04:07:46 Diversion: started separate Dnsmasq instance for ad-blocking exclusion on IP 192.168.1.16
Dec 24 04:07:46 Diversion: restarted Dnsmasq to apply settings
Dec 24 04:09:00 kernel: klogd: exiting
Dec 24 04:09:00 syslogd exiting
Dec 24 08:09:00 syslogd started: BusyBox v1.25.1
Dec 24 08:09:00 kernel: klogd started: BusyBox v1.25.1 (2024-11-17 14:18:51 EST)