You are here
Alexandr - Tue, 2025/01/14 - 16:30
Hello! My turnkey nextcloud works on virtualbox and starts when the host startup. In the webmin settings autostart pptp client is enabled, but it does not work, although it working manually.
Other processes start automatically without problems too. Need help, but my knowledge of linux is at the beginner level.
Jan 14 16:47:58 nextcloud systemd[1]: Failed to start pptp-client.service - Startup or shutdown PPTP connection. Jan 14 16:47:29 nextcloud ntpd[642]: IO: unable to create socket on eth0 (5) for fe80::a00:27ff:fe82:ffa7%2#123 Jan 14 16:47:29 nextcloud ntpd[642]: IO: bind(21) AF_INET6 fe80::a00:27ff:fe82:ffa7%2#123 flags 0x1 failed: Cannot assign requested address Jan 14 16:47:29 nextcloud ntpd[642]: CLOCK: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired less than 18 days ago Jan 14 16:47:29 nextcloud ntpd[642]: CONFIG: restrict nopeer ignored Jan 14 16:47:28 nextcloud pptp[468]: anon fatal[get_ip_address:pptp.c:472]: getaddrinfo(): Name or service not known Jan 14 16:47:28 nextcloud kernel: [drm:vmw_host_printf [vmwgfx]] *ERROR* Failed to send host log message. Jan 14 16:47:27 nextcloud systemd[1]: Invalid DMI field header.
Forum:
Investigating pptp-client.service Issue on NextCloud
Hi there, thanks for reaching out! We’re currently working on recreating the issue you’re experiencing with the PPTP client autostart on your Nextcloud appliance. We’ll follow up with you as soon as we have further guidance or a potential solution.
In the meantime, could you let us know which version of Nextcloud you’re running? Additionally, if you have any details about your configuration or changes made to the system, feel free to share them, as they could help us pinpoint the issue more quickly.
Thanks for your patience, and we’ll be in touch soon!
Thanks Mattie :)
Thanks for jumping in Mattie. :)
After assessing the situation re your PPTP issue, I don't think it's practical for us to try to recreate your issue. We're pretty snowed under with a huge backlog and we don't have a PPTP server set up - nor access to a Windows server to try to recreate your environment.
Regardless, I'm happy to try to help out. But I need a bit more info.
As Mattie said, could you please confirm the Nextcloud appliance version - if it's not the latest (v18.1) then please share the output of:
FYI the specific lines from the log lines you shared that are relevant are:
So long as you don't need to access external addresses via IPv6, all the other errors are unrelated to your issue and can safely be ignored for now. Although FWIW the ntpd CLOCK line is an easy fix if you want to do that. Just update the 'tzdata' package. I.e.:
To add some specifics to Mattie's request for other info, you said that it works when manually started, but not automatically at boot. Can you please give info on how you are manually starting it?
Also please reboot (so pptp isn't working) and share the output of these commands:
Then manually start it (so it is working) and re run those same commands again.
Thanks for your response!
My Nextcloud appliance version is 18.1
Manually pptp is launched in the Webmin panel -> Network -> pptp vpn client -> "Connect to" button.
Result of entering commands " journalctl -b -t pptp ip a":
Sorry if I wasn't clear, but please run those twice
Sorry if I wasn't clear, but please run those twice. I.e.:
That will hopefully give me enough info to get an idea of what the issue might be. If nothing else it should give me some ideas on any further info I might need.
when pptp-client enabled manually
Hmm, ok...
It's interesting that the 'fatal[get_ip_address:pptp.c:472]: getaddrinfo(): Name or service not known' error doesn't reoccur when you manually start it, only when it tries to auto start.
Something else to check - sorry I probably should have thought of this before.
As per what you did before, please reboot and then run this command (i.e. when it's not working) and post the output:
Then manually start it, re-run the above status command and post that output too.
I think that either the way that Webmin starts it is different to the way the service tries to. Or there is some sort of race condition during early boot where something is not yet ready to be configured when the service tries to start.
It would also be useful to see the contents of the service file:
My results
root@nextcloud ~# systemctl status pptp-client.service × pptp-client.service - Startup or shutdown PPTP connection Loaded: loaded (/lib/systemd/system/pptp-client.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2025-02-11 17:08:01 MSK; 6s ago Process: 421 ExecStart=/etc/webmin/pptp-client/start.pl (code=exited, status=1/FAILURE) CPU: 727ms Feb 11 17:07:31 nextcloud systemd[1]: Starting pptp-client.service - Startup or shutdown PPTP connection... Feb 11 17:07:31 nextcloud start.pl[421]: Establishing a PPTP connection with the command pptp 95.80.87.231 call museum .. Feb 11 17:07:31 nextcloud pptp[467]: anon fatal[get_ip_address:pptp.c:472]: getaddrinfo(): Name or service not known Feb 11 17:08:01 nextcloud start.pl[421]: .. connection failed! Check the log messages below for information why. Feb 11 17:08:01 nextcloud start.pl[421]: anon fatal[get_ip_address:pptp.c:472]: getaddrinfo(): Name or service not known Feb 11 17:08:01 nextcloud systemd[1]: pptp-client.service: Control process exited, code=exited, status=1/FAILURE Feb 11 17:08:01 nextcloud systemd[1]: pptp-client.service: Failed with result 'exit-code'. Feb 11 17:08:01 nextcloud systemd[1]: Failed to start pptp-client.service - Startup or shutdown PPTP connection.
root@nextcloud ~# systemctl cat pptp-client.service # /lib/systemd/system/pptp-client.service [Unit] Description=Startup or shutdown PPTP connection [Service] ExecStart=/etc/webmin/pptp-client/start.pl ExecStop=/etc/webmin/pptp-client/stop.pl Type=forking [Install] WantedBy=multi-user.target
When pptp enabled
Add new comment