DNS resolver not starting
-
I have the latest: Pfsense snort and pfgblocker.
I was running this which worked:
VM modem mode->pfsense wan->pfsense lan-> in to tp link-> tp link
out-> to: Asus (for wireless) and tp link out to desktop via Ethernet.
All was running well until a few days ago where at the web GUI I get DNS resolver not starting. So I press the "play" button with no result. I can ping 8.8.8.8 inside the Web GUI but have no internet access. But when I remove Pfsense and plug in my VM modem mode I have full access.
I am currently using this: VM cable modem mode to Asus for wireless and one of its Ethernet ports to my desktop. -
Hi,
Use the console access - or if it (still) work : the SSH access.
Go for option 8.Type
dfdoes that answer your question ?
-
Check the system and resolver logs for errors.
-
I will do that and thanks to all.
-
OK. I tried to look as if there were any errors, but I could not see any. Also I tried to do the "df" command. Made no difference. So I re-installed Pfsense with no added packages.
-
The
dfcommand itself would not do anything except show you the drive usage. If root was filled to 100% Unbound can refuse to start. Along witg other things breaking.Steve
-
I looked in there:
https://192.168.1.1/status_logs_settings.php
then saw that my log files were getting too big. currently log files are
"Disk space currently used by log files is: 9.3M Remaining disk space for log files: 95G".
My SSD is 120 GB.
OK. I just wanted a working system. Got it now.How do I stop this from happening:
"If root was filled to 100% Unbound can refuse to start." -
Basically: configure packages correctly.
When we see that it's almost always because some package is not rotating it's logs correctly ir has been set to unlimited log or cache size somewhere.
pfSense itself has size limited logs so you should not see that grow much beyond that value unless you have specifically set them larger.
Steve
-
Cheers Stephen!!
I would like to re-install Snort and PfgBlocker. Where these packages logs kept?
Since I would like to keep logs from taking up too much space. -
In /var/log. I would recommend checking and saving the log settings on each package even if you make no changes to be sure they are using them.
In Snort I would set an overall log directory size limit as well and the limits on individual logs.Steve
-
Thanks as I am currently using Pfsense with no added packages. But as you have stated to limit the log files as to prevent this occurring again.
What is the good size limits on these log files as to keep the add on functioning at their best?
Also my SSD is showing 96% health after about 2 years usage. Is there a way to prevent this from getting worse? -
The default log sizes are generally fine. If you have some specific need to log more or maybe your system is particularly busy so the default 512K does not span enough time then you can increase them. I would start out by doubling them to 1M or maybe 2M. But 10M logs is not that unusual and any current drive is going to be easily large enough to accommodate that.
But the biggest things you can do to reduce disk writes if you are seeing excessive wear is to enable RAM drives:
https://docs.netgate.com/pfsense/en/latest/config/advanced-misc.html#ram-disk-settings
Doing that will generally leave far less space for logs since the log files are on /var
I generally use double the default size so 80MB and 120MB for the drives. 10M logs files are not going to fit there but 1M or 2M will.The other thing to check is that the root slice is mounted 'noatime'. If you just re-installed it should be but it may not have been previously because: https://redmine.pfsense.org/issues/9483
Run at the CLImount. You should see / mounted noatime like:/dev/diskid/DISK-9E18E959s2a on / (ufs, local, noatime, journaled soft-updates) devfs on /dev (devfs, local) /dev/diskid/DISK-9E18E959s1 on /boot/u-boot (msdosfs, local, noatime) /dev/md0 on /tmp (ufs, local) /dev/md1 on /var (ufs, local) devfs on /var/dhcpd/dev (devfs, local)I have ramdisks enabled on that system too.
Steve
-
@stephenw10 said in DNS resolver not starting:
The default log sizes are generally fine. If you have some specific need to log more or maybe your system is particularly busy so the default 512K does not span enough time then you can increase them. I would start out by doubling them to 1M or maybe 2M. But 10M logs is not that unusual and any current drive is going to be easily large enough to accommodate that.
But the biggest things you can do to reduce disk writes if you are seeing excessive wear is to enable RAM drives:
https://docs.netgate.com/pfsense/en/latest/config/advanced-misc.html#ram-disk-settings
Doing that will generally leave far less space for logs since the log files are on /var
I generally use double the default size so 80MB and 120MB for the drives. 10M logs files are not going to fit there but 1M or 2M will.
The other thing to check is that the root slice is mounted 'noatime'. If you just re-installed it should be but it may not have been previously because: https://redmine.pfsense.org/issues/9483
Run at the CLI mount. You should see / mounted noatime like:
/dev/diskid/DISK-9E18E959s2a on / (ufs, local, noatime, journaled soft-updates)
devfs on /dev (devfs, local)
/dev/diskid/DISK-9E18E959s1 on /boot/u-boot (msdosfs, local, noatime)
/dev/md0 on /tmp (ufs, local)
/dev/md1 on /var (ufs, local)
devfs on /var/dhcpd/dev (devfs, local)I have ramdisks enabled on that system too.
SteveThanks a lot. I will increase my RAM disks as I have 8GB RAM in my Qotom box.
-
Keep in mind that the content of ram disk is gone when the system powers down.
-
This post is deleted! -
This post is deleted! -
I have set it to this and re-booted Pfsense.
If I add packages such as Snort & Pfgblocker, will this amount of RAM disk settings be enough? I have 8GB RAM in my Pfsense box.
-
You don't need them anywhere near that large.
The RAM disks are backed up and restored across a reboot. You only lose the contents if the box is rebooted unexpectedly.
Steve
-
OK thanks a lot.
-
OK, thanks a lot. I will reduce the RAM size.
