search

Ysurac / openmptcprouter-vps

OpenMPTCProuter VPS scripts
GNU General Public License v3.0
149 stars 63 forks source link

arm64 build for vps #72

Open TSJasonH opened 1 year ago

TSJasonH commented 1 year ago

It would be great to have an arm64 build. Oracle cloud gives free arm64 4core/24GB instances with the option of an ubuntu 20.04 image.

Network-Traditions commented 1 year ago

+1 Oracle Ampere instances can also easily be built with a Debian 11 ARM64 images as well. Been attempting to compile 5.4.65 on a Debian 11 instance per compile instructions, but when attempting to boot the compiled boot image, the instance freezes. We successfully operate an AMD64 version running on a 1 OCPU (2vcpu) / 1GB instance as a backup VPS, but it is dramatically under-powered, which results in an unreliable connection. We upgraded the instance from the "free" version to the ~$20/month "VM.Standard.E4.Flex" with 1 OCPU (2vcpu) / 1GB instance [newer higher speed hardware] without any noticeable improvement. Network bandwidth and/or potentially CPU power seem to be the bottlenecks preventing the VPS from functioning reasonably. Upgrading to 2 OCPU's comes with an additional ~$20/month expense, which starts to become a deal breaker. Our "master" VPS is with IONOS reselling 1&1 data center assets for $7/month, which run circles around Oracle's AMD budget offerings. Comparing the Oracle Ampere instances to the AMD instances is night and day. The "free tier" 4 core/24GB with 4GB networking provides a great deal of power for a VPS and Oracle has data centers in 22 countries making an attractive VPS provider.

xunil79 commented 11 months ago

I've the same issue. I compiled kernel on oracle cloud arm64 but the boot freezes at loading initrd image

Ysurac commented 11 months ago

VPS snapshot script using 6.1 kernel release support arm64. Not yet tested on Oracle, but tested on Scaleway.

xunil79 commented 11 months ago

@Ysurac that sounds very promising. Would you be so kind to link here the right script file? Thanks in advace

Ysurac commented 11 months ago

All is here: https://github.com/Ysurac/openmptcprouter/wiki/Snapshots

xunil79 commented 11 months ago

thanks for the link. Running the script I got the following output: root@instance-20230807-1557:~# wget -O - http://www.openmptcprouter.com/server-test/debian-x86_64.sh | UPSTREAM6="yes" sh --2023-08-12 19:37:11-- http://www.openmptcprouter.com/server-test/debian-x86_64.sh Resolving www.openmptcprouter.com (www.openmptcprouter.com)... 84.17.59.115 Connecting to www.openmptcprouter.com (www.openmptcprouter.com)|84.17.59.115|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 74049 (72K) [application/octet-stream] Saving to: ‘STDOUT’

Cannot write to ‘-’ (Broken pipe). root@instance-20230807-1557:~#

Ysurac commented 11 months ago

Try: wget http://www.openmptcprouter.com/server-test/debian-x86_64.sh && UPSTREAM6="yes" sh debian-x86_64.sh

xunil79 commented 11 months ago

