503 Service unavailable (opnsense has died)

[guest17399]

Hello.
This is the second time I have noticed a problem when opnsense stops responding and I have to reboot it.

In addition to the fact that when I try to connect to www, I get the code 503, so I still can not connect via ssh.
Opensense itself is available only locally.
After some period of time, the network drops and I can’t do anything else, how to reboot the device.

I have the latest version.

What data do I need?

[banym]

If you're logged in via SSH you could review the loggs what happened.
Such behaviour could be related to bad Flash or Harddisk. Maybe the services die because of I/O errors.

Have you checked the logfiles when it happened?

[guest17399]

Such behaviour could be related to bad Flash or Harddisk. Maybe the services die because of I/O errors.

The point is that after reboot for several days I’m doing fine ...

[banym]

Maybe it does not hit bad blocks or bad space while that.
Check the logs or the console to see what errors are printed.

[fabian]

I would suggest to watch at the memory. 503 means that it cannot reach a service (for example PHP) which could have died but also be killed in an OOM situation.

[guest17399]

Sorry, but so far I don’t have time to look at the logs.
I also suspected that RAM was ending and this is so.

[fabian]

Since the available memory is constantly decreasing I would guess it is a memory leak or a in memory database which is growing which causes that there is a problem on the first day but on the second day there is a big falling edge which think is because of some kind of memory bug.The service may got killed which would explain that the thing happened again on the next day on which the whole appliance failed.

[guest17399]

I found the reason and right now I'm running out of RAM.
I see a lot of processes from pinger.

By the way, I think it's worth including htop in the package...

[guest17399]

I found the reason and right now I'm running out of RAM.
I see a lot of processes from pinger.

I hasten to add that I do not have any special settings and this problem arose after moving from 19.1 (everything was stable there) to 19.7

[fabian]

Pinger belongs to squid (web proxy). Maybe it can be disabled.