OpenVPN net2net slave server won't connect to master server after reboot

[xcod (And)]

NethServer Version: 7.3.1611 (rc3) + last upd
Module: OpenVPN

master and slave server: NS 7.3.1611 (rc3) + last upd

i create master sever OpenVPN for net2net
and create slave. it’s work fine
if slave server restart
after restart slave server not connect to master
openvpn.log empty

[xcod (And)]

I found the cause of the problem
After the system boots the service does not start

I started in the service manual
systemctl start openvpn@servicename.service
servicename - this is my service name in the NS dashboard-openvpn-client.
it works.

service is not activated
systemctl enable openvpn@servicename.service
It shows the error:
Failed to execute operation: Too many levels of symbolic links

how to solve?

[giacomo (Giacomo Sanchietti)]

Sorry for the late reply.
This is probably a bug, but for now I don’t have time to reproduce it.

Just try to enable the service with the force flag:

systemctl -f enable openvpn@servicename.service

[xcod (And)]

@giacomo

Just try to enable the service with the force flag:

systemctl -f enable openvpn@servicename.service

Thanks for the answer!
same error: Failed to execute operation: Too many levels of symbolic links

[giacomo (Giacomo Sanchietti)]

It seems a bug in systemd:

Issue: systemctl enable on linked service: 'Failed to execute operation: Too many levels of symbolic links'

I found a workaround, try this:

touch '/etc/systemd/system/openvpn@.service.d/servicename.conf'
systemctl enable openvpn@servicename.service

[xcod (And)]

@giacomo

I found a workaround, try this:

touch ‘/etc/systemd/system/openvpn@.service.d/servicename.conf’
systemctl enable openvpn@servicename.service

Thank you!
but, same error: Failed to execute operation: Too many levels of symbolic links

[giacomo (Giacomo Sanchietti)]

This is strange, I could make it work in my machine.

Give me a little time, I will try to create a patched RPM.

[xcod (And)]

@giacomo

This is strange, I could make it work in my machine.

Give me a little time, I will try to create a patched RPM.

ok
Thank you!

[giacomo (Giacomo Sanchietti)]

Thank you for reporting! Just opened a issue and prepared the fix:

Issue: OpenVPN: client not starting at boot

To test is on your machine, simply update from testing repo:

yum --enablerepo=nethserver-testing update nethserver-openvpn

[alefattorini (Alessio Fattorini)]

@xcod can you verify the bug?
Some info here, if you need help feel free to ask

QA/Testing Team basic HOWTO

it’s only an adaption of the previous post for GitHub, there are more to change/enhance, but no more time for now… comments, hints, suggestions and corrections are welcomed Nethserver Testing Team - Why join Testing Team The main feature of Nethserver is the modular design, this means that there are many different setups as people has different interests. As member of Testing Team you could act as a contact person for a specific area to help developers fix the bugs you care about, and is the …

[xcod (And)]

Thank you so much!
issue solved!

[Brian_Johnson]

Since OpenVPN shares are not accessible, there may be errors when you are trying to access. My spectra server had some similar issue but relied on the basic troubleshooting by running certain commands.