Hi there. New here.
I’m trying to install p3x-onenote and now snapd is giving an error saying that it cannot communicate with the server, connection refused.
Here are some outputs:
# cat /etc/os-release
NAME=“Ubuntu”
VERSION=“16.04.5 LTS (Xenial Xerus)”
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=“Ubuntu 16.04.5 LTS”
VERSION_ID=“16.04”
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
# systemctl status snapd.socket
● snapd.socket - Socket activation for snappy daemon
Loaded: loaded (/lib/systemd/system/snapd.socket; enabled; vendor preset: enabled)
Active: inactive (dead)
Listen: /run/snapd.socket (Stream)
Jan 30 21:36:39 caelinuxz420 systemd[1]: Failed to listen on Socket activation for snappy daemon.
Jan 30 21:41:53 caelinuxz420 systemd[1]: Closed Socket activation for snappy daemon.
Jan 30 21:45:24 caelinuxz420 systemd[1]: snapd.socket: Socket service snapd.service not loaded, refusing.
Jan 30 21:45:24 caelinuxz420 systemd[1]: Failed to listen on Socket activation for snappy daemon.
Jan 30 21:45:36 caelinuxz420 systemd[1]: Closed Socket activation for snappy daemon.
Jan 30 21:46:27 caelinuxz420 systemd[1]: snapd.socket: Socket service snapd.service not loaded, refusing.
Jan 30 21:46:27 caelinuxz420 systemd[1]: Failed to listen on Socket activation for snappy daemon.
Jan 30 21:47:30 caelinuxz420 systemd[1]: Closed Socket activation for snappy daemon.
Jan 30 21:50:06 caelinuxz420 systemd[1]: snapd.socket: Socket service snapd.service not loaded, refusing.
Jan 30 21:50:06 caelinuxz420 systemd[1]: Failed to listen on Socket activation for snappy daemon.
# journalctl -xe
Jan 30 21:50:06 caelinuxz420 systemd[1]: snapd.socket: Socket service snapd.service not loaded, refusing.
Jan 30 21:50:06 caelinuxz420 systemd[1]: Failed to listen on Socket activation for snappy daemon.
-- Subject: Unit snapd.socket has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snapd.socket has failed.
--
-- The result is failed.
# journalctl -u snapd.service
-- Logs begin at Tue 2020-01-28 23:31:03 EST, end at Thu 2020-01-30 21:52:25 EST. --
Jan 28 23:31:03 caelinuxz420 systemd[1]: Starting Snappy daemon...
Jan 28 23:31:04 caelinuxz420 snapd[891]: AppArmor status: apparmor is enabled and all features are available
Jan 28 23:31:04 caelinuxz420 snapd[891]: 2020/01/28 23:31:04.178684 backend.go:112: snapd enabled NFS support, additional implicit
Jan 28 23:31:04 caelinuxz420 snapd[891]: 2020/01/28 23:31:04.442977 daemon.go:343: started snapd/2.34.2 (series 16; classic) ubunt
Jan 28 23:31:04 caelinuxz420 systemd[1]: Started Snappy daemon.
Jan 28 23:31:04 caelinuxz420 snapd[891]: 2020/01/28 23:31:04.444933 stateengine.go:101: state ensure error: Get https://api.snapcr
Jan 30 21:30:11 caelinuxz420 snapd[891]: 2020/01/30 21:30:11.313702 api.go:1046: Installing snap "p3x-onenote" revision unset
Jan 30 21:30:26 caelinuxz420 snapd[891]: 2020/01/30 21:30:26.600752 autorefresh.go:387: auto-refresh: all snaps are up-to-date
Jan 30 21:33:37 caelinuxz420 snapd[891]: 2020/01/30 21:33:37.135506 api.go:1046: Installing snap "p3x-onenote" revision unset
Jan 30 21:34:35 caelinuxz420 systemd[1]: Stopping Snappy daemon...
Jan 30 21:34:35 caelinuxz420 snapd[891]: 2020/01/30 21:34:35.565492 main.go:81: Exiting on terminated signal.
Jan 30 21:34:35 caelinuxz420 systemd[1]: Stopped Snappy daemon.
I’ve also tried uninstalling and re-installing p3x-onenote as well as uninstall and reinstall snapd but when it gets to trying to start the snap.socket, this is where and when it fails when I try to reinstall it.
Any help that the team would be able to provide in regards to how I can correct this issue would be greatly appreciated.
(I got the idea to run those commands from the other posts that I was able to find here, and tried them, and still to no avail, hence why I am starting yet another new topic with this error message.)
Thank you.