OpenVPN (SSL/TLS,TCP,Client) No Management Daemon

[jimp]

What type of connection do you have on WAN?

All of those OpenVPN instances should be starting at boot. If you get that "no management daemon" error now it's probably because that OpenVPN instance is not running at all, as you confirmed on the Status > Services page.

Your post seems to contradict itself though, or perhaps I'm not reading it right. You said at first that after a 24-hour disconnect/reconnect that they did not come up properly, but later you said they didn't come up properly on bootup but they did come back up after a reconnect. So which is it?  The system log (not the OpenVPN log) might have some information about why it didn't start.

[meson]

Thanks for your reply, I admit - sounds a little confusing, so here again a little bit more in order:

1. after reboot
-only one tunnel is started, an it hardly seems that its always the same one

2. after reboot
-started missing tunnels manually at the services tab
-tunnels come up instantly, seems ok then

3. after reconnect
-random tunnels are restarted properly and come up after a while
-noticeable is, that the ones which don't come back, are listed with "No Management Daemon" instantly (03_after_reconnect_status_01.jpg)

01_after_reboot_system_log.txt
03_after_reconnect_system_log.txt

[jimp]

The actual config from those OpenVPN instances might be more useful to see, along with the system logs

[meson]

Here the config and the whole system log…

client1.conf.txt
client2.conf.txt
client3.conf.txt
system.log.txt

[jimp]

Nothing really noteworthy there… How about the actual GUI portion of the OpenVPN config, not the generated config files.

That, and the system log file.

[meson]

Thanks for your Help! Attached the Screenshots and the system.log of the past days.

Maybe I should try reinstalling the box if I'm the only one with this issue?

system.log.txt

[meson]

some more

[jimp]

Looks like you may be on a snapshot that has a bug with check_reload_status starting too many times. It might be contributing.

Wait for the next new snapshot (it's building right now) and then upgrade and try it out again.

[meson]

I have tried the last snapshots, but the unfortunately the problem remains. Here the actual system log, seems that the ceck_reload_status behavior has changed. Maybe you have another idea?

system.log.txt

[jimp]

Still looks rather erratic, as though there are connectivity issues between all of the sites that make the tunnels go up and down.