Billion UK Forum

billion_fan wrote: ↑Mon Sep 10, 2018 9:52 am I will be trying to debug the issue with a customer, I'll drop a update once we have more information

If it's possible, how do I setup the Configure Log to output to a Raspberry Pi? As it's (usually) always on to monitor the VDSL connection, if I can get it to host the system log, I could also use this to keep an eye on further reboots.

# remote syslog
module(load="imudp")
input(type="imudp" port="514")

# Replace timestamp with local time
template(name="other" type="list") {
    property(name="timegenerated" dateFormat="rfc3339")
    constant(value=" ")
    property(name="syslogtag")
    constant(value=" ")
    property(name="msg")
    property(name="msg" droplastlf="on" )
    constant(value="\n")
    }

template(name="other_file" type="string"
    string="/var/log/others/%HOSTNAME%.log")

if $fromhost-ip != '127.0.0.1' then {
    action (type="omfile" dynaFile="other_file" template="other")
    & stop
}

sudo systemctl restart rsyslog
sudo systemctl status rsyslog

davews wrote: ↑Wed Sep 12, 2018 7:15 am Thanks for the input. It stayed up nearly 2 days yesterday then rebooted. May well be related to line errors (the VDSL line itself seems rock solid) which may explain why it seemed stable on ADSL2+.
I will revert to the BT Hub 6 for the moment and monitor this thread to see if a cure comes.

Pete-B wrote: ↑Wed Sep 12, 2018 10:57 am Running 2.52.d10 on an 8800NL R2.
I have been sending logs in debugging mode to my Raspberry Pi for a while.
The log shows nothing unusual prior to a reboot and then normal messages during the boot process.
Not sure if this advances matters much but I can send copies of the log files if it would help.
Last reboot was yesterday.

Pete-B wrote: ↑Wed Sep 12, 2018 11:24 am I am on a Plusnet VDSL connection and also have access to a Plusnet ADSL2+ connection.
I have an old 8800NL R1 that is currently not being used.

gerdesj wrote: ↑Wed Sep 12, 2018 12:41 am

If it's possible, how do I setup the Configure Log to output to a Raspberry Pi? As it's (usually) always on to monitor the VDSL connection, if I can get it to host the system log, I could also use this to keep an eye on further reboots.

Now this is something I can do (I'm a Linux sysadmin).

Your Pi will probably be running rsyslog. Create a file called say /etc/rsyslog.d/others.conf (anything with .conf on the end will do):

Code: Select all

# remote syslog
module(load="imudp")
input(type="imudp" port="514")

# Replace timestamp with local time
template(name="other" type="list") {
    property(name="timegenerated" dateFormat="rfc3339")
    constant(value=" ")
    property(name="syslogtag")
    constant(value=" ")
    property(name="msg")
    property(name="msg" droplastlf="on" )
    constant(value="\n")
    }

template(name="other_file" type="string"
    string="/var/log/others/%HOSTNAME%.log")

if $fromhost-ip != '127.0.0.1' then {
    action (type="omfile" dynaFile="other_file" template="other")
    & stop
}

The above config will switch on a standard issue syslog listener on port 514/udp and will dump logs named after the sending system in /var/log/others/ You may have to create /var/log/others but it looks like rsyslogd on Pi runs as root so it can probably create the top level folder itself.

Code: Select all

sudo systemctl restart rsyslog
sudo systemctl status rsyslog

Finally, add /var/log/others to /etc/logrotate.d/rsyslog unless you like running out of disc space!

[Edit]: On the BiPac: Configuration -> System -> Configure Log. Enable, set "Debugging" on both and put the IP address of your Pi in. Port 514/udp is standard for syslog.