[Solved] No logging after upgrade to 2.7.2
-
After upgrading my box to 2.7.2 yesterday, there is no logging anymore. All the log files have only 0 bytes. The only logfile written is "dmesg.boot"
What I have seen is, that /etc/syslog.conf does only have a reference to " "/var/etc/syslog.d" and this directory is empty.
So my question is: Should there somewhere a configuration file for syslogd and could it be that it is missing in my installation? Or, how is syslogd configured in pfSense?
What else could be the problem? Thanks a lot!
P.S. Syslog is running with
/usr/sbin/syslogd -O rfc3164 -s -c -c -l /var/dhcpd/var/run/log -P /var/run/syslog.pid -f /etc/syslog.conf
-
I don't normally syslog from my 2.7.2 test box, but I just enabled it and it works
there is a config file in /var/etc/syslog.d
next test
disabled syslog
moved the file to a backup
re-enabled syslog
file was recreated - logging worksMaybe just try changing / verify the syslog setting on the GUI and save them.
Or, how is syslogd configured in pfSense?
Status -> System Logs -> Settings (tab)
syslog settings are at bottom of that page.All the log files have only 0 bytes.
where ? on the pfSense or is that in reference to the syslog?
-
Ah, maybe I am wrong here?
My problem is that all the local logs (like e.g. the firewall logs, the NGINX log etc.) are 0 bytes on my local pfSense box.
I thought that the syslogd is responsible for this as well. I do not use any remote syslog server.
Just all local logging seems somehow to be disabled ...
-
So nothing is logging? Sorry I misunderstood thought you where shipping the log files.
have you "Reset Log Files" on the same setting page above.
If not, and since they are empty anyway, you could reset them once.the config file in /var/etc/syslog.d should be created in that case as well (just without the remote logging bits)
although I am logging, it is a test box, so I just did that
(I had to remove the config)
Reset Log Files
config is recreated and
immediately continue to see entries in the nginx log for example. -
@jrey I did that already (and now once more) but there is no config file created. Any glue where the skeleton for this file could be? I had some issues while upgrading and I had many *.conf files which did have 0 bytes and therefore almost nothing worked. I tried to find all of them, deleted them and reinstalled all packages again which fixed almost everything. The only thing I am currently aware of, that does not work, is the logging system.
Is there something machine dependent in that config file? Or would you be able to just post it so that I can try it here?
-
Think I would be more concerned why the file is not generated when you do that.
is there a failure message in the boot log? you should have that?
What did you upgrade from?
backup of your config settings, a fresh reinstall might be a better choice, since you had other issues.what does the /var/log directory look like? are there files there?
permissions -
@jrey There are no obvious errors in my boot log file.
However, thank you for providing me your conf file. I tried to implement that here and I saw that I was unable to save anything in the /var/etc/syslog.d directory! Even a "touch testfile" did not give me an error but also did not create any file.
I then removed the syslog.d directory and recreated it. After that a reset of all log files did successfully create the conf file by itself and now logging seems to work again.
So although that problem seems to be solved: What could be the reason that I am unable to write as root into a directory (but also do not get any errors while writing?) That is really strange.
-
@m0urs said in No logging after upgrade to 2.7.2:
not able to save anything in the /var/etc/syslog.d directory!
so again the concern would be what else didn't upgrade properly ...
Were me, grab a copy of your config Diag -> Backup & Restore (backup configuration)then do a fresh install
restore the config,
-
@jrey You are right. This concerns me also a bit. However, it is now running for two days an I cannot see any other issues so far. So I would like to wait until I see a big problem before doing a fresh install. I am a bit afraid, that afterwards I run into even bigger problems.
-
@m0urs
Fair enough --you should make a backup of your "system" config from the menu mentioned previously. (and if you are still making changes while you test, grab a fresh one regularly until you are comfortable there are no other issues)
(and for anyone thinking this is the system config file I shared, it is NOT) the file provided was specifically the logging config file the OP did not have)
Would have thought when you tried the reset and it couldn't create the file, there would have been an error
loggeddisplayed.
-
@jrey Thanks. Yes, I make regular back of my config so I should be fine if I need to recreate everything. I am just not really believe that a fresh install and restore of my config will really work without problems as I never did that before.
However: Due to the issue with the directory which could no longer be written to: I am a bit afraid that I do have some kind of file system error. So I normally would nee to do a file system check. But I guess afterwards it could be that the system is o longer booting at all.
So I am still not sure what I should do.
-
I would reinstall and restore the config in that situation. Something has failed at upgrade but without logs from that process it's impossible to say quite what.
-
Ok, I ordered a USB-serial cable and did a reinstall from scratch this morning.
It was easier than I thought and everything seems to be fine again.
I also saw that the router had (from factory) still UFS as file system before and that might be the reason why I had such strange file system corruptions. Hopefully ZFS is more robust now against power failures. And I will try to change the configuration so that my router is also powered by my UPS
Thanks to all,
Michael
