Device configuration status "Modified" and eventually health status as "Problem"

[Jack]

Dear all,

When i register my access point on openwisp, the configuration status is showing "Modified" and  after around 5 minutes openwisp gives a notification saying that the configuration of device has not been applied in timely manner and then health status becomes "Problem".

But if in between I changed the name of device in openwisp , the configuration status becomes applied and health status becomes OK. But in this case, i am getting delayed notification related to device health eg: when I turn off the access point , openwisp gives this notification after 5-6 minutes.

Can anyone please explain what to do?

Thanks & Regards

Jack

[Jack]

In addition to above query:

For the first time registration, I don't get the above issue but after registration when I delete the device from openwisp using python shell and re-register it on the same openwisp then configuration status becomes modified and health status becomes problem as mentioned above.

Best Regards,

Jack

[Federico Capoano]

Alerts have a tolerance by default to avoid getting spammed, real world deployments can have frequent occasional hiccups, without tolerance this generates a very high volume of emails which always ends up with users ignoring or turning off emails altogether.

In the development version we have increased the tolerance to 30 minutes and have started batching email alerts every 4 hours.

If you want immediate emails you have to reduce the tolerance to zero but I don't recommend it.

Regarding the rest, I haven't understood what your problem is, if you could try to expand on it we could try to help, eg:

- I am doing X

- I am expecting Y

- But I get Z instead

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/8cf2b9a0-a6f6-46ad-a794-155b647c8459n%40googlegroups.com.

[Jack]

Dear Fed

we are using openwisp to manage access point in a local network (not connected to internet).

we are expecting real time notification pop-ups related to access point (such as device is unreachable) on the openwisp site , not using email. For that we have reduced run check time to 5 sec in settings.py file.

Even after reducing run check time , we have observed that when we register the device on openwisp , initially pop-ups appear within 5 sec time but after some time these pop-up NOTIFICATION GETS DELAYED by 2-4 minutes.

For us , getting these pop-ups as soon as possible is requirement.
How can we achieve this?

Thanks & Regards

Jack

[Federico Capoano]

You have to set the tolerance to 0, see:

https://openwisp.io/docs/24.11/monitoring/user/settings.html#openwisp-monitoring-metrics

That setting allows you to override the default metric configuration which you can consult here:

https://github.com/openwisp/openwisp-monitoring/blob/1.1/openwisp_monitoring/monitoring/configuration.py#L51-L664

I linked the information related to the stable version. The default tolerance in the dev version was increased:

https://github.com/openwisp/openwisp-monitoring/commit/d9183f5b18e2a20b4b3d0b426e634079aa49d2a0

The dev version also has email notification batching defaulting to 3 hours, keep this in mind if you want to upgrade to the new upcoming version once we release it, see:

https://openwisp.io/docs/dev/notifications/user/web-email-notifications.html#email-batches

https://openwisp.io/docs/dev/notifications/user/settings.html#openwisp-notifications-email-batch-interval

These new default settings are designed for busy systems with many devices but need to be all set to zero if you want immediate alerts.

Best regards

Federico Capoano

OpenWISP OÜ

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

VAT: EE101989729

+372 59361689

openwisp.io

To view this discussion, visit https://groups.google.com/d/msgid/openwisp/8ffafcd3-b5e4-4bf6-a713-57c1d355edban%40googlegroups.com.

[Iván Ledesma Obelar]

Hi everybody,

 

I plan to use openwisp to provide Internet access in a community centre in a rural area in Spain. The access point´s will be installed in the community centre itself, but the openwisp server will be in a virtual machine hosted on my Synology NAS at home.

 

Consequently I plan to use wireguard to get the devices to reach the server.

 

I managed to deploy the server on Ubuntu 24.04 and to register two access points that, for the time being, are connected to my home network.

 

These two devices are registered but following ping checks fail.

 

The wireguard network is 10.8.0.0/24 and the server is given 10.8.0.1, whereas the access points are given 10.8.0.2 and 10.8.0.3.

 

Although the server and the devices can ping each other in the home network 192.168.0.0/24, they are unable to ping each other via wireguard.

 

The problem seems to be a routing one, but I´m not sure to tweak the routing table of the server without asking first; if it was such an evident problem, it would be covered in the guides, wouldn´t it?

 

If I don´t find a solution, I will have to revert to installing the server in the community centre and not using VPN´s.

 

Regards,            

 

Iván Ledesma Obelar

 

 

[Iván Ledesma]