Scribe scribe - syslog-ng and logrotate installer
- Thread starter cmkelley
- Start date
cmkelley
Very Senior Member
Sorry I didn't see this earlier, I've been super slammed with work and personal commitments, and even now I'm not actually at home. I'm sorry the scribe installation didn't work for you, I can try to help you out if you want to try again, although I must be honest, right now my plate is very full.
cmkelley
Very Senior Member
scribe v1.1_0 is up.
Note that when v2.0_0 is eventually released (with a menu), you will not be able to go directly from v1.0_0 to v2.0_0, you will need to be on v1.1_0 or later to upgrade to v2.0_0. Okay, technically you could, but it would involve editing a line in scribe.
There was a minor logic error in v1.0_0, when you upgrade to v1.1_0, after the upgrade it will print that v1.0_0 is still installed. Not to fear, it isn't, if you run "scribe status" you will see that v1.1_0 is installed. EDIT: This only occurs if you don't update the example files. If you do update them, it will show that v1.1_0 is installed.
Other than that, a bit of tweaking to the colors and wording, and the logic to support upgrading to v2.0_0 whenever I get around to adding the menu.
Note that when v2.0_0 is eventually released (with a menu), you will not be able to go directly from v1.0_0 to v2.0_0, you will need to be on v1.1_0 or later to upgrade to v2.0_0. Okay, technically you could, but it would involve editing a line in scribe.
There was a minor logic error in v1.0_0, when you upgrade to v1.1_0, after the upgrade it will print that v1.0_0 is still installed. Not to fear, it isn't, if you run "scribe status" you will see that v1.1_0 is installed. EDIT: This only occurs if you don't update the example files. If you do update them, it will show that v1.1_0 is installed.
Other than that, a bit of tweaking to the colors and wording, and the logic to support upgrading to v2.0_0 whenever I get around to adding the menu.
Last edited:
Butterfly Bones
Very Senior Member
I did not get the "v1.0_0 is still installed" doing the update just now. Not that I'm complaining.scribe v1.1_0 is up.
Note that when v2.0_0 is eventually released (with a menu), you will not be able to go directly from v1.0_0 to v2.0_0, you will need to be on v1.1_0 or later to upgrade to v2.0_0. Okay, technically you could, but it would involve editing a line in scribe.
There was a minor logic error in v1.0_0, when you upgrade to v1.1_0, after the upgrade it will print that v1.0_0 is still installed. Not to fear, it isn't, if you run "scribe status" you will see that v1.1_0 is installed.
Other than that, a bit of tweaking to the colors and wording, and the logic to support upgrading to v2.0_0 whenever I get around to adding the menu.
Code:
_ ( )
___ ___ _ __ (_)| |_ __
/',__) /'___)( '__)| || '_`\ /'__`\
\__, \( (___ | | | || |_) )( ___/
(____/`\____)(_) (_)(_,__/'`\____)
syslog-ng and logrotate installation
v1.0_0 (master) Coded by cynicastic
scribe installed version: v1.0_0 (master)
scribe GitHub version: v1.1_0 (master)
New version available!
Do you wish to upgrade [y|n] y
Do you want to update syslog-ng and logrotate example files? [y|n] y
fetching scribe from GitHub master branch ...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 122 0 122 0 0 266 0 --:--:-- --:--:-- --:--:-- 356
100 21727 0 21727 0 0 25088 0 --:--:-- --:--:-- --:--:-- 25088
.... %< snip ------------
setting up scribe ... done.
copying rc.func.syslog-ng to /opt/etc/init.d ... done.
scribe updated!
syslog-ng and logrotate example files updated!
checking configuration for necessary scribe hooks ...
checking S01syslog-ng ... present.
checking service-event ... present.
checking post-mount ... present.
checking logrotate cron job ... present.
checking syslog-ng daemon ...
syslog-ng syntax check ... okay!
checking syslog-ng daemon ... alive.
scribe installed version: v1.1_0 (master)
scribe GitHub version: v1.1_0 (master)
scribe is up to date!cmkelley
Very Senior Member
Oh, ooops, you'll only get the installed version still being v1.0_0 if you don't update the example files.I did not get the "v1.0_0 is still installed" doing the update just now. Not that I'm complaining.
Code:_ ( ) ___ ___ _ __ (_)| |_ __ /',__) /'___)( '__)| || '_`\ /'__`\ \__, \( (___ | | | || |_) )( ___/ (____/`\____)(_) (_)(_,__/'`\____) syslog-ng and logrotate installation v1.0_0 (master) Coded by cynicastic scribe installed version: v1.0_0 (master) scribe GitHub version: v1.1_0 (master) New version available! Do you wish to upgrade [y|n] y Do you want to update syslog-ng and logrotate example files? [y|n] y fetching scribe from GitHub master branch ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 122 0 122 0 0 266 0 --:--:-- --:--:-- --:--:-- 356 100 21727 0 21727 0 0 25088 0 --:--:-- --:--:-- --:--:-- 25088 .... %< snip ------------ setting up scribe ... done. copying rc.func.syslog-ng to /opt/etc/init.d ... done. scribe updated! syslog-ng and logrotate example files updated! checking configuration for necessary scribe hooks ... checking S01syslog-ng ... present. checking service-event ... present. checking post-mount ... present. checking logrotate cron job ... present. checking syslog-ng daemon ... syslog-ng syntax check ... okay! checking syslog-ng daemon ... alive. scribe installed version: v1.1_0 (master) scribe GitHub version: v1.1_0 (master) scribe is up to date!
I'll update the post.
Butterfly Bones
Very Senior Member
Ok, I can see that. I used to check against example files on GitHub, but now know I leave them alone, so unless you have changed something in them to improve handling, I never look at them, just trust to update.Oh, ooops, you'll only get the installed version still being v1.0_0 if you don't update the example files.
I can see where some who have not been knee deep in the syslog-ng mud before might be hesitant to update them.
L&LD
Part of the Furniture
Working on 384.12 Alpha 1.
https://www.snbforums.com/threads/384-12_alpha-builds-testing-all-variants.56639/#post-491571
https://www.snbforums.com/threads/384-12_alpha-builds-testing-all-variants.56639/#post-491571
Xentrk
Part of the Furniture
I migrated to 384.11_2 last night. I just tried to install scribe with the following curl error:
Code:
_
_ ( )
___ ___ _ __ (_)| |_ __
/',__) /'___)( '__)| || '_`\ /'__`\
\__, \( (___ | | | || |_) )( ___/
(____/`\____)(_) (_)(_,__/'`\____)
syslog-ng and logrotate installation
v1.1_0 (master) Coded by cynicastic
fetching scribe from GitHub master branch ...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 122 0 122 0 0 99 0 --:--:-- 0:00:01 --:--:-- 233
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
scribe GitHub repository is unavailable! -- Aborting.
Last edited:
Martineau
Part of the Furniture
Twiglets
Senior Member
I added a '-k' flag to the curl line (in the 'scribe' script) to ignore the verification part, BUT it had lots of problems running the script !!! (lots of dirs/files not found !!!???)
I ended up using git clone to copy the files/.zip down and manually set up the directories etc in /jffs/scripts/... and /opt/tmp/[scribe]|[scribe-master] .....
I ran the 'scribe' script multiple times and fixed the missing dirs/files until it was happy !!!
I was eventually able to run the 'scribe install' and 'scribe restart' to confirm all was working (after copying the 'right' files into /opt/tmp/[scribe]|[scribe-master]/[logrotate.share]|[syslog-ng.share])
Big Hint:
Make sure all the dirs/files are chmod'ed to '0755' otherwise the script is designed to ignore them.
I think this may possibly have been my problem !!!
Xentrk
Part of the Furniture
That was the fix! Thanks.
Xentrk
Part of the Furniture
I already have an existing syslog-ng installation. Appears this may have caused an issue with the installer script:
I then confirmed syslog-ng was no longer installed and reinstalled:
Running a check shows syslog-ng is dead.
Appears the installer is not handling the condition where an existing syslog-ng.conf file exists?
Code:
Downloading http://bin.entware.net/armv7sf-k2.6/Packages.gz
Updated list of available packages in /opt/var/opkg-lists/entware
syslog-ng already installed!
Forcing installation may overwrite modified configuration files!
Do you want to force re-installation of syslog-ng [y|n]? y
Checking syslog-ng... dead.
Removing package syslog-ng from root...
Not deleting modified conffile /opt/etc/syslog-ng.conf.
Installing syslog-ng (3.19.1-2) to root...
Downloading http://bin.entware.net/armv7sf-k2.6/syslog-ng_3.19.1-2_armv7-2.6.ipk
Configuring syslog-ng.
Collected errors:
* resolve_conffiles: Existing conffile /opt/etc/syslog-ng.conf is different from the conffile in the new package. The new conffile will be placed at /opt/etc/syslog-ng.conf-opkg.
syslog-ng version 3.19 or higher required!
Please update your Entware packages and run scribe install again.
Removing package syslog-ng from root...
Not deleting modified conffile /opt/etc/syslog-ng.conf.I then confirmed syslog-ng was no longer installed and reinstalled:
Code:
Xentrk@RT-AC88U-8248:/jffs/scripts# opkg list-installed | grep syslog
Xentrk@RT-AC88U-8248:/jffs/scripts# opkg install syslog-ng
Installing syslog-ng (3.19.1-2) to root...
Downloading http://bin.entware.net/armv7sf-k2.6/syslog-ng_3.19.1-2_armv7-2.6.ipk
Configuring syslog-ng.
Collected errors:
* resolve_conffiles: Existing conffile /opt/etc/syslog-ng.conf is different from the conffile in the new package. The new conffile will be placed at /opt/etc/syslog-ng.conf-opkg.Running a check shows syslog-ng is dead.
Code:
checking configuration for necessary scribe hooks ...
checking S01syslog-ng ... updated.
checking service-event ...sed: /jffs/scripts/service-event: No such file or directory
grep: /jffs/scripts/service-event: No such file or directory
updated.
checking post-mount ... updated.
checking logrotate cron job ... updated.
checking syslog-ng daemon ...
syslog-ng syntax check ...[2019-05-19T12:11:39.217635] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.19 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @version header at the top of the configuration file.;
okay!
checking syslog-ng daemon ... dead.
scribe installed version: v1.1_0 (master)
scribe GitHub version: v1.1_0 (master)
scribe is up to date!Search in this thread. There are some posts from @Butterfly Bones that are helpful.
Xentrk
Part of the Furniture
I renamed /opt/etc/syslog-ng.conf and got a little further in the install process:
Code:
Included from /opt/etc/syslog-ng.conf:
11 # source net function to get udp log messages from local network commented out
12 # destination log_server function added (commented out) to illustrate sending udp log messages to server on local network
13
14 @version: 3.19
15 @include "/opt/etc/syslog-ng.d/" # Put any customization files in this directory
16---->
16----> ^
17 options {
18 chain_hostnames(no); # Enable or disable the chained hostname format.
19 create_dirs(yes);
20 keep_hostname(yes); # Enable or disable hostname rewriting.
21 log_fifo_size(256); # The number of messages that the output queue can store.
syslog-ng documentation: https://www.balabit.com/support/documentation?product=syslog-ng-ose
contact: https://lists.balabit.hu/mailman/listinfo/syslog-ng
FAILED!
checking syslog-ng daemon ... dead.
scribe installed version: v1.1_0 (master)
scribe GitHub version: v1.1_0 (master)
scribe is up to date!
Code:
Xentrk@RT-AC88U-8248:/jffs/scripts# /opt/etc/init.d/S01syslog-ng start
Starting syslog-ng... done.
Xentrk@RT-AC88U-8248:/jffs/scripts# /opt/etc/init.d/S01syslog-ng check
Checking syslog-ng... dead.
Last edited:
Similar threads
Similar threads
Similar threads
-
Scribe Strange Issue with Scribe / Syslog-NG after Reboot
- Started by ScottW
- Replies: 7
-
Scribe Scribe nvram log_path - what should it be?
- Started by vibroverbus
- Replies: 4
-
Scribe Issues with scribe.... Errors all over the place after restarting scribe!
- Started by SomeWhereOverTheRainBow
- Replies: 8
-
Scribe [SOLVED] syslog-ng intermittent failure to shutdown which messes all logging
- Started by Tarek Yag
- Replies: 15
-
AdGuardHome There are tons of dnsproxy error messages occuring on syslog.
- Started by jklim
- Replies: 2
-
Updated scMerlin to 2.5.5 - syslog stops at 'syslogd exiting'
- Started by thecheapseats
- Replies: 9
Latest threads
-
-
Netgear EAX20 BTRM messages
- Started by makak
- Replies: 0
-
-
-
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!