New Installation losing network connection

Good morning. New Umbrel Home installation experiencing continuing network disconnection issues, every few hours, requiring a hard reboot to get back up.

I performed a factory reset and even with no apps installed, the problem persisted. I have a static IP allocated to the Umbrel.

I have searched and see many others with the same issue but I don’t see a solution - does anyone know of a fix?

I’m getting no res[onse from Umbrel support and would appreciate some assistance - thank you.

You are right a lot of people have been having this issue and so have I. Mine seems pretty consistent to stop at exactly 8 hours after boot.

On yesterday’s failure, I was finally able to capture the system logs.

I think I traced my problem with the Mender Client. This morning I ran the following command:

sudo apt-get --reinstall install mender-client

My Umbrel has been running for 14 hours now. :crossed_fingers:

Thank you RodB, I will give that a try…. I’m new here - is “umbrel support” really non-existent? Pretty disappointing experience so far.

I am now at 26 hours and counting!!! :raising_hands: Still have :crossed_fingers: !!!

1 Like

Any luck with yours?

Up for 12 hours so far after running the command you suggested - I’ll keep you updated!

1 Like

I had another crash at about 25 hours running … analyzing my logs … it was having problems with the WiFI … I am on Ethernet and not using WiFi so, I have now permanently disable the WiFi in the OS:

sudo nmcli radio wifi off
sudo systemctl stop wpa_supplicant && sudo systemctl disable wpa_supplicant

There was also some errors saying that I ran out of memory. I have 32GB of RAM and I have never seen it go over 50% Used but I will keep on eye on that when I get up-to 24 hours running again!

ah crap…. thanks for the update. I’m at 27 hours now which is a new record so crossing my fingers.

Ugh … another Memory Failure this morning while I was working with it!

Jan 19 03:55:11 umbrel systemd-journald[415]: Under memory pressure, flushing caches.
– Boot aa34175387f842be82e81d021c36d961 –

At least I have now tracked it down to the container that is causing the issue and consuming too much memory. I am just trying to do too many things at once even with 32GB of RAM on the system.

I stopped the container that was causing me issues and will see if my 24+ hour tests of running without failure holds up.

Glad to hear you are 27+ hours now on yours! Keep me informed, please.

Hi Rod - sorry to hear you’re still having issues. I’ve been up for nearly 48 hours now without any glitches - I’m just running knots and electrs.

Spoke too soon - lost network connection again @48 hours

Are you able to capture the system logs and determine what caused it?

I’m back at 10 hours now … our city had a power outage yesterday so, I shut everything down cleanly during the outage.

My free memory is looking good, so far,

I got some errors related to mender - but this was after I restarted - does that help? I’m far from an expert on all this as you m ay have gathered!

The way I look …

Settings → Troubleshoot → umbrelOS → Download umbrelOS logs

Open the log file that was downloaded and go to the very bottom of the file.

Search for – Boot (backwards)

The data right above this line is what got written to the log file before it completely logged up.

In my case below, I ran out of Memory:

Also, here is my script to clear the system logs completely out and start fresh:

umbrel@umbrel:/usr/local/bin$ cat cleanlogs.sh
#!/bin/bash

#Stop the Docker service

sudo systemctl stop docker.service
sleep 2

#Stop the Docker socket

sudo systemctl stop docker.socket
sleep 2

sudo systemctl stop systemd-journald
sleep 2
sudo systemctl start systemd-journald
sleep 2

sudo journalctl --rotate
sudo journalctl --vacuum-time=1s

sudo reboot

Much appreciated Rod - here are the logs right before the last network disconnection. Looking through the logs there are also continual errors referencing mender if that is relevant.