When click on print then check the console log (f12)/Error log
I also have the same problem
You might have socketio broken, multi-pdf print right now prints in background and then sends link using socketio.
I can’t confirm what caused it, but I’m sure it’s not caused by Socketio
I also have the same problem,do you have any solutions?
I haven’t found a solution yet!
when i check the supervisor status i got this result
sudo supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache RUNNING pid 972, uptime 0:06:52
frappe-bench-redis:frappe-bench-redis-queue RUNNING pid 973, uptime 0:06:52
frappe-bench-web:frappe-bench-frappe-web RUNNING pid 975, uptime 0:06:52
frappe-bench-web:frappe-bench-node-socketio FATAL Exited too quickly (process log may have details)
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING pid 987, uptime 0:06:52
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING pid 985, uptime 0:06:52
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING pid 986, uptime 0:06:52
and got this error in the error log for socketio
SyntaxError: Unexpected token ‘.’
at wrapSafe (internal/modules/cjs/loader.js:915:16)
at Module._compile (internal/modules/cjs/loader.js:963:27)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/home/erptaha/frappe-bench/apps/frappe/node_modules/@redis/client/dist/index.js:18:18)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:1027:10)
/home/erptaha/frappe-bench/apps/frappe/node_modules/@redis/client/dist/lib/client/index.js:35
modules: extensions?.modules,
^
hi sir do you have any solution for this issue
Can you share your supervisor config? It should be in bench/config folder.
bench setup socketio; Notes:
; priority=1 → Lower priorities indicate programs that start first and shut down last
; killasgroup=true → send kill signal to child processes too
; graceful timeout should always be lower than stopwaitsecs to avoid orphan gunicorn workers.
[program:frappe-bench-frappe-web]
command=/home/erptaha/frappe-bench/env/bin/gunicorn -b 127.0.0.1:8000 -w 9 --max-requests 5000 --max-requests-jitter 500 -t 120 --graceful-timeout 30 frappe.app:application --preload
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/web.log
stderr_logfile=/home/erptaha/frappe-bench/logs/web.error.log
stopwaitsecs=40
killasgroup=true
user=erptaha
directory=/home/erptaha/frappe-bench/sites
startretries=10
[program:frappe-bench-frappe-schedule]
command=/usr/local/bin/bench schedule
priority=3
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/schedule.log
stderr_logfile=/home/erptaha/frappe-bench/logs/schedule.error.log
user=erptaha
directory=/home/erptaha/frappe-bench
startretries=10
[program:frappe-bench-frappe-short-worker]
command=/usr/local/bin/bench worker --queue short,default
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/worker.log
stderr_logfile=/home/erptaha/frappe-bench/logs/worker.error.log
user=erptaha
stopwaitsecs=360
directory=/home/erptaha/frappe-bench
killasgroup=true
numprocs=1
process_name=%(program_name)s-%(process_num)d
startretries=10
[program:frappe-bench-frappe-long-worker]
command=/usr/local/bin/bench worker --queue long,default,short
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/worker.log
stderr_logfile=/home/erptaha/frappe-bench/logs/worker.error.log
user=erptaha
stopwaitsecs=1560
directory=/home/erptaha/frappe-bench
killasgroup=true
numprocs=1
process_name=%(program_name)s-%(process_num)d
startretries=10
[program:frappe-bench-redis-cache]
command=/usr/bin/redis-server /home/erptaha/frappe-bench/config/redis_cache.conf
priority=1
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/redis-cache.log
stderr_logfile=/home/erptaha/frappe-bench/logs/redis-cache.error.log
user=erptaha
directory=/home/erptaha/frappe-bench/sites
startretries=10
[program:frappe-bench-redis-queue]
command=/usr/bin/redis-server /home/erptaha/frappe-bench/config/redis_queue.conf
priority=1
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/redis-queue.log
stderr_logfile=/home/erptaha/frappe-bench/logs/redis-queue.error.log
user=erptaha
directory=/home/erptaha/frappe-bench/sites
startretries=10
[program:frappe-bench-node-socketio]
command=/usr/bin/node /home/erptaha/frappe-bench/apps/frappe/socketio.js
priority=4
autostart=true
autorestart=true
stdout_logfile=/home/erptaha/frappe-bench/logs/node-socketio.log
stderr_logfile=/home/erptaha/frappe-bench/logs/node-socketio.error.log
user=erptaha
directory=/home/erptaha/frappe-bench
startretries=10
[group:frappe-bench-web]
programs=frappe-bench-frappe-web,frappe-bench-node-socketio
[group:frappe-bench-workers]
programs=frappe-bench-frappe-schedule,frappe-bench-frappe-short-worker,frappe-bench-frappe-long-worker
[group:frappe-bench-redis]
programs=frappe-bench-redis-cache,frappe-bench-redis-queue
bench setup socketio
Can you share output of /usr/bin/node --version
v12.22.9
That’s the problem, you need to use Node18.x
Use nvm to install node18 and then change path in supervisor config. Restart supervisor for it to take effect
but when i use node -v the output is v18.20.1
Then you have node18 somewhere but not being used by supervisor.
Do which node and set that in supervisor config.
thank you for your help but can you explain for me the steps im not very familiar with these things