I got new errors

Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). Executing: /tmp/apt-key-gpghome.wn9eGB69Fj/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 3B4FE6ACC0B21F32 gpg: key 3B4FE6ACC0B21F32: public key "Ubuntu Archive Automatic Signing Key (2012) ftpmaster@ubuntu.com" imported gpg: Total number processed: 1 gpg: imported: 1 Install mptcp kernel and shadowsocks... Hit:1 http://eu-milan-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports jammy InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease Get:3 https://repo.openmptcprouter.com next InRelease [2121 B] Get:4 https://repo.openmptcprouter.com buster InRelease [2128 B] Hit:5 http://eu-milan-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports jammy-updates InRelease Hit:6 http://eu-milan-1-ad-1.clouds.ports.ubuntu.com/ubuntu-ports jammy-backports InRelease Get:7 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [83.3 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:9 https://repo.openmptcprouter.com next/main amd64 Packages [4748 B] Get:10 https://repo.openmptcprouter.com buster/main amd64 Packages [10.9 kB] Get:11 http://old-releases.ubuntu.com/ubuntu impish InRelease [270 kB] Ign:12 http://archive.ubuntu.com/ubuntu bionic-backports/main arm64 Packages Get:13 http://archive.ubuntu.com/ubuntu bionic-backports/main Translation-en [14.6 kB] Err:12 http://archive.ubuntu.com/ubuntu bionic-backports/main arm64 Packages 404 Not Found [IP: 185.125.190.39 80] Ign:12 http://archive.ubuntu.com/ubuntu bionic-backports/main arm64 Packages Err:12 http://archive.ubuntu.com/ubuntu bionic-backports/main arm64 Packages 404 Not Found [IP: 185.125.190.39 80] Ign:12 http://archive.ubuntu.com/ubuntu bionic-backports/main arm64 Packages Ign:14 http://archive.ubuntu.com/ubuntu bionic/universe arm64 Packages Get:15 http://archive.ubuntu.com/ubuntu bionic/universe Translation-en [4941 kB] Err:12 http://archive.ubuntu.com/ubuntu bionic-backports/main arm64 Packages 404 Not Found [IP: 185.125.190.39 80] Err:14 http://archive.ubuntu.com/ubuntu bionic/universe arm64 Packages 404 Not Found [IP: 185.125.190.39 80] Ign:14 http://archive.ubuntu.com/ubuntu bionic/universe arm64 Packages Err:14 http://archive.ubuntu.com/ubuntu bionic/universe arm64 Packages 404 Not Found [IP: 185.125.190.39 80] Ign:14 http://archive.ubuntu.com/ubuntu bionic/universe arm64 Packages Err:14 http://archive.ubuntu.com/ubuntu bionic/universe arm64 Packages 404 Not Found [IP: 185.125.190.39 80] Get:16 http://old-releases.ubuntu.com/ubuntu impish/main arm64 Packages [1367 kB] Get:17 http://old-releases.ubuntu.com/ubuntu impish/main Translation-en [511 kB] Get:18 http://old-releases.ubuntu.com/ubuntu impish/universe arm64 Packages [12.9 MB] Get:19 http://old-releases.ubuntu.com/ubuntu impish/universe Translation-en [5463 kB] Fetched 25.8 MB in 6s (4583 kB/s) Reading package lists... Done W: https://repo.openmptcprouter.com/dists/next/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEP RECATION section in apt-key(8) for details. W: https://repo.openmptcprouter.com/dists/buster/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the D EPRECATION section in apt-key(8) for details. W: http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. W: http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the D EPRECATION section in apt-key(8) for details. E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/universe/binary-arm64/Packages 404 Not Found [IP: 185.125.190.39 80] E: Some index files failed to download. They have been ignored, or old ones used instead.

Ysurac commented 11 months ago

Ubuntu is not supported on arm (at least not yet, not sure for future...)

xunil79 commented 11 months ago

I've also tried with debian 10 with the following output:

root@instance-20230807-1557:~# wget http://www.openmptcprouter.com/server-test/debian-x86_64.sh && UPSTREAM6="yes" sh debian-x86_64.sh --2023-08-13 20:18:58-- http://www.openmptcprouter.com/server-test/debian-x86_64.sh Resolving www.openmptcprouter.com (www.openmptcprouter.com)... 84.17.59.115 Connecting to www.openmptcprouter.com (www.openmptcprouter.com)|84.17.59.115|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 74049 (72K) [application/octet-stream] Saving to: ‘debian-x86_64.sh’

debian-x86_64.sh 100%[=====================================================================================================================================================>] 72.31K --.-KB/s in 0.003s

2023-08-13 20:18:58 (22.1 MB/s) - ‘debian-x86_64.sh’ saved [74049/74049]

