Scribe Obsolete network sources in Scribe

  • ATTENTION! You'll notice a Prefix dropdown when you create a thread. If your post applies to one of the topics listed, please use that Prefix for your post. When browsing the thread list you can use the Prefix to filter the view.
  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

elorimer

Very Senior Member
The network sources and destinations (specifically, the "udp" definition) in Scribe are obsolete and should be replaced with newer network() definitions if you are passing messages over the network from one logging program to another, such as from a mesh node or NAS to the router, or from the router to a NAS.

In the syslog-ng.conf file Scribe installs, you will find this source definition for "net":
Code:
# if you only want to pass network messages through some syslog-ng filters, uncomment the source line below

# then add "soource(net);" to the log statement in any filter you want to pass network messages through

#source net { udp(ip(192.168.x.y) port(514)); };

This should be replaced with
Code:
source net {
    network(
        ip(192.168.x.y)
        port(514)
        transport(udp)
    );
};
Note that the default port for udp is already 514, so that line can be omitted. The default ip is 0.0.0.0, and that line can also be omitted.

Similarly, in the syslog-ng.conf file a remote log destination is created:
Code:
# uncomment these three lines to send udp log messages to local network
# must also uncomment "destination(log_server);" below for messages that
# are not otherwise filtered out to be sent to the remote log server
# destination log_server {
#    udp("192.168.x.y" port(514));
#};
This should be replaced with:
Code:
destination log-server{
    network(
        transport(udp)
        ip(192.168.x.y)
        port(514)
    );
};
Here, too, the port is the same as the default. A similar issue is in the A00remote file in /opt/share/syslog-ng/examples.
 

cmkelley

Very Senior Member
Ugh. Why do they keep changing stuff? If it's not broke, fix it until it is?

With luck, my availability should increase in the next few months, I'll try to sort some of these lingering issues.
 

Latest threads

Sign Up For SNBForums Daily Digest

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