OPNsense Forum

Archive => 22.1 Legacy Series => Topic started by: iorx on June 02, 2022, 04:36:51 pm

Title: Dump in logs and loss of connection
Post by: iorx on June 02, 2022, 04:36:51 pm

Hi,

Loss of internet connection. Everything fine after a restart. Didn't have the time to troubleshoot while it was happening. But OPNsense was fully accessible on it's LAN-adress and a controlled reboot was performed.

Can/should I provide more info?

OPNsense 22.1.8_1-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1o 3 May 2022

2022-02-12T10:10:41       syslogd   exiting on signal 15   
2022-02-12T10:10:41       shutdown[15206]   reboot by root:   
2022-02-12T10:10:41       shutdown[15206]   reboot by root:   
2022-02-12T10:10:39       monit[67732]   'fw01.intdomain.local' Monit 5.29.0 stopped   
2022-02-12T10:10:39       monit[67732]   Monit daemon with pid [67732] stopped   
2022-02-12T10:10:28       kernel   hn0: promiscuous mode disabled   
2022-02-12T10:09:34       kernel   -> pid: 35692 ppid: 1 p_pax: 0xa50<SEGVGUARD,ASLR,NOSHLIBRANDOM,NODISALLOWMAP32BIT>   
2022-02-12T10:09:34       kernel   [HBSD SEGVGUARD] [syslog-ng (35692)] Preventing execution due to repeated segfaults.   
2022-02-12T10:09:34       kernel   -> pid: 12444 ppid: 35692 p_pax: 0xa50<SEGVGUARD,ASLR,NOSHLIBRANDOM,NODISALLOWMAP32BIT>   
2022-02-12T10:09:34       kernel   [HBSD SEGVGUARD] [syslog-ng (12444)] Suspending execution for 600 seconds after 5 crashes.   
2022-02-12T10:09:34       kernel   pid 12444 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)   
2022-02-12T10:09:34       supervise/syslog-ng[35692]   Error forking child process; error='Operation not permitted'   
2022-02-12T10:09:33       syslog-ng[49326]   syslog-ng starting up; version='3.35.1'   
2022-02-12T10:09:32       kernel   pid 90215 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)   
2022-02-12T10:09:32       kernel   pid 877 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)   
2022-02-12T10:09:31       kernel   pid 87704 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)   
2022-02-12T10:09:29       kernel   pid 48869 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum done   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum interface_086400.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum interface_003600.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum interface_000300.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum interface_000030.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum dst_port_086400.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum dst_port_003600.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum dst_port_000300.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum src_addr_086400.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum src_addr_003600.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum src_addr_000300.sqlite   
2022-02-12T09:54:32       /flowd_aggregate.py[52170]   vacuum src_addr_details_086400.sqlite   
2022-02-12T01:53:31       /flowd_aggregate.py[52170]   vacuum done

Title: Re: Dump in logs and loss of connection
Post by: franco on June 03, 2022, 11:45:00 am

2022-02-12T10:09:34       kernel   [HBSD SEGVGUARD] [syslog-ng (12444)] Suspending execution for 600 seconds after 5 crashes.

That definitely looks like 21.7, not 22.1. Mind you this is February 2022 and it's June already.


Cheers,
Franco

Title: Re: Dump in logs and loss of connection
Post by: iorx on June 09, 2022, 08:50:42 pm

So sorry, must have looked backwards on this one. You're totally right this is very old entries in the log. Can I wipe this thread so I don't have to be ashamed of posting such nonsense?  :P