It is happening continuously with me.
I have done fresh installation on a Ubuntu Server.
But, when I run the instance using a browser.
It gives me the below error:
Not Found
./localhost/site_config.json does not exist
Also I tried to do a bench start but I don’t think so it is also working.
I appreciate if anyone can help me in this regard.
sam@sam-VirtualBox:~/frappe-bench$ bench start
09:42:36 system | async_worker.1 started (pid=22607)
09:42:36 system | socketio.1 started (pid=22605)
09:42:36 system | worker.1 started (pid=22606)
09:42:36 system | web.1 started (pid=22604)
09:42:36 system | redis_async_broker.1 started (pid=22608)
09:42:36 redis_async_broker.1 | [22618] 19 Feb 09:42:36.104 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
09:42:36 redis_async_broker.1 | [22618] 19 Feb 09:42:36.104 # Creating Server TCP listening socket *:12311: bind: Address already in use
09:42:36 system | redis_async_broker.1 stopped (rc=1)
09:42:36 system | workerbeat.1 started (pid=22609)
09:42:36 system | redis_cache.1 started (pid=22620)
09:42:36 redis_cache.1 | [22624] 19 Feb 09:42:36.143 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
09:42:36 redis_cache.1 | [22624] 19 Feb 09:42:36.143 # Creating Server TCP listening socket *:11311: bind: Address already in use
09:42:36 system | redis_cache.1 stopped (rc=1)
09:42:36 system | longjob_worker.1 started (pid=22621)
09:42:36 system | sending SIGTERM to workerbeat.1 (pid 22609)
09:42:36 system | sending SIGTERM to worker.1 (pid 22606)
09:42:36 system | sending SIGTERM to web.1 (pid 22604)
09:42:36 system | sending SIGTERM to async_worker.1 (pid 22607)
09:42:36 system | sending SIGTERM to socketio.1 (pid 22605)
09:42:36 system | sending SIGTERM to longjob_worker.1 (pid 22621)
09:42:36 system | web.1 stopped (rc=-15)
09:42:36 system | workerbeat.1 stopped (rc=-15)
09:42:36 system | worker.1 stopped (rc=-15)
09:42:36 system | socketio.1 stopped (rc=-15)
09:42:36 system | async_worker.1 stopped (rc=-15)
09:42:36 system | longjob_worker.1 stopped (rc=-15)
not an expert here but a reason for site_config.json does not exist could be there is no existing site. Is there anything inside /home/frappe/frappe-bench/sites?
Hello ,
I am also getting the same error. I tried the solution but still getting the same error. I have checked in sites folder and site_config.json file is there.
I am also getting the same error in my debian installation.
The site works perfectly in developer mode.
But when it is setup in production mode throws this error. what could be the reason for this.
I cross checked the exists.
Yes, But it is not working,
I found out that my supervisor is not running.
$sudo supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache FATAL Exited too quickly (process log may have details)
frappe-bench-redis:frappe-bench-redis-queue FATAL Exited too quickly (process log may have details)
frappe-bench-redis:frappe-bench-redis-socketio FATAL Exited too quickly (process log may have details)
frappe-bench-web:frappe-bench-frappe-web RUNNING pid 5759, uptime 0:00:32
frappe-bench-web:frappe-bench-node-socketio FATAL Exited too quickly (process log may have details)
frappe-bench-workers:frappe-bench-frappe-default-worker-0 RUNNING pid 5696, uptime 0:00:35
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING pid 5721, uptime 0:00:34
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING pid 5695, uptime 0:00:35
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING pid 5742, uptime 0:00:33
My supervisor.log
$sudo tail /var/log/supervisor/supervisord.log
2016-08-18 04:08:28,998 INFO exited: frappe-bench-redis-queue (exit status 1; not expected)
2016-08-18 04:08:29,457 INFO gave up: frappe-bench-redis-queue entered FATAL state, too many start retries too quickly
2016-08-18 04:08:29,461 INFO exited: frappe-bench-node-socketio (exit status 1; not expected)
2016-08-18 04:08:30,462 INFO gave up: frappe-bench-node-socketio entered FATAL state, too many start retries too quickly
2016-08-18 04:08:30,463 INFO spawned: 'frappe-bench-redis-cache' with pid 5837
2016-08-18 04:08:30,464 INFO spawned: 'frappe-bench-redis-socketio' with pid 5838
2016-08-18 04:08:30,479 INFO exited: frappe-bench-redis-socketio (exit status 1; not expected)
2016-08-18 04:08:30,480 INFO gave up: frappe-bench-redis-socketio entered FATAL state, too many start retries too quickly
2016-08-18 04:08:30,480 INFO exited: frappe-bench-redis-cache (exit status 1; not expected)
2016-08-18 04:08:31,482 INFO gave up: frappe-bench-redis-cache entered FATAL state, too many start retries too quickly
This is why it works perfectly in devlop and not working in my production. It was working perfectly earlier. just added one more instance to the server and its not working.