[Important] Bench version 2 - see this before you run bench update

[revant_one]

@anand

If you still want to get rid of the above message, you will have to regenerate all your configuration files by going to the frappe-bench folder and running these commands:

mv config config-bak
mkdir -p config/pids
sudo supervisorctl stop all
sudo service nginx stop
bench setup config
bench setup redis
bench setup supervisor
bench setup nginx
bench setup procfile
sudo bench setup sudoers frappe # or the user that you used to install erpnext
sudo nginx -t # check if this command shows any error
sudo service nginx reload
sudo supervisorctl reread
sudo supervisorctl update

I followed note 4,

had to follow Redis cache server not running. Please contact Administrator / Techsupport error to remove redis-cache error

In brief :

@wroc77

Change save ‘’ to save 300 10

Details:

SNAPSHOTTING

· Save the DB on disk:· save ‘seconds’ ‘changes’· Will save the DB if both the given number of seconds and the given· number of write operations against the DB occurred.· In the example below the behaviour will be to save:· after 900 sec (15 min) if at least 1 key changed· after 300 sec (5 min) if at least 10 keys changed· after 60 sec if at least 10000 keys changed

· Note: you can disable saving at all commenting all the “save” lines.

I see no error on bench update now. I get error on sudo supervisorctl status

output of sudo supervisorctl status :

frappe-bench-processes:frappe-bench-frappe-async-worker RUNNING    pid 3461, uptime 0:07:55
frappe-bench-processes:frappe-bench-frappe-longjob-worker RUNNING    pid 3462, uptime 0:07:55
frappe-bench-processes:frappe-bench-frappe-web RUNNING    pid 3486, uptime 0:07:54
frappe-bench-processes:frappe-bench-frappe-worker RUNNING    pid 3497, uptime 0:07:54
frappe-bench-processes:frappe-bench-frappe-workerbeat RUNNING    pid 3479, uptime 0:07:55
frappe-bench-processes:frappe-bench-node-socketio RUNNING    pid 3517, uptime 0:07:51
frappe-bench-redis:frappe-bench-redis-cache RUNNING    pid 3514, uptime 0:07:52
frappe-bench-redis:frappe-bench-redis-queue FATAL      Exited too quickly (process log may have details)
frappe-bench-redis:frappe-bench-redis-socketio RUNNING    pid 3519, uptime 0:07:51

process log logs/redis-queue.log:

[3513] 25 Mar 09:22:45 # Opening port 6379: bind: Address already in use
[3518] 25 Mar 09:22:46 # Opening port 6379: bind: Address already in use
[3528] 25 Mar 09:22:49 # Opening port 6379: bind: Address already in use
[3529] 25 Mar 09:22:52 # Opening port 6379: bind: Address already in use

Everything is working fine on desk. No errors on desk.

solved with :

@anand

Ok. I think I got the problem. Try this if you are not using this server for anything else other than erpnext:

sudo update-rc.d redis-server disable
sudo supervisorctl start all

sudo update-rc.d redis-server disable
sudo service redis-server stop
sudo supervisorctl start all