Thanks Mustafa.
I am not sure I understood your answer. This is what I tried, after reading your response:
sudo systemctl stop nginx.service supervisor.service
After the above command, âps auxâ confirms that neither âsupervisorâ nor ânginxâ nor âfrappeâ process are running (and I can confirm that all of them were running before I stopped them using the above command).
After that, if I issue
bench start
I get
03:05:32 system | redis_socketio.1 started (pid=6410)
03:05:32 redis_socketio.1 | [6424] 24 May 03:05:32.860 # Creating Server TCP listening socket 127.0.0.1:12000: bind: Address already in use
03:05:32 system | redis_socketio.1 stopped (rc=1)
03:05:32 system | watch.1 started (pid=6414)
03:05:32 system | workerbeat.1 started (pid=6412)
03:05:32 system | web.1 started (pid=6419)
03:05:32 system | async_worker.1 started (pid=6418)
03:05:32 system | redis_cache.1 started (pid=6421)
03:05:32 system | redis_queue.1 started (pid=6423)
03:05:32 redis_queue.1 | [6438] 24 May 03:05:32.877 # Creating Server TCP listening socket 127.0.0.1:11000: bind: Address already in use
03:05:32 system | socketio.1 started (pid=6426)
03:05:32 system | redis_queue.1 stopped (rc=1)
03:05:32 redis_cache.1 | [6436] 24 May 03:05:32.880 # Creating Server TCP listening socket 127.0.0.1:13000: bind: Address already in use
03:05:32 system | redis_cache.1 stopped (rc=1)
03:05:32 system | longjob_worker.1 started (pid=6425)
03:05:32 system | worker.1 started (pid=6420)
03:05:32 system | sending SIGTERM to workerbeat.1 (pid 6412)
03:05:32 system | sending SIGTERM to watch.1 (pid 6414)
03:05:32 system | sending SIGTERM to web.1 (pid 6419)
03:05:32 system | sending SIGTERM to async_worker.1 (pid 6418)
03:05:32 system | sending SIGTERM to socketio.1 (pid 6426)
03:05:32 system | sending SIGTERM to worker.1 (pid 6420)
03:05:32 system | sending SIGTERM to longjob_worker.1 (pid 6425)
03:05:32 system | watch.1 stopped (rc=-15)
03:05:32 system | web.1 stopped (rc=-15)
03:05:32 system | async_worker.1 stopped (rc=-15)
03:05:32 system | longjob_worker.1 stopped (rc=-15)
03:05:32 system | workerbeat.1 stopped (rc=-15)
03:05:32 system | socketio.1 stopped (rc=-15)
03:05:32 system | worker.1 stopped (rc=-15)
If I try
sudo bench start
I get a similar message
03:06:54 system | redis_socketio.1 started (pid=6488)
03:06:54 redis_socketio.1 | [6501] 24 May 03:06:54.522 # Creating Server TCP listening socket 127.0.0.1:12000: bind: Address already in use
03:06:54 system | async_worker.1 started (pid=6495)
03:06:54 system | socketio.1 started (pid=6496)
03:06:54 system | redis_socketio.1 stopped (rc=1)
03:06:54 system | redis_queue.1 started (pid=6498)
03:06:54 system | web.1 started (pid=6493)
03:06:54 system | watch.1 started (pid=6497)
03:06:54 redis_queue.1 | [6512] 24 May 03:06:54.532 # Creating Server TCP listening socket 127.0.0.1:11000: bind: Address already in use
03:06:54 system | redis_queue.1 stopped (rc=1)
03:06:54 system | redis_cache.1 started (pid=6499)
03:06:54 system | workerbeat.1 started (pid=6489)
03:06:54 system | worker.1 started (pid=6503)
03:06:54 system | longjob_worker.1 started (pid=6500)
03:06:54 system | sending SIGTERM to workerbeat.1 (pid 6489)
03:06:54 system | sending SIGTERM to watch.1 (pid 6497)
03:06:54 system | sending SIGTERM to web.1 (pid 6493)
03:06:54 system | sending SIGTERM to async_worker.1 (pid 6495)
03:06:54 system | sending SIGTERM to socketio.1 (pid 6496)
03:06:54 system | sending SIGTERM to redis_cache.1 (pid 6499)
03:06:54 system | sending SIGTERM to worker.1 (pid 6503)
03:06:54 system | sending SIGTERM to longjob_worker.1 (pid 6500)
03:06:54 system | watch.1 stopped (rc=-15)
03:06:54 system | redis_cache.1 stopped (rc=-15)
03:06:54 system | async_worker.1 stopped (rc=-15)
03:06:54 system | worker.1 stopped (rc=-15)
03:06:54 system | workerbeat.1 stopped (rc=-15)
03:06:54 system | socketio.1 stopped (rc=-15)
03:06:54 system | longjob_worker.1 stopped (rc=-15)
03:06:54 system | web.1 stopped (rc=-15)
After either command, âps auxâ shows that neither âfrappeâ nor âsupervisorâ nor ânginxâ is running. If I try âlocalhost:8000â or âlocalhost:80â in a browser, I get âUnable to Connectâ message.
If I issue the command
sudo systemctl start nginx.service supervisor.service
then of course âps auxâ shows that âsupervisorâ and ânginxâ and âfrappeâ are running. Next, if I try âlocalhost:8000â in a browser, I get the error message previously reported:
Not Found
./localhost/site_config.json does not exist
If I try âlocalhost:80â, the page is similar to what I reported in my first message above. I get three separate options: (1) to enter email id and password, (2) to enter full name and email id or (3) to enter mail id and click on a âsend passwordâ button.
What am I doing wrong? And what should I be doing? This is my first experience with frappe and erpnext, so would appreciate a list of exact commands that I should be trying.
And Mustafa, I could change the password for administrator using the command you suggested, but that isnât really the problem. This is my problem: In a browser, how do I get the page which will allow me (i.e. the âuserâ with sudo privilege issuing all of the above mentioned commands) to login as administrator and proceed with setting up erpnext.
Thanks for any assistance.
arvind