Give me a few minutes. Just drove from Upstate NY to NH to return my in-laws to their home.Interesting. What's the contents of /jffs/addons/scribe.d/config ??
Interesting. What's the contents of /jffs/addons/scribe.d/config ??
# cat /jffs/addons/scribe.d/config
SYSLOG_LOC=/jffs/syslog.log
I thought we had it there. Turns out it's a gamma.I know less than @cmkelley about github, but I think this will get you there. I spent 12 seconds googling for it:
Code:https://github.com/cynicastic/scribe/tree/4a72b3275d7ab6ae8328576c70f34f5c534feb5e
@Ripshod Blowing up at someone because you are annoyed, then telling them to not take it personally may make you feel ok, but that doesn't make it right.So, let me check I got this right. I was running 2.4.4 and it was fine. Saw this update to 3.0.0 so I did the update but it broke my setup. I deleted everything and reinstalled and still had the same problem. Was advised here in this thread to uninstall and install it back - wouldn't install. I ask for help and I'm told to go elsewhere.
Have I missed anything?
Thanks for the blow-off!
At worst copy and paste it into a new file.No SSL Cert so it won't download
Thanks. At least that part is working correctly, lol.Code:# cat /jffs/addons/scribe.d/config SYSLOG_LOC=/jffs/syslog.log
okay, well there's one horribly embarrassing mistake of this, I totally munged the location of the scribe config file in rc.func.syslog-ng. I mean horribly, I have no idea what possessed me to put 'scribe_conf="/opt/jffs/addons/scribe/config"' in there. Not only is /jffs at root, not in /opt, but the subdirectory for the config file is scribe.d, not just scribe. Wow. I don't know how many times I must have seen that and my brain went "this is fine." Really proving my point, "this is why we don't do things late at night."Thanks. At least that part is working correctly, lol.
Okay, @visortgw, please have a go at it. Same as before, copy the /tmp/scribelog file each time. This time though, please also check 'ls -al /jffs/syslog*' between running S01syslog-ng restart and scribe restart. I'm hopeful, but not positive, lol.okay, well there's one horribly embarrassing mistake of this, I totally munged the location of the scribe config file in rc.func.syslog-ng. I mean horribly, I have no idea what possessed me to put 'scribe_conf="/opt/jffs/addons/scribe/config"' in there. Not only is /jffs at root, not in /opt, but the subdirectory for the config file is scribe.d, not just scribe. Wow. I don't know how many times I must have seen that and my brain went "this is fine." Really proving my point, "this is why we don't do things late at night."
ANYWAYS, congrats on making the drive back safe. I was lucky enough one year to go on a business trip to the Lake Seneca area in early October and really enjoyed the multi-colored leaves as we drove from Syracuse - the leaves don't do that here, lol.
Lemme look a little harder for more fat finger issues and I'll post another gamma for you. I'll post here when I do.
Okay, @visortgw, please have a go at it. Same as before, copy the /tmp/scribelog file each time. This time though, please also check 'ls -al /jffs/syslog*' between running S01syslog-ng restart and scribe restart. I'm hopeful, but not positive, lol.
# cd /opt/etc/init.d/
# ./S01syslog-ng restart
Shutting down syslog-ng... done.
Starting syslog-ng... done.
# cat /tmp/scribelog
scribe_conf = /opt/jffs/addons/scribe/config
optmsg = /opt/var/log/messages
jffslog = /jffs/syslog.log
tmplog = /tmp/syslog.log
isjffs = false
syslog_loc = /tmp/syslog.log
optmsg is NOT a link
syslog_loc is a link
syslog_loc is a link
jffslog is NOT a directory
tmplog is a link
jffslog is a directory
tmplog is a link
# ls -al /jffs/syslog*
/jffs/syslog.log:
drwxrwxrwx 2 TheS1R root 160 Apr 27 22:26 .
drwxr-xr-x 17 TheS1R root 1992 Apr 27 22:26 ..
/jffs/syslog.log-1:
drwxrwxrwx 2 TheS1R root 160 Apr 27 22:26 .
drwxr-xr-x 17 TheS1R root 1992 Apr 27 22:26 ..
# scribe restart
_
_ ( )
___ ___ _ __ (_)| |_ __
/',__) /'___)( '__)| || '_`\ /'__`\
\__, \( (___ | | | || |_) )( ___/
(____/`\____)(_) (_)(_,__/'`\____)
syslog-ng and logrotate installation
v3.0_4 (gamma) Coded by cmkelley
stopping syslog-ng ... Checking syslog-ng... alive.
Shutting down syslog-ng... done.
starting system klogd and syslogd ...
Done.
syslog-ng will be started at next reboot; you
may type 'scribe restart' at shell prompt, or
select rs from scribe menu to restart syslog-ng
syslog-ng NOT running! Starting ...
Starting syslog-ng... done.
Restarting uiScribe ...Mounting WebUI page for uiScribe
Mounted uiScribe WebUI page as Main_LogStatus_Content.asp
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 ... updated.
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: v3.0_4 (gamma)
scribe GitHub version: v3.0_4 (gamma)
scribe is up to date!
# cat /tmp/scribelog
scribe_conf = /opt/jffs/addons/scribe/config
optmsg = /opt/var/log/messages
jffslog = /jffs/syslog.log
tmplog = /tmp/syslog.log
isjffs = true
syslog_loc = /jffs/syslog.log
optmsg is a link
syslog_loc is NOT a link
syslog_loc is a link
jffslog is NOT a directory
tmplog is NOT a link
jffslog is NOT a directory
tmplog is a link
# ls -al /jffs/syslog*
lrwxrwxrwx 1 TheS1R root 21 Apr 27 22:32 /jffs/syslog.log -> /opt/var/log/messages
-rw-rw-rw- 1 TheS1R root 24 Apr 27 22:32 /jffs/syslog.log-1
Okay, that's weird, the /opt/etc/init.d/S01syslog-ng file didn't update ... I don't get it.Code:# cd /opt/etc/init.d/ # ./S01syslog-ng restart Shutting down syslog-ng... done. Starting syslog-ng... done. # cat /tmp/scribelog scribe_conf = /opt/jffs/addons/scribe/config optmsg = /opt/var/log/messages jffslog = /jffs/syslog.log tmplog = /tmp/syslog.log isjffs = false syslog_loc = /tmp/syslog.log optmsg is NOT a link syslog_loc is a link syslog_loc is a link jffslog is NOT a directory tmplog is a link jffslog is a directory tmplog is a link # ls -al /jffs/syslog* /jffs/syslog.log: drwxrwxrwx 2 TheS1R root 160 Apr 27 22:26 . drwxr-xr-x 17 TheS1R root 1992 Apr 27 22:26 .. /jffs/syslog.log-1: drwxrwxrwx 2 TheS1R root 160 Apr 27 22:26 . drwxr-xr-x 17 TheS1R root 1992 Apr 27 22:26 ..
Code:# scribe restart _ _ ( ) ___ ___ _ __ (_)| |_ __ /',__) /'___)( '__)| || '_`\ /'__`\ \__, \( (___ | | | || |_) )( ___/ (____/`\____)(_) (_)(_,__/'`\____) syslog-ng and logrotate installation v3.0_4 (gamma) Coded by cmkelley stopping syslog-ng ... Checking syslog-ng... alive. Shutting down syslog-ng... done. starting system klogd and syslogd ... Done. syslog-ng will be started at next reboot; you may type 'scribe restart' at shell prompt, or select rs from scribe menu to restart syslog-ng syslog-ng NOT running! Starting ... Starting syslog-ng... done. Restarting uiScribe ...Mounting WebUI page for uiScribe Mounted uiScribe WebUI page as Main_LogStatus_Content.asp 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 ... updated. 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: v3.0_4 (gamma) scribe GitHub version: v3.0_4 (gamma) scribe is up to date! # cat /tmp/scribelog scribe_conf = /opt/jffs/addons/scribe/config optmsg = /opt/var/log/messages jffslog = /jffs/syslog.log tmplog = /tmp/syslog.log isjffs = true syslog_loc = /jffs/syslog.log optmsg is a link syslog_loc is NOT a link syslog_loc is a link jffslog is NOT a directory tmplog is NOT a link jffslog is NOT a directory tmplog is a link # ls -al /jffs/syslog* lrwxrwxrwx 1 TheS1R root 21 Apr 27 22:32 /jffs/syslog.log -> /opt/var/log/messages -rw-rw-rw- 1 TheS1R root 24 Apr 27 22:32 /jffs/syslog.log-1
What version should I be running? scribe (gamma) didn't detect new version.Okay, that's weird, the /opt/etc/init.d/S01syslog-ng file didn't update ... I don't get it.
Run scribe again and see if it's there now. I've heard sometimes it takes a while to propagate across github's servers. It should have said there is a minor update to 3.0.4.What version should I be running? scribe (gamma) didn't detect new version.
gamma or master?Run scribe again and see if it's there now. I've heard sometimes it takes a while to propagate across github's servers. It should have said there is a minor update to 3.0.4.
Nevermind, I see what happened. A change didn't push for some reason.Run scribe again and see if it's there now. I've heard sometimes it takes a while to propagate across github's servers. It should have said there is a minor update to 3.0.4.
gamma.gamma or master?
It was weird, github desktop wash showing everything pushed, but when I went to github on the web it wasn't there. So I've pushed another tiny change to scribe and now it's showing updated on the web (at least for me).Nevermind, I see what happened. A change didn't push for some reason.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!