JGrana
Very Senior Member
I am away for a few days. I‘ll do some testing this Monday.
Thanks!
Thanks!
visortgw
Very Senior Member
@cmkelley Hope this shows you what you need. Let me know if you need anything else — I will be in and out today, but I will definitely get back to you.
Code:
_
_ ( )
___ ___ _ __ (_)| |_ __
/',__) /'___)( '__)| || '_`\ /'__`\
\__, \( (___ | | | || |_) )( ___/
(____/`\____)(_) (_)(_,__/'`\____)
syslog-ng and logrotate installation
v2.5_0 (gamma) Coded by cmkelley
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
s. Show scribe status
rl. Reload syslog-ng.conf
lr. Run logrotate now
rs. Restart syslog-ng
st. Stop syslog-ng & logrotate cron
u. Update scribe
uf. Update filters
su. scribe utilities
e. Exit scribe
is. Reinstall scribe
zs. Remove scribe
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
Please select an option: s
checking syslog-ng daemon ... alive.
checking system for necessary scribe hooks ...
checking S01syslog-ng ... present.
checking service-event ... present.
checking post-mount ... present.
checking unmount ... present.
checking logrotate cron job ... present.
checking directory links ... present.
checking syslog-ng configuration ...
syslog-ng.conf version check ... in sync. (3.38)
syslog-ng.conf syntax check ... okay!
scribe installed version: v2.5_0 (gamma)
scribe GitHub version: v2.5_0 (gamma)
scribe is up to date!
Press [Enter] to continue:
Code:
# pwd
/tmp
# ls -al syslog*
lrwxrwxrwx 1 TheS1R root 21 Apr 22 09:22 syslog.log -> /opt/var/log/messages
lrwxrwxrwx 1 TheS1R root 18 Apr 22 09:22 syslog.log-1 -> /jffs/syslog.log-1
# cat syslog.log
:
:
Apr 22 09:22:20 GT-AX6000-9980 uiScribe: Mounting WebUI page for uiScribe
Apr 22 09:22:20 GT-AX6000-9980 uiScribe: Mounted uiScribe WebUI page as Main_LogStatus_Content.asp
Apr 22 09:22:29 GT-AX6000-9980 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link DOWN.
Apr 22 09:22:29 GT-AX6000-9980 kernel: br0: port 2(eth2) entered disabled state
Apr 22 09:22:35 GT-AX6000-9980 kernel: eth2 (Int switch port: 1) (Logical Port: 1) (phyId: 2) Link Up at 100 mbps full duplex
Apr 22 09:22:35 GT-AX6000-9980 kernel: br0: port 2(eth2) entered blocking state
Apr 22 09:22:35 GT-AX6000-9980 kernel: br0: port 2(eth2) entered listening state
Apr 22 09:22:37 GT-AX6000-9980 kernel: br0: port 2(eth2) entered learning state
Apr 22 09:22:39 GT-AX6000-9980 kernel: br0: port 2(eth2) entered forwarding state
Apr 22 09:22:39 GT-AX6000-9980 kernel: br0: topology change detected, propagating
:
:
# cat syslog.log-1
### Top of Log File ###JT Strickland
Very Senior Member
Mine wasnb't working, so I forced an update, but still showing 2.4_4
I'm getting the following errror for syslog-ng cofiguration
I'm getting the following errror for syslog-ng cofiguration
Code:
Please select an option: s
checking syslog-ng daemon ... alive.
checking system for necessary scribe hooks ...
checking S01syslog-ng ... present.
checking service-event ... present.
checking post-mount ... present.
checking unmount ... present.
checking logrotate cron job ... present.
checking directory links ... present.
checking syslog-ng configuration ...
syslog-ng.conf version check ...Error opening plugin module; module='http', error='libssl.so.1.1: wrong ELF class: ELFCLASS32'
in sync. (3.38)
syslog-ng.conf syntax check ... okay!
scribe installed version: v2.4_4 (master)
scribe GitHub version: v2.4_4 (master)
scribe is up to date!
Press [Enter] to continue:visortgw
Very Senior Member
So... I had uninstalled scribe a couple of months back when I had issues on my GT-AX6000. This morning, I completed a clean install of v2.4_4, edited the script to designate "gamma", and updated to v2.5_0 (gamma).
JT Strickland
Very Senior Member
cmkelley
Very Senior Member
@JT Strickland
@visortgw
Only one more thing I'd like to see 'ls -al /jffs/syslog*'. /jffs/syslog.log should be a link to /opt/var/log/messages and /jffs/syslog.log-1 should be a small file.
Appreciate the help!
You have to change the code to look for the gamma branch as described in this post: https://www.snbforums.com/threads/scribe-2-5-0-testers-needed.84478/ ... but yes, the 'libssl.so.1.1' error is a separate issue from scribe or syslog-ng as you discovered.
@visortgw
Superb. Glad to hear you installed from scratch too, that part is working then.
Only one more thing I'd like to see 'ls -al /jffs/syslog*'. /jffs/syslog.log should be a link to /opt/var/log/messages and /jffs/syslog.log-1 should be a small file.
Appreciate the help!
Last edited:
visortgw
Very Senior Member
@JT Strickland
You have to change the code to look for the gamma branch as described in this post: https://www.snbforums.com/threads/scribe-2-5-0-testers-needed.84478/ ... but yes, the 'libssl.so.1.1' error is a separate issue from scribe or syslog-ng as you discovered.
@visortgw
Superb. Glad to hear you installed from scratch too, that part is working then.
Only one more thing I'd like to see 'ls -al /jffs/syslog*'. /jffs/syslog.log should be a link to /opt/var/log/messages and /jffs/syslog.log-1 should be a small file.
Appreciate the help!
Code:
# cd /jffs
# ls -al /jffs/syslog*
lrwxrwxrwx 1 TheS1R root 21 Apr 22 09:22 /jffs/syslog.log -> /opt/var/log/messages
-rw-rw-rw- 1 TheS1R root 24 Apr 22 13:00 /jffs/syslog.log-1cmkelley
Very Senior Member
visortgw
Very Senior Member
Yes, it is! Huge THANKS to you for taking the time to dust off the cobwebs from scribe!
cmkelley
Very Senior Member
You're welcome. And thanks for your patience.
As I've said before, my main purpose in writing scribe was actually to dive into shell scripting, and I've learned a ton along the way. I honestly had no altruistic intent of "helping people", lol. I specifically don't want donations for scribe because then I would feel a deeper sense of obligation than I already do*, and I want to be able to futz with this because I want to, not because I *have* to. Indeed, if this issue had come up in the middle of 2021, my answer may have had to be, "if you have one of those routers, sorry, you're out of luck or you have to fork it", because there was no way I had time then to devote to this.
For this latest issue with routers wanting to write to /jffs my desire to learn more awk drove me away from adamm's solution (even though it currently works perfectly) and actually get the log file location from the syslogd command string. In theory at least, if Asus changed their minds again and put syslog.log yet somewhere else, scribe should be able to handle that. I hope it never comes to testing that theory though.
So, while this is a more complex problem for scribe than other scripts, I did increase the complexity for myself a bit in the pursuit of learning.
* if you just HAVE to give money to someone for scribe, I would appreciate a donation to METAvivor.
Can we expect that Scribe 2.5.0 will soon become the main/official release rather than a gamma (test) release? No rush, just checking to see how long you expect it to take for it to be sufficiently tested/verified.You're welcome. And thanks for your patience.
As I've said before, my main purpose in writing scribe was actually to dive into shell scripting, and I've learned a ton along the way. I honestly had no altruistic intent of "helping people", lol. I specifically don't want donations for scribe because then I would feel a deeper sense of obligation than I already do*, and I want to be able to futz with this because I want to, not because I *have* to. Indeed, if this issue had come up in the middle of 2021, my answer may have had to be, "if you have one of those routers, sorry, you're out of luck or you have to fork it", because there was no way I had time then to devote to this.
For this latest issue with routers wanting to write to /jffs my desire to learn more awk drove me away from adamm's solution (even though it currently works perfectly) and actually get the log file location from the syslogd command string. In theory at least, if Asus changed their minds again and put syslog.log yet somewhere else, scribe should be able to handle that. I hope it never comes to testing that theory though.
So, while this is a more complex problem for scribe than other scripts, I did increase the complexity for myself a bit in the pursuit of learning.
* if you just HAVE to give money to someone for scribe, I would appreciate a donation to METAvivor.
cmkelley
Very Senior Member
Hopefully tomorrow evening. JGrana was out of town this weekend, and said he'd test it Monday. Since I don't have a router that puts syslog.log in /jffs, I'm a bit reluctant to just say "looks good from my house" and hope for the best. If JGrana gives it a thumbs up, then the gamma version that is up now will become the release, except it'll clear the screen before the menu comes up.
cmkelley
Very Senior Member
Decided to roll it all the way to 3.0_0. See announcement here: https://www.snbforums.com/threads/scribe-3-0_0-syslog-ng-and-logrotate-installer.84720/
If you participated the gamma test, you don't have to revert the branch name change in the code, just update scribe and it will go back to the master branch. Thought I could at least do that much for you.
If you participated the gamma test, you don't have to revert the branch name change in the code, just update scribe and it will go back to the master branch. Thought I could at least do that much for you.
Similar threads
Similar threads
Similar threads
-
Scribe Scribe nvram log_path - what should it be?
- Started by vibroverbus
- Replies: 4
-
Scribe Strange Issue with Scribe / Syslog-NG after Reboot
- Started by ScottW
- Replies: 7
-
Scribe Issues with scribe.... Errors all over the place after restarting scribe!- Started by SomeWhereOverTheRainBow
- Replies: 8