sumisha
September 4, 2020, 9:37pm
1
Followed the manual installation steps – Installation
All dependency installations were successful
new app created and installed on site successfully
But stuck on bench start, getting this error…please find the logs below
21:16:49 socketio.1 | listening on *: 9000
21:16:54 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
21:16:54 web.1 | * Restarting with inotify reloader
21:16:54 watch.1 | Parsing scenario file run
21:16:54 watch.1 | ERROR: [Errno 2] No such file or directory: ‘run’
21:16:54 system | watch.1 stopped (rc=0)
21:16:54 system | sending SIGTERM to redis_cache.1 (pid 3735)
21:16:54 system | sending SIGTERM to redis_socketio.1 (pid 3746)
21:16:54 system | sending SIGTERM to redis_queue.1 (pid 3744)
21:16:54 system | sending SIGTERM to web.1 (pid 3745)
21:16:54 system | sending SIGTERM to socketio.1 (pid 3748)
21:16:54 system | sending SIGTERM to schedule.1 (pid 3750)
21:16:54 system | sending SIGTERM to worker_short.1 (pid 3753)
21:16:54 system | sending SIGTERM to worker_long.1 (pid 3751)
21:16:54 system | sending SIGTERM to worker_default.1 (pid 3752)
21:16:54 redis_cache.1 | 3743:signal-handler (1599254214) Received SIGTERM scheduling shutdown…
21:16:54 redis_socketio.1 | 3756:signal-handler (1599254214) Received SIGTERM scheduling shutdown…
21:16:54 redis_queue.1 | 3749:signal-handler (1599254214) Received SIGTERM scheduling shutdown…
21:16:54 system | worker_short.1 stopped (rc=-15)
21:16:54 system | worker_long.1 stopped (rc=-15)
21:16:54 system | worker_default.1 stopped (rc=-15)
21:16:54 redis_cache.1 | 3743:M 04 Sep 2020 21:16:54.872 # User requested shutdown…
21:16:54 redis_cache.1 | 3743:M 04 Sep 2020 21:16:54.872 * Removing the pid file.
21:16:54 redis_cache.1 | 3743:M 04 Sep 2020 21:16:54.873 # Redis is now ready to exit, bye bye…
21:16:54 system | redis_cache.1 stopped (rc=-15)
21:16:54 system | socketio.1 stopped (rc=-15)
21:16:54 system | schedule.1 stopped (rc=-15)
21:16:54 redis_queue.1 | 3749:M 04 Sep 2020 21:16:54.910 # User requested shutdown…
21:16:54 redis_socketio.1 | 3756:M 04 Sep 2020 21:16:54.911 # User requested shutdown…
21:16:54 redis_socketio.1 | 3756:M 04 Sep 2020 21:16:54.911 * Removing the pid file.
21:16:54 redis_socketio.1 | 3756:M 04 Sep 2020 21:16:54.912 # Redis is now ready to exit, bye bye…
21:16:54 system | redis_socketio.1 stopped (rc=-15)
21:16:54 redis_queue.1 | 3749:M 04 Sep 2020 21:16:54.910 * Removing the pid file.
21:16:54 redis_queue.1 | 3749:M 04 Sep 2020 21:16:54.916 # Redis is now ready to exit, bye bye…
21:16:54 system | redis_queue.1 stopped (rc=-15)
21:16:55 system | web.1 stopped (rc=-15)
frappe@773f2613d94e:~/frappe-bench$
Any suggestions or help is greatly appreciated…
I used more detailed tutorial: The Hitchhiker's Guide to Installing Frappe on Linux · frappe/frappe Wiki · GitHub
I used it a few times and always worked. I know it’s not a solution for your error, but may be a solution for installation in general.
sumisha
September 5, 2020, 9:16am
3
Thanks a lo for the reply …I will follow these steps and get back with the updates.
sumisha
September 5, 2020, 11:32pm
4
bench started succesfully…but not able to access it with url ----http://localhost:8000/ .
23:17:33 socketio.1 | listening on *: 9000
23:17:34 schedule.1 | WARN: bench is installed in editable mode!
23:17:34 schedule.1 |
23:17:34 schedule.1 | This is not the recommended mode of installation for production. Instead, install the package from PyPI with: pip install frappe-bench
23:17:34 schedule.1 |
23:17:34 web.1 | WARN: bench is installed in editable mode!
23:17:34 web.1 |
23:17:34 web.1 | This is not the recommended mode of installation for production. Instead, install the package from PyPI with: pip install frappe-bench
23:17:34 web.1 |
23:17:34 watch.1 | WARN: bench is installed in editable mode!
23:17:34 watch.1 |
23:17:34 watch.1 | This is not the recommended mode of installation for production. Instead, install the package from PyPI with: pip install frappe-bench
23:17:34 watch.1 |
23:17:38 web.1 | * Running on http://0.0.0.0:8000/ (Press CTRL+C to quit)
23:17:38 web.1 | * Restarting with inotify reloader
23:17:38 watch.1 | yarn run v1.22.5
23:17:39 watch.1 | $ node rollup/watch.js
23:17:40 web.1 | * Debugger is active!
23:17:40 web.1 | * Debugger PIN: 302-068-939
23:17:40 watch.1 |
23:17:40 watch.1 | Rollup Watcher Started
23:17:40 watch.1 |
23:17:40 watch.1 | Watching…
23:17:42 watch.1 | Rebuilding frappe-web-b4.css
23:17:42 watch.1 | Rebuilding frappe-chat-web.css
23:17:42 watch.1 | Rebuilding chat.js
23:17:44 watch.1 | Rebuilding frappe-recorder.min.js
23:17:49 watch.1 | Rebuilding checkout.min.js
23:17:49 watch.1 | Rebuilding frappe-web.min.js
23:17:52 watch.1 | Rebuilding bootstrap-4-web.min.js
23:17:53 watch.1 | Rebuilding control.min.js
23:17:56 watch.1 | Rebuilding dialog.min.js
23:17:59 watch.1 | Rebuilding desk.min.css
23:17:59 watch.1 | Rebuilding frappe-rtl.css
23:17:59 watch.1 | Rebuilding printview.css
23:17:59 watch.1 | Rebuilding desk.min.js
23:18:06 watch.1 | Rebuilding module.min.css
23:18:06 watch.1 | Rebuilding form.min.css
23:18:06 watch.1 | Rebuilding form.min.js
23:18:09 watch.1 | Rebuilding list.min.css
23:18:09 watch.1 | Rebuilding list.min.js
23:18:11 watch.1 | Rebuilding report.min.css
23:18:11 watch.1 | Rebuilding report.min.js
23:18:13 watch.1 | Rebuilding web_form.min.js
23:18:15 watch.1 | Rebuilding web_form.css
23:18:15 watch.1 | Rebuilding email.css
23:18:15 watch.1 | Rebuilding social.min.js
23:18:16 watch.1 | Rebuilding modules.min.js
23:18:17 watch.1 | Rebuilding barcode_scanner.min.js
23:18:19 watch.1 | Rebuilding data_import_tools.min.js
It would be really great if anyone help on this…Thanks
Did you wait until all the rebuilds finished? Try waiting a few minutes after it looks like finished.
The same after first login: if the wizard “failed”, wait a minute and try again (and wait a little more if still failing). First start is quite long. But the files are built once and speed up future starts.
sumisha
September 7, 2020, 5:50pm
6
Thanks for the help . Resolved the issue, the problem was with windows features as I was using docker conatiner.