(Solved, a hardware failure)Need help on visiting pfsense config page

[nexusN]

I have just tried my installation on a new router,
things are fine and the links are up.

But I cannot enter the web config page on lan,
I typed the default password and it then reads:

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

and keep saying the credentials are wrong…...how can I solve this? thanks.

[Metu69salemi]

Sounds like this, but i'm not 100% sure

[nexusN]

Yes, likely the same case.
Mine was a fresh install with only the WAN and LAN NIC config-ed.
The harddisk is 320GB, old yet functions well.

Could this be a bug for the new version of pfsense?

[nexusN]

Strange, after a few reboots and trials it works again,
and after a quarter it still works.
Can't figure out why but as far as it works I would leave it. ???

Sigh, it has just returned and I think I will have to reboot my router before it is configurable again….......anyone has ideas?

[nexusN]

@nexusN:

Strange, after a few reboots and trials it works again,
and after a quarter it still works.
Can't figure out why but as far as it works I would leave it. ???

Sigh, it has just returned and I think I will have to reboot my router before it is configurable again….......anyone has ideas?

Today I reinstalled the OS harddisk formatted and MBR rebuilt, SATA cord replaced.
BIOS of MB upgraded.
Same issue.

[cmb]

It means what it says, it can't write to /var/tmp because there is no space available on the device. That's either because there is no space (something overrunning the disk? would have to be a package) or at times a dying disk will produce that output. Check "df -h" at the console when it's happening.

[nexusN]

@cmb:

It means what it says, it can't write to /var/tmp because there is no space available on the device. That's either because there is no space (something overrunning the disk? would have to be a package) or at times a dying disk will produce that output. Check "df -h" at the console when it's happening.

Sadly I don't have another harddisk to test it out;
They are too expensive now such that I must use an old one.

While I do think it works quite well as I have been using it to store and download new data frequently.
Maybe I should check it anyway. Thanks for your advice.

[nexusN]

@nexusN:

@cmb:

It means what it says, it can't write to /var/tmp because there is no space available on the device. That's either because there is no space (something overrunning the disk? would have to be a package) or at times a dying disk will produce that output. Check "df -h" at the console when it's happening.

Sadly I don't have another harddisk to test it out;
They are too expensive now such that I must use an old one.

While I do think it works quite well as I have been using it to store and download new data frequently.
Maybe I should check it anyway. Thanks for your advice.

Thanks for the check advice!
I am sorry for my irresponsible claim on the software,
on WD harddisk check the harddisk is found to have bad sector, and it cannot even pass a quick test.
Now I have switched to a 2.5" harddisk and hopefully I won't see the same error on the page.