Config gets not applied, lots of "checksum mismatch" and "Local configuration outdated" in log

[MichaelUray]

Hi guys,

I have a GL.iNet GL-AR300M16 which does not apply its configuration.
It is connected to the Openwisp server (docker, edge) and it seems it receives its configuration on the router itself, but it does not apply it.

That is my log:

Wed Oct 22 21:00:14 2025 daemon.notice openwisp: management interface not ready (attempt 2 of 3)
Wed Oct 22 21:00:24 2025 daemon.notice openwisp: management interface not ready (attempt 3 of 3)
Wed Oct 22 21:00:24 2025 daemon.warn openwisp: could not determine ip address of management interface, giving up...
Wed Oct 22 21:00:25 2025 daemon.info openwisp: Local configuration outdated
Wed Oct 22 21:00:25 2025 daemon.info openwisp: Downloading configuration from controller...
Wed Oct 22 21:00:25 2025 daemon.err openwisp: Configuration checksum mismatch! Local: 32639b2e6f7fa84e41cff3a5fe9694e6, Remote: a5cde1ef01784ecd0b1e9af3e36527df
Wed Oct 22 21:02:26 2025 daemon.notice openwisp: management interface not ready (attempt 1 of 3)
Wed Oct 22 21:02:36 2025 daemon.notice openwisp: management interface not ready (attempt 2 of 3)
Wed Oct 22 21:02:46 2025 daemon.notice openwisp: management interface not ready (attempt 3 of 3)
Wed Oct 22 21:02:46 2025 daemon.warn openwisp: could not determine ip address of management interface, giving up...
Wed Oct 22 21:02:46 2025 daemon.info openwisp: Local configuration outdated
Wed Oct 22 21:02:46 2025 daemon.info openwisp: Downloading configuration from controller...
Wed Oct 22 21:02:47 2025 daemon.err openwisp: Configuration checksum mismatch! Local: 32639b2e6f7fa84e41cff3a5fe9694e6, Remote: a5cde1ef01784ecd0b1e9af3e36527df
Wed Oct 22 21:04:47 2025 daemon.notice openwisp: management interface not ready (attempt 1 of 3)
Wed Oct 22 21:04:57 2025 daemon.notice openwisp: management interface not ready (attempt 2 of 3)
Wed Oct 22 21:05:07 2025 daemon.notice openwisp: management interface not ready (attempt 3 of 3)
Wed Oct 22 21:05:07 2025 daemon.warn openwisp: could not determine ip address of management interface, giving up...
Wed Oct 22 21:05:08 2025 daemon.info openwisp: Local configuration outdated
Wed Oct 22 21:05:08 2025 daemon.info openwisp: Downloading configuration from controller...
Wed Oct 22 21:05:08 2025 daemon.err openwisp: Configuration checksum mismatch! Local: 32639b2e6f7fa84e41cff3a5fe9694e6, Remote: a5cde1ef01784ecd0b1e9af3e36527df

The configuration gets downloaded

9483C46400A1-fwr-lunzamsee:/tmp/openwisp# ls -lh /tmp/openwisp/
-rw-r--r--    1 root     root           0 Oct 22 20:11 bootup
-rw-r--r--    1 root     root         393 Oct 22 21:00 checksum
-rw-r--r--    1 root     root        4.2K Oct 22 20:59 configuration.tar.gz
drwxr-xr-x    2 root     root          40 Oct 22 21:00 monitoring
-rw-r--r--    1 root     root           0 Oct 22 20:11 monitoring-bootup
drwxr-xr-x    2 root     root          40 Oct 22 20:09 unmanaged

and it also has content when I extract it:

root@9483C46400A1-fwr-lunzamsee:/tmp/openwisp# sed -n '1,200p' /tmp/ow-inspect/etc/config/openvpn
config openvpn 'default'
        option auth 'SHA1'
        option ca '/etc/x509/ca-1-OpenWISP.pem'
        option cert '/etc/x509/client-0ef8fb4dcd7741e986e96c1c4ebbeedf.pem'
        option cipher 'none'
        option comp_lzo 'no'
        option dev 'tun1'
        option dev_type 'tun'
        option enabled '1'
        option fast_io '1'
        option float '0'
        option group 'nogroup'
        option keepalive '10 120'
        option key '/etc/x509/key-0ef8fb4dcd7741e986e96c1c4ebbeedf.pem'
        option mode 'p2p'
        option mssfix '1450'
        option mtu_test '0'
        option mute '0'
        option mute_replay_warnings '0'
        option nobind '1'
        option persist_key '1'
        option persist_tun '1'
        option proto 'udp'
        option pull '1'
        list remote 'openvpn.[snipped].com 1194'
        option reneg_sec '0'
        option resolv_retry 'infinite'
        option script_security '2'
        option tls_client '1'
        option tls_timeout '2'
        option user 'nobody'
        option verb '3'

There is not much space left, but it should be enough for small configuration files.