Check user... Check Linux version... Check architecture... Check about broken packages... Check if OpenMPTCProuter VPS is already installed... Update mode Remove lock and update packages list... Hit:1 http://deb.debian.org/debian buster InRelease Hit:2 http://deb.debian.org/debian buster-updates InRelease Hit:3 http://deb.debian.org/debian buster-backports InRelease Hit:4 http://security.debian.org/debian-security buster/updates InRelease Reading package lists... Done Install apt-transport-https, gnupg and openssh-server... Reading package lists... Done Building dependency tree Reading state information... Done openssh-server is already the newest version (1:7.9p1-10+deb10u2). The following additional packages will be installed: dirmngr gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm libassuan0 libksba8 libnpth0 pinentry-curses Suggested packages: dbus-user-session pinentry-gnome3 tor parcimonie xloadimage scdaemon pinentry-doc The following NEW packages will be installed: apt-transport-https dirmngr gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm libassuan0 libksba8 libnpth0 pinentry-curses 0 upgraded, 15 newly installed, 0 to remove and 1 not upgraded. Need to get 7085 kB of archives. After this operation, 14.9 MB of additional disk space will be used. Get:1 http://security.debian.org/debian-security buster/updates/main arm64 libksba8 arm64 1.3.5-2+deb10u2 [96.6 kB] Get:2 http://deb.debian.org/debian buster/main arm64 apt-transport-https all 1.8.2.3 [149 kB] Get:3 http://deb.debian.org/debian buster/main arm64 libassuan0 arm64 2.5.2-1 [47.1 kB] Get:4 http://deb.debian.org/debian buster/main arm64 gpgconf arm64 2.2.12-1+deb10u2 [504 kB] Get:5 http://deb.debian.org/debian buster/main arm64 libnpth0 arm64 1.6-1 [17.6 kB] Get:6 http://deb.debian.org/debian buster/main arm64 dirmngr arm64 2.2.12-1+deb10u2 [694 kB] Get:7 http://deb.debian.org/debian buster/main arm64 gnupg-l10n all 2.2.12-1+deb10u2 [1009 kB] Get:8 http://deb.debian.org/debian buster/main arm64 gnupg-utils arm64 2.2.12-1+deb10u2 [824 kB] Get:9 http://deb.debian.org/debian buster/main arm64 gpg arm64 2.2.12-1+deb10u2 [827 kB] Get:10 http://deb.debian.org/debian buster/main arm64 pinentry-curses arm64 1.1.0-2 [62.7 kB] Get:11 http://deb.debian.org/debian buster/main arm64 gpg-agent arm64 2.2.12-1+deb10u2 [601 kB] Get:12 http://deb.debian.org/debian buster/main arm64 gpg-wks-client arm64 2.2.12-1+deb10u2 [478 kB] Get:13 http://deb.debian.org/debian buster/main arm64 gpg-wks-server arm64 2.2.12-1+deb10u2 [472 kB] Get:14 http://deb.debian.org/debian buster/main arm64 gpgsm arm64 2.2.12-1+deb10u2 [586 kB] Get:15 http://deb.debian.org/debian buster/main arm64 gnupg all 2.2.12-1+deb10u2 [715 kB] Fetched 7085 kB in 0s (102 MB/s) Selecting previously unselected package apt-transport-https. (Reading database ... 21168 files and directories currently installed.) Preparing to unpack .../00-apt-transport-https_1.8.2.3_all.deb ... Unpacking apt-transport-https (1.8.2.3) ... Selecting previously unselected package libassuan0:arm64. Preparing to unpack .../01-libassuan0_2.5.2-1_arm64.deb ... Unpacking libassuan0:arm64 (2.5.2-1) ... Selecting previously unselected package gpgconf. Preparing to unpack .../02-gpgconf_2.2.12-1+deb10u2_arm64.deb ... Unpacking gpgconf (2.2.12-1+deb10u2) ... Selecting previously unselected package libksba8:arm64. Preparing to unpack .../03-libksba8_1.3.5-2+deb10u2_arm64.deb ... Unpacking libksba8:arm64 (1.3.5-2+deb10u2) ... Selecting previously unselected package libnpth0:arm64. Preparing to unpack .../04-libnpth0_1.6-1_arm64.deb ... Unpacking libnpth0:arm64 (1.6-1) ... Selecting previously unselected package dirmngr. Preparing to unpack .../05-dirmngr_2.2.12-1+deb10u2_arm64.deb ... Unpacking dirmngr (2.2.12-1+deb10u2) ... Selecting previously unselected package gnupg-l10n. Preparing to unpack .../06-gnupg-l10n_2.2.12-1+deb10u2_all.deb ... Unpacking gnupg-l10n (2.2.12-1+deb10u2) ... Selecting previously unselected package gnupg-utils. Preparing to unpack .../07-gnupg-utils_2.2.12-1+deb10u2_arm64.deb ... Unpacking gnupg-utils (2.2.12-1+deb10u2) ... Selecting previously unselected package gpg. Preparing to unpack .../08-gpg_2.2.12-1+deb10u2_arm64.deb ... Unpacking gpg (2.2.12-1+deb10u2) ... Selecting previously unselected package pinentry-curses. Preparing to unpack .../09-pinentry-curses_1.1.0-2_arm64.deb ... Unpacking pinentry-curses (1.1.0-2) ... Selecting previously unselected package gpg-agent. Preparing to unpack .../10-gpg-agent_2.2.12-1+deb10u2_arm64.deb ... Unpacking gpg-agent (2.2.12-1+deb10u2) ... Selecting previously unselected package gpg-wks-client. Preparing to unpack .../11-gpg-wks-client_2.2.12-1+deb10u2_arm64.deb ... Unpacking gpg-wks-client (2.2.12-1+deb10u2) ... Selecting previously unselected package gpg-wks-server. Preparing to unpack .../12-gpg-wks-server_2.2.12-1+deb10u2_arm64.deb ... Unpacking gpg-wks-server (2.2.12-1+deb10u2) ... Selecting previously unselected package gpgsm. Preparing to unpack .../13-gpgsm_2.2.12-1+deb10u2_arm64.deb ... Unpacking gpgsm (2.2.12-1+deb10u2) ... Selecting previously unselected package gnupg. Preparing to unpack .../14-gnupg_2.2.12-1+deb10u2_all.deb ... Unpacking gnupg (2.2.12-1+deb10u2) ... Setting up libksba8:arm64 (1.3.5-2+deb10u2) ... Setting up apt-transport-https (1.8.2.3) ... Setting up libnpth0:arm64 (1.6-1) ... Setting up libassuan0:arm64 (2.5.2-1) ... Setting up gnupg-l10n (2.2.12-1+deb10u2) ... Setting up gpgconf (2.2.12-1+deb10u2) ... Setting up gpg (2.2.12-1+deb10u2) ... Setting up gnupg-utils (2.2.12-1+deb10u2) ... Setting up pinentry-curses (1.1.0-2) ... Setting up gpg-agent (2.2.12-1+deb10u2) ... Setting up gpgsm (2.2.12-1+deb10u2) ... Setting up dirmngr (2.2.12-1+deb10u2) ... Setting up gpg-wks-server (2.2.12-1+deb10u2) ... Setting up gpg-wks-client (2.2.12-1+deb10u2) ... Setting up gnupg (2.2.12-1+deb10u2) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-10+deb10u2) ... Update Debian 10 Stretch to Debian 11 Buster Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-image-4.19.0-25-arm64 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 41.2 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://security.debian.org/debian-security buster/updates/main arm64 linux-image-4.19.0-25-arm64 arm64 4.19.289-2 [41.2 MB] Fetched 41.2 MB in 0s (129 MB/s) apt-listchanges: Reading changelogs... (Reading database ... 21406 files and directories currently installed.) Preparing to unpack .../linux-image-4.19.0-25-arm64_4.19.289-2_arm64.deb ... Unpacking linux-image-4.19.0-25-arm64 (4.19.289-2) over (4.19.289-1) ... Setting up linux-image-4.19.0-25-arm64 (4.19.289-2) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.19.0-25-arm64 /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.19.0-25-arm64 Found initrd image: /boot/initrd.img-4.19.0-25-arm64 Adding boot menu entry for UEFI Firmware Settings ... done W: --force-yes is deprecated, use one of the options starting with --allow instead. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. W: --force-yes is deprecated, use one of the options starting with --allow instead. Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Ign:2 http://security.debian.org/debian-security bullseye/updates InRelease Err:3 http://security.debian.org/debian-security bullseye/updates Release 404 Not Found [IP: 146.75.54.132 80] Get:4 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Get:5 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB] Get:6 http://deb.debian.org/debian bullseye/main Sources [8637 kB] Get:7 http://deb.debian.org/debian bullseye/main arm64 Packages [8071 kB] Get:8 http://deb.debian.org/debian bullseye/main Translation-en [6240 kB] Get:9 http://deb.debian.org/debian bullseye-updates/main Sources [6240 B] Get:10 http://deb.debian.org/debian bullseye-updates/main arm64 Packages [14.7 kB] Get:11 http://deb.debian.org/debian bullseye-updates/main Translation-en [9964 B] Get:12 http://deb.debian.org/debian bullseye-backports/main Sources [438 kB] Get:13 http://deb.debian.org/debian bullseye-backports/main arm64 Packages [419 kB] Get:14 http://deb.debian.org/debian bullseye-backports/main Translation-en [353 kB] Reading package lists... Done E: The repository 'http://security.debian.org/debian-security bullseye/updates Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. root@instance-20230807-1557:~#

