Lxd init on new install does nothing

I have a VPS at SSDNodes. I reinstalled Ubuntu 18.04 on it, ran update, upgrade, autoremove and clean.
I then tried to configure lxd using the “lxd init”. The cursor moved to the next line and did nothing. It wasn’t flashing, it just sat there.
After more than 10 minutes it still hadn’t done anything. I tried “lxc list” and got the same result.
I did a “which lxd” and got /usr/bin/lxd
I did a “lxd --version” and got 3.0.3
I did a “which lxc” and got /usr/bin/lxc
I did a “lxc --version” and got 3.0.3
So why aren’t "lxd init"and “lxd list” working?

I also tried creating a container and got:
randall@server1:~$ lxc-create -n inglesnobrasil -t ubuntu
lxc-create: inglesnobrasil: parse.c: lxc_file_for_each_line_mmap: 100 No such file or directory - Failed to open file “/home/randall/.config/lxc/default.conf”
lxc-create: inglesnobrasil: utils.c: get_template_path: 918 No such file or directory - bad template: ubuntu
lxc-create: inglesnobrasil: lxccontainer.c: do_lxcapi_create: 1786 Unknown template “ubuntu”
lxc-create: inglesnobrasil: tools/lxc_create.c: main: 327 Failed to create container inglesnobrasil

Hi!

The LXD commands look like lxc launch ..., while the LXC commands are like lxc-create ....
I suggest to go for LXD.

I have written a few guides on running LXD on various hosting providers (VPS companies), and I have not covered SSD Nodes yet. See The LXD tutorials of Simos

If they accept Paypal, I’ll be happy to try them and write about it. In the meantime, have a look at my posts and try to follow the testing steps I show there.

From what you write, SSD Nodes likely uses the stock Ubuntu images so that should mean Ubuntu Linux kernel as well. I cannot think why LXD would not initialize.

what’s the output of lxc-checkconfig ?

First, I received a message that the command didn’t exist and I need to install utils, which I did. Then the result was:
randall@server1:~$ lxc-checkconfig
Kernel configuration not found at /proc/config.gz; searching…
Kernel configuration found at /boot/config-4.15.0-50-generic
— Namespaces —
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Network namespace: enabled

--- Control groups ---
Cgroups: enabled

Cgroup v1 mount points: 
/sys/fs/cgroup/systemd
/sys/fs/cgroup/blkio
/sys/fs/cgroup/memory
/sys/fs/cgroup/net_cls,net_prio
/sys/fs/cgroup/perf_event
/sys/fs/cgroup/hugetlb
/sys/fs/cgroup/freezer
/sys/fs/cgroup/pids
/sys/fs/cgroup/cpuset
/sys/fs/cgroup/devices
/sys/fs/cgroup/rdma
/sys/fs/cgroup/cpu,cpuacct

Cgroup v2 mount points: 
/sys/fs/cgroup/unified

Cgroup v1 clone_children flag: enabled
Cgroup device: enabled
Cgroup sched: enabled
Cgroup cpu account: enabled
Cgroup memory controller: enabled
Cgroup cpuset: enabled

--- Misc ---
Veth pair device: enabled, not loaded
Macvlan: enabled, not loaded
Vlan: enabled, not loaded
Bridges: enabled, loaded
Advanced netfilter: enabled, not loaded
CONFIG_NF_NAT_IPV4: enabled, loaded
CONFIG_NF_NAT_IPV6: enabled, not loaded
CONFIG_IP_NF_TARGET_MASQUERADE: enabled, loaded
CONFIG_IP6_NF_TARGET_MASQUERADE: enabled, not loaded
CONFIG_NETFILTER_XT_TARGET_CHECKSUM: enabled, loaded
CONFIG_NETFILTER_XT_MATCH_COMMENT: enabled, not loaded
FUSE (for use with lxcfs): enabled, not loaded

--- Checkpoint/Restore ---
checkpoint restore: enabled
CONFIG_FHANDLE: enabled
CONFIG_EVENTFD: enabled
CONFIG_EPOLL: enabled
CONFIG_UNIX_DIAG: enabled
CONFIG_INET_DIAG: enabled
CONFIG_PACKET_DIAG: enabled
CONFIG_NETLINK_DIAG: enabled
File capabilities: 

