This is my log
:~/frappe-bench$ bench start
10:44:38 system | redis_cache.1 started (pid=6974)
10:44:38 system | redis_queue.1 started (pid=6979)
10:44:38 system | web.1 started (pid=6982)
10:44:38 system | socketio.1 started (pid=6986)
10:44:38 redis_cache.1 | 6976:C 21 Aug 2024 10:44:38.446 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub. 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.
10:44:38 redis_cache.1 | 6976:C 21 Aug 2024 10:44:38.446 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10:44:38 redis_cache.1 | 6976:C 21 Aug 2024 10:44:38.446 * Redis version=7.4.0, bits=64, commit=00000000, modified=0, pid=6976, just started
10:44:38 redis_cache.1 | 6976:C 21 Aug 2024 10:44:38.446 * Configuration loaded
10:44:38 redis_cache.1 | 6976:M 21 Aug 2024 10:44:38.446 * Increased maximum number of open files to 10032 (it was originally set to 1024).
10:44:38 redis_cache.1 | 6976:M 21 Aug 2024 10:44:38.446 * monotonic clock: POSIX clock_gettime
10:44:38 redis_queue.1 | 6980:C 21 Aug 2024 10:44:38.447 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see vm.max_map_count growing steadily when vm.overcommit_memory is 2 · Issue #1328 · jemalloc/jemalloc · GitHub. 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.
10:44:38 redis_queue.1 | 6980:C 21 Aug 2024 10:44:38.447 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10:44:38 redis_queue.1 | 6980:C 21 Aug 2024 10:44:38.447 * Redis version=7.4.0, bits=64, commit=00000000, modified=0, pid=6980, just started
10:44:38 redis_queue.1 | 6980:C 21 Aug 2024 10:44:38.447 * Configuration loaded
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.447 * Increased maximum number of open files to 10032 (it was originally set to 1024).
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.447 * monotonic clock: POSIX clock_gettime
10:44:38 system | watch.1 started (pid=6990)
10:44:38 redis_cache.1 | 6976:M 21 Aug 2024 10:44:38.448 * Running mode=standalone, port=13000.
10:44:38 redis_cache.1 | 6976:M 21 Aug 2024 10:44:38.449 # Warning: Could not create server TCP listening socket 127.0.0.1:13000: bind: Address already in use
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.449 * Running mode=standalone, port=11000.
10:44:38 redis_cache.1 | 6976:M 21 Aug 2024 10:44:38.449 # Failed listening on port 13000 (tcp), aborting.
10:44:38 system | schedule.1 started (pid=6993)
10:44:38 system | worker.1 started (pid=6997)
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * Server initialized
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * Loading RDB produced by version 7.4.0
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * RDB age 246 seconds
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * RDB memory usage when created 0.92 Mb
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * Done loading RDB, keys loaded: 13, keys expired: 0.
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * DB loaded from disk: 0.000 seconds
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.450 * Ready to accept connections tcp
10:44:38 system | redis_cache.1 stopped (rc=1)
10:44:38 system | sending SIGTERM to redis_queue.1 (pid 6979)
10:44:38 system | sending SIGTERM to web.1 (pid 6982)
10:44:38 system | sending SIGTERM to socketio.1 (pid 6986)
10:44:38 system | sending SIGTERM to watch.1 (pid 6990)
10:44:38 system | sending SIGTERM to schedule.1 (pid 6993)
10:44:38 system | sending SIGTERM to worker.1 (pid 6997)
10:44:38 redis_queue.1 | 6980:signal-handler (1724217278) Received SIGTERM scheduling shutdown…
10:44:38 system | worker.1 stopped (rc=-15)
10:44:38 system | web.1 stopped (rc=-15)
10:44:38 system | watch.1 stopped (rc=-15)
10:44:38 system | schedule.1 stopped (rc=-15)
10:44:38 system | socketio.1 stopped (rc=-15)
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.552 * User requested shutdown…
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.552 * Saving the final RDB snapshot before exiting.
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.560 * DB saved on disk
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.560 * Removing the pid file.
10:44:38 redis_queue.1 | 6980:M 21 Aug 2024 10:44:38.560 # Redis is now ready to exit, bye bye…
10:44:38 system | redis_queue.1 stopped (rc=-15)
Maybe in the background another bench instance running
yeah, if I use this command :bench --site devo.com serve --port 8000
Address already in use
Port 8000 is in use by another program. Either identify and stop that program, or start the server with a different port.
how can solve this.
You can view by running
htop
Too kill process:
ps aux | grep schedule
kill -9 PROCESS_ID
1 Like
:~/frappe-bench$ ps aux | grep schedule
sumith 4532 0.0 0.7 79172 60520 ? SN 10:20 0:01 /home/sumith/frappe-bench/env/bin/python -m frappe.utils.bench_helper frappe schedule
sumith 7339 0.0 0.0 9212 2432 pts/0 S+ 10:52 0:00 grep --color=auto schedule
how should i use the next command, i mean what is process_id
4532