Bench stops automatically on local machine (WSL) – processes receive SIGTERM

Frappe Framework
1

Hi everyone,

I’m facing an issue while running Frappe / ERPNext locally using WSL.
bench start runs fine initially, but after some time (or when the system is actively used), bench stops automatically and all services receive SIGTERM.

This happens without me manually stopping bench.

Environment Details:

  • OS: Windows 10/11

  • Runtime: WSL (Ubuntu)

  • Frappe Version: v15.90.1

  • ERPNext: v15.93.1

  • HRMS: 15.52.4

  • India Compliance: v15.24.0

  • Wiki: 2.0.0

  • Python: 3.10.12

  • Node: v18.20.8

  • npm: 10.8.2

  • Redis Server: v=8.4.0

  • Command used: bench start

Observed Behavior:

  • Bench starts normally

  • Site works for some time

  • Suddenly all processes stop

  • Logs show SIGTERM being sent to workers, Redis, web, socketio, etc.

  • More frequent when system is under load or actively used

  • When idle, bench sometimes keeps running

Logs / Output:

worker.1 stopped (rc=0)
sending SIGTERM to redis_cache.1
sending SIGTERM to redis_queue.1
sending SIGTERM to web.1
sending SIGTERM to socketio.1
sending SIGTERM to watch.1
sending SIGTERM to schedule.1

redis_queue.1 Received SIGTERM scheduling shutdown...
redis_cache.1 User requested shutdown...
Redis is now ready to exit, bye bye...

web.1 stopped (rc=-15)
watch.1 stopped (rc=-15)

image
image1919×661 58.2 KB

What I’ve Tried:

  • Restarting WSL

  • Re-running bench setup requirements

  • Clear Cache

  • bench build

Issue still persists.

Any help or pointers would be greatly appreciated :folded_hands:
Thanks in advance!

2

Please run these commands to safely start the bench

pkill -9 -f node

pkill -9 -f python

pkill -9 -f redis

bench start

3

How much memory does you computer/ laptop have ??

4

It has 16GB RAM

5

Can you check on the task manager if you are maxing out your RAM somewhere else
SIGTERM normally means something is killing the process which could be due to low resource availablity

6

so without making any wsl config changes, for WSL2 by default, the memory limit is half your systems memory. So that would 8 GB of memory limit to use with WSL2 in your case.

Check your windows Task manger and look at the process ‘vmmemwsl’ .. you should able to get an idea how much its using while you are running erpnext