Cannot access host details: "host with empty platform"

[mpdeimos]

Fleet version: 4.17.0

Operating system: Ubuntu 20.04

Web browser: Chrome (latest)

---

🧑‍💻  Expected behavior

Access the host details page after update from 4.15 to 4.17

💥  Actual behavior

A loading spinner

More info

The console log is full with entries like:

 {"err":"host 38 with empty platform","level":"error","ts":"2022-07-14T06:30:04.860439335Z"}

Also the software inventory is also not loading.

Mysql is 5.7.36 (due to another issue I had to downgrade)

Everything was fine on 4.15

[lucasmrod]

Hi @mpdeimos!

There should also be logs for the requests that correspond to the loading spinner. Could you look for level=err logs around/after those? (the with empty platform error might be related, but that corresponds to ingestion of osquery data)

level=debug ts=2022-07-14T19:25:49.351925Z component=http user=[...] method=GET uri="/api/latest/fleet/hosts?[...]" took=23.270119ms

[lucasmrod]

Ah, sorry, you will need to run fleet with --logging_debug flag (or FLEET_LOGGING_DEBUG env var).

[mpdeimos]

I guess it's this line, this is the only error I get besides the other ones mentioned above.

{"component":"http","err":"load host software: select host software: context canceled","level":"error","method":"GET","took":"44.56295051s","ts":"2022-07-15T07:42:42.657673746Z","uri":"/api/latest/fleet/hosts/171","user":"xxx"}

[mpdeimos]

In addition there is a timeout error once the browser resets the connection

 {"component":"http","err":"write tcp 172.21.0.4:1337-\u003e172.21.0.3:40136: i/o timeout","level":"info","path":"/api/latest/fleet/hosts/171","ts":"2022-07-15T07:45:16.468235887Z"}

[RachelElysia]

@mpdeimos sorry, I'm just going to jump in here.

Is this error happening to a single host or multiple hosts?

[mpdeimos]

I would say for most hosts. It seems only the Arch Linux ones are loading. Ubuntu, Mac, WIndows, Debian fail.

[mpdeimos]

some additional info: the online status seems to report correctly

[polak785]

I have also this log for a host under Arch Linux, nothing with others (Ubuntu, Windows, MacOs)

The log reports every 10 seconds:

Aug  4 13:14:50 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:14:50.934723006Z"}
Aug  4 13:15:01 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:15:01.317589071Z"}
Aug  4 13:15:11 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:15:11.631241221Z"}
Aug  4 13:15:21 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:15:21.973528333Z"}
Aug  4 13:15:32 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:15:32.187294979Z"}
Aug  4 13:15:42 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:15:42.42346563Z"}
Aug  4 13:15:52 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:15:52.8306386Z"}
Aug  4 13:16:03 server01/server01 fleet[10808]: {"err":"host 554 with empty platform","level":"error","ts":"2022-08-04T13:16:03.176468481Z"}

[xpkoala]

@mpdeimos I'm sorry for the delay with the help on this one. Are you still experiencing the same trouble you originally reported? Have you attempted to upgrade to the latest fleet version, 4.19.1?

I'm in the process of standing up an arch linux machine to enroll and play with to see if I can recreate your issue. Any new information would help in that regard.

All the best!

[mpdeimos]

Not yet, I'm on vacation right now :)

But lemme clarify, Arch Linux worked, all other did not work.

[xpkoala]

Thank you for the update @mpdeimos. I haven't been able to reproduce your issue using a handful of different OS's. When you return from vacation could you please update to the latest release of Fleet and then report back if you are still encountering then broken manage hosts page?

[xpkoala]

Hi @mpdeimos. I wanted to check in and see if there was any update to this issue you encountered.

[mpdeimos]

I cannot reproduce atm. Will close for now.