March 15, 20224 yr My server crashed again. This time syslog was being mirrored to flash so I have something to show. Attached is `syslog` from /flash/logs/. There was nothing unusual before the cropped section. It completed its appdata backup as usual at 3am, then crashed at just before 9am. The server was hard-reset and is now running a parity check. This happens every few weeks. What can I do to fix this? EDIT: Attached a diagnostics dump. syslog-cropped.txt tower1-diagnostics-20220315-1044.zip Edited March 15, 20224 yr by jj_uk
March 15, 20224 yr Community Expert Nothing obvious, I do see some data corruption detected by btrfs, you should run a scrub and delete/replace any corrupt files, they will be listed in the syslog after the scrub, this corruption can be the result of some hardware issue and related to the crashing, you should also update to rc3.
March 15, 20224 yr I think I saw a MACVLAN in there. If you are using custom IP on dockers, you should upgrade to the latest RC and use IPVLAN instead of MACVLAN.
March 15, 20224 yr Author Thanks guys. I've updated to rc3. changed settings -> docker -> `Docker custom network type` to `ipvlan`. I've scrubbed the cache disk and the docker volume, no errors found. Hopefully that'll fix it. I have had a few issues with macvlan in the past taking down the server. Edited March 15, 20224 yr by jj_uk
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.