[SOLVED] /var/run error system full

[doktornotor]

/var/run is a ramdisk; "some error" is certainly useless for diagnosing the issue.

[pfsenseboonie]

@doktornotor:

/var/run is a ramdisk; "some error" is certainly useless for diagnosing the issue.

Can you tell me where the log is that keeps the boot?
I have searched the system.log file and boot.dmesg but cannot see the erro i saw in those.

[jimp]

It should be in /var/log/system.log – be sure to view that or run it through clog first, for example:

clog /var/log/system.log | grep -i run

You can also check the kernel message buffer by running:

dmesg

If the error was somewhere else, like the GUI or printed during boot, then you may have to copy/paste or screenshot it.

It's unusual for /var/run to be full, it's normally only PID files and some small but volatile files (like the gateway status)

[pfsenseboonie]

Just adding these while i hunt down that error…

[KOM]

My /var/run only holds 30-some .pid & status files totaling 58KB, with utmp and ld-elf.so.hints being the largest and everything else really small.  What's in yours?

[pfsenseboonie]

@KOM:

My /var/run only holds 30-some .pid & status files totaling 58KB, with utmp and ld-elf.so.hints being the largest and everything else really small.  What's in yours?

Good find.

Look at that 3.3MB file ps.core.
I have no idea what it is.

I am thinking some sorta core dump.

[pfsenseboonie]

can i safely delete that?

[jimp]

Yes, it shouldn't be there.

Though I wonder what could have caused ps to crash. Has the hardware been stable? Or has it had issues? That's the sort of thing I'd only expect to crash if there was a hardware issue.

[pfsenseboonie]

@jimp:

Yes, it shouldn't be there.

Though I wonder what could have caused ps to crash. Has the hardware been stable? Or has it had issues? That's the sort of thing I'd only expect to crash if there was a hardware issue.

It's new hardware. Just installed. 
I will delete it reboot and see if it re-occurs.

[pfsenseboonie]

ugh it came back. Not sure of the cause.

[pfsenseboonie]

I was able to get a screenshot of the error.

[doktornotor]

That new hardware sounds like a DoA to me…

[pfsenseboonie]

Hi again.  I think I have resolved the issue.

I reinstalled 2.1.3 from a CD (previously i had used 2.2.2 memstick install)

I then upgraded via the console to 2.2.2 which presented a problem with unbound not starting.

following some advice here https://forum.pfsense.org/index.php?PHPSESSID=85j3ap423rg5mtrurrgslvvpc6&topic=92712.msg514140#msg514140
I downloaded the update patch locally and applied it to the system again via the web interface.

I then restored my configuration and everything seems to be working so far.

Not sure if somewhere along the process of first install there was some data corruption somewhere.

Thank you guys for the assistance.