Help me for debug on server openwisp

[Michele Salerno]

Hi,

I don't understand, it's a few routers....
in a few hours I have 99+ notifications
The connection is up and down all the time

I've emptied the openwisp logs to see if I can find anything with tail -f logs/* but I can't find anything.
Can you tell me how I can debug it?

A thousand times thanks to those who can help me.

Thanks.

Michele

[Federico Capoano]

The management VPN is unstable, either debug your VPN or increase the tolerance in the alert settings of the ping metric to 1 hour or more.

You can do both if you prefer.

F.

--
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/e27c7498-0199-4bb4-93cf-e5b265bd568c%40gmail.com.

[Michele Salerno]

Hi,

Before updating I did not have these problems.
Only on 2 routers I put the new version of openwrt

I find these errors:

root@openwisp:openwisp2 # cat log/* |grep error
[2025-02-25 17:47:30,915: ERROR/MainProcess] beat: Connection error: Error 111 connecting to localhost:6379. Connection refused.. Trying again in 2.0 seconds...
    fail(error)
    lambda error: self._disconnect_raise_connect(conn, error),
    raise error
    return conn.read_response(disconnect_on_error=False, push_request=True)
    fail(error)
    lambda error: self._disconnect_raise_connect(conn, error),
    raise error
    return conn.read_response(disconnect_on_error=False, push_request=True)
    fail(error)
    lambda error: self._disconnect_raise_connect(conn, error),
    raise error
    return conn.read_response(disconnect_on_error=False, push_request=True)
    fail(error)
    lambda error: self._disconnect_raise_connect(conn, error),
    raise error
    return conn.read_response(disconnect_on_error=False, push_request=True)
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -3] Temporary failure in name resolution
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -2] Name or service not known
socket.gaierror: [Errno -2] Name or service not known
    fail(error)
    fail(error)
    lambda error: self._disconnect_raise_connect(conn, error),
    raise error
    return conn.read_response(disconnect_on_error=False, push_request=True)
    fail(error)

Il 06/03/25 22:29, Federico Capoano ha scritto:

To view this discussion, visit https://groups.google.com/d/msgid/openwisp/CAAGgX6KU34CAJGbz5a43cMDAKk%3DZY_zG0Zz0wB7XO-uK38bacA%40mail.gmail.com.

-- 
Informativa Privacy - Ai sensi del D. Lgs n. 196/2003 (Codice Privacy) si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie.

Privacy Information - This message, for the D. Lgs n. 196/2003 (Privacy Code), may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.

[Federico Capoano]

We have updated a good number of instances, updating OpenWISP doesn't have to do anything with the stability of the VPN tunnel.

The errors in the log you shared seem to indicate a problem in DNS resolution when connecting to redis, double check your configuration.

F.

[Michele Salerno]

I have no doubt that the instances updated by you have no problems,
being the developers you know where to intervene for any problem.

Redis runs locally, why the DNS resolution if it is in localhost?
Redis is installed from the ansible playbook of openwisp.

Anyway I was just asking how to debug openwisp.
On routers with OpenWrt 23.05.4 I had no problems, now I have continuous
up and down problems. With the update done with ansible-openwisp2
something has changed.

I tried installing wireguard, it does the same thing with wireguard as well.


Il 06/03/25 23:01, Federico Capoano ha scritto:

[Federico Capoano]

Hi Michele,

On Fri, 7 Mar 2025 at 18:02, Michele Salerno <miky...@gmail.com> wrote:

I have no doubt that the instances updated by you have no problems,
being the developers you know where to intervene for any problem.

That doesn't mean anything, we also incur into issues from time to time.

If there was a bug like the one you are describing we would have noticed, so what I am trying to say is that it is most likely a misconfiguration, unless you can provide instructions on replicating the bug you're having.

 

Redis runs locally, why the DNS resolution if it is in localhost?
Redis is installed from the ansible playbook of openwisp.

Indeed the resolution is not the issue, the log points out the system can't connect to redis.

 

Anyway I was just asking how to debug openwisp.
On routers with OpenWrt 23.05.4 I had no problems, now I have continuous
up and down problems. With the update done with ansible-openwisp2
something has changed.

As you should know, the ansible role does not touch the configuration of your management VPN.

 

I tried installing wireguard, it does the same thing with wireguard as well.

Is the ping check hallucinating and inventing bad results? Or are there real VPN stability issues?

Assuming you backed up your system before upgrading, in the worst case scenario you could go back there.

F.