ZTNET ui not responding #540

qwaldo · 2024-09-06T09:22:01Z

qwaldo
Sep 6, 2024

Hi

ZTNET service cannot load and work normally. What could be the problem?
Thank you in advance!

sinamics · 2024-09-06T09:33:20Z

sinamics
Sep 6, 2024
Maintainer

You need to provide logs.
docker logs ztnet

But i guess you have issues with zerotier connection.
Goto Admin=>ZT Controller, do you see status from the controller?

6 replies

sinamics Sep 6, 2024
Maintainer

I still need logs.
If you use docker:
docker logs ztnet

If you use standalone version:
journalctl -u ztnet.service

qwaldo Sep 6, 2024
Author

sudo journalctl -u ztnet.service

-- Logs begin at Mon 2024-07-08 14:11:22 UTC, end at Fri 2024-09-06 09:45:32 UTC. --
Jul 08 15:09:47 ztc systemd[1]: Started ZTnet Service.
Jul 08 15:09:48 ztc node[57818]:    ▲ Next.js 14.1.4
Jul 08 15:09:48 ztc node[57818]:    - Local:        http://localhost:3000
Jul 08 15:09:48 ztc node[57818]:    - Network:      http://0.0.0.0:3000
Jul 08 15:09:49 ztc node[57818]:  ✓ Ready in 877ms
-- Reboot --
Aug 09 10:05:21 ztc systemd[1]: Started ZTnet Service.
Aug 09 10:05:25 ztc node[741]:    ▲ Next.js 14.1.4
Aug 09 10:05:25 ztc node[741]:    - Local:        http://localhost:3000
Aug 09 10:05:25 ztc node[741]:    - Network:      http://0.0.0.0:3000
Aug 09 10:05:27 ztc node[741]:  ✓ Ready in 1316ms
-- Reboot --
Aug 19 07:02:35 ztc systemd[1]: Started ZTnet Service.
Aug 19 07:02:43 ztc node[743]:    ▲ Next.js 14.1.4
Aug 19 07:02:43 ztc node[743]:    - Local:        http://localhost:3000
Aug 19 07:02:43 ztc node[743]:    - Network:      http://0.0.0.0:3000
Aug 19 07:02:44 ztc node[743]:  ✓ Ready in 1341ms
Sep 06 05:39:51 ztc systemd[1]: Stopping ZTnet Service...
Sep 06 05:40:00 ztc node[743]: prisma:error
Sep 06 05:40:00 ztc node[743]: Invalid `prisma.user.findMany()` invocation:
Sep 06 05:40:00 ztc node[743]: Can't reach database server at `127.0.0.1`:`5432`
Sep 06 05:40:00 ztc node[743]: Please make sure your database server is running at `127.0.0.1`:`5432`.
Sep 06 05:40:00 ztc node[743]: cron task updatePeers: PrismaClientKnownRequestError:
Sep 06 05:40:00 ztc node[743]: Invalid `prisma.user.findMany()` invocation:
Sep 06 05:40:00 ztc node[743]: Can't reach database server at `127.0.0.1`:`5432`
Sep 06 05:40:00 ztc node[743]: Please make sure your database server is running at `127.0.0.1`:`5432`.
Sep 06 05:40:00 ztc node[743]:     at In.handleRequestError (/opt/ztnet/node_modules/@prisma/client/runtime/library.js:122:6854)
Sep 06 05:40:00 ztc node[743]:     at In.handleAndLogRequestError (/opt/ztnet/node_modules/@prisma/client/runtime/library.js:122:6188)
Sep 06 05:40:00 ztc node[743]:     at In.request (/opt/ztnet/node_modules/@prisma/client/runtime/library.js:122:5896)
Sep 06 05:40:00 ztc node[743]:     at async l (/opt/ztnet/node_modules/@prisma/client/runtime/library.js:127:11167)
Sep 06 05:40:00 ztc node[743]:     at async CronJob.<anonymous> (/opt/ztnet/.next/server/chunks/1875.js:1:867) {
Sep 06 05:40:00 ztc node[743]:   code: 'P1001',
Sep 06 05:40:00 ztc node[743]:   clientVersion: '5.12.1',
Sep 06 05:40:00 ztc node[743]:   meta: {
Sep 06 05:40:00 ztc node[743]:     modelName: 'User',
Sep 06 05:40:00 ztc node[743]:     database_host: '127.0.0.1',
Sep 06 05:40:00 ztc node[743]:     database_port: 5432
Sep 06 05:40:00 ztc node[743]:   }
Sep 06 05:40:00 ztc node[743]: }
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: State 'stop-sigterm' timed out. Killing.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 743 (next-server) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 857 (node) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 858 (node) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 859 (node) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 860 (node) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 861 (node) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Killing process 72932 (tokio-runtime-w) with signal SIGKILL.
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Main process exited, code=killed, status=9/KILL
Sep 06 05:41:21 ztc systemd[1]: ztnet.service: Failed with result 'timeout'.
Sep 06 05:41:21 ztc systemd[1]: Stopped ZTnet Service.
-- Reboot --
Sep 06 05:42:20 ztc systemd[1]: Started ZTnet Service.
Sep 06 05:42:24 ztc node[730]:    ▲ Next.js 14.1.4
Sep 06 05:42:24 ztc node[730]:    - Local:        http://localhost:3000
Sep 06 05:42:24 ztc node[730]:    - Network:      http://0.0.0.0:3000
Sep 06 05:42:25 ztc node[730]:  ✓ Ready in 1009ms```

sinamics Sep 6, 2024
Maintainer

seems like you have issues with the database.
Post the results of:
sudo tail -n 50 -f /var/log/postgresql/postgresql-*.log

sinamics Sep 6, 2024
Maintainer

also check that postgres is running:
sudo systemctl status postgresql

qwaldo Sep 6, 2024
Author

2024-09-06 05:39:52.200 UTC [73379] ztnet@ztnet FATAL:  terminating connection due to administrator command
2024-09-06 05:39:52.230 UTC [5141] LOG:  background worker "logical replication launcher" (PID 5148) exited with exit code 1
2024-09-06 05:39:52.244 UTC [5143] LOG:  shutting down
2024-09-06 05:39:52.533 UTC [5141] LOG:  database system is shut down
2024-09-06 05:42:22.350 UTC [867] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 05:42:22.361 UTC [867] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 05:42:22.437 UTC [867] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 05:42:22.690 UTC [876] LOG:  database system was shut down at 2024-09-06 05:39:52 UTC
2024-09-06 05:42:22.899 UTC [867] LOG:  database system is ready to accept connections
2024-09-06 05:57:54.763 UTC [1484] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 05:57:54.769 UTC [1483] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 05:57:54.771 UTC [1892] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 05:57:54.777 UTC [1893] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 05:57:54.789 UTC [1891] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 05:57:55.435 UTC [867] LOG:  received fast shutdown request
2024-09-06 05:57:55.487 UTC [867] LOG:  aborting any active transactions
2024-09-06 05:57:55.524 UTC [867] LOG:  background worker "logical replication launcher" (PID 902) exited with exit code 1
2024-09-06 05:57:55.527 UTC [897] LOG:  shutting down
2024-09-06 05:57:55.708 UTC [867] LOG:  database system is shut down
2024-09-06 05:59:01.252 UTC [881] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 05:59:01.256 UTC [881] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 05:59:01.277 UTC [881] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 05:59:01.501 UTC [891] LOG:  database system was shut down at 2024-09-06 05:57:55 UTC
2024-09-06 05:59:01.724 UTC [881] LOG:  database system is ready to accept connections
2024-09-06 06:23:43.065 UTC [889] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 06:23:43.073 UTC [889] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 06:23:43.223 UTC [889] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 06:23:43.576 UTC [919] LOG:  database system was interrupted; last known up at 2024-09-06 05:59:01 UTC
2024-09-06 06:23:45.556 UTC [919] LOG:  database system was not properly shut down; automatic recovery in progress
2024-09-06 06:23:45.607 UTC [919] LOG:  redo starts at 0/788A918
2024-09-06 06:23:45.616 UTC [919] LOG:  invalid record length at 0/788C9B0: wanted 24, got 0
2024-09-06 06:23:45.616 UTC [919] LOG:  redo done at 0/788C978
2024-09-06 06:23:46.127 UTC [889] LOG:  database system is ready to accept connections
2024-09-06 08:57:38.740 UTC [888] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 08:57:38.746 UTC [888] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 08:57:38.784 UTC [888] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 08:57:38.933 UTC [900] LOG:  database system was interrupted; last known up at 2024-09-06 06:28:46 UTC
2024-09-06 08:57:41.322 UTC [900] LOG:  database system was not properly shut down; automatic recovery in progress
2024-09-06 08:57:41.386 UTC [900] LOG:  redo starts at 0/788D170
2024-09-06 08:57:41.386 UTC [900] LOG:  invalid record length at 0/788D258: wanted 24, got 0
2024-09-06 08:57:41.386 UTC [900] LOG:  redo done at 0/788D220
2024-09-06 08:57:41.726 UTC [888] LOG:  database system is ready to accept connections
2024-09-06 09:10:20.043 UTC [3117] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:10:21.264 UTC [3123] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:10:30.377 UTC [3180] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:10:30.379 UTC [3181] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.909 UTC [982] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.912 UTC [1183] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.924 UTC [3375] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.927 UTC [3374] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
----------------------------

sudo systemctl status postgresql

Active: active (exited)

sinamics · 2024-09-06T10:12:40Z

sinamics
Sep 6, 2024
Maintainer

how much memory is available on your system? You need 2GB.
free -h

If you have enough memory, try to restart postgres and then post the logs again:
sudo systemctl restart postgresql

Then after 1 minute:
sudo tail -n 50 -f /var/log/postgresql/postgresql-*.log

1 reply

qwaldo Sep 6, 2024
Author

free -h
              total        used        free      shared  buff/cache   available
Mem:          3.8Gi       316Mi       3.1Gi        14Mi       359Mi       3.2Gi
Swap:         3.8Gi          0B       3.8Gi

sudo tail -n 50 -f /var/log/postgresql/postgresql-*.log

2024-09-06 06:23:43.576 UTC [919] LOG:  database system was interrupted; last known up at 2024-09-06 05:59:01 UTC
2024-09-06 06:23:45.556 UTC [919] LOG:  database system was not properly shut down; automatic recovery in progress
2024-09-06 06:23:45.607 UTC [919] LOG:  redo starts at 0/788A918
2024-09-06 06:23:45.616 UTC [919] LOG:  invalid record length at 0/788C9B0: wanted 24, got 0
2024-09-06 06:23:45.616 UTC [919] LOG:  redo done at 0/788C978
2024-09-06 06:23:46.127 UTC [889] LOG:  database system is ready to accept connections
2024-09-06 08:57:38.740 UTC [888] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 08:57:38.746 UTC [888] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 08:57:38.784 UTC [888] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 08:57:38.933 UTC [900] LOG:  database system was interrupted; last known up at 2024-09-06 06:28:46 UTC
2024-09-06 08:57:41.322 UTC [900] LOG:  database system was not properly shut down; automatic recovery in progress
2024-09-06 08:57:41.386 UTC [900] LOG:  redo starts at 0/788D170
2024-09-06 08:57:41.386 UTC [900] LOG:  invalid record length at 0/788D258: wanted 24, got 0
2024-09-06 08:57:41.386 UTC [900] LOG:  redo done at 0/788D220
2024-09-06 08:57:41.726 UTC [888] LOG:  database system is ready to accept connections
2024-09-06 09:10:20.043 UTC [3117] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:10:21.264 UTC [3123] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:10:30.377 UTC [3180] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:10:30.379 UTC [3181] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.909 UTC [982] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.912 UTC [1183] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.924 UTC [3375] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 09:16:24.927 UTC [3374] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 10:15:17.742 UTC [888] LOG:  received fast shutdown request
2024-09-06 10:15:17.773 UTC [888] LOG:  aborting any active transactions
2024-09-06 10:15:17.782 UTC [888] LOG:  background worker "logical replication launcher" (PID 949) exited with exit code 1
2024-09-06 10:15:17.813 UTC [4635] ztnet@ztnet FATAL:  terminating connection due to administrator command
2024-09-06 10:15:17.813 UTC [5893] ztnet@ztnet FATAL:  terminating connection due to administrator command
2024-09-06 10:15:17.816 UTC [3870] ztnet@ztnet FATAL:  terminating connection due to administrator command
2024-09-06 10:15:17.817 UTC [4255] ztnet@ztnet FATAL:  terminating connection due to administrator command
2024-09-06 10:15:17.819 UTC [3880] ztnet@ztnet FATAL:  terminating connection due to administrator command
2024-09-06 10:15:17.842 UTC [944] LOG:  shutting down
2024-09-06 10:15:18.031 UTC [888] LOG:  database system is shut down
2024-09-06 10:15:18.424 UTC [5943] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 10:15:18.425 UTC [5943] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 10:15:18.450 UTC [5943] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 10:15:18.585 UTC [5944] LOG:  database system was shut down at 2024-09-06 10:15:17 UTC
2024-09-06 10:15:18.645 UTC [5943] LOG:  database system is ready to accept connections
2024-09-06 10:16:06.410 UTC [6117] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 10:16:06.413 UTC [6116] ztnet@ztnet LOG:  could not receive data from client: Connection reset by peer
2024-09-06 10:16:06.659 UTC [5943] LOG:  received fast shutdown request
2024-09-06 10:16:06.696 UTC [5943] LOG:  aborting any active transactions
2024-09-06 10:16:06.700 UTC [5943] LOG:  background worker "logical replication launcher" (PID 5950) exited with exit code 1
2024-09-06 10:16:06.707 UTC [5945] LOG:  shutting down
2024-09-06 10:16:06.946 UTC [5943] LOG:  database system is shut down
2024-09-06 10:17:19.743 UTC [891] LOG:  starting PostgreSQL 12.20 (Ubuntu 12.20-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0, 64-bit
2024-09-06 10:17:19.751 UTC [891] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2024-09-06 10:17:19.784 UTC [891] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-09-06 10:17:20.129 UTC [892] LOG:  database system was shut down at 2024-09-06 10:16:06 UTC
2024-09-06 10:17:20.374 UTC [891] LOG:  database system is ready to accept connections

sinamics · 2024-09-06T10:54:58Z

sinamics
Sep 6, 2024
Maintainer

I think your database is in an inconsistent state after a power failure of some sort.

Did these errors shows up after the inital installation?
Have you changed any settings related to database connections?

4 replies

qwaldo Sep 6, 2024
Author

No!
After the initial installation everything was fine! There were no problems for 3 months, everything worked perfectly!

qwaldo Sep 6, 2024
Author

curl -s http://install.ztnet.network | sudo bash -s -- -u
+
curl -s http://install.ztnet.network | sudo bash

Only this way?

sinamics Sep 6, 2024
Maintainer

Those commands would not solve anything.
post the content of:

ps aux | grep postgres

sudo -u postgres /usr/lib/postgresql/12/bin/pg_ctl status -D /var/lib/postgresql/12/main

sudo journalctl -u postgresql -n 100

qwaldo Sep 6, 2024
Author

ps aux | grep postgres
postgres     891  0.0  0.7 215704 29316 ?        Ss   10:17   0:00 /usr/lib/postgresql/12/bin/postgres -D /var/lib/postgresql/12/main -c config_file=/etc/postgresql/12/main/postgresql.conf
postgres     893  0.0  0.2 215848  8632 ?        Ss   10:17   0:00 postgres: 12/main: checkpointer
postgres     894  0.0  0.1 215704  6164 ?        Ss   10:17   0:00 postgres: 12/main: background writer
postgres     895  0.0  0.2 215704 10308 ?        Ss   10:17   0:00 postgres: 12/main: walwriter
postgres     896  0.0  0.2 216372  8748 ?        Ss   10:17   0:00 postgres: 12/main: autovacuum launcher
postgres     897  0.0  0.1  70204  5012 ?        Ss   10:17   0:00 postgres: 12/main: stats collector
postgres     898  0.0  0.1 216136  7052 ?        Ss   10:17   0:00 postgres: 12/main: logical replication launcher
postgres    1801  0.0  0.4 217140 18472 ?        Ss   11:14   0:00 postgres: 12/main: ztnet ztnet 127.0.0.1(59466) idle
postgres    1914  0.0  0.4 217016 18240 ?        Ss   11:44   0:00 postgres: 12/main: ztnet ztnet 127.0.0.1(48892) idle
postgres    1934  0.0  0.4 217016 18220 ?        Ss   11:49   0:00 postgres: 12/main: ztnet ztnet 127.0.0.1(43326) idle
postgres    1947  0.0  0.3 216768 15616 ?        Ss   11:53   0:00 postgres: 12/main: ztnet ztnet 127.0.0.1(58768) idle
postgres    1948  0.1  0.3 216776 15604 ?        Ss   11:53   0:00 postgres: 12/main: ztnet ztnet 127.0.0.1(58772) idle

sudo -u postgres /usr/lib/postgresql/12/bin/pg_ctl status -D /var/lib/postgresql/12/main
pg_ctl: server is running (PID: 891)
/usr/lib/postgresql/12/bin/postgres "-D" "/var/lib/postgresql/12/main" "-c" "config_file=/etc/postgresql/12/main/postgresql.conf"

sudo journalctl -u postgresql -n 100
-- Logs begin at Mon 2024-07-08 14:11:22 UTC, end at Fri 2024-09-06 11:53:53 UTC. --
Jul 08 14:48:26 ztc systemd[1]: Starting PostgreSQL RDBMS...
Jul 08 14:48:26 ztc systemd[1]: Finished PostgreSQL RDBMS.
-- Reboot --
Aug 09 10:05:39 ztc systemd[1]: Starting PostgreSQL RDBMS...
Aug 09 10:05:39 ztc systemd[1]: Finished PostgreSQL RDBMS.
-- Reboot --
Aug 19 07:02:46 ztc systemd[1]: Starting PostgreSQL RDBMS...
Aug 19 07:02:46 ztc systemd[1]: Finished PostgreSQL RDBMS.
Sep 06 05:39:51 ztc systemd[1]: postgresql.service: Succeeded.
Sep 06 05:39:51 ztc systemd[1]: Stopped PostgreSQL RDBMS.
-- Reboot --
Sep 06 05:42:25 ztc systemd[1]: Starting PostgreSQL RDBMS...
Sep 06 05:42:25 ztc systemd[1]: Finished PostgreSQL RDBMS.
Sep 06 05:57:54 ztc systemd[1]: postgresql.service: Succeeded.
Sep 06 05:57:54 ztc systemd[1]: Stopped PostgreSQL RDBMS.
-- Reboot --
Sep 06 05:59:04 ztc systemd[1]: Starting PostgreSQL RDBMS...
Sep 06 05:59:04 ztc systemd[1]: Finished PostgreSQL RDBMS.
-- Reboot --
Sep 06 06:23:48 ztc systemd[1]: Starting PostgreSQL RDBMS...
Sep 06 06:23:48 ztc systemd[1]: Finished PostgreSQL RDBMS.
-- Reboot --
Sep 06 08:57:44 ztc systemd[1]: Starting PostgreSQL RDBMS...
Sep 06 08:57:44 ztc systemd[1]: Finished PostgreSQL RDBMS.
Sep 06 10:15:17 ztc systemd[1]: postgresql.service: Succeeded.
Sep 06 10:15:17 ztc systemd[1]: Stopped PostgreSQL RDBMS.
Sep 06 10:15:17 ztc systemd[1]: Stopping PostgreSQL RDBMS...
Sep 06 10:15:20 ztc systemd[1]: Starting PostgreSQL RDBMS...
Sep 06 10:15:20 ztc systemd[1]: Finished PostgreSQL RDBMS.
Sep 06 10:16:06 ztc systemd[1]: postgresql.service: Succeeded.
Sep 06 10:16:06 ztc systemd[1]: Stopped PostgreSQL RDBMS.
-- Reboot --
Sep 06 10:17:22 ztc systemd[1]: Starting PostgreSQL RDBMS...
Sep 06 10:17:22 ztc systemd[1]: Finished PostgreSQL RDBMS.

sinamics · 2024-09-06T12:27:57Z

sinamics
Sep 6, 2024
Maintainer

what does this command returns?

npx prisma migrate deploy --schema /opt/ztnet/prisma/prisma/schema.prisma

5 replies

qwaldo Sep 6, 2024
Author

npx prisma migrate deploy --schema /opt/ztnet/prisma/prisma/schema.prisma
Need to install the following packages:
[email protected]
Ok to proceed? (y) y

Prisma schema loaded from ../../opt/ztnet/prisma/prisma/schema.prisma
Datasource "db": PostgreSQL database

Error: Prisma schema validation - (get-config wasm)
Error code: P1012
error: Environment variable not found: DATABASE_URL.
  -->  /opt/ztnet/prisma/prisma/schema.prisma:11
   |
10 |   provider          = "postgresql"
11 |   url               = env("DATABASE_URL")
   |

Validation Error Count: 1
[Context: getConfig]

Prisma CLI Version : 5.19.1
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.8.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.3
npm notice To update run: npm install -g [email protected]
npm notice

qwaldo Sep 6, 2024
Author

npm install -g [email protected]
npm error code EACCES
npm error syscall rename
npm error path /usr/lib/node_modules/npm
npm error dest /usr/lib/node_modules/.npm-qUIFSsiV
npm error errno -13
npm error [Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm-qUIFSsiV'] {
npm error   errno: -13,
npm error   code: 'EACCES',
npm error   syscall: 'rename',
npm error   path: '/usr/lib/node_modules/npm',
npm error   dest: '/usr/lib/node_modules/.npm-qUIFSsiV'
npm error }
npm error
npm error The operation was rejected by your operating system.
npm error It is likely you do not have the permissions to access this file as the current user
npm error
npm error If you believe this might be a permissions issue, please double-check the
npm error permissions of the file and its containing directories, or try running
npm error the command again as root/Administrator.

cat /home/user/.npm/_logs/2024-09-06T12_33_44_046Z-debug-0.log

0 verbose cli /usr/bin/node /usr/bin/npm
1 info using [email protected]
2 info using [email protected]
3 silly config:load:file:/usr/lib/node_modules/npm/npmrc
4 silly config:load:file:/home/user/.npmrc
5 silly config:load:file:/usr/etc/npmrc
6 verbose title npm install [email protected]
7 verbose argv "install" "--global" "[email protected]"
8 verbose logfile logs-max:10 dir:/home/user/.npm/_logs/2024-09-06T12_33_44_046Z-
9 verbose logfile /home/user/.npm/_logs/2024-09-06T12_33_44_046Z-debug-0.log
10 silly logfile done cleaning log files
11 http fetch GET 200 https://registry.npmjs.org/npm 533ms (cache miss)
12 silly idealTree buildDeps
13 silly fetch manifest [email protected]
14 http fetch GET 200 https://registry.npmjs.org/npm 1412ms (cache miss)
15 silly placeDep ROOT [email protected] OK for:  want: 10.8.3
16 silly reify mark retired [ '/usr/lib/node_modules/npm', '/usr/bin/npm', '/usr/bin/npx' ]
17 silly reify moves {
17 silly reify   '/usr/lib/node_modules/npm': '/usr/lib/node_modules/.npm-qUIFSsiV',
17 silly reify   '/usr/bin/npm': '/usr/bin/.npm-CxSgn0z2',
17 silly reify   '/usr/bin/npx': '/usr/bin/.npx-akSQqeWh'
17 silly reify }
18 verbose stack Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm-qUIFSsiV'
19 verbose cwd /home/user
20 verbose Linux 5.4.0-193-generic
21 verbose node v18.20.4
22 verbose npm  v10.7.0
23 error code EACCES
24 error syscall rename
25 error path /usr/lib/node_modules/npm
26 error dest /usr/lib/node_modules/.npm-qUIFSsiV
27 error errno -13
28 error [Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm-qUIFSsiV'] {
28 error   errno: -13,
28 error   code: 'EACCES',
28 error   syscall: 'rename',
28 error   path: '/usr/lib/node_modules/npm',
28 error   dest: '/usr/lib/node_modules/.npm-qUIFSsiV'
28 error }
29 error
29 error The operation was rejected by your operating system.
29 error It is likely you do not have the permissions to access this file as the current user
29 error
29 error If you believe this might be a permissions issue, please double-check the
29 error permissions of the file and its containing directories, or try running
29 error the command again as root/Administrator.
30 verbose exit -13
31 verbose code -13
32 silly unfinished npm timer reify 1725626026042
33 silly unfinished npm timer reify:retireShallow 1725626029417

sinamics Sep 6, 2024
Maintainer

try

cd /opt/ztnet

Then

npx prisma migrate deploy --schema prisma/prisma/schema.prisma

qwaldo Sep 6, 2024
Author

npx prisma migrate deploy --schema prisma/prisma/schema.prisma
Environment variables loaded from .env
Prisma schema loaded from prisma/prisma/schema.prisma
Datasource "db": PostgreSQL database "ztnet", schema "public" at "127.0.0.1:5432"

36 migrations found in prisma/migrations

No pending migrations to apply.

sinamics Sep 6, 2024
Maintainer

That looks fine.
Im not sure what could be the issue. ztnet logs shows that it cannot talk with the postgres db

Sep 06 05:40:00 ztc node[743]: Can't reach database server at `127.0.0.1`:`5432`

But when you run the npx prisma migrate command it can communicate with db

Datasource "db": PostgreSQL database "ztnet", schema "public" at "127.0.0.1:5432"

You can also test if you can reach the db using nc, this should return localhost [127.0.0.1] 5432 (postgresql) open

nc -zv 127.0.0.1 5432

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ZTNET ui not responding #540

{{title}}

Replies: 4 comments 16 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

ZTNET ui not responding #540

qwaldo Sep 6, 2024

Replies: 4 comments · 16 replies

sinamics Sep 6, 2024 Maintainer

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

qwaldo Sep 6, 2024 Author

sinamics Sep 6, 2024 Maintainer

qwaldo
Sep 6, 2024

Replies: 4 comments 16 replies

sinamics
Sep 6, 2024
Maintainer

sinamics Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

sinamics Sep 6, 2024
Maintainer

sinamics Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

sinamics
Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

sinamics
Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

qwaldo Sep 6, 2024
Author

sinamics Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

sinamics
Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

qwaldo Sep 6, 2024
Author

sinamics Sep 6, 2024
Maintainer

qwaldo Sep 6, 2024
Author

sinamics Sep 6, 2024
Maintainer