It's worth noting, this had the same result as rebooting the entire machine. Landscape no longer produces a 503 error, the dashboard is served by the LXD juju-acf4dc-1 instance successfully. However, I am fully expecting this issue to reoccur after several weeks.
@Thomas - `lxc restart -f` worked. Output shown below:
ubuntu@ landscape- beta:~$ lxc list ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ landscape- beta:~$ lxc restart juju-acf4dc-1 -f landscape- beta:~$ lxc list ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+ ------- --+---- -----+- ------- ------- ------- -+----- -+----- ------+ ------- ----+
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| juju-0f524d-0 | RUNNING | 10.251.146.20 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-0 | RUNNING | 10.251.146.186 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-1 | RUNNING | | | CONTAINER | 0 |
+------
| juju-acf4dc-2 | RUNNING | 10.251.146.217 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-3 | RUNNING | 10.251.146.94 (eth0) | | CONTAINER | 0 |
+------
ubuntu@
ubuntu@
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| juju-0f524d-0 | RUNNING | 10.251.146.20 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-0 | RUNNING | 10.251.146.186 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-1 | RUNNING | 10.251.146.75 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-2 | RUNNING | 10.251.146.217 (eth0) | | CONTAINER | 0 |
+------
| juju-acf4dc-3 | RUNNING | 10.251.146.94 (eth0) | | CONTAINER | 0 |
+------
After running: `lxc exec juju-acf4dc-1 bash`: juju/machine- 1.log` I see: https:/ /pastebin. canonical. com/p/SWY7H3NMg g/ juju/machine- lock.log` I see: https:/ /pastebin. canonical. com/p/9nCGBBk6T 2/ juju/unit- landscape- server- 0.log` I see: https:/ /pastebin. canonical. com/p/244hzjndz j/
- For `cat /var/log/
- For `cat /var/log/
- For `cat /var/log/
It's worth noting, this had the same result as rebooting the entire machine. Landscape no longer produces a 503 error, the dashboard is served by the LXD juju-acf4dc-1 instance successfully. However, I am fully expecting this issue to reoccur after several weeks.