Bug: debian agent not sending report because it says it has no IP address

[trobbelke]

Hello,

I'm trying to run the agent on a Proxmox 8.4 server which is based on Debian 12.10 (I started with a Debian install and installed Proxmox on the fresh Debian install), but apparently the agent can't find the IP address? When I compare the log file with the log on a regular Debian VM, I don't see anything different, other than the line about the agent not having an IP address. Here is the log: openuem-agent: 2025/04/18 17:47:56 [INFO]: agent has read its settings from the INI file openuem-agent: 2025/04/18 17:47:56 [INFO]: agent has been started! openuem-agent: 2025/04/18 17:47:56 [INFO]: agent is run as root openuem-agent: 2025/04/18 17:47:56 [INFO]: config has been saved to /etc/openuem-agent/openuem.ini openuem-agent: 2025/04/18 17:47:56 [INFO]: task scheduler has started! openuem-agent: 2025/04/18 17:47:56 [INFO]: connection established with NATS server openuem-agent: 2025/04/18 17:47:56 [INFO]: Agent consumer is ready to serve openuem-agent: 2025/04/18 17:47:56 [INFO]: Subscribed to NATS subjects! openuem-agent: 2025/04/18 17:47:56 [INFO]: config has been saved to /etc/openuem-agent/openuem.ini openuem-agent: 2025/04/18 17:47:56 [DEBUG]: new default frequency is 60 openuem-agent: 2025/04/18 17:47:56 [INFO]: remote config requested openuem-agent: 2025/04/18 17:47:56 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> openuem-agent: 2025/04/18 17:47:56 [INFO]: agent is running a report... openuem-agent: 2025/04/18 17:47:56 [DEBUG]: preparing report info openuem-agent: 2025/04/18 17:47:56 [DEBUG]: report info ready openuem-agent: 2025/04/18 17:47:56 [DEBUG]: launching goroutines openuem-agent: 2025/04/18 17:47:56 [DEBUG]: update task info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: network adapters info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: update task info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: applications info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: computer system info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: printers info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: remote desktop info has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: monitors info has been requested openuem-agent: 2025/04/18 17:47:56 [INFO]: computer system info has been retrieved from SysInfo openuem-agent: 2025/04/18 17:47:56 [DEBUG]: serial number has been requested openuem-agent: 2025/04/18 17:47:56 [DEBUG]: operating system info has been requested openuem-agent: 2025/04/18 17:47:56 [INFO]: serial number info has been retrieved from SysInfo openuem-agent: 2025/04/18 17:47:56 [DEBUG]: processor info has been requested openuem-agent: 2025/04/18 17:47:56 [INFO]: OS installation date has been retrieved from Linux openuem-agent: 2025/04/18 17:47:56 [INFO]: system boot up time has been retrieved from Linux openuem-agent: 2025/04/18 17:47:56 [DEBUG]: username info has been requested openuem-agent: 2025/04/18 17:47:56 [INFO]: resolvectl status failed or not found openuem-agent: 2025/04/18 17:47:56 [INFO]: network adapters information has been retrieved from ethtool openuem-agent: 2025/04/18 17:47:56 [INFO]: processor info has been retrieved from SysInfo openuem-agent: 2025/04/18 17:47:56 [ERROR]: could not get user info, reason: user: unknown user openuem-agent: 2025/04/18 17:47:56 [INFO]: supported Remote Desktop service found: X11VNC openuem-agent: 2025/04/18 17:47:56 [INFO]: linux username has been retrieved from Linux openuem-agent: 2025/04/18 17:47:56 [INFO]: desktop apps information has been retrieved from package manager openuem-agent: 2025/04/18 17:47:57 [INFO]: printers information has been retrieved from Linux hwinfo openuem-agent: 2025/04/18 17:47:57 [INFO]: monitors information has been retrieved from Linux hwinfo openuem-agent: 2025/04/18 17:47:59 [INFO]: get pending security updates info has been retrieved openuem-agent: 2025/04/18 17:47:59 [DEBUG]: logical disks info has been requested openuem-agent: 2025/04/18 17:47:59 [DEBUG]: logical disk info started for: / openuem-agent: 2025/04/18 17:47:59 [INFO]: logical disks information has been retrieved from mountinfo openuem-agent: 2025/04/18 17:47:59 [WARN]: agent has no IP address, report won't be sent and we're flagging this so the watchdog can restart the service openuem-agent: 2025/04/18 17:47:59 [WARN]: the flag to restart the service by the watchdog has been raised

Now the output from the 'ip a' command is very different of course, Proxmox sets up bridges etc.

I installed this on a non-production machine so I can test code on it if necessary, and if you need any more info, please let me know.

Best Regards,

Johan

[doncicuto]

Hi, first of all thank you for testing OpenUEM and for opening the issue.

I've fixed a bug for the Debian agent four days ago that would be the reason of the error you're reporting.

If the agent cannot check the NIC speed (bridges or WLAN interfaces) it fails to continue and the IP address is not retrieved.

I'm preparing a new agent version next week that will include the fix once I test it thoroughly. If you'd like to have a fixed version right now I can provide you a compiled binary version of the current agent or give you instructions to compile the source code. Just let me know what you'd prefer so you can test it

Again, thanks for reporting this issue

[trobbelke]

ah that would make sense then, on a bridge interface. If you would like me to test it, with a compiled binary version, I can do that tomorrow.

Thanks for the quick response,

Best Regards, Johan

[doncicuto]

Cool, here is the download URL: https://downloads.openuem.eu/agents/testing/openuem-agent

The SHA256 hash for this file is: adcdc2b4360e381d09e8c44b049d24bfec7ee19bfbced5d6006a75233de54670

To use it please follow these instructions:

1) Stop the agent with systemctl stop openuem-agent 2) Replace the binary located at /opt/openuem-agent/bin/openuem-agent with this binary 3) Start the agent with systemctl start openuem-agent

Hope that the new binary fixes the issue and you can start getting the information from the agent. Sorry that I cannot provide you an updated package with the agent but I'm having a problem with my CI/CD so that's why I'm offering you the binary

Thanks!

[trobbelke]

Good morning,

I'm getting the exact same error message: openuem-agent: 2025/04/19 08:44:00 [WARN]: agent has no IP address, report won't be sent and we're flagging this so the watchdog can restart the service

Would it help you to know that in this setup, no physical interface has an IP address? Only a bridge interface has an IP address.

[doncicuto]

Hi there, could you add the following entry to your /etc/openuem-agent/openuem.ini config file, inside the Agent section, using the IP address assigned to the bridge?

IPAddress=x.x.x.x

Then restart the Agent and check if the report is finally sent

Thanks!

[trobbelke]

Good morning,

that works, and the endpoint gets picked up in the OpenUEM server immediately.

Best Regards, Johan

[doncicuto]

Excellent, I'll try to improve the bridge detection to avoid the IPAddress workaround for future versions.

Thanks for your feedback, I'll keep the issue opened until I find a good approach to the bridges issue