Note : Before booting a new kernel, you can check its configuration
usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig

all of this seems pretty normal to me. Try to reboot if it’s not already done and try

systemctl status lxd

Reboot didn’t seem to do any good. Here’s the result of the systemctl status lxd command.

randall@server1:~$ sudo lxd init
[sudo] password for randall: 
^C
randall@server1:~$ lxd init
^C
randall@server1:~$ systemctl status lxd
● lxd.service - LXD - main daemon
   Loaded: loaded (/lib/systemd/system/lxd.service; indirect; vendor preset: ena
   Active: activating (start-post) (Result: exit-code) since Wed 2019-08-07 19:0
     Docs: man:lxd(1)
  Process: 1534 ExecStart=/usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.lo
  Process: 1519 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load (co
 Main PID: 1534 (code=exited, status=1/FAILURE); Control PID: 1535 (lxd)
    Tasks: 7
   CGroup: /system.slice/lxd.service
           └─1535 /usr/lib/lxd/lxd waitready --timeout=600

Well, the lxd service seems to not have started successfully. Unfortunately you did not paste the full output so it’s not possible to see the return code of lxc-apparmor-load, for example.
If it’s a fail, could you check that /sys/kernel/security/apparmor/features/mount/mask does exist ?
if yes, can you try to start the load manually by

/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load

(edit: oups, I used an arm system to paste the first time)

Anyway, syslog should have information on a service that did not start correctly.

I copied and pasted all of the output that was displayed in the terminal.

If it’s a fail, could you check that /sys/kernel/security/apparmor/features/mount/mask does exist ?
if yes, can you try to start the load manually by

/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load

This is getting beyond my limited knowlwedge. Yes, /sys/kernel/security/apparmor/features/mount/mask does exist. When I ran /usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load as root, I got a request for password and then the cursor just went to the next line, which I interpreted as meaning the but I don’t know how to load manuall command executed successfully. But running lxd init still has the same result.

I guess than the system console is accessed only through a web interface, then.?
Here is how it appears on a truue console, see the difference ?

 lxd.service - LXD - main daemon
   Loaded: loaded (/lib/systemd/system/lxd.service; indirect; vendor preset: enabled)
   Active: active (running) since Tue 2019-08-06 15:11:52 CEST; 1 day 6h ago
     Docs: man:lxd(1)
  Process: 1253 ExecStartPost=/usr/bin/lxd waitready --timeout=600 (code=exited, status=0/SUCCESS)
  Process: 1251 ExecStartPre=/usr/lib/arm-linux-gnueabihf/lxc/lxc-apparmor-load (code=exited, status=0/SUCCESS)
 Main PID: 1252 (lxd)
   CGroup: /system.slice/lxd.service
           ├─1252 /usr/lib/lxd/lxd --group lxd --logfile=/var/log/lxd/lxd.log
           └─1349 dnsmasq --strict-order --bind-interfaces --pid-file=/var/lib/lxd/networks/lxdbr0/dnsmasq.pid --except-interface=lo --interface=lxdbr0 --quiet-dhcp --quiet-dhcp6 --quie

In your post it’s not possible to see the full line for ExecStartPre

Anyway, can you try to

  • reboot
  • immediately after, lxd init
  • then grab the 200 last lines of /varlog/syslog and paste them here.
Aug  7 20:35:27 server1 systemd[1]: Starting System Logging Service...
Aug  7 20:35:27 server1 systemd[1]: Starting LXD - container startup/shutdown...
Aug  7 20:35:27 server1 systemd[1]: Started Deferred execution scheduler.
Aug  7 20:35:27 server1 systemd[1]: Started Regular background program processing daemon.
Aug  7 20:35:27 server1 systemd[1]: Starting LSB: Record successful boot for GRUB...
Aug  7 20:35:27 server1 cron[765]: (CRON) INFO (pidfile fd = 3)
Aug  7 20:35:27 server1 systemd[1]: Starting Snappy daemon...
Aug  7 20:35:27 server1 systemd[1]: Starting Login Service...
Aug  7 20:35:27 server1 systemd[1]: Started FUSE filesystem for LXC.
Aug  7 20:35:27 server1 systemd[1]: Starting Accounts Service...
Aug  7 20:35:27 server1 systemd[1]: Started D-Bus System Message Bus.
Aug  7 20:35:27 server1 rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.32.0]
Aug  7 20:35:27 server1 rsyslogd: rsyslogd's groupid changed to 106
Aug  7 20:35:27 server1 rsyslogd: rsyslogd's userid changed to 102
Aug  7 20:35:27 server1 rsyslogd:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="753" x-info="http://www.rsyslog.com"] start
Aug  7 20:35:27 server1 cron[765]: (CRON) INFO (Running @reboot jobs)
Aug  7 20:35:27 server1 kernel: [   17.511480] new mount options do not match the existing superblock, will be ignored
Aug  7 20:35:27 server1 lxcfs[772]: mount namespace: 5
Aug  7 20:35:27 server1 lxcfs[772]: hierarchies:
Aug  7 20:35:27 server1 lxcfs[772]:   0: fd:   6: devices
Aug  7 20:35:27 server1 lxcfs[772]:   1: fd:   7: pids
Aug  7 20:35:27 server1 lxcfs[772]:   2: fd:   8: rdma
Aug  7 20:35:27 server1 lxcfs[772]:   3: fd:   9: hugetlb
Aug  7 20:35:27 server1 lxcfs[772]:   4: fd:  10: memory
Aug  7 20:35:27 server1 lxcfs[772]:   5: fd:  11: freezer
Aug  7 20:35:27 server1 lxcfs[772]:   6: fd:  12: perf_event
Aug  7 20:35:27 server1 lxcfs[772]:   7: fd:  13: cpu,cpuacct
Aug  7 20:35:27 server1 lxcfs[772]:   8: fd:  14: blkio
Aug  7 20:35:27 server1 lxcfs[772]:   9: fd:  15: net_cls,net_prio
Aug  7 20:35:27 server1 lxcfs[772]:  10: fd:  16: cpuset
Aug  7 20:35:27 server1 lxcfs[772]:  11: fd:  17: name=systemd
Aug  7 20:35:27 server1 lxcfs[772]:  12: fd:  18: unified
Aug  7 20:35:26 server1 systemd-timesyncd[650]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
Aug  7 20:35:26 server1 dbus-daemon[774]: [system] AppArmor D-Bus mediation is enabled
Aug  7 20:35:26 server1 systemd[1]: Started ZFS Event Daemon (zed).
Aug  7 20:35:26 server1 systemd[1]: Starting ZFS file system shares...
Aug  7 20:35:26 server1 systemd[1]: Started irqbalance daemon.
Aug  7 20:35:26 server1 systemd[1]: Started Network Name Resolution.
Aug  7 20:35:26 server1 systemd[1]: Started System Logging Service.
Aug  7 20:35:26 server1 systemd[1]: Started ZFS file system shares.
Aug  7 20:35:26 server1 systemd[1]: Started Login Service.
Aug  7 20:35:26 server1 systemd[1]: Reached target ZFS startup target.
Aug  7 20:35:26 server1 systemd[1]: Reached target Network.
Aug  7 20:35:26 server1 grub-common[766]:  * Recording successful boot for GRUB
Aug  7 20:35:26 server1 systemd[1]: Started Unattended Upgrades Shutdown.
Aug  7 20:35:26 server1 zed[804]: ZFS Event Daemon 0.7.5-1ubuntu16.6 (PID 804)
Aug  7 20:35:26 server1 zed[804]: Processing events since eid=0
Aug  7 20:35:26 server1 systemd[1]: Reached target Host and Network Name Lookups.
Aug  7 20:35:26 server1 dbus-daemon[774]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.4' (uid=0 pid=773 comm="/usr/lib/accountsservice/accounts-daemon " label="unconfined")
Aug  7 20:35:26 server1 systemd[1]: Starting Authorization Manager...
Aug  7 20:35:26 server1 grub-common[766]:    ...done.
Aug  7 20:35:26 server1 systemd[1]: Started LSB: Record successful boot for GRUB.
Aug  7 20:35:26 server1 polkitd[823]: started daemon version 0.105 using authority implementation `local' version `0.105'
Aug  7 20:35:26 server1 dbus-daemon[774]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug  7 20:35:26 server1 systemd[1]: Started Authorization Manager.
Aug  7 20:35:26 server1 accounts-daemon[773]: started daemon version 0.6.45
Aug  7 20:35:26 server1 systemd[1]: Started Accounts Service.
Aug  7 20:35:26 server1 snapd[770]: AppArmor status: apparmor is enabled and all features are available
Aug  7 20:35:26 server1 snapd[770]: daemon.go:379: started snapd/2.39.2+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-50-generic.
Aug  7 20:35:26 server1 systemd[1]: Started Snappy daemon.
Aug  7 20:35:26 server1 systemd[1]: Starting Wait until snapd is fully seeded...
Aug  7 20:35:26 server1 systemd[1]: Started LXD - container startup/shutdown.
Aug  7 20:35:26 server1 networkd-dispatcher[748]: No valid path found for iwconfig
Aug  7 20:35:26 server1 systemd[1]: Started Wait until snapd is fully seeded.
Aug  7 20:35:26 server1 systemd[1]: Started Dispatcher daemon for systemd-networkd.
Aug  7 20:35:27 server1 systemd-networkd[654]: ens3: Gained IPv6LL
Aug  7 20:35:27 server1 systemd-networkd[654]: ens3: Configured
Aug  7 20:35:27 server1 systemd-timesyncd[650]: Network configuration changed, trying to establish connection.
Aug  7 20:35:27 server1 systemd-networkd-wait-online[696]: managing: ens3
Aug  7 20:35:27 server1 systemd-networkd-wait-online[696]: ignoring: lo
Aug  7 20:35:27 server1 systemd[1]: Started Wait for Network to be Configured.
Aug  7 20:35:27 server1 systemd[1]: Reached target Network is Online.
Aug  7 20:35:27 server1 systemd[1]: Starting LXC network bridge setup...
Aug  7 20:35:27 server1 systemd[1]: Starting /etc/rc.local Compatibility...
Aug  7 20:35:27 server1 systemd[1]: Starting Availability of block devices...
Aug  7 20:35:27 server1 systemd[1]: Reached target Remote File Systems (Pre).
Aug  7 20:35:27 server1 systemd[1]: Reached target Remote File Systems.
Aug  7 20:35:27 server1 systemd[1]: Starting LSB: automatic crash report generation...
Aug  7 20:35:27 server1 systemd[1]: Starting LSB: QEMU Guest Agent startup script...
Aug  7 20:35:27 server1 systemd[1]: Starting Permit User Sessions...
Aug  7 20:35:27 server1 systemd[1]: Starting OpenBSD Secure Shell server...
Aug  7 20:35:27 server1 systemd[1]: Started Availability of block devices.
Aug  7 20:35:27 server1 systemd[1]: Started Permit User Sessions.
Aug  7 20:35:27 server1 apport[957]:  * Starting automatic crash report generation: apport
Aug  7 20:35:27 server1 systemd[1]: Started /etc/rc.local Compatibility.
Aug  7 20:35:27 server1 systemd[1]: Starting Hold until boot process finishes up...
Aug  7 20:35:27 server1 systemd[1]: Starting Terminate Plymouth Boot Screen...
Aug  7 20:35:27 server1 systemd[1]: Started Hold until boot process finishes up.
Aug  7 20:35:27 server1 systemd[1]: Starting Set console scheme...
Aug  7 20:35:27 server1 systemd-timesyncd[650]: Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com).
Aug  7 20:35:27 server1 systemd[1]: Started Terminate Plymouth Boot Screen.
Aug  7 20:35:27 server1 apport[957]:    ...done.
Aug  7 20:35:27 server1 systemd[1]: Started LSB: automatic crash report generation.
Aug  7 20:35:27 server1 systemd[1]: Started Set console scheme.
Aug  7 20:35:27 server1 systemd[1]: Started LSB: QEMU Guest Agent startup script.
Aug  7 20:35:27 server1 systemd[1]: Created slice system-getty.slice.
Aug  7 20:35:27 server1 systemd[1]: Started Getty on tty1.
Aug  7 20:35:27 server1 systemd[1]: Reached target Login Prompts.
Aug  7 20:35:27 server1 kernel: [   18.794733] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Aug  7 20:35:27 server1 systemd[1]: Started OpenBSD Secure Shell server.
Aug  7 20:35:27 server1 systemd-udevd[1034]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug  7 20:35:27 server1 systemd-udevd[1034]: Could not generate persistent MAC address for lxcbr0: No such file or directory
Aug  7 20:35:27 server1 systemd-timesyncd[650]: Network configuration changed, trying to establish connection.
Aug  7 20:35:27 server1 kernel: [   18.806972] IPv6: ADDRCONF(NETDEV_UP): lxcbr0: link is not ready
Aug  7 20:35:27 server1 networkd-dispatcher[748]: WARNING:Unknown index 3 seen, reloading interface list
Aug  7 20:35:27 server1 kernel: [   18.850672] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
Aug  7 20:35:27 server1 systemd-timesyncd[650]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com).
Aug  7 20:35:27 server1 dnsmasq[1074]: started, version 2.79 cachesize 150
Aug  7 20:35:27 server1 dnsmasq[1074]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify
Aug  7 20:35:27 server1 dnsmasq-dhcp[1074]: DHCP, IP range 10.0.3.2 -- 10.0.3.254, lease time 1h
Aug  7 20:35:27 server1 dnsmasq-dhcp[1074]: DHCP, sockets bound exclusively to interface lxcbr0
Aug  7 20:35:27 server1 dnsmasq[1074]: reading /etc/resolv.conf
Aug  7 20:35:27 server1 dnsmasq[1074]: using nameserver 8.8.8.8#53
Aug  7 20:35:27 server1 dnsmasq[1074]: read /etc/hosts - 5 addresses
Aug  7 20:35:27 server1 systemd[1]: Started LXC network bridge setup.
Aug  7 20:35:27 server1 systemd[1]: Starting LXC Container Initialization and Autoboot Code...
Aug  7 20:35:27 server1 systemd[1]: Started LXC Container Initialization and Autoboot Code.
Aug  7 20:35:27 server1 systemd[1]: Reached target Multi-User System.
Aug  7 20:35:27 server1 systemd[1]: Reached target Graphical Interface.
Aug  7 20:35:27 server1 systemd[1]: Starting Update UTMP about System Runlevel Changes...
Aug  7 20:35:27 server1 systemd[1]: Started Update UTMP about System Runlevel Changes.
Aug  7 20:35:27 server1 systemd[1]: Startup finished in 13.394s (kernel) + 5.908s (userspace) = 19.303s.
Aug  7 20:35:31 server1 snapd[770]: daemon.go:611: gracefully waiting for running hooks
Aug  7 20:35:31 server1 snapd[770]: daemon.go:613: done waiting for running hooks
Aug  7 20:35:31 server1 snapd[770]: daemon stop requested to wait for socket activation
Aug  7 20:35:32 server1 prl_nettool[1135]: call: prl_nettool prl_nettool set --hostname server1.rpaserver1.com --ip 00:1c:42:f5:19:dc 209.182.233.167/255.255.255.0 --gateway 00:1c:42:f5:19:dc "209.182.233.1 " --dns 00:1c:42:f5:19:dc 8.8.8.8
Aug  7 20:35:32 server1 prl_nettool[1147]: call: prl_nettool prl_nettool
Aug  7 20:35:32 server1 systemd[1]: Stopped Wait for Network to be Configured.
Aug  7 20:35:32 server1 systemd[1]: Stopping Network Service...
Aug  7 20:35:32 server1 systemd-timesyncd[650]: Network configuration changed, trying to establish connection.
Aug  7 20:35:32 server1 systemd[1]: Stopped Network Service.
Aug  7 20:35:32 server1 systemd[1]: Starting Network Service...
Aug  7 20:35:33 server1 systemd-networkd[1174]: ens3: Gained IPv6LL
Aug  7 20:35:33 server1 systemd-networkd[1174]: Enumeration completed
Aug  7 20:35:33 server1 systemd[1]: Started Network Service.
Aug  7 20:35:33 server1 systemd-timesyncd[650]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com).
Aug  7 20:35:33 server1 systemd-networkd[1174]: lxcbr0: Link is not managed by us
Aug  7 20:35:33 server1 systemd-networkd[1174]: lo: Link is not managed by us
Aug  7 20:35:33 server1 systemd-timesyncd[650]: Network configuration changed, trying to establish connection.
Aug  7 20:35:33 server1 systemd-networkd[1174]: ens3: Configured
Aug  7 20:35:33 server1 systemd[1]: Stopping Network Service...
Aug  7 20:35:33 server1 systemd[1]: Stopped Network Service.
Aug  7 20:35:33 server1 systemd[1]: Starting Network Service...
Aug  7 20:35:33 server1 systemd-networkd[1208]: ens3: Gained IPv6LL
Aug  7 20:35:33 server1 systemd-networkd[1208]: Enumeration completed
Aug  7 20:35:33 server1 systemd[1]: Started Network Service.
Aug  7 20:35:33 server1 systemd-networkd[1208]: lo: Link is not managed by us
Aug  7 20:35:33 server1 systemd-networkd[1208]: lxcbr0: Link is not managed by us
Aug  7 20:35:33 server1 systemd-networkd[1208]: ens3: Configured
Aug  7 20:35:33 server1 dnsmasq[1074]: no servers found in /etc/resolv.conf, will retry
Aug  7 20:35:33 server1 dnsmasq[1074]: reading /etc/resolv.conf
Aug  7 20:35:33 server1 dnsmasq[1074]: using nameserver 8.8.8.8#53
Aug  7 20:35:48 server1 kernel: [   39.955577] random: crng init done
Aug  7 20:35:48 server1 kernel: [   39.955584] random: 7 urandom warning(s) missed due to ratelimiting
Aug  7 20:35:49 server1 systemd[1]: Created slice User Slice of randall.
Aug  7 20:35:49 server1 systemd[1]: Starting User Manager for UID 1000...
Aug  7 20:35:49 server1 systemd[1]: Started Session 1 of user randall.
Aug  7 20:35:49 server1 systemd[1276]: Reached target Paths.
Aug  7 20:35:49 server1 systemd[1276]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug  7 20:35:49 server1 systemd[1276]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Aug  7 20:35:49 server1 systemd[1276]: Listening on GnuPG network certificate management daemon.
Aug  7 20:35:49 server1 systemd[1276]: Listening on GnuPG cryptographic agent and passphrase cache.
Aug  7 20:35:49 server1 systemd[1276]: Reached target Timers.
Aug  7 20:35:49 server1 systemd[1276]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Aug  7 20:35:49 server1 systemd[1276]: Reached target Sockets.
Aug  7 20:35:49 server1 systemd[1276]: Reached target Basic System.
Aug  7 20:35:49 server1 systemd[1276]: Reached target Default.
Aug  7 20:35:49 server1 systemd[1276]: Startup finished in 112ms.
Aug  7 20:35:49 server1 systemd[1]: Started User Manager for UID 1000.
Aug  7 20:36:10 server1 systemd[1]: Starting LXD - main daemon...
Aug  7 20:36:10 server1 kernel: [   61.887060] kauditd_printk_skb: 10 callbacks suppressed
Aug  7 20:36:10 server1 kernel: [   61.887062] audit: type=1400 audit(1565210170.371:22): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/bin/lxc-start" pid=1442 comm="apparmor_parser"
Aug  7 20:36:10 server1 kernel: [   61.900140] audit: type=1400 audit(1565210170.383:23): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="lxc-container-default" pid=1446 comm="apparmor_parser"
Aug  7 20:36:10 server1 kernel: [   61.900146] audit: type=1400 audit(1565210170.383:24): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="lxc-container-default-cgns" pid=1446 comm="apparmor_parser"
Aug  7 20:36:10 server1 kernel: [   61.900149] audit: type=1400 audit(1565210170.383:25): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="lxc-container-default-with-mounting" pid=1446 comm="apparmor_parser"
Aug  7 20:36:10 server1 kernel: [   61.900152] audit: type=1400 audit(1565210170.383:26): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="lxc-container-default-with-nesting" pid=1446 comm="apparmor_parser"
Aug  7 20:36:10 server1 lxd[1447]: Error: Log file path doesn't exist: /var/log/lxd
Aug  7 20:36:10 server1 systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE
Aug  7 20:36:42 server1 systemd[1]: Stopping User Manager for UID 1000...
Aug  7 20:36:42 server1 systemd[1276]: Stopped target Default.
Aug  7 20:36:42 server1 systemd[1276]: Stopped target Basic System.
Aug  7 20:36:42 server1 systemd[1276]: Stopped target Timers.
Aug  7 20:36:42 server1 systemd[1276]: Stopped target Paths.
Aug  7 20:36:42 server1 systemd[1276]: Stopped target Sockets.
Aug  7 20:36:42 server1 systemd[1276]: Closed GnuPG network certificate management daemon.
Aug  7 20:36:42 server1 systemd[1276]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug  7 20:36:42 server1 systemd[1276]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Aug  7 20:36:42 server1 systemd[1276]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Aug  7 20:36:42 server1 systemd[1276]: Closed GnuPG cryptographic agent and passphrase cache.
Aug  7 20:36:42 server1 systemd[1276]: Reached target Shutdown.
Aug  7 20:36:42 server1 systemd[1276]: Starting Exit the Session...
Aug  7 20:36:42 server1 systemd[1276]: Received SIGRTMIN+24 from PID 1470 (kill).
Aug  7 20:36:42 server1 systemd[1]: Stopped User Manager for UID 1000.
Aug  7 20:36:42 server1 systemd[1]: Removed slice User Slice of randall.
Aug  7 20:37:18 server1 systemd[1]: Created slice User Slice of root.
Aug  7 20:37:18 server1 systemd[1]: Starting User Manager for UID 0...
Aug  7 20:37:18 server1 systemd[1]: Started Session 3 of user root.
Aug  7 20:37:18 server1 systemd[1473]: Reached target Timers.
Aug  7 20:37:18 server1 systemd[1473]: Reached target Paths.
Aug  7 20:37:18 server1 systemd[1473]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Aug  7 20:37:18 server1 systemd[1473]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Aug  7 20:37:18 server1 systemd[1473]: Listening on GnuPG network certificate management daemon.
Aug  7 20:37:18 server1 systemd[1473]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug  7 20:37:18 server1 systemd[1473]: Listening on GnuPG cryptographic agent and passphrase cache.
Aug  7 20:37:18 server1 systemd[1473]: Reached target Sockets.
Aug  7 20:37:18 server1 systemd[1473]: Reached target Basic System.
Aug  7 20:37:18 server1 systemd[1473]: Reached target Default.
Aug  7 20:37:18 server1 systemd[1473]: Startup finished in 31ms.
Aug  7 20:37:18 server1 systemd[1]: Started User Manager for UID 0.

