You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tailed all the logs and it is waiting for localhost:3101 and localhost:3103
2025-04-22 13:55:59,846 INFO success: syncing-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
==> /portainer/Files/AppData/Config/standard_notes/logs/auth-worker.log <==
localhost:3103 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/files-worker.log <==
localhost:3101 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/revisions-worker.log <==
localhost:3101 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/auth.log <==
localhost:3101 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/syncing-server-worker.log <==
localhost:3101 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/supervisord.log <==
2025-04-22 13:56:05,835 WARN exited: syncing-server (exit status 1; not expected)
==> /portainer/Files/AppData/Config/standard_notes/logs/api-gateway.log <==
localhost:3103 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/supervisord.log <==
2025-04-22 13:56:05,846 INFO spawned: 'syncing-server' with pid 1637
==> /portainer/Files/AppData/Config/standard_notes/logs/revisions.log <==
localhost:3101 is unavailable yet - waiting for it to start
==> /portainer/Files/AppData/Config/standard_notes/logs/syncing-server.log <==
db:3306 is up. Proceeding to startup.
cache:6379 is up. Proceeding to startup.
But all the docker containers logs, looks good to me.
db logs
2025-04-22 13:42:30+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2025-04-22 13:42:30+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.5-1.el9 started.
'/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2025-04-22T13:42:30.624273Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2025-04-22T13:42:30.904056Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.5) starting as process 1
2025-04-22T13:42:30.921602Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-04-22T13:42:31.499417Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2025-04-22T13:42:31.903231Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2025-04-22T13:42:31.903346Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2025-04-22T13:42:31.911735Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2025-04-22T13:42:31.972989Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock
2025-04-22T13:42:31.973557Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.4.5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server - GPL.
Localstack Logs
LocalStack version: 3.0.2
LocalStack build date: 2023-11-29
LocalStack build git hash: 60518e11
2025-04-22T13:15:59.574 WARN --- [ MainThread] localstack.deprecations : HOSTNAME_EXTERNAL is deprecated (since 2.0.0) and will be removed in upcoming releases of LocalStack! This configuration will be migrated to LOCALSTACK_HOST
2025-04-22T13:16:01.760 INFO --- [-functhread6] hypercorn.error : Running on https://0.0.0.0:4566 (CTRL + C to quit)
Ready.
Server logs (it continuosly spamming this kind of logs, changing the PID)
2025-04-22 13:59:51,462 INFO spawned: 'syncing-server' with pid 2352
2025-04-22 13:59:52,491 INFO success: syncing-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-22 13:59:57,887 WARN exited: syncing-server (exit status 1; not expected)
2025-04-22 13:59:58,890 INFO spawned: 'syncing-server' with pid 2381
2025-04-22 13:59:59,912 INFO success: syncing-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-22 14:00:09,580 WARN exited: syncing-server (exit status 1; not expected)
2025-04-22 14:00:10,586 INFO spawned: 'syncing-server' with pid 2410
2025-04-22 14:00:11,613 INFO success: syncing-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-22 14:00:17,333 WARN exited: syncing-server (exit status 1; not expected)
2025-04-22 14:00:18,338 INFO spawned: 'syncing-server' with pid 2439
2025-04-22 14:00:19,360 INFO success: syncing-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-04-22 14:00:25,673 WARN exited: syncing-server (exit status 1; not expected)
2025-04-22 14:00:26,098 INFO spawned: 'syncing-server' with pid 2462
Cache logs
1:C 22 Apr 2025 13:15:56.239 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 22 Apr 2025 13:15:56.239 # Redis version=6.0.20, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 22 Apr 2025 13:15:56.239 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 22 Apr 2025 13:15:56.243 * Running mode=standalone, port=6379.
1:M 22 Apr 2025 13:15:56.243 # Server initialized
1:M 22 Apr 2025 13:15:56.243 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 22 Apr 2025 13:15:56.243 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled (set to 'madvise' or 'never').
1:M 22 Apr 2025 13:15:56.244 * Ready to accept connections
Here is my docker compose, that is the same from the example, I am usign portainer because of that I use the stack.env instead of only .env
Yeah, I'm having issues as well, mainly with the server starting and stopping itself. I'm assuming this project has been abandoned based on the updates.
Yeah, I'm having issues as well, mainly with the server starting and stopping itself. I'm assuming this project has been abandoned based on the updates.
Uh oh!
There was an error while loading. Please reload this page.
``Hi there, I am trying to follow the instructions of the self hosting guide, but I ran into an issue.
Nothing happen in the browser when I try to reach the url: http://server-local-ip:3000 but if I try to reach http://server-local-ip:3125 something anwsers with a Not Found.
I tailed all the logs and it is waiting for localhost:3101 and localhost:3103
But all the docker containers logs, looks good to me.
db logs
Localstack Logs
Server logs (it continuosly spamming this kind of logs, changing the PID)
Cache logs
Here is my docker compose, that is the same from the example, I am usign portainer because of that I use the stack.env instead of only .env
And my .env
The text was updated successfully, but these errors were encountered: