Messages

Yes, that is indeed strange. My guess is that the agent was fixed in the Azure Marketplace image at some point in the past, and by chance it managed to survive the latest updates.

Is there a contact point at Deciso that we can reach out to? Does anyone have any experience with this?

That's very strange. I hope the issue gets fixed. For now, I have no choice but to restore the VMs I've already updated. I hope Deciso fixes this soon... after all, we pay platform fees to Deciso for the license and the image, which are significantly higher than a "default" BE license. :-)

Hi,
I'm having a problem after updating our OPNSense VM to version 26.4. The installed Linux agent won't start anymore. Does anyone have any ideas on how I can fix this?

2025-03-19T15:28:42.961162Z ERROR TelemetryEventsCollector ExtHandler Event: name=WALinuxAgent, op=UnhandledError, message=Failure in collecting telemetry events: [Errno 2] No such file or directory: '/var/lib/waagent/events
', duration=0
ystemctl 025-03-19T15:30:41.434965Z WARNING TelemetryEventsCollector ExtHandler Error in _ProcessExtensionEvents: format_exception() got an unexpected keyword argument 'etype' --- [NOTE: Will not log the same error for the n
ext hour]
2025-03-19T15:30:51.291988Z INFO Daemon Daemon Agent WALinuxAgent-2.7.0.6 forwarding signal 15 to WALinuxAgent-2.7.0.6
2026-01-21T07:23:57.579618Z INFO Daemon Daemon Azure Linux Agent Version:2.7.0.6
2026-01-21T07:23:57.581052Z INFO Daemon Daemon OS: opnsense 25.1.3
2026-01-21T07:23:57.582858Z INFO Daemon Daemon Python: 3.11.11
2026-01-21T07:23:57.592054Z INFO Daemon Daemon Run daemon
2026-01-21T07:23:57.594450Z INFO Daemon Daemon No RDMA handler exists for distro='OPNsense' version='25.1.3'
2026-01-21T07:23:57.600250Z INFO Daemon Daemon Unable to get cloud-init enabled status from systemctl: [Errno 2] No such file or directory: 'systemctl'
2026-01-21T07:23:57.624740Z INFO Daemon Daemon Unable to get cloud-init enabled status from service: Command '['service', 'cloud-init', 'status']' returned non-zero exit status 1.
2026-01-21T07:23:57.625639Z INFO Daemon Daemon cloud-init is enabled: False
2026-01-21T07:23:57.627400Z INFO Daemon Daemon Using waagent for provisioning
2026-01-21T07:23:57.630945Z INFO Daemon Daemon Activate resource disk
2026-01-21T07:23:57.702169Z ERROR Daemon Daemon Command: [sysctl dev.storvsc | grep pnpinfo | grep deviceid=00000000-0001], return code: [1], result: []
2026-01-21T07:23:57.711264Z ERROR Daemon Daemon Command: [camcontrol periphlist 2:1:0], return code: [1], result: [camcontrol: cam_open_btl: no passthrough device found at 2:1:0
]
2026-01-21T07:23:57.719767Z ERROR Daemon Daemon Command: [camcontrol periphlist 3:1:0], return code: [1], result: [camcontrol: cam_open_btl: no passthrough device found at 3:1:0
]
2026-01-21T07:23:57.721081Z ERROR Daemon Daemon Failed to mount resource disk [ResourceDiskError] Unable to detect resource disk device:camcontrol: cam_open_btl: no passthrough device found at 3:1:0

2026-01-21T07:23:57.723330Z ERROR Daemon Daemon Event: name=WALinuxAgent, op=ActivateResourceDisk, message=[ResourceDiskError] Unable to detect resource disk device:camcontrol: cam_open_btl: no passthrough device found at 3:
1:0
, duration=0
2026-01-21T07:23:57.737278Z INFO Daemon Daemon Clean protocol and wireserver endpoint
2026-01-21T07:23:57.746195Z INFO Daemon Daemon Running default provisioning handler
2026-01-21T07:23:57.752897Z INFO Daemon Daemon Unable to get cloud-init enabled status from systemctl: [Errno 2] No such file or directory: 'systemctl'
2026-01-21T07:23:57.762640Z INFO Daemon Daemon Unable to get cloud-init enabled status from service: Command '['service', 'cloud-init', 'status']' returned non-zero exit status 1.
2026-01-21T07:23:57.765099Z INFO Daemon Daemon cloud-init is enabled: False

ok, thanks anyway!

Hi Patrick,

the agent was already installiert (as expected in the offical deciso Azure Image). I have reinstalled it anyway, but unfortunately the problem persists.

In the VM overview the agent itself seems to be fine, could it be a firewall problem? I don`t see a dropped packet in the log, but you never know.

not that I know of. The Azure Backup queries the snapshop status via the linux agent and probably gets no feedback there.

Hi,

i have a problem with a opnsense azure instance and cannot get azure backup to sucessfully backup the VM.  It keeps failing with error message "Could not communicate with the VM agent for snapshot status."

Any ideas how to fix this issue?