OPNsense Forum

Archive => 20.7 Legacy Series => Topic started by: m4rtin on March 04, 2021, 05:13:53 PM

Title: An issue was detected. (21.1 sorry)
Post by: m4rtin on March 04, 2021, 05:13:53 PM
Hallo,
my opnsense tells me that an issue was detected. I didn't found something opnsense-related on google. Can you help me?

System Information:
User-Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:86.0) Gecko/20100101 Firefox/86.0
FreeBSD 12.1-RELEASE-p13-HBSD #0  5a415173060(stable/21.1)-dirty: Fri Feb  5 16:41:22 CET 2021     root@sensey:/usr/obj/usr/src/amd64.amd64/sys/SMP amd64
OPNsense 21.1.2 9e87d87d0
Plugins os-acme-client-2.4 os-clamav-1.7_1 os-dyndns-1.23_2 os-postfix-1.18 os-redis-1.1_1 os-rspamd-1.11 os-sensei-1.7.1 os-sensei-agent-1.7.2.beta4 os-sensei-updater-1.7 os-sunnyvalley-1.2_1 os-wireguard-1.4_1
Time Thu, 04 Mar 2021 15:55:29 +0000
OpenSSL 1.1.1j  16 Feb 2021
PHP 7.3.27


PHP Errors:
[03-Mar-2021 20:05:05 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 00:40:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 00:40:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4344 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 02:07:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 02:07:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4344 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 04:37:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 04:37:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4344 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 05:03:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 05:45:05 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 05:45:05 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4344 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 08:48:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4343 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476
[04-Mar-2021 08:48:01 Etc/UTC] PHP Warning:  stream_socket_client(): unable to connect to unix:///usr/local/sensei/run/mgmt.sock.4344 (Connection refused) in /usr/local/opnsense/mvc/app/models/OPNsense/Sensei/Sensei.php on line 476


dmesg.boot:

vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5
vm_fault: pager read error, pid 1 (init)
g_vfs_done():gpt/rootfs[READ(offset=-8714257207296, length=32768)]error = 5

Title: Re: An issue was detected. (21.1 sorry)
Post by: allebone on March 04, 2021, 05:22:25 PM
Either your disk is bad (replace) or your cabling to the disk is bad (check and replace cabling). Either way backup your config in case the system stops booting because of failed disk.
Title: Re: An issue was detected. (21.1 sorry)
Post by: m4rtin on March 04, 2021, 06:45:27 PM
I forgot to mention it runs as a VM on Hyper-V (Windows Server 2012). So don't you think a hardware failure is unlikely?
Title: Re: An issue was detected. (21.1 sorry)
Post by: allebone on March 04, 2021, 09:14:22 PM
Then the disk subsystem is taxed on your host and causing issues on the VM. Maybe check you dont have it on a slow disk or something. Another alternative is that you did something strange like extend the disk which is not supported without making some careful adjustments etc.
Title: Re: An issue was detected. (21.1 sorry)
Post by: m4rtin on March 04, 2021, 09:18:30 PM
Can you be more specific please? (I don't think that my disk subsystem pays taxes  ;)
Title: Re: An issue was detected. (21.1 sorry)
Post by: m4rtin on March 04, 2021, 09:20:02 PM
OK thanks, it should run fast because it is stored on a raid 1, but I will move it to another raid 1 with newer hard disks.
Title: Re: An issue was detected. (21.1 sorry)
Post by: allebone on March 04, 2021, 11:28:21 PM
Let me know if there is an improvement.
Title: Re: An issue was detected. (21.1 sorry)
Post by: m4rtin on March 05, 2021, 05:18:12 PM
there are some more errors now:

dmesg.boot:
https://pastebin.com/h9JZXCuE

/var/crash/info.0:
https://pastebin.com/zjYiWnkG

/var/crash/textdump.tar.0:
https://pastebin.com/ksXk5jAt

here are some errors of the logs:


Panic String: swp_pager_force_pagein: read from swap failed


swap_pager: I/O error - pagein failed; blkno 621648,size 24576, error 5
panic: swp_pager_force_pagein: read from swap failed
cpuid = 0
time = 1613145876
__HardenedBSD_version = 1200059 __FreeBSD_version = 1201000
version = FreeBSD 12.1-RELEASE-p12-HBSD #0  3c6040c7243(stable/21.1)-dirty: Mon Jan 25 12:27:52 CET 2021
    root@sensey:/usr/obj/usr/src/amd64.amd64/sys/SMP
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe002e69a680
vpanic() at vpanic+0x1a2/frame 0xfffffe002e69a6d0
panic() at panic+0x43/frame 0xfffffe002e69a730
swp_pager_force_pagein() at swp_pager_force_pagein+0x292/frame 0xfffffe002e69a7c0
swapoff_one() at swapoff_one+0x38e/frame 0xfffffe002e69a840
swapoff_all() at swapoff_all+0x117/frame 0xfffffe002e69a880
bufshutdown() at bufshutdown+0x30b/frame 0xfffffe002e69a8d0
kern_reboot() at kern_reboot+0x212/frame 0xfffffe002e69a920
sys_reboot() at sys_reboot+0x41b/frame 0xfffffe002e69a970
amd64_syscall() at amd64_syscall+0x364/frame 0xfffffe002e69aab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe002e69aab0
--- syscall (55, FreeBSD ELF64, sys_reboot), rip = 0x5bb10cb8caa, rsp = 0x7036cbfdb978, rbp = 0x7036cbfdb9e0 ---
KDB: enter: panic



I tried to do a fsck but for repairing I need a live os I think, can you recommend one with ufs support? didn't found that on ubuntu

root@OPNsense:~ # fsck /dev/gpt/rootfs
** /dev/gpt/rootfs (NO WRITE)
** Last Mounted on /mnt
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE  I=14927767  OWNER=rspamd MODE=100644
SIZE=177 MTIME=Mar  5 16:07 2021
RECONNECT? no


CLEAR? no

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no

SUMMARY INFORMATION BAD
SALVAGE? no

BLK(S) MISSING IN BIT MAPS
SALVAGE? no

78417 files, 1585919 used, 29898366 free (4038 frags, 3736791 blocks, 0.0% fragmentation)
Title: Re: An issue was detected. (21.1 sorry)
Post by: allebone on March 05, 2021, 08:27:37 PM
can you boot into single user mode and run fsck?