ERPNext Vagrant on MacOS Not Able To Access

alan · February 21, 2018, 5:13pm

I’m following the guidelines as following to setup the local development for ERPNext,
Create A Erpnext 9.0 Local Dev Environment Using Vagrant

however I’m not able to access via local host after bench start.

Would like to check if the following is necessary even though I’m using the Intel Network card.

Change network card to PCnet-FAST III

For NAT adapter

#vb.customize [“modifyvm”, :id, “–nictype1”, “Am79C973”]

For host-only adapter

#vb.customize [“modifyvm”, :id, “–nictype2”, “Am79C973”]

alan · February 23, 2018, 8:31pm

Anyone have solutions for this ?

What is the correct network setup at vagrant file for mac os 10.12 , virtual box 5.2.6 and vagrant Vagrant 2.0.2.

clarkej · February 23, 2018, 9:03pm

Your various logs - erpnext, nginx and so on should give you pointers to what is working and not.

To debug network connectivity and closed port issues netcat or telnet are invaluable.

That said I am not VB, Vagrant or MacOS savvy

good luck

System19 · February 25, 2018, 1:35pm

Hi @alan The Am79C973 nics are virtual so it doesn’t matter what actual physical nic your host machine has. Just use Am79C973.
What happens when you bench start from within cd /home/frappe/frappe-bench/
You are opening your web browser at localhost:8080

alan · March 9, 2018, 9:58am

Hi @System19
Following show during bench start :

