<html><head>
<meta name="Generator" content="Novell Groupwise Client (Version 14.2.2 Build: 126868)">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head>
<body style="font: 12pt/normal Segoe UI; font-size-adjust: none; font-stretch: normal;"><div class="GroupWiseMessageBody" id="GroupWiseSection_1558661933000_robert@gainplus.asia_0AE2278002F000008C53A30038005B00_"><div>Hi Lars,</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>These are the sequence of commands which eventually got everything working for me</div><div><br></div><div>Note that I now have in addition to my first Tinc VPN <strong>/etc/tinc/gainplus</strong> a second, <strong>/etc/tinc/stats</strong></div><span style="margin-bottom: 5px; display: block;"><br></span><span style="margin-bottom: 5px; display: block;"><strong><font face="Courier New">sudo systemctl disable </font></strong><a href="mailto:tinc@VPN1"><strong><font face="Courier New">tinc@VPN1</font></strong></a> # the previous name that I used for the VPN causing an error in syslog</span><span style="margin-bottom: 5px; display: block;"><strong><font face="Courier New">sudo systemctl stop tinc</font></strong></span><span style="margin-bottom: 5px; display: block;"><strong><font face="Courier New">systemctl enable </font></strong><a href="mailto:tinc@gainplus"><strong><font face="Courier New">tinc@gainplus</font></strong></a><strong><font face="Courier New"> </font></strong></span><span style="margin-bottom: 5px; display: block;"><strong><font face="Courier New">systemctl enable </font></strong><a href="mailto:tinc@stats"><strong><font face="Courier New">tinc@stats</font></strong></a><br></span><div><strong><font face="Courier New">sudo systemctl start tinc</font></strong></div><div><br></div><div>At this point I could run <strong>systemctl</strong> and see the 3 x tinc entries in the output.</div><div>Everything up and running with VPNs identified in <strong>ip a</strong> as <strong>gainplus</strong> and <strong>stats</strong></div><strong></strong></div><div><br></div><div>So what was possibly required in this distribution that when starting a second VPN when using <strong>systemctl</strong>, it seems necessary to register with <strong>systemctl</strong> with the full service name. Without that my second VPN would not start.</div><div><br></div><div>I suppose what muddied the waters were the simple errors I had made in the conf files.</div><div><br></div><div>Thanks for your help in getting me on the right track.<br></div><span id="GWSignatureSent" style="padding-right: 0px; padding-left: 0px; margin-bottom: 5px; display: block;"><span style="display: block;"><br><span style="font-size: 12pt; display: inline-block; -ms-word-wrap: normal;">
<div><div><div><font face="Segoe UI">regards</font></div><div><font face="Segoe UI">Robert</font></div><br></div></div></span></span></span><span style="margin-bottom: 5px; display: block;"><br></span><div class="GroupWiseMessageBody" id="GroupWiseSection_1558661932000_robert@gainplus.asia_0AE2278002F000008C53A30038005B00_"><span class="GroupwiseReplyHeader">>>> Lars Kruse <lists@sumpfralle.de> 23-May-19 4:22 PM >>><br></span><div><div>Hello Robert,</div><div><br></div><div><br></div><div>Am Thu, 23 May 2019 14:56:50 +0700</div><div>schrieb "Robert Horgan" <robert@gainplus.asia>:</div><div><br></div><div>> Could this be as simple as a name conflict ("tun0" for both VPN setups)?</div><div>> </div><div>> The first VPN that comes up is now gainplus after changing details above so no possible conflict</div><div>> </div><div>> ip a shows:</div><div>> </div><div>> 5: gainplus: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500</div><div>> link/none</div><div>> inet 10.0.0.51/24 scope global gainplus</div><div>> valid_lft forever preferred_lft forever</div><div><br></div><div>The above address is "10.0.0.51/24" - but you expected</div><div>"10.3.0.51/24" (according to your scripts) - correct?</div><div>In this case you need to find out, why the scripts are not called properly (or</div><div>what else may be executed in parallel, that messes with your interface setup).</div><div><br></div><div><br></div><div>> If not: do you find any information in your local logs?</div><div>> (e.g. /var/log/daemon.log)</div><div>> </div><div>> no /var/log/daemon.log exists but in /var/log/syslog displays these errors, but I am confused about resolving them!</div><div>> </div><div>> May 23 14:35:14 db2 systemd[1]: tinc@VPN1.service: Service hold-off time over, scheduling restart.</div><div>> May 23 14:35:14 db2 systemd[1]: tinc@VPN1.service: Scheduled restart job, restart counter is at 1165.</div><div>> May 23 14:35:14 db2 systemd[1]: Stopped Tinc net VPN1.</div><div>> May 23 14:35:14 db2 systemd[1]: Started Tinc net VPN1.</div><div>> May 23 14:35:14 db2 systemd[31386]: tinc@VPN1.service: Changing to the requested working directory failed: No such file or directory</div><div>> May 23 14:35:14 db2 systemd[31386]: tinc@VPN1.service: Failed at step CHDIR spawning /usr/sbin/tincd: No such file or directory</div><div>> May 23 14:35:14 db2 systemd[1]: tinc@VPN1.service: Main process exited, code=exited, status=200/CHDIR</div><div><br></div><div>The above lines look a bit weird.</div><div>Which distribution do you use?</div><div>Did you take a look at the bug tracker of your distribution in order to find</div><div>out, where the two error messages above come from?</div><div>But I am quite sure, that this problem is unrelated to the interface issue, that</div><div>you are experiencing.</div><div><br></div><div>Cheers,</div><div>Lars</div><div><br></div></div></div></body></html>