Messages

> Such corruptions may also be caused by a bad/weak power supply.

I see. Well it's easier to change the power supply than the RAM (not sure if that's even possible), so I'll try to change the power supply and see what happens!

> Looks like memory corruptions to me

That sounds bad... so my RAM would be dead? I don't think I can change it on my APU board  :'(

> Observing the crash in a console first might help

So connecting over serial to the router, staying logged in without doing anything in particular, and hoping that a message appears before it reboots?

Or did you mean something more elaborate? I have an easy serial access so I can do that :D

> If you submitted it please PM the email you used to submit. I can't find it at first glance.

I did, thanks!

In the meantime, it just rebooted again, but this time there is nothing in the crash reporter. The CPU temperature has been stable the whole morning at around 60 degrees Celcius, the RAM is stable around 15% of usage, the disk at 7%.

A power issue has been mentioned multiple times... should I try to buy a new power supply and see if that's better? Or is there a better way to check that?

Oh I see! So I probably already had a swap partition, and I did not need to enable the swap file. Still learning, sorry about that :-).

So there was something in the Crash Reporter, but I could not easily download it as a file so I submitted it. And now it disappeared! I thought I would get a copy on my email address, but I did not.

So I guess next time there is a crash I will go and manually copy-paste all the boxes of the crash dump, or something like that  ::)

> Ok swap partition is there then

Maybe I was not clear. I just enabled it, and now it seems to be there! So I need to wait for a new reboot (which should happen today anyway) :-).

> but swap file don't work for dumps.

And the system.log I attached above is a "dump", so it wouldn't be attached there? Is that what you mean?

> Nothing in the crash reporter?

I'll go read about the "crash reporter" so that I find it when it reboots again. I'll keep you posted!

> Without a swap partition to capture kernel crash reports it's impossible to say what the issue could be.

Oh, let me enable the swap partition!

Will the crash reports then appear in the same log file?

EDIT: I did enable the swap partition in System > Settings > Miscellaneous and rebooted the router, and found a widget on the dashboard that shows it. Somehow it shows 10GB, which seems off (in "Miscellaneous" it was mentioned 2GB).

EDIT 2: Actually, `$ top` says that there is now 10GB of swap as well:

```
CPU:  5.6% user,  0.0% nice,  2.4% system,  0.0% interrupt, 92.0% idle
Mem: 148M Active, 141M Inact, 547M Wired, 56K Buf, 3071M Free
ARC: 219M Total, 70M MFU, 109M MRU, 3288K Anon, 1915K Header, 35M Other
     134M Compressed, 360M Uncompressed, 2.68:1 Ratio
Swap: 10G Total, 10G Free
```

I guess now I just have to wait for the next crash and find a way to extract the kernel crash reports!

Thanks for the answers!

I actually have an APU.6B4 [1] with 4 GB DDR3-1333 DRAM.
Shouldn't that be enough?

Also is there a way to run diagnostics with OPNsense, in case my RAM is faulty?

[1]: https://www.pcengines.ch/apu6b4.htm

For some reason, my OPNsense router reboots multiple times per day, and I can't understand why. Looking into the "General" logs, I don't see anything special, except that it does reboot indeed (see `---<<BOOT>>---`) below:

```
2024-08-20T00:48:08     Notice  kernel   FreeBSD clang version 18.1.5 (https://github.com/llvm/llvm-project.git llvmorg-18.1.5-0-g617a15a9eac9)
2024-08-20T00:48:08     Notice  kernel   FreeBSD 14.1-RELEASE-p3 stable/24.7-n267778-bb2c86773c1b SMP amd64
2024-08-20T00:48:08     Notice  kernel   FreeBSD is a registered trademark of The FreeBSD Foundation.
2024-08-20T00:48:08     Notice  kernel          The Regents of the University of California. All rights reserved.
2024-08-20T00:48:08     Notice  kernel   Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
2024-08-20T00:48:08     Notice  kernel   Copyright (c) 1992-2023 The FreeBSD Project.
2024-08-20T00:48:08     Notice  kernel   ---<<BOOT>>---
2024-08-20T00:48:08     Notice  syslog-ng        syslog-ng starting up; version='4.8.0'
2024-08-20T00:38:49     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:38:33     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:38:22     Notice  opnsense         /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for opt1(igb2)
2024-08-20T00:38:17     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure dns (execute task : unbound_configure_do())
2024-08-20T00:38:17     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure dns (execute task : dnsmasq_configure_do())
2024-08-20T00:38:17     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:38:17     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure dns ()
2024-08-20T00:38:17     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:38:16     Error   opnsense         /usr/local/etc/rc.linkup: The command '/usr/sbin/daemon -f -p '/var/run/dhcpleases6.pid' '/usr/local/opnsense/scripts/dhcp/prefixes.sh'' returned exit code '3', the output was 'daemon: process already running, pid: 9786'
2024-08-20T00:38:15     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure dhcp (execute task : dhcpd_dhcp_configure())
2024-08-20T00:38:15     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure dhcp ()
2024-08-20T00:38:15     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure ipsec (execute task : ipsec_configure_do(,opt1))
2024-08-20T00:38:15     Notice  opnsense         /usr/local/etc/rc.linkup: plugins_configure ipsec (,opt1)
2024-08-20T00:38:15     Notice  opnsense         /usr/local/etc/rc.linkup: ROUTING: entering configure using 'opt1'
2024-08-20T00:38:14     Notice  opnsense         /usr/local/etc/rc.linkup: DEVD: Ethernet attached event for opt1(igb2)
2024-08-20T00:38:13     Notice  kernel   <6>igb2: link state changed to DOWN
2024-08-20T00:38:13     Notice  kernel   <6>igb2: link state changed to UP
2024-08-20T00:36:11     Notice  dhcp6c   dhcp6c_script: RENEW on igb0_vlan10 executing
2024-08-20T00:35:49     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:30:30     Notice  dhclient         dhclient-script: Creating resolv.conf
2024-08-20T00:30:30     Notice  dhclient         dhclient-script: Reason RENEW on igb0_vlan10 executing
2024-08-20T00:28:17     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:19:54     Warning radvd    prefix length should be 64 for igb1
2024-08-20T00:12:11     Notice  dhcp6c   dhcp6c_script: RENEW on igb0_vlan10 executing
```

In the attached system(1).log, it can be seen that it happens regularly.

Why is that?