very strange, can you try
sudo mkdir /var/log/lxd
then
sudo systemctl start lxd

When I did this, it just froze like the lxd init command does. I then ran systemctl status lxd and got the info below. This time I widened my terminal window and hopefully everything is now there.

randall@server1:~$ sudo systemctl start lxd
^C
randall@server1:~$ systemctl status lxd
● lxd.service - LXD - main daemon
   Loaded: loaded (/lib/systemd/system/lxd.service; indirect; vendor preset: enabled)
   Active: activating (start-post) (Result: exit-code) since Wed 2019-08-07 21:26:11 UTC; 8min ago
     Docs: man:lxd(1)
  Process: 1921 ExecStart=/usr/bin/lxd --group lxd --logfile=/var/log/lxd/lxd.log (code=exited, status=1/FAILURE)
  Process: 1907 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load (code=exited, status=0/SUCCESS)
 Main PID: 1921 (code=exited, status=1/FAILURE); Control PID: 1922 (lxd)
    Tasks: 8
   CGroup: /system.slice/lxd.service
           └─1922 /usr/lib/lxd/lxd waitready --timeout=600

the lxd.log file in the directory you had me make has:
t=2019-08-07T21:36:11+0000 lvl=info msg=“LXD 3.0.3 is starting in normal mode” path=/var/lib/lxd
t=2019-08-07T21:36:11+0000 lvl=info msg=“Kernel uid/gid map:”
t=2019-08-07T21:36:11+0000 lvl=info msg=" - u 0 0 4294967295"
t=2019-08-07T21:36:11+0000 lvl=info msg=" - g 0 0 4294967295"
t=2019-08-07T21:36:11+0000 lvl=info msg=“Configured LXD uid/gid map:”
t=2019-08-07T21:36:11+0000 lvl=info msg=" - u 0 100000 65536"
t=2019-08-07T21:36:11+0000 lvl=info msg=" - g 0 100000 65536"
t=2019-08-07T21:36:11+0000 lvl=warn msg=“CGroup memory swap accounting is disabled, swap limits will be ignored.”
t=2019-08-07T21:36:11+0000 lvl=info msg=“Kernel features:”
t=2019-08-07T21:36:11+0000 lvl=info msg=" - netnsid-based network retrieval: no"
t=2019-08-07T21:36:11+0000 lvl=info msg=" - unprivileged file capabilities: yes"
t=2019-08-07T21:36:11+0000 lvl=info msg=“Initializing local database”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Starting /dev/lxd handler:”
t=2019-08-07T21:36:17+0000 lvl=info msg=" - binding devlxd socket" socket=/var/lib/lxd/devlxd/sock
t=2019-08-07T21:36:17+0000 lvl=info msg=“REST API daemon:”
t=2019-08-07T21:36:17+0000 lvl=info msg=" - binding Unix socket" inherited=true socket=/var/lib/lxd/unix.socket
t=2019-08-07T21:36:17+0000 lvl=info msg=“Initializing global database”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Initializing storage pools”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Initializing networks”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Pruning leftover image files”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Done pruning leftover image files”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Loading daemon configuration”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Pruning expired images”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Done pruning expired images”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Updating instance types”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Done updating instance types”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Expiring log files”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Done expiring log files”
t=2019-08-07T21:36:17+0000 lvl=info msg=“Updating images”

