On Mon, Jul 16, 2018 at 4:30 PM, Reyk Floeter <r...@openbsd.org> wrote:

> https://www.openbsd.org/faq/current.html#r20180613b
>
> I can respond in more details when I’m back online later this week.
>
> Reyk
>
>
Thanks, Reyk. I missed that in the -CURRENT docs. Indeed, this clause seems
to work, as far as httpd starting:

-----
server "meta-data" {
        listen on 169.254.169.254 port 80
        fastcgi socket "/run/httpd.sock"
        root  "/"
        request strip 1
}
-----

I also added an alias of 169.254.168.254 to vether0 (not with
hostname.vether0, just from the command-line) and re-started httpd to see
what happens.

This is what I'm getting from cloud-init now:

         Starting Initial cloud-init job (metadata service crawler)...
[   10.292630] cloud-init[939]: Cloud-init v. 18.2 running 'init' at Thu,
19 Jul 2018 14:22:12 +0000. Up 5.16 seconds.
[   10.340633] cloud-init[939]: ci-info:
++++++++++++++++++++++++++++++++++++++Net device
info++++++++++++++++++++++++++++++++++++++
[   10.392636] cloud-init[939]: ci-info:
+--------+------+-----------------------------+---------------+-------+-------------------+
[   10.448639] cloud-init[939]: ci-info: | Device |  Up  |
Address           |      Mask     | Scope |     Hw-Address    |
[   10.504643] cloud-init[939]: ci-info:
+--------+------+-----------------------------+---------------+-------+-------------------+
[   10.560646] cloud-init[939]: ci-info: | enp0s4 | True |
10.13.37.47         | 255.255.255.0 |   .   | fe:e1:bb:d1:03:a8 |
[   10.620650] cloud-init[939]: ci-info: | enp0s4 | True |
fe80::fce1:bbff:fed1:3a8/64 |       .       |  link | fe:e1:bb:d1:03:a8 |
[   10.676654] cloud-init[939]: ci-info: |   lo   | True |
 127.0.0.1          |   255.0.0.0   |   .   |         .         |
[   10.728657] cloud-init[939]: ci-info: |   lo   | True |
::1/128           |       .       |  host |         .         |
[   10.784660] cloud-init[939]: ci-info:
+--------+------+-----------------------------+---------------+-------+-------------------+
[   10.840664] cloud-init[939]: ci-info: ++++++++++++++++++++++++++++Route
IPv4 info+++++++++++++++++++++++++++++
[   10.892667] cloud-init[939]: ci-info:
+-------+-------------+------------+---------------+-----------+-------+
[   10.940670] cloud-init[939]: ci-info: | Route | Destination |  Gateway
|    Genmask    | Interface | Flags |
[   10.992673] cloud-init[939]: ci-info:
+-------+-------------+------------+---------------+-----------+-------+
[   11.040676] cloud-init[939]: ci-info: |   0   |   0.0.0.0   | 10.13.37.1
|    0.0.0.0    |   enp0s4  |   UG  |
[   11.092680] cloud-init[939]: ci-info: |   1   |  10.13.37.0 |  0.0.0.0
| 255.255.255.0 |   enp0s4  |   U   |
[   11.140683] cloud-init[939]: ci-info:
+-------+-------------+------------+---------------+-----------+-------+
[   11.192686] cloud-init[939]: 2018-07-19 14:22:18,108 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]:
bad status code [404]
[   11.296692] cloud-init[939]: 2018-07-19 14:22:19,112 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]:
bad status code [404]
[   12.300755] cloud-init[939]: 2018-07-19 14:22:20,116 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]:
bad status code [404]
[   13.308818] cloud-init[939]: 2018-07-19 14:22:21,124 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [3/120s]:
bad status code [404]
[   14.312881] cloud-init[939]: 2018-07-19 14:22:22,128 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [4/120s]:
bad status code [404]
[   15.320944] cloud-init[939]: 2018-07-19 14:22:23,136 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [5/120s]:
bad status code [404]
[   17.329069] cloud-init[939]: 2018-07-19 14:22:25,145 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [7/120s]:
bad status code [404]
[   19.333195] cloud-init[939]: 2018-07-19 14:22:27,149 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [9/120s]:
bad status code [404]
[   21.541333] cloud-init[939]: 2018-07-19 14:22:29,357 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [11/120s]:
bad status code [404]
[   23.545458] cloud-init[939]: 2018-07-19 14:22:31,361 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [13/120s]:
bad status code [404]
[   26.141620] cloud-init[939]: 2018-07-19 14:22:33,957 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [15/120s]:
bad status code [404]
[   29.145808] cloud-init[939]: 2018-07-19 14:22:36,961 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [18/120s]:
bad status code [404]
[   32.149996] cloud-init[939]: 2018-07-19 14:22:39,965 -
url_helper.py[WARNING]: Calling '
http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [21/120s]:
bad status code [404]
[   35.150183] cloud-init[939]: 2018-07-19 14:25:18,300 -
DataSourceEc2.py[CRITICAL]: Giving up on md from ['
http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 180 seconds
[   40.202499] cloud-init[939]: 2018-07-19 14:25:23,352 - util.py[WARNING]:
Failed fetching meta-data/ from url http://10.13.37.1/latest/meta-data/
[   40.270503] cloud-init[939]: 2018-07-19 14:25:23,372 - util.py[WARNING]:
Failed to fetch password from virtual router 10.13.37.1
[   40.322506] cloud-init[939]: 2018-07-19 14:25:23,372 - util.py[WARNING]:
Getting data from <class
'cloudinit.sources.DataSourceCloudStack.DataSourceCloudStack'> failed
[  OK  ] Started Initial cloud-init job (metadata service crawler).

While Cloud-Init was querying meta-data, I attached ktrace to the child pid
to see if maybe I could unearth something (like a file path it's expecting
- I'm not particularly skilled at this level of troubleshooting) and just
got these 7 lines over and over again:

 17259 kfcgi    STRU  struct pollfd { fd=3, events=0x1<POLLIN>, revents=0<>
}
 17259 kfcgi    RET   poll 0
 17259 kfcgi    CALL  sigprocmask(SIG_BLOCK,0x84001<SIGHUP|SIGTERM|SIGCHLD>)
 17259 kfcgi    RET   sigprocmask 0<>
 17259 kfcgi    CALL
 sigprocmask(SIG_UNBLOCK,0x84001<SIGHUP|SIGTERM|SIGCHLD>)
 17259 kfcgi    RET   sigprocmask 0x84001<SIGHUP|SIGTERM|SIGCHLD>
 17259 kfcgi    CALL  poll(0xf134653c2e0,1,1000)

Reply via email to