How To Perform Bench Update

Hi Everyone,

I am new to Erpnext and want to install it on my Windows 7 system. I want to use this in a network environment of server and client.
I am trying to install it using Vitual box but i am stuck. I Have installed it successfully and opened the internet explorer and went to location http://localhost:8080/desk#setup-wizard . In the last step of the setup wizard i am getting this error.

After going through the forum i found different suggestions one of them was to update bench. I dont know how to do it. Can you please help me get through this error and help me setup my company. Also can anyone tell me how to use itas server and client.

Thank you IN Advance

Regards
Sagar

Are you using erpnext old image? Its very old bug.
Please refer this post

No i downloaded the latest image from this location
https://erpnext.com/download

https://erpnext.com/downloads/ERPNext-100915.ova (1.1GB, MD5 Checksum - 753d07d58dfc03ba0d4793b768e69760)

Created on 10th September, 2015.

Thanks Reagrds

I Downloaded Virtual box and Image today only. 18-12-2015

Run this commands

cd frappe-bench
bench update
bench reinstall

i Have done that and it is installed properly now. Thank you for the Help.

Can you please tell me how i can use erp next in two systems simultaneously. Server and client

Thanks
regards

@sagar1

You need to create new site and assign port to new site.

bench new-site site2name
bench set-nginx-port site2name 9000
bench setup nginx
sudo service nginx reload 

you can refer this link https://github.com/frappe/bench/wiki/Multitenant-Setup

hi
after upgrading the bench is not starting. following is the message. Please help

next@NEXT-ERP:~/frappe-bench$ bench start
10:55:07 system | redis_socketio.1 started (pid=39587)
10:55:07 redis_socketio.1 | 39594:C 28 Oct 10:55:07.400 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10:55:07 redis_socketio.1 | 39594:C 28 Oct 10:55:07.400 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=39594, just started
10:55:07 redis_socketio.1 | 39594:C 28 Oct 10:55:07.400 # Configuration loaded
10:55:07 redis_socketio.1 | 39594:M 28 Oct 10:55:07.401 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
10:55:07 redis_socketio.1 | 39594:M 28 Oct 10:55:07.401 # Server can’t set maximum open files to 10032 because of OS error: Operation not permitted.
10:55:07 redis_socketio.1 | 39594:M 28 Oct 10:55:07.401 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.
10:55:07 redis_socketio.1 | 39594:M 28 Oct 10:55:07.401 # Creating Server TCP listening socket 127.0.0.1:12000: bind: Address already in use
10:55:07 system | redis_socketio.1 stopped (rc=1)
10:55:07 system | worker_long.1 started (pid=39593)
10:55:07 system | worker_default.1 started (pid=39600)
10:55:07 system | watch.1 started (pid=39599)
10:55:07 system | socketio.1 started (pid=39598)
10:55:07 system | schedule.1 started (pid=39612)
10:55:07 system | redis_cache.1 started (pid=39616)
10:55:07 redis_cache.1 | 39618:C 28 Oct 10:55:07.521 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10:55:07 redis_cache.1 | 39618:C 28 Oct 10:55:07.521 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=39618, just started
10:55:07 redis_cache.1 | 39618:C 28 Oct 10:55:07.521 # Configuration loaded
10:55:07 redis_cache.1 | 39618:M 28 Oct 10:55:07.530 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
10:55:07 redis_cache.1 | 39618:M 28 Oct 10:55:07.530 # Server can’t set maximum open files to 10032 because of OS error: Operation not permitted.
10:55:07 redis_cache.1 | 39618:M 28 Oct 10:55:07.530 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.
10:55:07 redis_cache.1 | 39618:M 28 Oct 10:55:07.530 # Creating Server TCP listening socket 127.0.0.1:13000: bind: Address already in use
10:55:07 system | redis_cache.1 stopped (rc=1)
10:55:07 system | worker_short.1 started (pid=39615)
10:55:07 system | web.1 started (pid=39610)
10:55:07 system | redis_queue.1 started (pid=39621)
10:55:07 system | sending SIGTERM to worker_long.1 (pid 39593)
10:55:07 system | sending SIGTERM to watch.1 (pid 39599)
10:55:07 system | sending SIGTERM to redis_queue.1 (pid 39621)
10:55:07 system | sending SIGTERM to web.1 (pid 39610)
10:55:07 system | sending SIGTERM to schedule.1 (pid 39612)
10:55:07 system | sending SIGTERM to worker_default.1 (pid 39600)
10:55:07 system | sending SIGTERM to socketio.1 (pid 39598)
10:55:07 system | sending SIGTERM to worker_short.1 (pid 39615)
10:55:07 redis_queue.1 | 39625:C 28 Oct 10:55:07.601 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10:55:07 redis_queue.1 | 39625:C 28 Oct 10:55:07.601 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=39625, just started
10:55:07 system | worker_long.1 stopped (rc=-15)
10:55:07 system | worker_short.1 stopped (rc=-15)
10:55:07 system | schedule.1 stopped (rc=-15)
10:55:07 system | web.1 stopped (rc=-15)
10:55:07 redis_queue.1 | 39625:C 28 Oct 10:55:07.601 # Configuration loaded
10:55:07 redis_queue.1 | 39625:M 28 Oct 10:55:07.610 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
10:55:07 redis_queue.1 | 39625:M 28 Oct 10:55:07.610 # Server can’t set maximum open files to 10032 because of OS error: Operation not permitted.
10:55:07 redis_queue.1 | 39625:M 28 Oct 10:55:07.610 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase ‘ulimit -n’.
10:55:07 redis_queue.1 | 39625:M 28 Oct 10:55:07.611 # Creating Server TCP listening socket 127.0.0.1:11000: bind: Address already in use
10:55:07 system | redis_queue.1 stopped (rc=1)
10:55:07 system | socketio.1 stopped (rc=-15)
10:55:07 system | worker_default.1 stopped (rc=-15)
10:55:07 system | watch.1 stopped (rc=-15)

You seem to have a permissions problem.
Try…

supervisorctl restart all

hi
After restarting the linux server itself. it seems all are ok. thanks for your reply.