Feedback logging 2.5 snap

w0w

Yep, thanks, @kiokoman, sure I can change it, but I think if we already have global changes made by @jimp in logging subsystem, why not fine tune some hidden settings also, I mean officially, by Netgate, not by me.
BTW I've already tried 20000 and it works. Yes it's slower, but it's not critical.

kiokoman

indeed, we should listen to what @jimp think about this, i don't know what impact could that have for small netgate's device
you can always open a request on redmine

w0w

@kiokoman
If user don't touch it, there is no impact by default, but I am not sure why it was limited.

stephenw10

It's limited because for some systems 2000 lines is a huge page. 10000 lines can become unusable.

But it could be limited via an 'are you sure?' style check box or similar I guess. Or just have a warning on the field.

Steve

jimp

I'm fairly sure that limit was a hold-over from the era when ALIX-level devices were more common. I'm not sure what the current limit should be, but 2000 seems small. The default should probably be 250-500 or so these days.

jimp

https://redmine.pfsense.org/issues/9734

jimp

These should hopefully all be addressed by the commits I've pushed today.

kiokoman

Tested it now. good work as always !

i've messed up with squid and there is no log in the captive portal tab.
default line is now 2000
TTY / Duration match the log filter

is there any log about the initialization of pfsense ? i mean the part where the boot process end and pfsense start to configure the interfaces / create route etc etc

kiokoman

Status / System Logs / Settings

Reset Log Files
Clears all local log files and reinitializes them as empty logs. This also restarts the DHCP daemon. Use the Save button first if any setting changes have been made.

Does not work for all the logs,
affected logs still present after pushing reset button:

System -> OS Boot
DHCP
Authentication -> OS User Events
Authentication -> OS Account Changes

individual "clear log" button work as expected

jimp

The DHCP log is definitely cleared, but you might not notice it because the daemon is restarted which immediately puts a bunch of log messages back into the file.

The others are not cleared because they are not maintained by syslog, so that function doesn't catch them. I can add them to the clear function specifically, though.

jimp

https://redmine.pfsense.org/issues/9802

kiokoman

2.5.0-DEVELOPMENT (amd64)
built on Mon Oct 21 20:52:27 EDT 2019

dhcp is logged twice

jimp

On which tab?

jimp

Nevermind, I found the problem and pushed a fix.

kiokoman

there is no logging info from open-vm-tools
maybe the gui is trying to read from vmware-vmsvc.log but it's 0 byte
and all the info are inside vmware-vmsvc-root.log instead?

-rw-------   1 root      wheel      76822 May  2 12:04 vmware-vmsvc-root.log
-rw-------   1 root      wheel          0 Mar 28 18:11 vmware-vmsvc.log
-rw-------   1 root      wheel      23046 May  2 18:52 vmware-vmtoolsd-root.log
-rw-------   1 root      wheel          0 May  2 18:45 vpn.log
-rw-------   1 root      wheel          0 May  2 12:01 wireless.log
[2.5.0-DEVELOPMENT][root@pfSense.kiokoman.home]/var/log:

jimp

That must have changed recently, I didn't notice since I still had log content in that file:

-rw-------  1 root  wheel   98767 Apr 30 11:40 vmware-vmsvc-root.log
-rw-------  1 root  wheel  140329 Jan  6 15:30 vmware-vmsvc.log
-rw-------  1 root  wheel   26386 Apr 30 11:40 vmware-vmtoolsd-root.log

I'll update the package