when there is not any conectivity to network this loop is happening that has not handled in code
mahdidadashi65 opened this issue · 5 comments
[2023/04/03 12:32:35:9243] N: __lws_lc_tag: ++ [wsicli|3|WS/h1/default/10.19.1.15] (1)
[2023/04/03 12:32:35:9243] N: [wsicli|3|WS/h1/default/10.19.1.15]: lws_sort_dns: 10.19.1.15 has no route out
[2023/04/03 12:32:35:9243] N: [wsicli|3|WS/h1/default/10.19.1.15]: lws_sort_dns_dump: empty
[2023/04/03 12:32:35:9243] N: __lws_lc_untag: -- [wsicli|3|WS/h1/default/10.19.1.15] (0) 53μs
[2023/04/03 12:32:37:0555] N: __lws_lc_tag: ++ [wsicli|4|WS/h1/default/10.19.1.15] (1)
[2023/04/03 12:32:37:0556] N: [wsicli|4|WS/h1/default/10.19.1.15]: lws_sort_dns: 10.19.1.15 has no route out
[2023/04/03 12:32:37:0556] N: [wsicli|4|WS/h1/default/10.19.1.15]: lws_sort_dns_dump: empty
[2023/04/03 12:32:37:0556] N: __lws_lc_untag: -- [wsicli|4|WS/h1/default/10.19.1.15] (0) 130μs
[2023/04/03 12:32:38:1429] N: __lws_lc_tag: ++ [wsicli|5|WS/h1/default/10.19.1.15] (1)
[2023/04/03 12:32:38:1430] N: [wsicli|5|WS/h1/default/10.19.1.15]: lws_sort_dns: 10.19.1.15 has no route out
Hi,
Does it means that event when connectivity has been restored the chargepoint doesn't reconnect?
Could you please just describe how you loose your network connectivity so that I can try to reproduce the problem?
Thanks.
Hi,
I test ocpp on linux by vmware workstation.
When I disconnect the vmware network and run the program it stays in mentioned loop for ever and does not recognize the network disconnection to go oflline mode.
This situation also happens when my linux computer is not connected to any wireless network.
Thanks.
Hi,
I may have found something but I'm not sure that this fully fix your issue.
Could you please try to add the following line in the https://github.com/c-jimenez/open-ocpp/blob/develop/3rdparty/CMakeLists.txt file just before line 31 (add_subdirectory(libwebsockets)
) :
set(LWS_WITH_NETLINK OFF)
Thanks.
Is the issue solved?
Hi,
With the setting I proposed in the previous response, I think I fixed the issue.
I'm waiting a confirmation from @mahdidadashi65 to check if it is the same issue or another one before merging and closing the issue.