| 30 Dec 2019 |
 bgins | Oh yeah, that makes sense | 18:31:28 |
| bgins | Ok, I'm logged in | 18:31:43 |
 cmart | super. what does something like netstat -lntp show? anything on port 9090? | 18:32:06 |
| cmart | alternatively if you do something like curl -k https://localhost:9090 do you get anything back? | 18:32:31 |
| bgins | I don't see anything on 9090 and curl fails to connect | 18:33:20 |
| cmart | OK. so Cockpit probably didn't get installed. is this CentOS or Ubuntu? | 18:33:43 |
| bgins | Ubuntu | 18:33:49 |
| cmart | heavily_superb_trout? | 18:34:07 |
| bgins | yeah, that's the one | 18:34:16 |
| cmart | ok, i'm gonna try to share your console | 18:34:23 |
| cmart | cloud-init is supposed to set up cockpit so i'm trying to diagnose that.. | 18:36:09 |
| cmart | Exosphere passes something like the following to cloud-init
#cloud-config
users:
- default
- name: exouser
shell: /bin/bash
groups: sudo, admin
sudo: ['ALL=(ALL) NOPASSWD:ALL']
{ssh-authorized-keys}
packages:
- cockpit
runcmd:
- systemctl enable cockpit.socket
- systemctl start cockpit.socket
- systemctl daemon-reload
chpasswd:
list: |
exouser:ultimately-overruling-cub-funereally-wise-blackfish
expire: False
| 18:37:02 |
| bgins | Oh yeah, I saw that in the "Advanced" section of the setup | 18:37:31 |
| cmart | yeah. that YAML tells cloud-init what to do on first boot | 18:37:49 |
| bgins | Or something like it at least | 18:37:50 |
| cmart | at least it succeeded in setting up the exouser! because you logged in as that user | 18:38:14 |
| cmart | but the cockpit stuff did not verk | 18:38:26 |
 Julian Pistorius (Gitter) | @c-mart FYI I created an issue for this. Tyson reported the same thing. | 18:39:27 |
| cmart | aye! we're aware | 18:39:51 |
| Julian Pistorius (Gitter) | 👌 | 18:40:54 |
| cmart | cockpit didn't get intsalled. i'm looking through cloud-init.log but the console is small | 18:41:38 |
| bgins | Yeah, I'm following along. It is tiny :) | 18:43:00 |
| cmart | apt install cockpit worked | 18:43:54 |
| bgins | Yep, I am seeing the Terminal / Dashboard now | 18:44:21 |
| cmart | woohoo. that's what it's supposed to look like when this works | 18:44:45 |
| cmart | the question remains "why is cloud-init failing to install cockpit" | 18:45:05 |
| bgins | I'm only barely familiar with cloud-init, but it looks like you have it as a package in the boot script | 18:46:04 |
| cmart | cloud-init did set up a cockpit user | 18:49:13 |
| cmart | trying this on a new instance just for hehes and hahas. I stuck in a apt-get -y install cockpit at the beginning of the runcmd section, and commented out the packages: section
#cloud-config
users:
- default
- name: exouser
shell: /bin/bash
groups: sudo, admin
sudo: ['ALL=(ALL) NOPASSWD:ALL']
{ssh-authorized-keys}
# packages:
# - cockpit
runcmd:
- apt-get -y install cockpit
- systemctl enable cockpit.socket
- systemctl start cockpit.socket
- systemctl daemon-reload
chpasswd:
list: |
exouser:tactlessly-replete-bullfrog-proficiently-ample-broadbill
expire: False
| 18:53:10 |
| cmart | aha progress | 18:57:09 |
