Harware Pfsense is not responding
-
Harware Opnsense is not responding
Really? I hope that's a typing mistake…. if not then I think I see your issue. ;)
I'd be checking the console for buffer exhaustion errors.
Try this: https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#mbuf_.2F_nmbclusters
Steve
-
Thank you for your answer.
let try it and report back -
i am having the same issue with the 1000 NIC of Intel
does this fix the job? -
If you are using Opnsense and not pfSense we can't really help you because it's not the same thing.
-
@johnkeates:
If you are using Opnsense and not pfSense we can't really help you because it's not the same thing.
I don't know what Opensense is but we are always used Pfsense and will .
-
When you reset the system afterwards, does it have any core dumps?
-
@johnkeates:
When you reset the system afterwards, does it have any core dumps?
no it does not, when the system is rebooted I can't seem to find any error or logs on the logs.
when we have checked the hardware it was not responding either usb or LAN networktried to log in using ssh just to collect the logs nothing was available, the only solution we have was to reboot,
-
Very strange. Hard lockups would have at least some evidence in mcelogs, system logs or dump devices.
You might have more luck configuring an external syslog server. In case the hardware can no longer store the last few writes and then crashes, at least the external log will have the data.
Another option is having a serial port and kernel debugger. -
@johnkeates:
Very strange. Hard lockups would have at least some evidence in mcelogs, system logs or dump devices.
You might have more luck configuring an external syslog server. In case the hardware can no longer store the last few writes and then crashes, at least the external log will have the data.
Another option is having a serial port and kernel debugger.this behaviour has started after we updated to the 2.3.4
isn't a NIC drivers issue ? -
@johnkeates:
Very strange. Hard lockups would have at least some evidence in mcelogs, system logs or dump devices.
You might have more luck configuring an external syslog server. In case the hardware can no longer store the last few writes and then crashes, at least the external log will have the data.
Another option is having a serial port and kernel debugger.this behaviour has started after we updated to the 2.3.4
isn't a NIC drivers issue ?If you can't get local console, serial console or USB to work, it's probably not the NIC.
-
Have you tried accessing the console directly? SSH obviously relies on the NIC still passing traffic.
If it is some issue with the NIC I would expect something logged or at least shown on the console.
If it's some more catastrophic hardware issue it may lock up entirely and log nothing….
Steve
-
Look at the output of # dmesg and see if there is anything there..
-
we have a new hardware now, and it seems to be up for two days without issues.
I'll report backup either it crashes again.
thank you for all your support