Ysurac commented 11 months ago

For latest 6.1 release, Debian 12 is needed. Here the script first try to update to Debian 11 and there is an issue. It should be fixed now in the script.

xunil79 commented 11 months ago

I upgraded to debian 11.7 but I got the same error again. Upgrading to 12.1 it works but I got an errror: in this condition: if [ "$UPSTREAM6" = "yes" ]; then apt-get -y install $(dpkg --get-selections | grep linux-image-6.1 | grep -v dbg | cut -f1)-dbg apt-get -y install systemtap mkdir -p /usr/share/systemtap-mptcp wget -O /usr/share/systemtap-mptcp/mptcp-app.stap ${VPSURL}${VPSPATH}/mptcp-app.stap output: E: Command line option 'b' [from -dbg] is not understood in combination with the other options.

removing the flags -dbg at the end like apt-get -y install $(dpkg --get-selections | grep linux-image-6.1 | grep -v dbg | cut -f1) , it worked. Now I'm gonna install the router. I'll keep you posted

TSJasonH commented 11 months ago

I've been following along here with xunil79's progress. I was able to get my oracle arm64 instance on debian 12 and the vps installed (thanks for the dbg tip). Likewise, I spun up a router on v0.59.2alpha-6.1-r0+23414-ed816f6ba8-x86-64. I've got it behind two LTE connections. So far, everything seems to be working quite well.

