[Support]: ZTNET container exits with code 0 #440
Labels
support
support request for ZTNET
Comments
|
Thank you for the logs and detailed report. I tested opensuse-15.5-default_20231118_amd64.tar.xz in a proxmox container, but was not able to replicate the issue. |
|
Tested openSUSE Tumbleweed version 20240613 sinamics@localhost:~> cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20240613"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240613"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240613:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20240613"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"sinamics@localhost:~> uname -a
Linux localhost.localdomain 6.9.3-1-default #1 SMP PREEMPT_DYNAMIC Thu May 30 08:29:01 UTC 2024 (279162a) x86_64 x86_64 x86_64 GNU/Linuxsinamics@localhost:~> docker info
Client:
Version: 26.1.0-ce
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: 0.15.0
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: 2.27.1
Path: /usr/lib/docker/cli-plugins/docker-compose
Server:
Containers: 3
Running: 3
Paused: 0
Stopped: 0
Images: 3
Server Version: 26.1.0-ce
Storage Driver: overlay2
Backing Filesystem: btrfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 oci runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3a4de459a68952ffb703bbe7f2290861a75b6b67
runc version: v1.2.0-rc.1-0-g275e6d85f78a
init version:
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.9.3-1-default
Operating System: openSUSE Tumbleweed
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.927GiB
Name: localhost.localdomain
ID: 489e7928-3ee0-4c21-b15e-83530b1a6eb0
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false |
|
I'll try reinstalling ZTNET and run it with defaults. I'm unsure if it could be caused by my hardware or any software misconfiguration on my side, as it only happens while interacting with the GUI. |
|
I tested it in a different hardware with other distros (Debian and Arch), it worked. Within this specific one running Tumbleweed (RV415), I made a second and clean install of the OS (20240613 build) and ZTNET in Docker, seems to be working fine now. I'll close this, as it's not reproducible and maybe it's caused by a broken environment on my side. Thank you for your attention and time. |
|
great, glad you got it working. |
|
update I had a Debian 12 container with zerotier-one client installed on it, which was not running while I tried to use ZTNET but after purging everything from docker and reinstalling only ZTNET in the "RV415" machine, it works now. update-1 to the comment: the docker-compose file used on the clean install on RV415 was the default provided in the guide, without any changes. |
|
Hi there! I started a deeper investigation for finding out the specific reason of the "code 0" on my legacy machine. About the machineFor reference, the legacy machine is the Samsung Sens RV415 (NP-RV415-CD3BR), a laptop launched circa 2011 with the AMD E-300 APU. According to the "x86_64 microarchitecture levels" defined in 2020, this APU have few x86-64-v2 extensions, however it does not comply with any of the defined levels. Output of: "lscpu"
$ lscpu | grep "Flags:"
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate vmmcall arat npt lbrv svm_lock nrip_save pausefilterThe problemZTNet crashes while interacting with the web interface, specially after the login while the UI is loading. The crashI experimented building the docker image and it fails with: Dockerfile layer: `RUN SKIP_ENV_VALIDATION=1 npm run build`
Output: `Compiler server unexpectedly exited with code: null and signal: SIGILL`Output of: "docker build --progress=plain ."
As i am unable to build the project and not much skilled enough to debug a Docker container, i extracted the '/app' folder from the official v0.6.6 image and replicated the environment on the host machine (running Arch Linux) according to the Dockerfile, before jumping into the core dump. The 'code 0' is caused by the following crash: $ node server.js
▲ Next.js 14.2.4
- Local: http:https://localhost:3000
- Network: http:https://0.0.0.0:3000
✓ Starting...
✓ Ready in 1723ms
Illegal instruction (core dumped)Core dumpGoing further, analysing the generated core dump, the backtrace points to the Sharp 'libvips-cpp.so.42' prebuilt as root cause of the crash. Output of: "coredumpctl debug 2517"
From there, having an idea of what is wrong on my end i proceeded to search about this lib in and the sharp project and i found out that: The solutionInstalling libvips from the OS repositories before the ZTNET dependencies will do the trick on legacy CPUs that does not support the required features, without touching ZTNET code. References[1] Sharp documentation - prebuilt binaries; since the following PRs: lovell/sharp-libvips#88 & lovell/sharp-libvips#155 |
|
Thank you for the detailed report. I know that the Sharp package has caused issues for FreeBSD due to the libvips version. Since Next.js uses Sharp for the |
|
Following your answer
I removed libvips from the host machine and tried the following changes: diff --git a/package.json b/package.json
index 8588d52..5b6a0dc 100644
--- a/package.json
+++ b/package.json
@@ -57,7 +57,6 @@
"react-dom": "18.2.0",
"react-hot-toast": "^2.4.0",
"react-timeago": "^7.1.0",
- "sharp": "0.32.6",
"socket.io": "^4.7.2",
"socket.io-client": "^4.7.2",
"superjson": "1.9.1",
@@ -106,4 +105,4 @@
"prisma": {
"seed": "ts-node --compiler-options {\"module\":\"CommonJS\"} prisma/seed.ts"
}
-}
\ No newline at end of file
+}
diff --git a/src/components/layouts/header.tsx b/src/components/layouts/header.tsx
index 29ed42f..465ef97 100644
--- a/src/components/layouts/header.tsx
+++ b/src/components/layouts/header.tsx
@@ -1,6 +1,5 @@
import { useSession } from "next-auth/react";
import { useTheme } from "next-themes";
-import Image from "next/image";
import { globalSiteTitle } from "~/utils/global";
import { useSidebarStore } from "~/utils/store";
import ZtnetLogo from "docs/images/logo/ztnet_200x178.png";
@@ -30,11 +29,11 @@ const Header = () => {
<div className="header-content flex flex-row items-center">
<div className="hidden md:inline-flex">
<Link href="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/network" className="inline-flex flex-row items-center gap-2">
- <Image
+ <img
style={{ width: 25, height: 25 }}
alt="ztnet logo"
title="ztnet logo"
- src={ZtnetLogo}
+ src={ZtnetLogo.src}
/>
<span className="ml-1 text-2xl font-bold uppercase leading-10 text-accent">
{globalSiteTitle}Probably isn't the 'proper way' but it worked out. I'm able to build the project for standalone and docker now, and it doesn't crash upon login or interacting with the web interface. Thanks! |
fuyukihidekii
added a commit
to fuyukihidekii/ztnet
that referenced
this issue
Jun 21, 2024
fuyukihidekii
added a commit
to fuyukihidekii/ztnet
that referenced
this issue
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
📝 Inquiry
Hi there, ZTNET container exits with code 0 while interacting with the web interface and restarts on its own. However if i let it running w/o interacting with the web UI, it does keep running. There's no other zerotier program running either in the host or in containers.
I did changed the postgres user and password before running it for the first time, but i believe that this is not causing the problem.
I would like to know if is there any other information or debug step that i can follow to properly report this.
🔖 Version
v0.6.6
🔧 Deployment Type
💻 Operating System
Other Linux
📚 Any Other Information That May Be Helpful
I have attached a log, my docker-compose.yml and information about my system / docker/ hardware.
/etc/os-release
neofetch
docker-compose.yml
docker compose ps -a
docker compose logs -f -t
docker info
The text was updated successfully, but these errors were encountered: