Log files aren't updating

madivad

A week ago I changed the size of the log files to 100MB (I was going to make it a GB but thought it might be too much—I have the space available and I prefer more than less information)

However, I checked everything the next day and I didn't appear to notice any relevant log updates and just thought it was quiet and haven't thought about it since.

A week later and no log files are updating at all.

Before reseting the log files everything seemed to be recording fine.

I did a backup of them (if needed)

I changed the file size and reset them on the 19th June. Today is the 27th, and here is the latest from the log files:

[2.3.3-RELEASE][admin@gateway.dav3.net]/var/log: find . -maxdepth 1 -name "[sfdngr]*.log" -print -exec sh -c "clog {} | tail -n 2" \;
./system.log
Jun 19 00:18:17 gateway php-fpm[10204]: /interfaces.php: Creating rrd update script
Jun 19 00:20:43 gateway check_reload_status: Syncing firewall
./filter.log
Jun 19 00:20:44 gateway filterlog: 5,16777216,,1000000103,pppoe0,match,block,in,4,0x0,,113,495,0,DF,6,tcp,52,67.167.174.102,59.167.252.142,62870,16881,0,S,4282231669,,64240,,mss;nop;wscale;nop;nop;sackOK
Jun 19 00:20:44 gateway filterlog: 5,16777216,,1000000103,pppoe0,match,block,in,4,0x0,,114,28376,0,none,17,udp,48,173.160.132.93,59.167.252.142,12012,16881,28
./dhcpd.log
Jun 19 00:18:14 gateway dhcpleases: Sending HUP signal to dns daemon(84819)
Jun 19 00:18:14 gateway dhcpleases: Sending HUP signal to dns daemon(84819)
./relayd.log
./nginx.log
Jun 19 00:20:43 gateway gateway.dav3.net nginx: 192.168.1.77 - - [19/Jun/2017:00:20:43 +1000] "GET /vendor/sortable/sortable-theme-bootstrap.css HTTP/1.1" 200 780 "https://192.168.1.1/interfaces.php?if=opt2" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36"
Jun 19 00:20:43 gateway gateway.dav3.net nginx: 192.168.1.77 - - [19/Jun/2017:00:20:43 +1000] "GET /css/pfSense.css HTTP/1.1" 200 7239 "https://192.168.1.1/interfaces.php?if=opt2" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36"
./ntpd.log
./gateways.log
Jun 19 00:00:04 gateway dpinger: send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 150.101.32.14  bind_addr 59.167.252.142  identifier "WAN_DHCP "
Jun 19 00:18:17 gateway dpinger: send_interval 500ms  loss_interval 2000ms  time_period 60000ms  report_interval 0ms  data_len 0  alert_interval 1000ms  latency_alarm 500ms  loss_alarm 20%  dest_addr 150.101.32.14  bind_addr 59.167.252.142  identifier "WAN_DHCP "
./resolver.log
Jun 19 00:20:29 gateway unbound: [84819:1] info: reply from <pool.ntp.org.>103.1.213.38#53
Jun 19 00:20:29 gateway unbound: [84819:1] info: query response was ANSWER
./routing.log
Jun 19 00:18:15 gateway radvd[33623]: no auto-selected prefix on interface igb0, disabling advertisements
Jun 19 00:18:15 gateway radvd[33623]: resuming normal operation
[2.3.3-RELEASE][admin@gateway.dav3.net]/var/log:</pool.ntp.org.>

If anyone can let me know what they'd like to see and I'll post it up.

kapara

I had a similar problem and found errors during pfsense boot. Backed up config, reinstall and restore config fixed it for me

madivad

I have done a reboot… Don't fancy a reinstall everytime I get a problem. I already had to do one because the drive got corrupted in an outage.

However, if no-one offers anything better in the next day or two I will do just that :(

I would really like it if someone has any idea where to look to try and fix this.

cheers

madivad

Ok, kinda solved.

I had changed the size of the log files and saved that and reset the log files (back on the 19th). At the time I initially made them 1GB each and quickly decided that might be a bit too big. I went thru the process and changed them down to 100MB.

Tonight I thought I would change them again and have further reduced it to 50MB and they are now logging again.

I may try and raise it a little and play with the size and see what happens, but I'll leave that for another time. For the moment, it works with 50MB log files.