Hummingbird randomly stopped working

[6gh54F4 0]

Hi, turn on my computer today (Arch linux) and hummingbird no longer works.
I tried running: /usr/local/bin/hummingbird --recover-network

and got this result:

"It seems this program has properly exited in its last run and

it has already restored network settings on exit.

 

ERROR: Backup copy of resolv.conf not found.

ERROR: Backup copy of network filter not found."

If I run systemctl status I get the following:
"Active: failed (Result: exit-code) since Wed 2020-06-17 10:06:01 AEST; 6min ago

Process: 1582 ExecStart=/usr/local/bin/hummingbird /home/bob/.local/bin/profiles/AirVPN_Austria_UDP-443.ovpn (code=exited, status=1/>

Main PID: 1582 (code=exited, status=1/FAILURE)

 

Jun 17 10:06:01 manjaro systemd[1]: vpn.service: Scheduled restart job, restart counter is at 5.

Jun 17 10:06:01 manjaro systemd[1]: Stopped AirVPN Client (hummingbird).

Jun 17 10:06:01 manjaro systemd[1]: vpn.service: Start request repeated too quickly.

Jun 17 10:06:01 manjaro systemd[1]: vpn.service: Failed with result 'exit-code'.

Jun 17 10:06:01 manjaro systemd[1]: Failed to start AirVPN Client (hummingbird)."

I've tried updating Hummingbird, I changed config files, reset systemd files.... nothing works

Edited ... by 6gh54F4

[eburom 16]

Hello.
A very similar thing happens to me from time to time (normally after I suspend system to ram).
You can try to call hummingbird manually instead of using the systemd unit (easier to check logs) or use "journalctl -u vpn" and push G to go to the last lines.
What I get is a very short log with a "core dumped" line.

Anyway, in my case what I need to do is restart (preferably with the systemd unit disabled) and call "hummingbird --recover-network".

After that I normally start it manually to check that it works again.

You can also enable back your systemd unit for future restarts.

 

[Staff 9973]

Hello!

It's very important to point out that Hummingbird is a process running in the userspace of a superuser. It is not designed to be a service. A real daemon is being developed and you will hear news soon.

That said, we need additional information, and specifically:
- what dependencies have been declared and their level
- when Hummingbird is started (in particular before or after the network layer)
- how and when systemd unit launches the service (we guess it's defined as a service and not as a target)

About the core dump, please feel free to send us a bt (in a ticket or attached to an e-mail to support@airvpn.org ). Did you notice any change after some Arch update?

Kind regards
 

[eburom 16]

9 minutes ago, Staff said:

t is not designed to be a service. A real daemon is being developed and you will hear news soon.

Good to know, anyway I've been using a systemd unit to start it out at boot with no issues so far (except for sometimes not working after suspend). My unit looks as follows:

[Unit]
Description = AirVPN Client (hummingbird)
Wants = network-online.target
After = network-online.target

[Service]
ExecStart = /usr/bin/hummingbird /root/AirVPN/hvpn-init.ovpn
Restart = always

[Install]
WantedBy = multi-user.target

I'm running Arch linux, for his post I would say the OP runs manjaro (based on arch).

I'll try to send you the backtrace, thanks.
 

[6gh54F4 0]

Yep exactly the same as Eburom. Happened after suspend.

My systemd file is the same as above. 

[Staff 9973]

Hello!

When you enter suspension state systemd sends SIGHUP to processes.Hummingbird reacts with "restart connection" when it receives SIGHUP. Core dump is unexpected and under investigation.

@eburom

The systemd unit is formally correct.

Kind regards