ANSWERED Hummingbird - How to delete ".lock" file after macOS crash

[spinmaster 30]

I'm using Hummingbird and while I had an active Hummingbird connection, my MacBook crashed today. After a Reboot, Hummingbird says that it cannot be restarted, since there is a lock file in place:
 

  Quote

This program is already running (PID 25865) or it did not gracefully exit in its previous execution. In case you have restarted this computer or just powered it on, you can remove the lock file /etc/airvpn/hummingbird.lock and start this program again.

What is the purpose of this .lock file? It seems it is not documented on https://airvpn.org/hummingbird/readme/
Is it safe to just delete it? When I try, I am getting this prompt:
 

spinmaster@MacBook airvpn % rm hummingbird.lock 
override rw-r--r-- root/wheel for hummingbird.lock?

Why is it asking for "override"? Any help appreciated!

 

[Staff 10116]

 @spinmaster

Hello!

This lock file is a temporary file created by Hummingbird to mark that the application is running. It is deleted when Hummingbird is shut down. If it exists while Hummingbird is not running the lock file is a "mark" that Hummingbird did not shut down properly (for example it was closed without grace, or it crashed) and it may hint to something that is not working properly. In your case the cause was surely the OS crash: it's normal that Hummingbird could not delete the file.

To delete the file, from a terminal:

sudo rm /etc/airvpn/hummingbird.lock

because the file can be written/deleted only by root.

Kind regards


 

[spinmaster 30]

Thank you, appreciate it! I have removed the .lock file and have also rebooted my Mac. The .lock file is definetly not there any longer, however, I still cannot get a new connection:
 

spinmaster@MacBook hummingbird-macos-arm64-1.3.0 % sudo ./hummingbird AirVPN_Switzerland_UDP-443-Entry3.ovpn 
Password:
Hummingbird - OpenVPN3 Client 1.3.0 - 1 June 2023

OpenVPN core 3.8.4 AirVPN mac arm64 64-bit
Copyright (C) 2012-2022 OpenVPN Inc. All rights reserved.
OpenSSL 3.0.8 7 Feb 2023

It seems this program did not exit gracefully or has been killed.
Your system may not be working properly and your network connection may not work
as expected. To recover your network settings, run this program again and use
the "--recover-network" option.

spinmaster@MacBook hummingbird-macos-arm64-1.3.0 % sudo ./hummingbird --recover-network AirVPN_Switzerland_UDP-443-Entry3.ovpn
Hummingbird - OpenVPN3 Client 1.3.0 - 1 June 2023

OpenVPN core 3.8.4 AirVPN mac arm64 64-bit
Copyright (C) 2012-2022 OpenVPN Inc. All rights reserved.
OpenSSL 3.0.8 7 Feb 2023

It seems this program did not exit gracefully or has been killed.
Your system may not be working properly and your network connection may not work
as expected. To recover your network settings, run this program again and use
the "--recover-network" option.

Even with "--recover-network" as argument and no .lock file, Hummingbird complains that it had not been exited properly...

Any ideas what I can do?

[Staff 10116]

Hello!

Please delete even any *.airvpnbackup file. The previous OS crash must have left a "dirty" status that requires manual intervention.

sudo rm /etc/airvpn/*.airvpnbackup

If the problem persists please send us the whole content of /etc/airvpn directory:

sudo ls -l /etc/airvpn

Kind regards
 

[spinmaster 30]

Thank you! OK, something is really weird: the *.airvpnbackup file (as visible in my screenshot from post #1) is not there any longer, there is just this one file:
 

spinmaster@MacBook ~ % sudo ls -l /etc/airvpn
total 8
-rw-r--r--@ 1 root  wheel  1027 Dec  7 09:16 pf-save.txt

Here is the contents of this file:
 

spinmaster@MacBook airvpn % less pf-save.txt

#
# Default PF configuration file.
#
# This file contains the main ruleset, which gets automatically loaded
# at startup.  PF will not be automatically enabled, however.  Instead,
# each component which utilizes PF is responsible for enabling and disabling
# PF via -E and -X as documented in pfctl(8).  That will ensure that PF
# is disabled only when the last enable reference is released.
#
# Care must be taken to ensure that the main ruleset does not get flushed,
# as the nested anchors rely on the anchor point defined here. In addition,
# to the anchors loaded by this file, some system services would dynamically 
# insert anchors into the main ruleset. These anchors will be added only when
# the system service is used and would removed on termination of the service.
#
# See pf.conf(5) for syntax.
#

#
# com.apple anchor point
#
scrub-anchor "com.apple/*"
nat-anchor "com.apple/*"
rdr-anchor "com.apple/*"
dummynet-anchor "com.apple/*"
anchor "com.apple/*"
load anchor "com.apple" from "/etc/pf.anchors/com.apple"
pf-save.txt (END)

Even with no *.airvpnbackup file existing, I am getting the

It seems this program did not exit gracefully or has been killed. Your system may not be working properly and your network connection may not work as expected. To recover your network settings, run this program again and use the "--recover-network" option.

error when trying to establish a connection...

Any ideas? Hummingbird was just a backup to Eddie for me anyway, but Eddie is currently not working for me because of https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/?do=findComment&comment=241840

[Staff 10116]

  On 12/8/2024 at 6:30 PM, spinmaster said:

there is just this one file:

Hello!

Please delete this one too and test again.

Kind regards
 

[spinmaster 30]

Thank you, removing the pf-save.txt did the job! After removing it, I am now able to establish a "normal" Hummingbird connection again. Appreciate the support & help!