Warning: fopen(/tmp/config.lock): failed to open stream
We have around 5 pfsense installed on different different locations. Last 5 months we have facing the issue with our all firewalls. One by one we are getting the same issue on the firewalls. Can you please help me for this error.
We are using the psfense 2.1.5 verison
1. Even we are not able to ssh the firewall and not able to access GUI
2. On GUI console below error is showing:-
Warning: fopen(/tmp/config.lock): failed to open stream: Device not configured in /etc/inc/util.inc on line 127 Warning: flock() expects parameter 1 to be resource, null given in /etc/inc/util.inc on line 138 Warning: fclose() expects parameter 1 to be resource, null given in /etc/inc/util.inc on line 139 Warning: session_start(): open(/var/tmp//sess_510e96ce34ccb974e45be263be7bf402, O_RDWR) failed: No space left on device (28) in /etc/inc/auth.inc on line 1355
The disk is full - seems that both /var and /tmp are full.
What pfSense version?
Full install or nanoBSD?
How big a disk?
What packages are you running?
What changed/was new 5 months ago?
I guess that some process is writing a huge file and filling up the disk. If you can get to the console, get to a command prompt (menu option 8), then have a look at what files are in /var… /tmp... that are big.
Thanks for update.
Please find your questions answer below:-
1. What pfSense version? = 2.1.5 Version
2. What hardware? = Intel(R) Atom(TM) CPU D525 @ 1.80GHz
3. Full install or nanoBSD? = Full Installation
4. How big a disk? = 32 GB
5. What packages are you running? = Zabbix Ajent only
What changed/was new 5 months ago? = 2 months back We have upgraded the version of pfsense.
This issue we have faced on our 4 pfsenses different different location. Even if we will try to install the pfsens on that hard disk then we are getting the error. Please find the error for same. Then we have plugged hard disk on other computer and formatted the hard disk.Then we are able to install the pf sens on same hard disk.
Please help us our clinet is really frustared with our services.
What kind of SSDs are these?
We are using the 32gb crucial hard drive
Those are real errors accessing the disk. So it is not that the file system is full - it is that there is some disk problem. If this was working fine for a few months, then the errors started, that means it is not a general FreeBSD driver or disk SSD firmware issue. It seems that the disks are failing in some way. It is surprising that you are getting similar failures then on 5 different systems.
Someone else might be able to advise what might be going wrong with a whole batch of disks!