On some locked down versions Butler cannot get all sysinformation, leading to log errors

[mountaindude]

What version of Butler are you using?

9.2.3

What version of Node.js are you using? Not applicable if you use the standalone version of Butler.

What command did you use to start Butler?

What operating system are you using?

WIndows

What CPU architecture are you using?

Intel

What Qlik Sense versions are you using?

2023-Aug

Describe the Bug

Only observed on one server, but still.
Looks like Butler cannot get some network info from the OS. Probably because of this being a rather locked down server.

Expected Behavior

Make the reading of sys info more fault tolerant.

To Reproduce

No response

[mountaindude]

Looks like it's not a matter of permissions, but rather servers having multiple network interfaces, and the first one being disabled (or at least not having a full set of info).

Butler creates an anonymised id that represent this specific Butler instance from a telemetry perspective.
The id is created using a one-way hash function, starting with a set of server-specific info such as Mac address of the first network interface.
So, if that interface does not have a Mac address, we get the error above.

A more robust method would be to find the first network interface with a full set of info (e.g. Mac address etc), then use that network if.