Restart

fm restart¶

Restart bench services (web, workers, redis, nginx).

Choose between container-level restarts or supervisor-level restarts for faster in-container restarts.

Usage:

$ fm restart BENCHNAME [OPTIONS]

Arguments:

• BENCHNAME: Name of the bench.

Options:

• --web: Restart web service i.e socketio and frappe server.
• --workers: Restart worker services i.e schedule and all workers.
• --redis: Restart redis services.
• --nginx: Restart nginx service.
• --container: Restart entire Docker container(s). Stops and starts the container.
• --supervisor: Restart supervisor processes inside container. Faster than container restart.
• --force: Force restart: --supervisor uses stop+start (kills processes), --container uses timeout=0 (immediate kill).

Examples¶

Restart web and workers (default)¶

Restarts both web and worker services for the bench. Safe for applying configuration changes.

fm restart mybench

Restart via container restart¶

Restarts by restarting the entire Docker containers (slower but thorough).

fm restart mybench --container

Restart via supervisor (faster)¶

Uses supervisor to restart processes inside containers for a faster restart without recreating containers.

fm restart mybench --supervisor

Restart web services only¶

Restarts only web-related services (frappe, socketio) without touching workers.

fm restart mybench --web --no-workers

Restart workers only¶

Restarts worker processes (schedule, long/short workers) while leaving web services running.

fm restart mybench --workers --no-web

Force restart (immediate kill)¶

Performs an immediate kill and restart; use when processes are unresponsive.

fm restart mybench --force

Restart redis services¶

Restarts Redis instances used by the bench (cache and queue backends).

fm restart mybench --redis

Restart nginx service¶

Restarts the nginx service for the bench, useful after configuration changes to proxy or TLS.

fm restart mybench --nginx