Maybe something like this for a script:
theScript | logger -t dehydrated 2>&1
I don’t know if tee would work with this…
That’s how you would do it manually when running the script but then if you hadn’t read the addon page and didn’t run that compound command but just the dehydrated command then nothing would be in the logs but you would still have a Dehydrated entry in the system logs drop down box which would show an empty output.
I was hoping to think of a way where someone has to actively change things somewhere from the default to prevent the data getting into the logfile.
The file redirection command you show could be put into every line that outputs stuff in the script but that would be a lot of update editing when the Dehydrated script is updated.
You could certainly add into the script the commands to feed the whole output of the script to a log file although I am not sure that the logger command then works in terms of adding the title for every entry.
I think it could need a lot of experimentation to confirm a solution that is built into the script so that when people use the dehydrated command it automatically feeds the output to a log file and the screen and puts a dehydrated title on each line in the logfile.
I am open to further ideas to try out when I get to working on the Dehydrated situation.
I knew it wouldn’t be easy since Dehydrated is not a service/daemon/process that delivers standard logs to messages but using it’s own format.
The same applies for HAproxy, too, as already mentioned in the bug/feature request.
At the end, I would like to see at least NUT logs in the WebIF 
I’ve done this already by modifying the appropriate source.
If the other packages will find their way into the WebIF some time, too, it would be great but this is certainly not highest priority of course.
Thanks!
Currently my script for Dehydrated looks like this
#!/usr/bin/env bash
cd /etc/dehydrated
#Remove previous log file
mv -f renewal.log renewal.log.bak
#Renew certificates forcing renewal, clean up old certs moving to archive folder
date >> renewal.log
/usr/bin/dehydrated -gc >> renewal.log
/usr/bin/dehydrated -c -g -x >> renewal.log
#Merge certificates
/etc/dehydrated/merge_pem.sh
#Reload haproxy
/etc/init.d/haproxy reload >> renewal.log
##Write metrics
cd /root/metrics
python3 /root/metrics/system_certs.py
All output from Dehydrated goes into a text file, nothing fancy, but for debugging issues enough detail.
Question and suggestion.
HAproxy can log to a syslog server, can IPFire act as a syslog server and probably receive HAProxy logs, if configured?
Though I don’t know if a syslog server itself writes into /var/log/messages.
IPFire is an open source project. So everyone can easily find the function
#
# log (“message”) use default ‘ipcop’ tag
# log (“tag”,“message”) use your tag
#
sub log
{
my $tag=‘ipfire’;
$tag = shift if (@>1);
my $logmessage = $[0];
$logmessage =~ /([\w\W]*)/;
$logmessage = $1;
&system(‘logger’, ‘-t’, $tag, $logmessage);
}
in file /var/ipfire/general-functions.pl.
Looking at this code, you can see that the software writes the systemlog using the Linux utility logger.
Man page about logger reads:
DESCRIPTION
logger makes entries in the system log. When the optional message argument is present, it is written to the log. If it is not present, and the -f option is not given either, then standard input is logged.
To answer your question:
yes, IPFire contains a local syslog server; if HAProxy is able to send to a local syslog server, the messages are written to /var/log/messages. These should be tagged with ‘HAProxy’. Then it is possible to filter them to an own section of the Logs part of the WebGUI.
EDIT: I’ve just scrolled a bit through this thread and followed the links to the ‘uncomfortable’ Bugzilla.
I think your questions are answered before and there. Adolf is working at this.
1 Like
I know Adolf is already taking some action on my tickets, at least for nut logging and filtering. HAProxy and Deyhdrated are IMO, more complicated regarding the possibilities of writing to the system log.
So, I just wanted to give Adolf some possible help for HAProxy logging, nothing else 
I am open to any help available. I will remember to come back here when I get to looking at HAProxy and Dehydrated.
Thanks for all the input. 
1 Like
FYI, I’ve just updated the bugzilla ticket with some information on how to let HAproxy log into /var/log/messages.
Maybe it’s of any help for you and others: Add a WebIF option for logs originated from HAProxy
Now, I just need an entry for HAProxy in the WebIf to filter for those logs
3 Likes
Just did some tests again and re-checked /var/log/messages. I noticed that HAProxy now writes proper logs into the syslog file.
Don’t ask me how this happened, I do not know. I did not change anything on my side, not even restarted IPFire, HAproxy or anything else.
An entry in messages now looks like. You should notice that localhost.localdomain disappeared and now reads localhost.
Sep 19 19:30:55 localhost haproxy[13742]: 100.20.194.139:46494 http_https~ collab_server/collab01 207 1821 --VN “PROPFI
ND /dav.php/calendars/family/holiday/ HTTP/1.1”
Wait a minute: I’ve written here that the file /etc/hosts looks like:
127.0.0.1 localhost.localdomain localhost
172.17.0.1 gateway
I had a look again and now there is a totally different content!
127.0.0.1 localhost
192.168.0.1 ipfire.ourhome ipfire
172.17.0.1 gateway
So how on earth did this content found it’s way into this file?
Ah!!! A few days ago I’ve edited the hosts list in WebIf, inserted one single host. I assume that this action did re-write the file /etc/hosts, too. Presumably with the correct content! I do not know, so devs please check this yourself if necessary.
But why has there been some unusual content before?
1 Like
My hosts file looked like your original with just the two lines.
I then added my IPFire hostname to the Hosts page and my hosts file now looks like your second table but with my IPFire hostname and domain name shown.
I then deleted the IPFire host entry in the Hosts page and checked the hosts file and it has stayed with the three lines.
I still need to check what happens when I reboot.
Don’t fully understand what is happening.
2 Likes
Have confirmed that when you doi a reboot the /etc/hosts file goes back to the original default setting.
3 Likes
while finished my XDP DNS query blocklist feature to log DNS query from green network source ip, and search if unbound could log source ip in google, leads to this request. now XDP DNS blocklist could log the query and source ip from green network
Oct 1 19:02:28 bpfire-1 qname_logger[3543]: Received qname: 1-courier.push.apple.com from source IP: 172.16.1.9
Oct 1 19:02:28 bpfire-1 qname_logger[3543]: Received qname: 1-courier.sandbox.push.apple.com from source IP: 172.16.1.9