ERPnext manual install

[AbinayaSekar]

Hi all,
I am trying to install erpnext by using the below guide,

Guide: Manual Install ERPNext on Ubuntu 17.xx & 18.xx

Setup Supervisor & Nginx for Production By default, the ERPNext application listens on port 8000, not the standard HTTP port 80. Also, running the built in web server for production use is not recommended as we will be exposing the server to the world. You should use a production web server as a reverse proxy such as Apache or Nginx. We will use Nginx as a reverse proxy as it can be automatically configured using Bench. Bench can automatically generate and install the configuration according to …

In the Setup Supervisor & Nginx for Production step,
when i give the sudo supervisorctl status all i am getting the following error,
bench@abhi:~/erpnext$ sudo supervisorctl status all
erpnext-redis:erpnext-redis-cache FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-queue FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-socketio FATAL Exited too quickly (process log may have details)
erpnext-web:erpnext-frappe-web RUNNING pid 30123, uptime 0:00:03
erpnext-web:erpnext-node-socketio FATAL Exited too quickly (process log may have details)
erpnext-workers:erpnext-frappe-default-worker-0 RUNNING pid 29901, uptime 0:00:59
erpnext-workers:erpnext-frappe-long-worker-0 RUNNING pid 29903, uptime 0:00:59
erpnext-workers:erpnext-frappe-schedule RUNNING pid 29902, uptime 0:00:59
erpnext-workers:erpnext-frappe-short-worker-0 RUNNING pid 29904, uptime 0:00:59

Kindly help…

[arokia]

@AbinayaSekar What is the result for this command sudo systemctl status redis ?

[AbinayaSekar]

@AbinayaSekar

erpnext-redis:erpnext-redis-cache FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-queue FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-socketio FATAL Exited too quickly (process log may have details)
erpnext-web:erpnext-frappe-web RUNNING pid 30123, uptime 0:00:03
erpnext-web:erpnext-node-socketio FATAL Exited too quickly (process log may have details)
erpnext-workers:erpnext-frappe-default-worker-0 RUNNING pid 29901, uptime 0:00:59
erpnext-workers:erpnext-frappe-long-worker-0 RUNNING pid 29903, uptime 0:00:59
erpnext-workers:erpnext-frappe-schedule RUNNING pid 29902, uptime 0:00:59
erpnext-workers:erpnext-frappe-short-worker-0 RUNNING pid 29904, uptime 0:00:59

erpnext-redis:erpnext-redis-cache FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-queue FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-socketio FATAL Exited too quickly (process log may have details)
erpnext-web:erpnext-frappe-web RUNNING pid 30123, uptime 0:00:03
erpnext-web:erpnext-node-socketio FATAL Exited too quickly (process log may have details)
erpnext-workers:erpnext-frappe-default-worker-0 RUNNING pid 29901, uptime 0:00:59
erpnext-workers:erpnext-frappe-long-worker-0 RUNNING pid 29903, uptime 0:00:59
erpnext-workers:erpnext-frappe-schedule RUNNING pid 29902, uptime 0:00:59
erpnext-workers:erpnext-frappe-short-worker-0 RUNNING pid 29904, uptime 0:00:59

[arokia]

@AbinayaSekar sudo supervisorctl stop all
sudo supervisorctl start all try these codes and clear your browsing history then check am not sure it may clear your problem.

[saurabh6790]

@AbinayaSekar

erpnext-redis:erpnext-redis-cache FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-queue FATAL Exited too quickly (process log may have details)
erpnext-redis:erpnext-redis-socketio FATAL Exited too quickly (process log may have details)
erpnext-web:erpnext-frappe-web RUNNING pid 30123, uptime 0:00:03
erpnext-web:erpnext-node-socketio FATAL Exited too quickly (process log may have details)
erpnext-workers:erpnext-frappe-default-worker-0 RUNNING pid 29901, uptime 0:00:59
erpnext-workers:erpnext-frappe-long-worker-0 RUNNING pid 29903, uptime 0:00:59
erpnext-workers:erpnext-frappe-schedule RUNNING pid 29902, uptime 0:00:59
erpnext-workers:erpnext-frappe-short-worker-0 RUNNING pid 29904, uptime 0:00:59

Seems dependancies are broken. First run bench setup requirements and then restart the supervisor.

If above thing not works then check frappe-bench/logs or [bench-name]/logs for more details.

[AbinayaSekar]

Hi this i fixed some how. But even after successful installation of ERPnext, i am unable to view the erpnext page. The site cant be reached error is still coming.

[trentmu]

You can try this… (log in as the user you created frappe/erpnext with [eg. frappe] - not as root)

cd ~/frappe-bench
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
sudo supervisorctl restart all

[AbinayaSekar]

Thanks trentmu, but still same issue is persisting. still unable to reach the site.

[AbinayaSekar]

Thanks you fixed this issue. The problem was port. I was listening to a wrong port. I found the port from the ngnix.conf file and it was listening to 8002 and when i mentioned in the url, it worked. Thanks a lot for ur support