Recent content by elorimer

Interesting. Did you try the native Loki() destination and template?

The entware version of syslog-ng is at 4.7; the current release is at 4.10 and 4.11 is around the corner. Because the reboot.LOG only needs to be read on reboot, I experimented with follow-freq() and set it at 9000 seconds. Much higher values wouldn't load. But that means the reboot.LOG source...

Also, because health insurance is tied to employment in the US (when it is offered) it is often the case that health insurance doesn't continue during a sabbatical.

I just had a go at this. I used amtm's email settings +test email to send, successfully, to my US Google Fi phone number through the Fi SMS gateway, and successfully to my US T-Mobile phone number through the TMobile SMS gateway, after a delay.

Still larking about with the Reboot.LOG: I removed the iw-window() line, on the theory that without flow-control() it wasn't doing anything, and changed the log-fetch-limit() to 100 from 1000. Rebooted, and the upshot was that I recorded (almost?) none of the startup sequence in messages. So...

Yes, I'm guessing you've removed the *OFF* from the network destination in syslog-ng.conf.

No difficulty here with 3.2.9 develop on 102.6 or 388.11. Must have been the reboot that fixed it.

email to your phone carrier's sms gateway?

This is somewhat of a shot in the dark, but in S01 does the export of the timezone look ok? Do you have ipv6 enabled?

Playing around with this: wildcard_file(base_dir("/opt/var/log") filename_pattern("syslogd.ScribeInitReboot.LOG") recursive(no) max-files(1) follow_freq(1) log_iw_size(1200) log_fetch_limit(1000) keep-timestamp(no)...

That sounds unlikely to me. I think syslog-ng ignores things like that. But from a command line you can run syslog-ng -Fevdand it might point to what is the problem. I had a similar error moving to the develop branch and I think running the forceupdate again fixed it...but I regret to say I...

Playing around with this further, udp() is working. Go figure. I'll give network() a try later, following your lead on using the recommended functions. In the meantime, you might think about changing the lines in syslog-ng.conf to source net { udp(port(514) flags(syslog-protocol)); }; The...

I'll be interested in trying your approach, but no need to rush. I fooled with different approaches for a while years ago: was it better to have messages be a clean log from the reboot, saving the pre-reboot sequence somewhere else (if the reboot was a problem), or was it better to preserve the...

The messages shouldn't be gone. In fact, with the new behaviour script messages that were being lost might now not be lost. They might end up in messages though. The startup sequence has all the startup messages going to syslog, and when those thousand messages or so simmer down, they are...

Perhaps I wasn't clear. Syslog-ng is at version 4.10; the entware version of it is at 4.7. The @version switch in syslog-ng controls what level features are enabled. If you set the @version to 3.5, features introduced in later versions would not be enabled. But, if the installed version is newer...