I've been contributing to open source since 1998.
| FreshPorts | https://freshports.org |
| homepage | https://langille.org |
| BSDCan | https://bsdcan.org |
| PGCon | https://pgcon.org |
Getting #syslog-ng onto a #FreeBSD host, replacing sylogd. Mainly to send data to victoria-logs
This post is still new, there might be more to do soon.
https://dan.langille.org/2026/06/16/replacing-syslogd-with-syslog-ng-sysutils-syslog-ng-on-freebsd/
Starting with LibreNMS-26.6.0, there is a new configuration item needed: the font cache directory for fontconfig.
https://dan.langille.org/2026/06/16/librenms-26-6-0-itable-cache-directories-vntl-var-db/
However, because this changes the host from syslogd to syslog-ng, I'm not rushing.
I want to see if log rotation is completed correctly. I've seen some permissions issues and want to follow through on those changes first.
We've got data in Victoria Logs!
It was my syslog-ng config, which now has this bit appended to a stock config file:
destination d_victorialogs {
network("logs.int.unixathome.org" port(29514) transport("tcp"));
};
# Log path linking your sources to VictoriaLogs
log {
source(src); # Use your existing system source name here
destination(d_victorialogs);
};
After about 15 minutes, I have a reverse Nginx proxy giving me access to the Victoria Logs UI.
Never mind that 'unsupported path requested' and 'Failed to load logs' - I suspect that's a proxy issue.
No data yet. Walking. Not running.
@meena @briandorsey @dvl Day-to-day from an admin perspective it's hands off. Upgrades are dead simple being a static binary. I wouldn't hesitate to deploy it again in another environment.
Biggest issue has been retraining employees on different search syntax, and our ingestion pipeline (which isn't anything to do with VL).
fukawi2