mirror of
				https://github.com/zulip/zulip.git
				synced 2025-11-03 21:43:21 +00:00 
			
		
		
		
	docs: Remove references to supervisorctl (re)start all.
This commit is contained in:
		
				
					committed by
					
						
						Tim Abbott
					
				
			
			
				
	
			
			
			
						parent
						
							a4d0f03319
						
					
				
				
					commit
					f39ee5a16c
				
			@@ -339,7 +339,7 @@ cd ~
 | 
			
		||||
tar -xf /path/to/export/file/zulip-export-zcmpxfm6.tar.gz
 | 
			
		||||
cd /home/zulip/deployments/current
 | 
			
		||||
./manage.py import '' ~/zulip-export-zcmpxfm6
 | 
			
		||||
# supervisorctl start all # Starts the Zulip server
 | 
			
		||||
# ./scripts/start-server
 | 
			
		||||
# ./manage.py reactivate_realm -r ''  # Reactivates the organization
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
@@ -77,27 +77,29 @@ isn't running. If you don't see relevant logs in
 | 
			
		||||
`/etc/supervisor/conf.d/zulip.conf` for details. Logs only make it to
 | 
			
		||||
`/var/log/zulip/errors.log` once a service has started fully.
 | 
			
		||||
 | 
			
		||||
### Restarting services with `supervisorctl restart all`
 | 
			
		||||
### Restarting services with `supervisorctl restart`
 | 
			
		||||
 | 
			
		||||
After you change configuration in `/etc/zulip/settings.py` or fix a
 | 
			
		||||
misconfiguration, you will often want to restart the Zulip application.
 | 
			
		||||
You can restart Zulip using:
 | 
			
		||||
misconfiguration, you will often want to restart the Zulip
 | 
			
		||||
application. Running `scripts/restart-server` will restart all of
 | 
			
		||||
Zulip's services; if you want to restart just one of them, you can use
 | 
			
		||||
`supervisorctl`:
 | 
			
		||||
 | 
			
		||||
```bash
 | 
			
		||||
supervisorctl restart all
 | 
			
		||||
# You can use this for any service found in `supervisorctl list`
 | 
			
		||||
supervisorctl restart zulip-django
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
### Stopping services with `supervisorctl stop all`
 | 
			
		||||
### Stopping services with `supervisorctl stop`
 | 
			
		||||
 | 
			
		||||
Similarly, you can stop Zulip using:
 | 
			
		||||
Similarly, while stopping all of Zulip is best done by running
 | 
			
		||||
`scripts/stop-server`, you can stop individual Zulip services using:
 | 
			
		||||
 | 
			
		||||
```bash
 | 
			
		||||
supervisorctl stop all
 | 
			
		||||
# You can use this for any service found in `supervisorctl list`
 | 
			
		||||
supervisorctl stop zulip-django
 | 
			
		||||
```
 | 
			
		||||
 | 
			
		||||
If you're looking to shut down the server, it is often better to run
 | 
			
		||||
`./scripts/stop-server`.
 | 
			
		||||
 | 
			
		||||
## Troubleshooting services
 | 
			
		||||
 | 
			
		||||
The Zulip application uses several major open source services to store
 | 
			
		||||
 
 | 
			
		||||
@@ -174,7 +174,7 @@ after resolving an issue. The most common causes of errors are:
 | 
			
		||||
  minimal RAM for running Zulip can run into out-of-memory issues
 | 
			
		||||
  during the upgrade process (generally `tools/webpack` is the step
 | 
			
		||||
  that fails). You can get past this by shutting down the Zulip
 | 
			
		||||
  server with `supervisorctl stop all` to free up RAM before running
 | 
			
		||||
  server with `./scripts/stop-server` to free up RAM before running
 | 
			
		||||
  the upgrade process.
 | 
			
		||||
 | 
			
		||||
Useful logs are available in a few places:
 | 
			
		||||
@@ -419,7 +419,7 @@ instructions for other supported platforms.
 | 
			
		||||
   to back up the system:
 | 
			
		||||
 | 
			
		||||
   ```bash
 | 
			
		||||
   supervisorctl stop all
 | 
			
		||||
   /home/zulip/deployments/current/scripts/stop-server
 | 
			
		||||
   /home/zulip/deployments/current/manage.py backup --output=/home/zulip/release-upgrade.backup.tar.gz
 | 
			
		||||
   ```
 | 
			
		||||
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user