Error: context deadline exceeded

[Cikaros]

After each restart, the message Error: context deadline exceeded appears. When executing netbird status, it prompts Error: failed to connect to daemon error: context deadline exceeded. If the daemon is not running please run: netbird service install netbird service start. It is necessary to execute netbird service uninstall && netbird service install && netbird service start to restore normal operation, but the error Error: context deadline exceeded still occurs after the next restart.

ubuntu 22.04 arm64
netbird v0.32.0

[mlsmaycon]

@Cikaros can you share the file generated by the command:

netbird debug for 1m -SA

[Cikaros]

Every time the system is restarted, the initial error will occur.

netbird.debug.3494745759.zip

[mlsmaycon]

Thanks @Cikaros the context deadline here might be related to the daemon service not being started. Everytime you run netbird service install you must netbird service start so it cat talk to the cli commands.

If it was running and then stopped, can you please check if the file /var/log/netbird.err is not empty, and if is not, please share with us the last updated date with ls -l /var/log/netbird.err and share its content.

[Cikaros]

There is no issue without restarting Linux; however, after I restart Linux, I must run netbird service uninstall && netbird service install to restart the daemon service.

[Cikaros]

I do not know the reason, and there is no output in the log either.

[Cikaros]

It is quite strange that the daemon can only start normally after reinstallation.

[mlsmaycon]

Sorry, I missed you running on Linux. The error file will be /var/log/netbird/netbird.err. Please run the same ls command.

[Cikaros]

I know, but the result is the same

[Cikaros]

May I ask what other methods are available to check the operation of the guardian service? I suspect the issue lies within the guardian service, but I do not see any error logs.

[Cikaros]

I checked the systemctl status after restarting Linux, and its status was not active.

[Cikaros]

The log folder does not exist after attempting to restart...I didn't take the initiative to delete it

[mlsmaycon]

You can try the following:

journalctl -u netbird.service

The fact that you don't have the logs might indicate that the /var/log is unavailable during boot and netbird startup time.

[Cikaros]

It is very strange; it seems as if it has not started at all.

[mlsmaycon]

Can you share the text from the /etc/systemd/system/netbird.service?

[Cikaros]

[mlsmaycon]

Can you add the following line before ExecStart=...?

ExecStartPre=-/usr/bin/mkdir -p /var/log/netbird

Then run:

sudo systemctl daemon-reload

[Cikaros]

[Cikaros]

debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78.)
debconf: falling back to frontend: Readline

debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 58094 files and directories currently installed.)

sudo apt-get update
sudo apt-get install dialog
sudo apt-get install apt-utils

It has been discovered that there are issues during the installation process, and even after handling them, they remain unresolved. Currently, an attempt is being made to run it using Docker.

[mlsmaycon]

@Cikaros can you share your distribution name and version?

[Cikaros]

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy

[Guik]

FYI: I have same behavior on Mac Os, service start only after an upgrade. Then after a reboot I have to run "sudo netbird service start"

[mlsmaycon]

@Guik can you share the output of netbird debug for 1m -SA?