01:55:08 system | redis_socketio.1 started (pid=2135)
01:55:08 system | watch.1 started (pid=2136)
01:55:08 redis_socketio.1 | [2142] 09 Mar 01:55:08.827 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
01:55:08 redis_socketio.1 | [2142] 09 Mar 01:55:08.827 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with ‘noeviction’ policy now.
01:55:08 redis_socketio.1 | .
01:55:08 redis_socketio.1 | .-__ ''-._ 01:55:08 redis_socketio.1 | _.- . . ‘’-._ Redis 2.8.4 (00000000/0) 32 bit
01:55:08 redis_socketio.1 | .- .-```. ```\/ _.,_ ''-._ 01:55:08 redis_socketio.1 | ( ' , .-` | `, ) Running in stand alone mode 01:55:08 redis_socketio.1 | |`-._`-...-` __...-.-.|'_.-'| Port: 12000 01:55:08 redis_socketio.1 | | -. ._ / _.-' | PID: 2142 01:55:08 redis_socketio.1 | -._ -._ -./ .-’ .-’
01:55:08 redis_socketio.1 | |-._-. -.__.-' _.-'_.-'| 01:55:08 redis_socketio.1 | | -.-._ _.-'_.-' | http://redis.io 01:55:08 redis_socketio.1 | -._ -._-..-'.-’ .-’
01:55:08 redis_socketio.1 | |-._-. -.__.-' _.-'_.-'| 01:55:08 redis_socketio.1 | | -.-._ _.-'_.-' | 01:55:08 redis_socketio.1 | -._ -._-..-‘.-’ .-’
01:55:08 redis_socketio.1 | -._ -..-’ _.-’
01:55:08 redis_socketio.1 | -._ _.-' 01:55:08 redis_socketio.1 | -..-’
01:55:08 redis_socketio.1 |
01:55:08 redis_socketio.1 | [2142] 09 Mar 01:55:08.846 # Server started, Redis version 2.8.4
01:55:08 redis_socketio.1 | [2142] 09 Mar 01:55:08.846 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
01:55:08 redis_socketio.1 | [2142] 09 Mar 01:55:08.851 * The server is now ready to accept connections on port 12000
01:55:09 system | web.1 started (pid=2137)
01:55:09 system | redis_queue.1 started (pid=2147)
01:55:09 system | worker_default.1 started (pid=2150)
01:55:08 redis_queue.1 | [2151] 09 Mar 01:55:08.900 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
01:55:08 redis_queue.1 | [2151] 09 Mar 01:55:08.900 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with ‘noeviction’ policy now.
01:55:08 redis_queue.1 | .
01:55:08 redis_queue.1 | .-__ ''-._ 01:55:08 redis_queue.1 | _.- . . ‘’-. Redis 2.8.4 (00000000/0) 32 bit
01:55:08 redis_queue.1 | .- .-```. ```\/ _.,_ ''-._ 01:55:08 redis_queue.1 | ( ' , .-` | `, ) Running in stand alone mode 01:55:08 redis_queue.1 | |`-._`-...-` __...-.-.|’_.-'| Port: 11000 01:55:08 redis_queue.1 | | -._ ._ / _.-' | PID: 2151 01:55:08 redis_queue.1 | -._ -._ -./ .-’ .-’
01:55:08 redis_queue.1 | |-._-. -.__.-' _.-'_.-'| 01:55:08 redis_queue.1 | | -.-._ _.-'_.-' | http://redis.io 01:55:08 redis_queue.1 | -._ -._-..-'.-’ .-’
01:55:08 redis_queue.1 | |-._-. -.__.-' _.-'_.-'| 01:55:08 redis_queue.1 | | -.-._ _.-'_.-' | 01:55:08 redis_queue.1 | -._ -._-..-‘.-’ .-’
01:55:08 redis_queue.1 | -._ -..-’ _.-’
01:55:08 redis_queue.1 | -._ _.-' 01:55:08 redis_queue.1 | -..-’
01:55:08 redis_queue.1 |
01:55:08 redis_queue.1 | [2151] 09 Mar 01:55:08.925 # Server started, Redis version 2.8.4
01:55:08 redis_queue.1 | [2151] 09 Mar 01:55:08.925 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
01:55:08 redis_queue.1 | [2151] 09 Mar 01:55:08.931 * The server is now ready to accept connections on port 11000
01:55:09 system | worker_long.1 started (pid=2138)
01:55:09 system | schedule.1 started (pid=2146)
01:55:09 system | socketio.1 started (pid=2149)
01:55:09 system | redis_cache.1 started (pid=2167)
01:55:09 system | worker_short.1 started (pid=2162)
01:55:09 redis_cache.1 | [2168] 09 Mar 01:55:09.125 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
01:55:09 redis_cache.1 | .
01:55:09 redis_cache.1 | .-__ ''-._ 01:55:09 redis_cache.1 | _.- . . ‘’-. Redis 2.8.4 (00000000/0) 32 bit
01:55:09 redis_cache.1 | .- .-```. ```\/ _.,_ ''-._ 01:55:09 redis_cache.1 | ( ' , .-` | `, ) Running in stand alone mode 01:55:09 redis_cache.1 | |`-._`-...-` __...-.-.|’_.-'| Port: 13000 01:55:09 redis_cache.1 | | -._ ._ / _.-' | PID: 2168 01:55:09 redis_cache.1 | -._ -._ -./ .-’ .-’
01:55:09 redis_cache.1 | |-._-. -.__.-' _.-'_.-'| 01:55:09 redis_cache.1 | | -.-._ _.-'_.-' | http://redis.io 01:55:09 redis_cache.1 | -._ -._-..-'.-’ .-’
01:55:09 redis_cache.1 | |-._-. -.__.-' _.-'_.-'| 01:55:09 redis_cache.1 | | -.-._ _.-'_.-' | 01:55:09 redis_cache.1 | -._ -._-..-‘_.-’ _.-’
01:55:09 redis_cache.1 | -._ -..-’ _.-’
01:55:09 redis_cache.1 | -._ _.-' 01:55:09 redis_cache.1 | -..-’
01:55:09 redis_cache.1 |
01:55:09 redis_cache.1 | [2168] 09 Mar 01:55:09.167 # Server started, Redis version 2.8.4
01:55:09 redis_cache.1 | [2168] 09 Mar 01:55:09.167 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add ‘vm.overcommit_memory = 1’ to /etc/sysctl.conf and then reboot or run the command ‘sysctl vm.overcommit_memory=1’ for this to take effect.
01:55:09 redis_cache.1 | [2168] 09 Mar 01:55:09.170 * The server is now ready to accept connections on port 13000
01:55:22 socketio.1 | listening on *: 9000

but can’t access through local host, after a while , it show the following and exit from bench start

01:57:32 worker_long.1 | 01:57:32 RQ worker u’rq:worker:erpnext.2160.long’ started, version 0.8.2
01:57:32 worker_long.1 | 01:57:32 Cleaning registries for queue: long
01:57:32 worker_long.1 | 01:57:32
01:57:32 worker_long.1 | 01:57:32 *** Listening on long…
01:57:32 worker_short.1 | 01:57:32 RQ worker u’rq:worker:erpnext.2170.short’ started, version 0.8.2
01:57:32 worker_short.1 | 01:57:32 Cleaning registries for queue: short
01:57:32 worker_short.1 | 01:57:32
01:57:32 worker_short.1 | 01:57:32 *** Listening on short…
01:57:32 worker_default.1 | 01:57:32 RQ worker u’rq:worker:erpnext.2154.default’ started, version 0.8.2
01:57:32 worker_default.1 | 01:57:32 Cleaning registries for queue: default
01:57:32 worker_default.1 | 01:57:32
01:57:32 worker_default.1 | 01:57:32 *** Listening on default…
01:57:32 watch.1 | Please install yarn using below command and try again.
01:57:32 watch.1 | npm install -g yarn
01:57:32 watch.1 | /bin/sh: 1: yarn: not found
01:57:33 system | watch.1 stopped (rc=0)
01:57:33 system | sending SIGTERM to redis_socketio.1 (pid 2135)
01:57:33 system | sending SIGTERM to worker_long.1 (pid 2138)
01:57:33 system | sending SIGTERM to redis_queue.1 (pid 2147)
01:57:33 system | sending SIGTERM to web.1 (pid 2137)
01:57:33 system | sending SIGTERM to schedule.1 (pid 2146)
01:57:33 system | sending SIGTERM to worker_default.1 (pid 2150)
01:57:33 system | sending SIGTERM to socketio.1 (pid 2149)
01:57:33 system | sending SIGTERM to redis_cache.1 (pid 2167)
01:57:33 system | sending SIGTERM to worker_short.1 (pid 2162)
01:57:33 redis_socketio.1 | [2142 | signal handler] (1520589453) Received SIGTERM, scheduling shutdown…
01:57:33 worker_long.1 | 01:57:33 Warm shut down requested
01:57:33 redis_queue.1 | [2151 | signal handler] (1520589453) Received SIGTERM, scheduling shutdown…
01:57:33 worker_default.1 | 01:57:33 Warm shut down requested
01:57:33 system | socketio.1 stopped (rc=-15)
01:57:33 system | web.1 stopped (rc=-15)
01:57:33 redis_cache.1 | [2168 | signal handler] (1520589453) Received SIGTERM, scheduling shutdown…
01:57:33 system | schedule.1 stopped (rc=-15)
01:57:33 worker_short.1 | 01:57:33 Warm shut down requested
01:57:33 redis_socketio.1 | [2142] 09 Mar 01:57:33.148 # User requested shutdown…
01:57:33 redis_socketio.1 | [2142] 09 Mar 01:57:33.148 # Redis is now ready to exit, bye bye…
01:57:33 redis_cache.1 | [2168] 09 Mar 01:57:33.149 # User requested shutdown…
01:57:33 redis_cache.1 | [2168] 09 Mar 01:57:33.149 # Redis is now ready to exit, bye bye…
01:57:33 system | redis_cache.1 stopped (rc=-15)
01:57:33 redis_queue.1 | [2151] 09 Mar 01:57:33.150 # User requested shutdown…
01:57:33 redis_queue.1 | [2151] 09 Mar 01:57:33.150 # Redis is now ready to exit, bye bye…
01:57:33 system | redis_queue.1 stopped (rc=-15)
01:57:33 system | redis_socketio.1 stopped (rc=-15)
01:57:33 system | worker_default.1 stopped (rc=-15)
01:57:33 system | worker_short.1 stopped (rc=-15)
01:57:33 system | worker_long.1 stopped (rc=-15)
frappe@erpnext:~/frappe-bench$

alan · March 9, 2018, 10:16am

and also when i try from another terminal with the command

curl -I http://localhost:8000 and curl -I http://localhost:8080

Following is being returned

curl: (7) Failed to connect to localhost port 8080: Connection refused

System19 · March 9, 2018, 10:42am

From /frappe/frappe-bench/
You could try:
npm install -g yarn
and then try
bench start
again

alan · March 10, 2018, 11:36am

Hi,
Tested still not ok.

When ping localhost, there’s reply,
but use curl localhost it shows following,
curl: (7) Failed to connect to localhost port 80: Connection refused

System19 · March 10, 2018, 2:07pm

@alan Hard to say what is causing the issue from the logs provided. I have a working Centos7 Vagrant box with latest ERPNext that i could upload which may make your install easier. If required let me know.
Cheers

alan · March 11, 2018, 9:29am

Hi @System19, yes please, kindly provide the VB that I could download from.

Thanks in advance.

alan · March 11, 2018, 6:15pm

Hi @System19
Problem is now solved. I tried to download again the vagrant box and redo everything, now it’s working fine.

System19 · March 11, 2018, 10:15pm

Cool
I think the core team (Thanks @codingCoffee) may have just updated the VM the other day.