-
Hello guys,
Does anyone know what could be causing these log issues and how they can be resolved
-
The first log looks like there was no current repo data at that point. Was probably still updating after you logged in.
The second one is a log rotating. See: https://redmine.pfsense.org/issues/12747
-
-
Yup, see that bug I linked.
-
@stephenw10 said in Logs:
The second one is a log rotating. See: https://redmine.pfsense.org/issues/12747
Exact.
It could be considered as 'cosmetic' and if you want to see them less, don't do what said here : https://redmine.pfsense.org/issues/12747 (last comment) :The fix is not to reduce the size of the logs.
No, make the logs somewhat bigger => means less rotation => sshguard won't get restarted as often.
sshguard is a security process. When it stops, starts, restarts, that's actually not 'garbage' imho.pfSense doesn't log that much to the default syslog system channel, but, as people tend to add "whatever possible", the system log can get quiet busy => more often rotated.
Example : my logs are 2 Mbytes in size, and not the default 500 Kbytes (I've space enough on my drive) and the system log contains 3 weeks of info.
-
Sure.
@stephenw10 for some reason I'm getting more errors from the second log for the repo where you told me that: "The first log looks like there was no current repo data at that point. Was probably still updating after you logged in."
Do you know what to be done so this can be fixed?
-
Maybe unable to pull repo data for some other reason then. Does
pfSense-repoc -N
return without error?
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.