• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Warning: fopen(/tmp/config.lock): failed to open stream

Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
2 Posts 2 Posters 1.6k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    tarun
    last edited by Jan 16, 2015, 10:57 AM Jan 16, 2015, 10:08 AM

    I have pf sense installed on Supermicro Model 502-2 P/N 5015A-EHF-D525 with 32 GB crucial hdd.

    Things are fine but after few days I cannot enter the web config page and getting below error.
    I typed the default password and it then give the below error and it can't login.

    Error 1

    Warning: fopen(/tmp/config.lock): failed to open stream: Device not configured in /etc/inc/util.inc on line 123 Warning: flock() expects parameter 1 to be resource, null given in /etc/inc/util.inc on line 134 Warning: fclose(): supplied argument is not a valid stream resource in /etc/inc/util.inc on line 135 Warning: session_start(): open(/var/tmp//sess_fd59264b4e5cf3b6ae1121f1ccf4762a, O_RDWR) failed: No space left on device (28) in /etc/inc/auth.inc on line 1254

    Error 2

    Tried to use console menu option 8 to get a command prompt but its unable me to get into the command prompt. Its giving below error.

    1. Logout (SSH only)                  8 ) Shell
    2. Assign Interfaces                  9) pfTop
    3. Set interface(s) IP address      10) Filter Logs
    4. Reset webConfigurator password    11) Restart webConfigurator
    5. Reset to factory defaults        12) pfSense Developer Shell
    6. Reboot system                    13) Upgrade from console
    7. Halt system                      14) Disable Secure Shell (sshd)
    8. Ping host                        15) Restore recent configuration

    Enter an option: 8

    /etc/rc.initial: /bin/tcsh: Device not configured
    /: write failed, filesystem is full
    Fatal error: PHP Startup: apc_fcntl_create: open(/tmp/.apc.PA8GQF, O_RDWR|O_CREAT, 0666) failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_lock failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_unlock failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_create: open(/tmp/.apc.LMIIbh, O_RDWR|O_CREAT, 0666) failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_create: open(/tmp/.apc.I7p46p, O_RDWR|O_CREAT, 0666) failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_lock failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_unlock failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_create: open(/tmp/.apc.UPJxwV, O_RDWR|O_CREAT, 0666) failed: in Unknown on line 0
    Fatal error: PHP Startup: apc_fcntl_create: open(/tmp/.apc.tZet8w, O_RDWR|O_CREAT, 0666) failed: in Unknown on line 0
    Fatal error: Unknown: apc_fcntl_rdlock failed: in Unknown on line 0

    We have installed pf sense on different SSD and its keep crashing with the same error. We are facing this on our multiple sites.

    Please help

    Thanks

    pfsense.jpg
    pfsense.jpg_thumb
    ![pfsense screen.jpg](/public/imported_attachments/1/pfsense screen.jpg)
    ![pfsense screen.jpg_thumb](/public/imported_attachments/1/pfsense screen.jpg_thumb)

    1 Reply Last reply Reply Quote 0
    • C
      cmb
      last edited by Jan 17, 2015, 6:33 PM

      Either you're filling the entire drive, or it's dying.
      https://doc.pfsense.org/index.php/Filesystem_Full_/_Out_of_Inode_Errors

      Having multiple sites seeing the same thing, and seeing the same thing after putting in a diff SSD, doesn't necessary narrow it down. It's rare, but we have seen instances of people buying SSDs in bulk where the entire lot of 50-100 were bad and would fail along those lines after running for a handful of days. A power cycle would make it last a few more days. Eventually those were confirmed with the manufacturer to be a defective lot.

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received