Ysurac commented 11 months ago

I disabled systemtap part on VPS script, it's not used, script should be ok now.

xunil79 commented 11 months ago

image

Ysurac commented 11 months ago

You rebooted VPS after script install ? Check if the key is correct and check system log.

xunil79 commented 11 months ago

yes I restarted the both VPS and router and the key is good:

Aug 14 16:54:10 OpenMPTCProuter user.notice omr-tracker: Launching... Aug 14 16:54:17 OpenMPTCProuter user.notice omr-tracker: Launched Aug 14 16:54:17 OpenMPTCProuter daemon.err /usr/bin/ss-redir[16472]: remote recv: Connection refused Aug 14 16:54:17 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:17 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:21 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:54:22 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:27 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:54:27 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:27 OpenMPTCProuter daemon.info omr-tracker-ss: Shadowsocks sss0 is down (can't contact via http 1.0.0.1, 212.27.48.10, 198.27.92.1) Aug 14 16:54:27 OpenMPTCProuter user.notice Shadowsocks: Rules DOWN Aug 14 16:54:28 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:33 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:36 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:54:38 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:41 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:54:43 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:48 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:50 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:54:53 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:54:56 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:54:58 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:03 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:05 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:09 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:10 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:14 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:19 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:19 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:24 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:24 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:29 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:34 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:34 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:39 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:39 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:44 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:48 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:49 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:53 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:55:54 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:55:59 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:56:03 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:56:04 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:56:08 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:56:09 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:56:14 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:56:17 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:56:19 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:56:22 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can ping server vps on 129.152.xxx.yyy, no server API answer on 129.152.xxx.yyy) Aug 14 16:56:24 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected Aug 14 16:56:29 OpenMPTCProuter daemon.err /usr/bin/ss-local[16470]: getpeername: Socket not connected

Ysurac commented 11 months ago

There is no answer from the API. What is the result of ps aux | grep omr on the VPS ?

xunil79 commented 11 months ago

root@instance-20230813-2215:~# ps -aux | grep omr root 626 0.3 0.3 1227632 81008 ? Ssl 19:45 0:01 python3 /usr/local/bin/omr-admin.py --host=:: root 632 0.1 0.0 4476 3288 ? Ss 19:45 0:00 /bin/bash /usr/local/bin/omr-service root 686 0.0 0.0 0 0 ? I< 19:45 0:00 [omr-bonding] root 10617 11.2 0.3 1227648 81348 ? Ssl 19:51 0:01 python3 /usr/local/bin/omr-admin.py root 10697 0.0 0.0 3632 1736 pts/0 S+ 19:51 0:00 grep omr

I've just noticed ss-server is not running:

root@instance-20230813-2215:~# ps -aux | grep shadowsocks root 12578 0.0 0.0 3116 2068 ? Ss 19:52 0:00 /usr/bin/ss-manager -c /etc/shadowsocks-libev/manager.json --manager-address 127.0.0.1:8839 root 12839 0.0 0.0 3632 1732 pts/0 S+ 19:52 0:00 grep shadowsocks root@instance-20230813-2215:~# ps -aux | grep ss-server root 13553 0.0 0.0 3632 1724 pts/0 S+ 19:53 0:00 grep ss-server root@instance-20230813-2215:~#

even telnet localhost 65101 doesn't work.

Ysurac commented 11 months ago

What is the result of curl -k https://127.0.0.1:65500 ? Yes ss-server should be running, it's ss-manager job. What do you have in journalctl -u shadowsocks-libev-manager@manager ?

xunil79 commented 11 months ago

curl: (7) Failed to connect to 127.0.0.1 port 65500 after 0 ms: Couldn't connect to server

Aug 14 21:01:05 instance-20230813-2215 ss-server[113178]: failed to listen on any address Aug 14 21:01:19 instance-20230813-2215 systemd[1]: Stopping Shadowsocks-Libev Custom Manager Service for manager... Aug 14 21:01:19 instance-20230813-2215 systemd[1]: shadowsocks-libev-manager@manager.service: Succeeded. Aug 14 21:01:19 instance-20230813-2215 systemd[1]: Stopped Shadowsocks-Libev Custom Manager Service for manager. Aug 14 21:01:19 instance-20230813-2215 systemd[1]: Started Shadowsocks-Libev Custom Manager Service for manager. Aug 14 21:01:19 instance-20230813-2215 ss-manager[113540]: 2023-08-14 21:01:19 INFO: using tcp fast open Aug 14 21:01:19 instance-20230813-2215 ss-manager[113540]: 2023-08-14 21:01:19 INFO: using tcp no-delay Aug 14 21:01:19 instance-20230813-2215 ss-manager[113540]: 2023-08-14 21:01:19 INFO: using MPTCP Aug 14 21:01:19 instance-20230813-2215 ss-manager[113540]: 2023-08-14 21:01:19 INFO: running from root user Aug 14 21:01:19 instance-20230813-2215 ss-manager[113540]: 2023-08-14 21:01:19 INFO: working directory points to /root/.shadowsocks Aug 14 21:01:19 instance-20230813-2215 ss-manager[113540]: 2023-08-14 21:01:19 INFO: try to bind interface: 0.0.0.0, port: 65101 Aug 14 21:01:19 instance-20230813-2215 ss-manager[113543]: 2023-08-14 21:01:19 INFO: initializing acl... Aug 14 21:01:19 instance-20230813-2215 ss-manager[113543]: 2023-08-14 21:01:19 INFO: enable TCP no-delay Aug 14 21:01:19 instance-20230813-2215 ss-manager[113543]: 2023-08-14 21:01:19 INFO: enable multipath TCP Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: resolving hostname to IPv6 address first Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: using tcp fast open Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: UDP relay enabled Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: enable TCP no-delay Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: initializing ciphers... chacha20-ietf-poly1305 Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: tcp server listening at 0.0.0.0:65101 Aug 14 21:01:19 instance-20230813-2215 ss-server[113545]: failed to listen on any address Aug 14 21:01:34 instance-20230813-2215 systemd[1]: Stopping Shadowsocks-Libev Custom Manager Service for manager... Aug 14 21:01:34 instance-20230813-2215 systemd[1]: shadowsocks-libev-manager@manager.service: Succeeded. Aug 14 21:01:34 instance-20230813-2215 systemd[1]: Stopped Shadowsocks-Libev Custom Manager Service for manager. Aug 14 21:01:34 instance-20230813-2215 systemd[1]: Started Shadowsocks-Libev Custom Manager Service for manager. Aug 14 21:01:34 instance-20230813-2215 ss-manager[113907]: 2023-08-14 21:01:34 INFO: using tcp fast open Aug 14 21:01:34 instance-20230813-2215 ss-manager[113907]: 2023-08-14 21:01:34 INFO: using tcp no-delay Aug 14 21:01:34 instance-20230813-2215 ss-manager[113907]: 2023-08-14 21:01:34 INFO: using MPTCP Aug 14 21:01:34 instance-20230813-2215 ss-manager[113907]: 2023-08-14 21:01:34 INFO: running from root user Aug 14 21:01:34 instance-20230813-2215 ss-manager[113907]: 2023-08-14 21:01:34 INFO: working directory points to /root/.shadowsocks Aug 14 21:01:34 instance-20230813-2215 ss-manager[113907]: 2023-08-14 21:01:34 INFO: try to bind interface: 0.0.0.0, port: 65101 Aug 14 21:01:34 instance-20230813-2215 ss-manager[113910]: 2023-08-14 21:01:34 INFO: initializing acl... Aug 14 21:01:34 instance-20230813-2215 ss-manager[113910]: 2023-08-14 21:01:34 INFO: enable TCP no-delay Aug 14 21:01:34 instance-20230813-2215 ss-manager[113910]: 2023-08-14 21:01:34 INFO: enable multipath TCP Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: resolving hostname to IPv6 address first Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: using tcp fast open Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: UDP relay enabled Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: enable TCP no-delay Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: initializing ciphers... chacha20-ietf-poly1305 Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: tcp server listening at 0.0.0.0:65101 Aug 14 21:01:34 instance-20230813-2215 ss-server[113912]: failed to listen on any address

Ysurac commented 11 months ago

Strange... What is the result of uname -a and netstat -laputen ?

xunil79 commented 11 months ago

I deployed another vps from scratch with debian12 without any upgrade from my previous debian10 vps. Suddenly I got all green. Thanks for your support. :)

Ysurac commented 11 months ago

ok, strange but cool if this work