I just tried lxd init AND IT WORKED!

Well, that’s not surprising since the lxd.log file you quoted shows just a normal start of the lxd daemon. Once it could log, it started.
What’s very difficult to understand is that the normal lxd log directory was not created.

Thanks for your help. But I’ve got a question. I’m just learning about using containers and I’m using this SSDNodes VPS to experiment. I’ll undoubtedly reinstall the server several times while I’m experimenting. What do I need to do each time I do a reinstall to make sure it works. Do I just need to make sure that directory /var/log/lxd is there and if it isn’t, make it?

It’s quite clear that this missing directory was the culprit, from the log:

Aug  7 20:36:10 server1 lxd[1447]: Error: Log file path doesn't exist: /var/log/lxd
Aug  7 20:36:10 server1 systemd[1]: lxd.service: Main process exited, code=exited, status=1/FAILURE

so yes, if your install everything again and this directory is missng, you have to create it and it should work. This said, if you really see this, you could ask your provider’s support if this comes from their specific sauce, and if they are adamant they have nothing to do with that, raise an Ubuntu bug. It’s not normal.

OK and thanks again!!!

@rpallen Can you verify whether this missing LXD directory is an issue of the Ubuntu 18.04 image of SSD Nodes? That is, they may be doing something with the images, like clearing the /bar, etc.

It does not look they offer a per-hour rate, so will not try them.