| rjschwei | Working on updating cloud-init in SUSE distros, first time since the switch to the socket based start up and the process is stuck, there is no log yet, how do I figure out what cloud-init is waiting for? | 11:47 |
|---|---|---|
| rjschwei | # journalctl --unit cloud-init-main.service May 03 10:20:21 ip-192-168-10-228 systemd[1]: Starting Cloud-init: Single Proce> May 03 10:20:23 ip-192-168-10-228 systemd[1]: Started Cloud-init: Single Proces> | 11:47 |
| === kuraudo1 is now known as kuraudo | ||
| falcojr | rjschwei: what does stuck mean? Has cloud-init-main.service started? Has cloud-init-local.service started? Are either of them still running? | 13:26 |
| falcojr | you should see new .sock files in /run/cloud-init/share . Do they exist? | 13:27 |
| rjschwei | Yes the .sock files exist and cloud-init-main.service is considered to be running by systemd. "stuck" means the process is waiting fro something, I think, but I do not know what thta would be. | 13:29 |
| falcojr | has cloud-init-local.service started? | 13:30 |
| rjschwei | cloud-init-local.service ran and has exited | 13:33 |
| falcojr | woah...it's weird that it ran and there's still nothing in the logs | 13:34 |
| rjschwei | systemctl status cloud-init-local.service .... Active: active (exited) s | 13:34 |
| falcojr | have any other cloud-init services run? e.g., cloud-init-network.service? | 13:34 |
| rjschwei | cloud-init-network.service also "active (exited)" | 13:35 |
| falcojr | does a journalctl -u on either of those services show anything interesting? | 13:36 |
| rjschwei | both show a help message for "nc" which would lead me to believe that something went wrong but both also show a "Finished Cloud-init: $NAME Stage" message | 13:39 |
| rjschwei | If I run the command from cloud-init-local.service in a shell I also get the help message but also 0 as the exit status | 13:41 |
| falcojr | hmmm, looks like you're running a version of netcat that doesn't support all of the options we're providing then. There's a link from https://docs.cloud-init.io/en/latest/reference/breaking_changes.html#single-process-optimization on how to replace that with a python call, but that probably also loses much of the performance benefit unfortunately | 13:43 |
| rjschwei | netcat-openbsd-1.203 what version is expected? | 13:47 |
| rjschwei | While performance improvements are nice it first and foremost has to work ;) | 13:48 |
| falcojr | hmmm, I would think that version should work. If you cat the cloud-init-local.service file and compare the options passed to what's in the help/man page, do you see any of the options missing? | 13:54 |
| rjschwei | Looks like the source socket does not exist "ls /run/cloud-init/share/local-return.sock" complains with "ls: cannot access " the options look OK to me based on the man page. | 14:02 |
| rjschwei | what would create "local-return.sock" | 14:02 |
| falcojr | the '-s /run/cloud-init/share/local-return.sock' part of netcat should create that socket file when invoked | 14:04 |
| blackboxsw | FWIW: netcat-openbsd 1.226-1.1 worksc | 14:07 |
| blackboxsw | I see netcat-openbsd 1.203 on opensuse 15.6. poking at that a bit now | 14:07 |
| rjschwei | OK, I am going to poke people as to why we do not have an updated netcat, at least for the upcoming new release and I am going to test the patch to move to Python and multi stage execution | 14:08 |
| blackboxsw | ly | 14:21 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!