root@9483C46400A1-fwr-lunzamsee:/tmp/openwisp# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 4.0M      4.0M         0 100% /rom
tmpfs                    59.2M     33.9M     25.3M  57% /tmp
/dev/mtdblock5            9.3M      8.7M    640.0K  93% /overlay
overlayfs:/overlay        9.3M      8.7M    640.0K  93% /
tmpfs                   512.0K         0    512.0K   0% /dev
```

```
root@9483C46400A1-fwr-lunzamsee:/tmp/openwisp# opkg list | grep openwi
openwisp-config - 1.1.0-1
openwisp-monitoring - 0.2.1-1
```

Do you have any idea how to further debug that, or what could cause such an issue?
I did find the `verbose_mode` option, but that only works for the monitoring, but not for the config client.

[nemesifier]

Clear the cache with:

cd /opt/openwisp2 # or the directory where you installed openwisp
source env/bin/activate # if you are using the ansible role or python virtualenv
python manage.py clear_cache

Another workaround to clear the cache but only for the device where you're having this issue would be to edit something in the device configuration.

Let me know how it goes, I hope this helps.

This problem should be solved in the development version.

If anyone finds this problem in newer versions (from source code dating from October 2025 onwards), please let us know, a procedure to replicate the bug would be helpful.

[MichaelUray]

To change the configuration of a single device indeed helped for it.

I did run the following commands, but it did not apply the configuration on all the other devices.

root@dk2:~# docker ps | grep openwisp
81880ebdf250   openwisp/openwisp-nginx:edge             "/docker-entrypoint.…"   41 hours ago   Up 41 hours             80/tcp, 443/tcp                                                                                                             openwisp-nginx-1
6c6e97ff7d71   openwisp/openwisp-dashboard:edge         "bash init_command.sh"   41 hours ago   Up 41 hours                                                                                                                                         openwisp-celery_monitoring-1
20ca0d93a889   openwisp/openwisp-dashboard:edge         "bash init_command.sh"   41 hours ago   Up 41 hours                                                                                                                                         openwisp-celery-1
313206f93e91   openwisp/openwisp-api:edge               "bash init_command.sh"   41 hours ago   Up 41 hours             8001/tcp                                                                                                                    openwisp-api-1
5efba16efad0   openwisp/openwisp-websocket:edge         "supervisord --nodae…"   41 hours ago   Up 41 hours             8002/tcp                                                                                                                    openwisp-websocket-1
c60da3e9f41c   openwisp/openwisp-dashboard:edge         "bash init_command.sh"   41 hours ago   Up 41 hours             8000/tcp                                                                                                                    openwisp-celerybeat-1
90d084f20eff   openwisp/openwisp-dashboard:edge         "bash init_command.sh"   41 hours ago   Up 41 hours             8000/tcp                                                                                                                    openwisp-dashboard-1
1554ff7274e9   openwisp/openwisp-openvpn:edge           "sh init_command.sh"     41 hours ago   Up 41 hours (healthy)   1194/tcp, 1194/udp, 0.0.0.0:1195->1195/udp, [::]:1195->1195/udp                                                             openwisp-openvpn-1
74ffcec2c7aa   postgis/postgis:15-3.4-alpine            "docker-entrypoint.s…"   41 hours ago   Up 41 hours             5432/tcp                                                                                                                    openwisp-postgres-1
d1ba2f145916   redis:alpine                             "docker-entrypoint.s…"   41 hours ago   Up 41 hours             6379/tcp                                                                                                                    openwisp-redis-1
54416eb639a8   openwisp/openwisp-postfix:edge           "sh init_command.sh"     41 hours ago   Up 41 hours             25/tcp                                                                                                                      openwisp-postfix-1
907c8e9ff1ed   influxdb:1.8-alpine                      "/entrypoint.sh infl…"   41 hours ago   Up 41 hours             8086/tcp                                                                                                                    openwisp-influxdb-1

root@dk2:~# docker exec -it openwisp-celery_monitoring-1 bash -lc "cd /opt/openwisp && python manage.py clear_cache"
Cache "default" has been cleared!

root@dk2:~# docker exec -it openwisp-celery-1 bash -lc "cd /opt/openwisp && python manage.py clear_cache"
Cache "default" has been cleared!

root@dk2:~# docker exec -it openwisp-api-1 bash -lc "cd /opt/openwisp && python manage.py clear_cache"
Cache "default" has been cleared!

root@dk2:~# docker exec -it openwisp-celerybeat-1 bash -lc "cd /opt/openwisp && python manage.py clear_cache"
Cache "default" has been cleared!

root@dk2:~# docker exec -it openwisp-dashboard-1 bash -lc "cd /opt/openwisp && python manage.py clear_cache"
Cache "default" has been cleared!

[nemesifier]

The other devices will update their config only if there's an actual change.

If you think there's a bug and you want to help us detect it and fix it, please try to replicate it in a separate dev env: https://openwisp.io/docs/dev/controller/developer/installation.html#installing-for-development, if you can replicate it, please share with us the procedure so we can replicate it and find a solution for it. Thanks 🙏

[MichaelUray]

This problem should be solved in the development version.

I can confirm that the problem is gone in the current edge version.
Thanks a lot for your help.