ERPNext 13 beta install issue

Rgottsch1 · March 8, 2021, 3:49am

I am having issues. I’ve installed ERPNext on an Amazon EC2 environment and it installed ok. I was able to access it on port 8000. I then ran the following to deploy in production mode. Didn’t have any errors but upon the restart i can’t access my site on port 80 or 8000. I’ve ran bench start, and still cannot access. Any ideas? Any input is greatly appreciated. For the few moments I looked at v13 beta it looks great.

----- NOW deploy it in production mode - on nginx server -------
sudo apt install nginx supervisor
bench setup supervisor --yes
bench setup nginx
sudo ln -s pwd/config/supervisor.conf /etc/supervisor/conf.d/frappe-bench.conf
sudo ln -s pwd/config/nginx.conf /etc/nginx/conf.d/frappe-bench.conf
sudo systemctl enable supervisor
sudo systemctl enable nginx
restart the system - init 6

trentmu · March 9, 2021, 9:39am

I assume that the shown pwd /config/ refers to the install subdir?
Maybe hardcode that or use

sudo ln -s $HOME/frappe-bench/config/supervisor.conf /etc/supervisor/conf.d/frappe-bench.conf
sudo ln -s $HOME/frappe-bench/config/nginx.conf /etc/nginx/conf.d/frappe-bench.conf

Rgottsch1 · March 11, 2021, 2:19am

Sorry for the delay, thank-you for the reply. I ran the referenced hardcode lines you provided and it said they were already created. I ran bench start and still no luck. What port should I be referencing 80 or 8000 do not work. During bench start details are below -

/opt/bench/frappe-bench$ bench start
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
01:59:36 system           | redis_cache.1 started (pid=26194)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
/usr/lib/python3.8/subprocess.py:844: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  self.stdout = io.open(c2pread, 'rb', bufsize)
01:59:36 system           | redis_socketio.1 started (pid=26202)
01:59:36 system           | redis_queue.1 started (pid=26201)
01:59:36 system           | watch.1 started (pid=26210)
01:59:36 system           | web.1 started (pid=26215)
01:59:36 redis_cache.1    | 26204:C 11 Mar 2021 01:59:36.996 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
01:59:36 redis_cache.1    | 26204:C 11 Mar 2021 01:59:36.997 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=26204, just started
01:59:36 redis_cache.1    | 26204:C 11 Mar 2021 01:59:36.997 # Configuration loaded
01:59:36 redis_cache.1    | 26204:M 11 Mar 2021 01:59:36.998 * Increased maximum number of open files to 10032 (it was originally set to 1024).
01:59:36 redis_cache.1    | 26204:M 11 Mar 2021 01:59:36.999 # Could not create server TCP listening socket 127.0.0.1:13000: bind: Address already in use
01:59:37 system           | redis_cache.1 stopped (rc=1)
01:59:37 redis_socketio.1 | 26214:C 11 Mar 2021 01:59:37.007 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
01:59:37 redis_socketio.1 | 26214:C 11 Mar 2021 01:59:37.007 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=26214, just started
01:59:37 redis_socketio.1 | 26214:C 11 Mar 2021 01:59:37.007 # Configuration loaded
01:59:37 redis_queue.1    | 26207:C 11 Mar 2021 01:59:37.002 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
01:59:37 redis_queue.1    | 26207:C 11 Mar 2021 01:59:37.008 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=26207, just started
01:59:37 redis_queue.1    | 26207:C 11 Mar 2021 01:59:37.009 # Configuration loaded
01:59:37 redis_queue.1    | 26207:M 11 Mar 2021 01:59:37.009 * Increased maximum number of open files to 10032 (it was originally set to 1024).
01:59:37 system           | worker_long.1 started (pid=26213)
01:59:37 redis_queue.1    | 26207:M 11 Mar 2021 01:59:37.011 # Could not create server TCP listening socket 127.0.0.1:11000: bind: Address already in use
01:59:37 system           | worker_default.1 started (pid=26206)
01:59:37 system           | schedule.1 started (pid=26212)
01:59:37 system           | redis_queue.1 stopped (rc=1)
01:59:37 system           | worker_short.1 started (pid=26211)
01:59:37 system           | socketio.1 started (pid=26205)
01:59:37 system           | sending SIGTERM to redis_socketio.1 (pid 26202)
01:59:37 system           | sending SIGTERM to web.1 (pid 26215)
01:59:37 system           | sending SIGTERM to socketio.1 (pid 26205)
01:59:37 system           | sending SIGTERM to watch.1 (pid 26210)
01:59:37 system           | sending SIGTERM to schedule.1 (pid 26212)
01:59:37 system           | sending SIGTERM to worker_short.1 (pid 26211)
01:59:37 system           | sending SIGTERM to worker_long.1 (pid 26213)
01:59:37 system           | sending SIGTERM to worker_default.1 (pid 26206)
01:59:37 system           | worker_short.1 stopped (rc=-15)
01:59:37 system           | worker_long.1 stopped (rc=-15)
01:59:37 system           | worker_default.1 stopped (rc=-15)
01:59:37 redis_socketio.1 | 26214:signal-handler (1615427977) Received SIGTERM scheduling shutdown...
01:59:37 system           | web.1 stopped (rc=-15)
01:59:37 redis_socketio.1 | 26214:M 11 Mar 2021 01:59:37.020 * Increased maximum number of open files to 10032 (it was originally set to 1024).
01:59:37 redis_socketio.1 | 26214:M 11 Mar 2021 01:59:37.020 # Could not create server TCP listening socket 127.0.0.1:12000: bind: Address already in use
01:59:37 system           | socketio.1 stopped (rc=-15)
01:59:37 system           | redis_socketio.1 stopped (rc=-15)
01:59:37 system           | watch.1 stopped (rc=-15)
01:59:37 system           | schedule.1 stopped (rc=-15)

trentmu · March 11, 2021, 7:30am

01:59:37 redis_socketio.1 | 26214:M 11 Mar 2021 01:59:37.020 # Could not create server TCP listening socket 127.0.0.1:12000: bind: Address already in use

You already seem to have an instance running, so the bench start is causing a port conflict. Either you need to kill those processes, or maybe restart the server

Rgottsch1 · March 11, 2021, 11:50am

I rebooted and still can’t access. Ideas?

system · March 25, 2021, 11:52am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.