Can you check what those file descriptors are?
# ls -l /proc/$(pgrep expressvpnd)/fd
I'm guessing they're just sockets, but I'm not sure why you have so many of them. (I have 11)
Your cluster list file version is outdated, but I doubt this would cause the issue you are seeing. Try updating it with expressvpn refresh just in case.
Other things to check are that your booted kernel (uname -r) matches the installed version (pacman -Q linux), and whether downgrading to the previous kernel fixes things.
I don't think that any AUR packages would cause problems for expressvpn, but going over your pacman -Qm list and rebuilding any potentially suspect packages just in case may help.
Pinned Comments
paintie commented on 2020-07-28 21:16 (UTC)
Info from expressvpn's site ...
wget https://www.expressvpn.com/expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc
gpg --import expressvpn_release_public_key_0xAFF2A1415F6A3A38.asc
All installed fine; thank you very much for maintaining.
WorMzy commented on 2019-11-06 13:15 (UTC)
Looks like update notifications are working for the linux client now, but unfortunately the current version (2.3.2) thinks it's an older version (2.3.1 -- check
expressvpn --version), so the update alert people get when they runexpressvpn statusmay be a false positive.Please check what version is reported at https://www.expressvpn.com/latest (or https://www.expressvpn.com/support/troubleshooting/china-status/#linux as this sometimes gets updates listed sooner) before flagging the package as out-of-date.
WorMzy commented on 2019-01-11 11:38 (UTC) (edited on 2019-01-23 20:41 (UTC) by WorMzy)
Please note that, from v2.0.0, ExpressVPN will be providing signed Arch packages on their website (alongside the deb and rpm packages). I'll be continuing to update this package, but for those that find using the AUR cumbersome or just don't want to wait, please be aware of this option.
EDIT: packages were delayed for testing, but seem to be live as of 2019-01-23.