What's new
By:

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Scribe scribe - syslog-ng and logrotate installer

I force downloaded v0.10_2 and now this is shown:
Code: 
 checking configuration files for necessary scribe hooks ...

          checking S01syslog-ng ... present.

         checking service-event ... present.

            checking post-mount ... present.

    checking logrotate cron job ... alive.

      checking syslog-ng daemon ... dead.


Edit: But update now works. :)

Edit: Still with the syslog-ng daemon ... dead issue though. :(
 
upload_2019-5-5_21-52-58.png

Can you add support for other routers which have both entware and asuswrt firmware installed, like Netgear R7000.
uname -o = GNU/Linux
or full
Linux router 2.6.36.4brcmarm #1 SMP PREEMPT Thu Apr 4 08:15:40 MSK 2019 armv7l GNU/Linux

edit:
as a workarround I have to change this value to
readonly merlin="GNU/Linux"
 
L&LD said:
checking syslog-ng daemon ... dead.
[/CODE]


Edit: Still with the syslog-ng daemon ... dead issue though. :(
Click to expand...

You may still have references to 'kernel' in your existing rules?

Run
Code: 
syslog-ng -Fevd
 
Martineau said:
You may still have references to 'kernel' in your existing rules?

Run
Code: 
syslog-ng -Fevd
Click to expand...

I don't have any rules.

Edit: using the scMerlin script to restart all Entware scripts 't' didn't work either: failed.
 
L&LD said:
I don't have any rules.

Edit: using the scMerlin script to restart all Entware scripts 't' didn't work either: failed.
Click to expand...

So '/opt/etc/syslog-ng.d' is empty?

Did you run the diagnostic command?
 
L&LD said:
I force downloaded v0.10_2 and now this is shown:
Code: 
 checking configuration files for necessary scribe hooks ...

          checking S01syslog-ng ... present.

         checking service-event ... present.

            checking post-mount ... present.

    checking logrotate cron job ... alive.

      checking syslog-ng daemon ... dead.


Edit: But update now works. :)

Edit: Still with the syslog-ng daemon ... dead issue though. :(
Click to expand...
Try "scribe config" and see if it throws an error at you.
 
Me too, I whitelisted both "codeload.github.com" and "raw.githubusercontent.com" and still blocked.
Code: 
 scribe GitHub repository is unavailable!  -- Aborting.
         scribe installed version: v0.10_1 
            scribe GitHub version: 
[: bad number
 No new version available. (GitHub version[: bad number
 LESS THAN local version)

Running "syslog-ng -Fevd" worked fine, everything clean, I use this often!

@L&LD I'll upload my filter files when we get this solved, most of them are installed automagically when you install or update scribe, just say yes when it asks if "Do you want to update syslog-ng and logrotate example files? [y|n]"

cmkelley said:
Try "scribe config" and see if it throws an error at you.
Click to expand...
That works here, here is the end of the long output.
Code: 
syslog-ng syntax check ... okay! 
         Checking S01syslog-ng ... present. 
        Checking service-event ... present.
 
Martineau said:
So '/opt/etc/syslog-ng.d' is empty?

Did you run the diagnostic command?
Click to expand...

That directory is not empty. Must be the default install?

Which diagnostic command?


cmkelley said:
Try "scribe config" and see if it throws an error at you.
Click to expand...

Does this command seem to show me the source script file? I don't see any obvious errors.
 
I uninstalled scribe and it asked to reboot the router, which I did. I just re-installed it again and am running the syslog-ng -Fevd command (seems to be taking a long time).

I CTRL-C the syslog-ng -Fevd command and ran scribe status instead. All are present and alive. :)
 
Butterfly Bones said:
Me too, I whitelisted both "codeload.github.com" and "raw.githubusercontent.com" and still blocked.
Code: 
 scribe GitHub repository is unavailable!  -- Aborting.
         scribe installed version: v0.10_1
            scribe GitHub version:
[: bad number
 No new version available. (GitHub version[: bad number
 LESS THAN local version)

Running "syslog-ng -Fevd" worked fine, everything clean, I use this often!

@L&LD I'll upload my filter files when we get this solved, most of them are installed automagically when you install or update scribe, just say yes when it asks if "Do you want to update syslog-ng and logrotate example files? [y|n]"


That works here, here is the end of the long output.
Code: 
syslog-ng syntax check ... okay!
         Checking S01syslog-ng ... present.
        Checking service-event ... present.
Click to expand...
Did you remember to use "4. Process all lists" in Diversion after editing the whitelist?
 
Butterfly Bones said:
Me too, I whitelisted both "codeload.github.com" and "raw.githubusercontent.com" and still blocked.
Code: 
 scribe GitHub repository is unavailable!  -- Aborting.
         scribe installed version: v0.10_1
            scribe GitHub version:
[: bad number
 No new version available. (GitHub version[: bad number
 LESS THAN local version)

Running "syslog-ng -Fevd" worked fine, everything clean, I use this often!

@L&LD I'll upload my filter files when we get this solved, most of them are installed automagically when you install or update scribe, just say yes when it asks if "Do you want to update syslog-ng and logrotate example files? [y|n]"


That works here, here is the end of the long output.
Code: 
syslog-ng syntax check ... okay!
         Checking S01syslog-ng ... present.
        Checking service-event ... present.
Click to expand...

Butterfly Bones, I seem to be on v0.10_2 stable with everything working now and I did say 'y' to that question. The logs in /opt/var/log/ are the same as I had before, not what you have. :)
 
L&LD said:
Butterfly Bones, I seem to be on v0.10_2 stable with everything working now and I did say 'y' to that question. The logs in /opt/var/log/ are the same as I had before, not what you have. :)
Click to expand...
Crap. It's a logic error because I changed the way it stored version numbers. I _THOUGHT_ I had tested it out and it was okay.

However it doesn't die as you found, so just answering yes to updating the scribe script.
 
I tried a force install and that worked, however I am getting this error that does not seem correct, what am I missing?
Code: 
 running logrotate ...
 check the output below for errors (blank = no errors)
==> /opt/tmp/logrotate.daily <==
error: Ignoring chkwan because it is writable by group or others.
error: Ignoring dropbear because it is writable by group or others.
error: Ignoring ethernet because it is writable by group or others.
error: Ignoring openvpn because it is writable by group or others.
error: Ignoring pixelsrv because it is writable by group or others.
error: Ignoring skynet because it is writable by group or others.
error: Ignoring vpnfailover because it is writable by group or others.
error: Ignoring wlceventd because it is writable by group or others.


/tmp/mnt/SNB/entware/etc/logrotate.d# ls -al
drwxr-xr-x    2 [redacted] root          4096 May  5 13:16 .
drwxr-xr-x   10 [redacted] root          4096 May  5 13:16 ..
-rw-------    1 [redacted] root           308 May  5 13:16 A00global
-rw-------    1 [redacted] root           123 Apr 12 12:21 chkwan
-rw-------    1 [redacted] root           124 May  5 13:16 crash
-rw-------    1 [redacted] root           125 Apr 26 06:53 divstats
-rw-------    1 [redacted] root           125 Apr 12 12:13 ethernet
-rw-------    1 [redacted] root           117 May  5 13:16 logrotate
-rw-------    1 [redacted] root           136 May  5 13:16 messages
-rw-------    1 [redacted] root           124 Apr 12 12:09 openvpn
-rw-------    1 [redacted] root           142 Apr 20 19:29 pixelsrv
-rw-------    1 [redacted] root           100 May  5 13:16 syslogng
-rw-------    1 [redacted] root           127 May  1 09:56 vpnfailover
-rw-------    1 [redacted] root           125 May  5 13:16 wlceventd
 
cmkelley said:
Crap. It's a logic error because I changed the way it stored version numbers. I _THOUGHT_ I had tested it out and it was okay.

However it doesn't die as you found, so just answering yes to updating the scribe script.
Click to expand...

I tried all ways (updated example files, updated script, and the script and example files), but no change in /opt/var/log. :(
 
Butterfly Bones said:
I tried a force install and that worked, however I am getting this error that does not seem correct, what am I missing?
Code: 
 running logrotate ...
 check the output below for errors (blank = no errors)
==> /opt/tmp/logrotate.daily <==
error: Ignoring chkwan because it is writable by group or others.
error: Ignoring dropbear because it is writable by group or others.
error: Ignoring ethernet because it is writable by group or others.
error: Ignoring openvpn because it is writable by group or others.
error: Ignoring pixelsrv because it is writable by group or others.
error: Ignoring skynet because it is writable by group or others.
error: Ignoring vpnfailover because it is writable by group or others.
error: Ignoring wlceventd because it is writable by group or others.


/tmp/mnt/SNB/entware/etc/logrotate.d# ls -al
drwxr-xr-x    2 [redacted] root          4096 May  5 13:16 .
drwxr-xr-x   10 [redacted] root          4096 May  5 13:16 ..
-rw-------    1 [redacted] root           308 May  5 13:16 A00global
-rw-------    1 [redacted] root           123 Apr 12 12:21 chkwan
-rw-------    1 [redacted] root           124 May  5 13:16 crash
-rw-------    1 [redacted] root           125 Apr 26 06:53 divstats
-rw-------    1 [redacted] root           125 Apr 12 12:13 ethernet
-rw-------    1 [redacted] root           117 May  5 13:16 logrotate
-rw-------    1 [redacted] root           136 May  5 13:16 messages
-rw-------    1 [redacted] root           124 Apr 12 12:09 openvpn
-rw-------    1 [redacted] root           142 Apr 20 19:29 pixelsrv
-rw-------    1 [redacted] root           100 May  5 13:16 syslogng
-rw-------    1 [redacted] root           127 May  1 09:56 vpnfailover
-rw-------    1 [redacted] root           125 May  5 13:16 wlceventd
Click to expand...
I'm at a loss here. They're clearly not writable by anyone but the user. That's all logrotate output. Try rebooting?
 
Ok, I found that that file (not directory) contains this error message, but the timestamp is Apr 18, 2019. Should I delete it and let it regenerate or will that cause more problems?
Code: 
error: Ignoring chkwan because it is writable by group or others.
error: Ignoring dropbear because it is writable by group or others.
error: Ignoring ethernet because it is writable by group or others.
error: Ignoring openvpn because it is writable by group or others.
error: Ignoring pixelsrv because it is writable by group or others.
error: Ignoring skynet because it is writable by group or others.
error: Ignoring vpnfailover because it is writable by group or others.
error: Ignoring wlceventd because it is writable by group or others.

edit - no longer using the "dropbear" file, I removed from syslog-ng.d and logrotate.d
 
Butterfly Bones said:
Ok, I found that that file (not directory) contains this error message, but the timestamp is Apr 18, 2019. Should I delete it and let it regenerate or will that cause more problems?
Code: 
error: Ignoring chkwan because it is writable by group or others.
error: Ignoring dropbear because it is writable by group or others.
error: Ignoring ethernet because it is writable by group or others.
error: Ignoring openvpn because it is writable by group or others.
error: Ignoring pixelsrv because it is writable by group or others.
error: Ignoring skynet because it is writable by group or others.
error: Ignoring vpnfailover because it is writable by group or others.
error: Ignoring wlceventd because it is writable by group or others.
Click to expand...
Yes, delete it. It will be automatically re-created.
 
You must log in or register to reply here.

Similar threads

Tarek Yag
Scribe [SOLVED] syslog-ng intermittent failure to shutdown which messes all logging
Replies
15
Views
992
Tarek Yag
Tarek Yag
SomeWhereOverTheRainBow
Scribe Issues with scribe.... Errors all over the place after restarting scribe!
Replies
8
Views
2K
SomeWhereOverTheRainBow
SomeWhereOverTheRainBow
S
Scribe Strange Issue with Scribe / Syslog-NG after Reboot
Replies
7
Views
1K
Ripshod
Ripshod
cmkelley
Scribe scribe 3.x_y - syslog-ng and logrotate installer
11 12 13
Replies
246
Views
23K
bibikalka
B
Davidncali001
Skynet Message on SKYNET I havent seen before
Replies
1
Views
433
Davidncali001
Davidncali001
Similar threads
Thread starter Title Forum Replies Date
Tarek Yag Scribe [SOLVED] syslog-ng intermittent failure to shutdown which messes all logging Asuswrt-Merlin AddOns 15
J AdGuardHome There are tons of dnsproxy error messages occuring on syslog. Asuswrt-Merlin AddOns 2
T Updated scMerlin to 2.5.5 - syslog stops at 'syslogd exiting' Asuswrt-Merlin AddOns 9

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Members online

Total: 701 (members: 29, guests: 672)
Back
Top