Second VPN network fails to start

[Robert Horgan]

Hi Lars,

I am using Ubuntu 18.04.2 at Digital Ocean hosting.  The server is running MariaDB 10.3 and Postfix 3.3 and little else.

With your help I finally have my existing configuration working so it was not eventually an error with the config files but with the start process.

These are the sequence of commands which eventually got everything working for me

Note that I now have in addition to my first Tinc VPN /etc/tinc/gainplus a second, /etc/tinc/stats



sudo systemctl disable tinc at VPN1		  # the previous name that I used for the VPN causing an error in syslog
sudo systemctl stop tinc
systemctl enable tinc at gainplus 
systemctl enable tinc at stats
sudo systemctl start tinc

At this point I could run systemctl and see the 3 x tinc entries in the output.
Everything up and running with VPNs identified in ip a as gainplus and stats

So what was possibly required in this distribution that when starting a second VPN when using systemctl, it seems necessary to register with systemctl with the full service name.  Without that my second VPN would not start.

I suppose what muddied the waters were the simple errors I had made in the conf files.

Thanks for your help in getting me on the right track.

regards
Robert



>>> Lars Kruse <lists at sumpfralle.de> 23-May-19 4:22 PM >>>
Hello Robert,


Am Thu, 23 May 2019 14:56:50 +0700
schrieb "Robert Horgan" <robert at gainplus.asia>:

> Could this be as simple as a name conflict ("tun0" for both VPN setups)?
> 
> The first VPN that comes up is now gainplus after changing details above so no possible conflict
> 
> ip a shows:
> 
> 5: gainplus: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
>	 link/none
>	 inet 10.0.0.51/24 scope global gainplus
> 	   valid_lft forever preferred_lft forever

The above address is "10.0.0.51/24" - but you expected
"10.3.0.51/24" (according to your scripts) - correct?
In this case you need to find out, why the scripts are not called properly (or
what else may be executed in parallel, that messes with your interface setup).


> If not: do you find any information in your local logs?
> (e.g. /var/log/daemon.log)
> 
> no  /var/log/daemon.log exists but in /var/log/syslog displays these errors, but I am confused about resolving them!
> 
> May 23 14:35:14 db2 systemd[1]: tinc at VPN1.service: Service hold-off time over, scheduling restart.
> May 23 14:35:14 db2 systemd[1]: tinc at VPN1.service: Scheduled restart job, restart counter is at 1165.
> May 23 14:35:14 db2 systemd[1]: Stopped Tinc net VPN1.
> May 23 14:35:14 db2 systemd[1]: Started Tinc net VPN1.
> May 23 14:35:14 db2 systemd[31386]: tinc at VPN1.service: Changing to the requested working directory failed: No such file or directory
> May 23 14:35:14 db2 systemd[31386]: tinc at VPN1.service: Failed at step CHDIR spawning /usr/sbin/tincd: No such file or directory
> May 23 14:35:14 db2 systemd[1]: tinc at VPN1.service: Main process exited, code=exited, status=200/CHDIR

The above lines look a bit weird.
Which distribution do you use?
Did you take a look at the bug tracker of your distribution in order to find
out, where the two error messages above come from?
But I am quite sure, that this problem is unrelated to the interface issue, that
you are experiencing.

Cheers,
Lars

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20190524/8fae7495/attachment.html>