Inconsistency in Device Health Status between List View and Detail View

[Logunath K]

Dear team,

                  I am writing to report a potential synchronization issue I've noticed in the OpenWISP2 dashboard regarding device health statuses.

Issue Description: In the main device list page, several devices are showing a "Critical" status. However, when I click on an individual device to view its overview page, the status correctly updates to "OK."

Interestingly, once I navigate back to the list page, the status for that specific device remains "OK." This suggests that the status is only being refreshed when the device's detail page is manually visited.

Technical Evidence: I have verified this discrepancy using the Python shell. Even when a device is physically reachable, the DeviceMonitoring model still reflects a stale "critical" status until the web interface triggers an update:

>>> from openwisp_monitoring.device.models import DeviceMonitoring
>>> d = DeviceMonitoring.objects.get(device__id='[DEVICE_UUID]')
>>> print(d.status)
critical

I've inspected the Celery task logs; all background processes appear to be running correctly without any reported failures.

regards,

logu

[Federico Capoano]

The health status turns to OK as soon as the device communicates with the server by sending a checksum request or it sends monitoring data, this triggers "device recovery detection", which makes the system execute monitoring checks again on the device.

Opening the device details page has no effect on the device health status, the only difference it makes is that refreshing the page gets the latest information.

So I am not really sure what problem you're pointing out.

Do you care to expand?

Best regards

Federico Capoano

OpenWISP OÜ

Kotkapoja tn 2a-10, 10615, Harju maakond, Tallinn, Estonia

VAT: EE101989729

+372 59361689

openwisp.io

--
You received this message because you are subscribed to the Google Groups "OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openwisp+u...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAJy2ivrVO9gBxiJLL0BR8n_ta9EZdsZwqzJhOSafE05MxHhHug%40mail.gmail.com.

[Logunath K]

Yes I will expand this, what I have seen in the application.

 I monitored a few specific devices (VPN IP pinging, metrics being sent) that remained 'Critical' in the List View (/admin/config/device/) for over 10 minutes. This is well beyond my 5-minute run_checks interval. But they were "OK" inside the "Detail VIew" page.

       The Test for specific device:

       1. In list page: The devices Health status showing " Critical"

       2. Before visiting the web page: I checked the Python shell. The database record for this device still showed status='critical'.

       3. During the visit: I navigated to the device Detail View (/change/). The status was showing 'OK'

        4. After the visit: I returned to the List View, and the status was now 'OK'. [Here is the catch for 1 and 4th point]

         Based on my observations, the status seems to refresh only when the detail page is opened manually. Is there another way to confirm this?          

Regards,

logu

To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6%2BRxb27EzBAaCp_-5g9GgVyKF0Nav-6FVgFJHyoxxWMUQ%40mail.gmail.com.

[Federico Capoano]

This is highly unlikely, if you refresh the list page instead of navigating to the detail page you'll observe the same result.

F.

To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAJy2ivr8XQ9V_%3DHN%2BJMFoY-bs%3D2%2BcF-O7xPuYpmqtHzFvYLYbA%40mail.gmail.com.

[Logunath K]

Thank you for your explanation.

This is actually where I first noticed the issue. Even though the device has a VPN IP and is responding to ping, the error is still appearing.

I refreshed the list page using a hard refresh (Ctrl + Shift + R), but the health status did not change. After receiving your email, I checked again, and the result is still the same.

That’s why I raised the question in the forum.

Could you please advise if there’s anything else I should verify from my side?

Regards,

logu

To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6JZabiBRQBfPEXWpB_cXgsgu35cdo5qwvgf_VDpvxCEMw%40mail.gmail.com.

[Federico Capoano]

AFAIK the UI does not affect device management and monitoring.

Make sure you're using the latest available version: 25.10.

If the issue persists we will need to replicate it in a development environment to validate it.

F.

To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAJy2ivq_4vgc%3Dphh7pSDwFy8-BA8XoAU5VYNciB7NgPcWP_hTg%40mail.gmail.com.