Frappe Server Stops Unexpectedly After bench start During Development

dhiashalabi · December 10, 2024, 7:10am

Hello,

I’ve set up Frappe (version 14) for local development with custom apps using Bench (version 5.23.0). Initially, everything works fine when I start the server with bench start. However, after several minutes of development, the server suddenly stops without any error message or apparent reason.

Here’s the final output from the terminal before the server stops:

09:56:15 web.1         |   import cgitb
09:56:16 web.1         |  * Debugger is active!
09:56:16 web.1         |  * Debugger PIN: 427-298-249
09:56:16 watch.1       | Browserslist: caniuse-lite is outdated. Please run:
09:56:16 watch.1       |   npx browserslist@latest --update-db
09:56:16 watch.1       |   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
09:56:17 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
09:56:17 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
09:56:17 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
09:56:17 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
09:56:17 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
09:56:17 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
09:56:17 watch.1       | clean: postcss.plugin was deprecated. Migration guide:
09:56:17 watch.1       | https://evilmartians.com/chronicles/postcss-8-plugin-migration
09:56:35 watch.1       | Watching for changes...
10:00:17 web.1         | 127.0.0.1 - - [10/Dec/2024 10:00:17] "POST /api/method/frappe.desk.reportview.get HTTP/1.1" 200 -
10:00:17 web.1         | 127.0.0.1 - - [10/Dec/2024 10:00:17] "POST /api/method/frappe.desk.reportview.get_count HTTP/1.1" 200 -
10:02:54 system        | worker.1 stopped (rc=0)
10:02:54 system        | sending SIGTERM to redis_cache.1 (pid 76530)
10:02:54 system        | sending SIGTERM to redis_queue.1 (pid 76533)
10:02:54 system        | sending SIGTERM to web.1 (pid 76536)
10:02:54 system        | sending SIGTERM to socketio.1 (pid 76544)
10:02:54 system        | sending SIGTERM to watch.1 (pid 76542)
10:02:54 system        | sending SIGTERM to schedule.1 (pid 76545)
10:02:54 redis_cache.1 | 76531:signal-handler (1733814174) Received SIGTERM scheduling shutdown...
10:02:54 redis_queue.1 | 76534:signal-handler (1733814174) Received SIGTERM scheduling shutdown...
10:02:54 system        | socketio.1 stopped (rc=-15)
10:02:54 redis_cache.1 | 76531:M 10 Dec 2024 10:02:54.628 # User requested shutdown...
10:02:54 redis_cache.1 | 76531:M 10 Dec 2024 10:02:54.628 * Removing the pid file.
10:02:54 redis_cache.1 | 76531:M 10 Dec 2024 10:02:54.628 # Redis is now ready to exit, bye bye...
10:02:54 system        | redis_cache.1 stopped (rc=-15)
10:02:54 system        | schedule.1 stopped (rc=-15)
10:02:54 redis_queue.1 | 76534:M 10 Dec 2024 10:02:54.643 # User requested shutdown...
10:02:54 redis_queue.1 | 76534:M 10 Dec 2024 10:02:54.644 * Saving the final RDB snapshot before exiting.
10:02:54 redis_queue.1 | 76534:M 10 Dec 2024 10:02:54.665 * DB saved on disk
10:02:54 redis_queue.1 | 76534:M 10 Dec 2024 10:02:54.665 * Removing the pid file.
10:02:54 redis_queue.1 | 76534:M 10 Dec 2024 10:02:54.666 # Redis is now ready to exit, bye bye...
10:02:54 system        | redis_queue.1 stopped (rc=-15)
10:02:54 system        | watch.1 stopped (rc=-15)
10:02:54 system        | web.1 stopped (rc=-15)

The shutdown happens without any errors or warnings that I can see.

I’ve already verified that:

There are no system resource limitations (e.g., CPU, memory).
Redis and other services seem to shut down cleanly, but I can’t find what triggers the shutdown.

Has anyone else faced a similar issue? Could this be related to some configuration or a background task? Any advice or troubleshooting tips would be greatly appreciated.

I appreciate any help you can provide.

ejaaz · December 10, 2024, 6:20pm

Just rub bench start and it will start again
It sometimes happens, and I’ve faced this issue (in version 14) when changing code… for example, in app.py which then stops the server. I don’t currently recall the exact file name.

mihailsbut · September 16, 2025, 1:33pm

Same problem! Restarting is of course a “solution”, but I don’t even have 5 minutes before the same problem occurs again

techmaniacc · October 5, 2025, 9:43pm

Did you find solution to this

Elnegren · October 6, 2025, 3:40pm

We can’t develop with this error, the server stop every 5-6 min

black_mamba · October 7, 2025, 3:56am

I experience something similar long time ago. The cause of the issue was on a terminal I used to ssh and do bench start. But because this process was attached to terminal (and because of other network issue) the process would get terminated. In scenarios like this you can use screen command to possibly mitigate this issue.

Basically

Start a screen using screen -t localdev (attaching to screen)
Run bench start
Press Ctrl a followed by d (detaching from screen)

Would be great to know if you’re facing similar issue or bench start just randomly gets terminated - Although at time I’ve seen this happen because or server resource limitations.

nikitabrij · October 24, 2025, 4:45am

I have same problem pls anyone given valid answer…..above reply i unble to understand…pls tell me in detail…