lxd_troubleshooting
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
lxd_troubleshooting [2020/10/11 11:42] – neoon | lxd_troubleshooting [2021/11/25 22:42] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Network | + | === Process |
+ | Lookup the container who runs this process | ||
+ | grep -rn pid / | ||
+ | |||
+ | === Storage === | ||
+ | Error: The ‘default’ profile cannot be deleted | ||
+ | printf ' | ||
+ | |||
+ | Existing Parition, create new lvm storage pool | ||
+ | pvcreate /dev/sda2 | ||
+ | lxc storage create myPool lvm source=/ | ||
+ | |||
+ | === Network | ||
lxc network create vmbr03 | lxc network create vmbr03 | ||
Error: Unable to kill dnsmasq: Could not kill process: os: process not initialized | Error: Unable to kill dnsmasq: Could not kill process: os: process not initialized | ||
- | Check / | + | In my case, the network did not appear when I ran lxc network list.\\ |
+ | Check / | ||
rm -r vmbr03 | rm -r vmbr03 | ||
lxc network create vmbr03 | lxc network create vmbr03 | ||
Network vmbr03 created | Network vmbr03 created | ||
+ | | ||
+ | === Livepatch === | ||
+ | This machine ID is already enabled with a different key or is non-unique. | ||
+ | Or | ||
+ | error executing enable: cannot enable machine: bad temporary server status 500 | ||
+ | Likely you installed your VM with a template and the machine ID is not unique.\\ | ||
+ | But you can easy fix that.\\ | ||
+ | rm -f / | ||
+ | dbus-uuidgen --ensure=/ | ||
+ | rm / | ||
+ | dbus-uuidgen --ensure | ||
+ | | ||
+ | You need to reboot afterwards.\\ | ||
+ | **Warning: Some people say it might fuck up things.**\\ | ||
+ | So far it worked fine even on running LXD nodes (no clusters tested). |
lxd_troubleshooting.1602416578.txt.gz · Last modified: 2021/11/25 22:43 (external edit)