Hi,

I update from libreswan 4.7 to 4.9 the connection is establish OK, but the 
ipsec service is restarting continuously.. and that restart the connection. 

The restart is provoked by systemd, because the service is not starting 
normally, it gives timeout and that triggers the restart. 

I later remove the connection definition from the configuration and try to 
start ipsec and I got the same error, timeout.  
Reverting to version 4.7 everything is ok.


I can’t see where is the timeout. 

[10:36:15][beelink][~]# systemctl start ipsec
Job for ipsec.service failed because a timeout was exceeded.
See "systemctl status ipsec.service" and "journalctl -xe" for details.


Small log before timed out:

Oct 21 10:37:37 beelink pluto[21609]: | FOR_EACH_UNORIENTED_CONNECTION_... in 
check_orientations
Oct 21 10:37:37 beelink pluto[21609]: | spent 0.132 (0.133) milliseconds in in 
connection_check_ddns for hostname lookup
Oct 21 10:37:37 beelink pluto[21609]: | spent 0.191 (0.189) milliseconds in 
global timer EVENT_PENDING_DDNS
Oct 21 10:37:37 beelink pluto[21609]: | processing global timer EVENT_SHUNT_SCAN
Oct 21 10:37:37 beelink pluto[21609]: | kernel: checking for aged bare shunts 
from shunt table to expire
Oct 21 10:37:37 beelink pluto[21609]: | spent 0.0442 (0.0416) milliseconds in 
global timer EVENT_SHUNT_SCAN
Oct 21 10:37:57 beelink pluto[21609]: | processing global timer EVENT_SHUNT_SCAN
Oct 21 10:37:57 beelink pluto[21609]: | kernel: checking for aged bare shunts 
from shunt table to expire
Oct 21 10:37:57 beelink pluto[21609]: | spent 0.0614 (0.049) milliseconds in 
global timer EVENT_SHUNT_SCAN
Oct 21 10:38:07 beelink systemd[1]: ipsec.service: Start operation timed out. 
Terminating.


Full log here: https://pastebin.com/qJ7DY9QU <https://pastebin.com/qJ7DY9QU> 

Thanks. 

—
Saludos / Regards / Cumprimentos
António Silva

_______________________________________________
Swan mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan

Reply via email to