pfsense reboots randomly not sure how to read this error log
-
if someone could please guide me in the right direction my pfsense server reboots itself randomly, im not sure how to decipher the logs
-
<5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <5>ix0: link state changed to UP <5>ix0: link state changed to DOWN <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: sendto(udp_notify=8, 192.168.3.1): No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=473, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=401, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto failed to send 2 packets <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=449, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=409, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=469, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=409, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto failed to send 4 packets <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=465, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=465, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=481, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=463, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto(sock=8, len=409, dest=239.255.255.250:1900): sendto: No buffer space available <118>Oct 12 22:02:22 miniupnpd[39143]: try_sendto failed to send 5 packets <118>Oct 12 22:02:27 php-fpm[59620]: /status_logs_settings.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1602554547] unbound[65760:0] error: bind: address already in use [1602554547] unbound[65760:0] fatal error: could not open ports' Sleeping thread (tid 100105, pid 13700) owns a non-sleepable lock KDB: stack backtrace of thread 100105: sched_switch() at sched_switch+0x64a/frame 0xfffffe000038c530 mi_switch() at mi_switch+0xeb/frame 0xfffffe000038c560 sleepq_wait() at sleepq_wait+0x2c/frame 0xfffffe000038c590 _sx_xlock_hard() at _sx_xlock_hard+0x2fe/frame 0xfffffe000038c640 bxe_ioctl() at bxe_ioctl+0x7a/frame 0xfffffe000038c680 if_delmulti() at if_delmulti+0x114/frame 0xfffffe000038c6c0 vlan_setmulti() at vlan_setmulti+0x43/frame 0xfffffe000038c700 vlan_ioctl() at vlan_ioctl+0x8c/frame 0xfffffe000038c780 inp_setmoptions() at inp_setmoptions+0x177e/frame 0xfffffe000038c950 ip_ctloutput() at ip_ctloutput+0x11b/frame 0xfffffe000038c9a0 rip_ctloutput() at rip_ctloutput+0x133/frame 0xfffffe000038c9d0 sosetopt() at sosetopt+0xb1/frame 0xfffffe000038ca30 kern_setsockopt() at kern_setsockopt+0xc8/frame 0xfffffe000038caa0 sys_setsockopt() at sys_setsockopt+0x24/frame 0xfffffe000038cac0 amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe000038cbf0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe000038cbf0 --- syscall (105, FreeBSD ELF64, sys_setsockopt), rip = 0x80092ea8a, rsp = 0x7fffffffea38, rbp = 0x7fffffffea80 ---
something with your network card
you have alot of ix0 up and down and after that a crash from bxe network card driver perhapsbxe1: ERROR: resource (0x8) not in use (status 0x0 bit 0x100) bxe1: ERROR: Can't unload in closed or error state recover_state 0x1 state = 0x0
my 2 cent on that bxe network card
-
@kiokoman
Thank you for the reply the bxe1 is not being used only bxe0 for my fibre connection ix0 is a straight 10gb connection to my pc... -
This post is deleted!