restart-server: Must be run as user 'zulip'.

这个错误提示是因为你需要使用 `zulip` 用户来运行 `restart-server` 命令。你可以尝试使用以下命令来切换到 `zulip` 用户并重新运行 `restart-server`：

sudo su zulip -c '/home/zulip/deployments/current/scripts/restart-server'

如果你没有 `zulip` 用户的密码，则可以使用以下命令切换到 `zulip` 用户并重新运行 `restart-server`：

sudo -u zulip /home/zulip/deployments/current/scripts/restart-server

确保在运行命令之前已经切换到了 `zulip` 用户。

相关问题

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon

The error message "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?" indicates that there is a problem connecting to the Docker daemon. The Docker daemon is responsible for managing Docker containers and must be running for Docker commands to work.

In the provided references, the user encountered this issue after restarting the server, and the Docker containers were not working. They tried various solutions but were unable to resolve the problem until they manually started the Docker daemon.

To fix this issue, you can try the following steps:

1. Check if the Docker daemon is running by using the command: [2]

systemctl status docker

This command will show the status of the Docker service. If it is not running, you will need to start it.

2. Start the Docker daemon by using the command: [2]

dockerd

This command will start the Docker daemon and allow you to connect to it.

3. If the above steps do not resolve the issue, you can try restarting the Docker service: [2]

systemctl restart docker

This command will restart the Docker service and may help in resolving any underlying issues.

Additionally, you can use the following commands for troubleshooting:
- To check the running services, you can use: [3]

systemctl | grep running

This command will show the list of running services, and you can check if the Docker service is listed.

- To view the Docker service startup logs, you can use: [3]

journalctl -u docker

This command will display the logs related to the Docker service startup, which can help in identifying any errors or issues.

Remember to check the system requirements and ensure that Docker is properly installed and configured on your CentOS system.<span class="em">1</span><span class="em">2</span><span class="em">3</span>
#### 引用[.reference_title]
- *1* *2* *3* [cannot connect to the docker daemon at unix ///var/run/docker.sock. Is the docker daemon running?](https://blog.csdn.net/l751475472/article/details/122968595)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_1"}}] [.reference_item style="max-width: 100%"]
[ .reference_list ]

The innodb_system data file 'ibdata1' must be writable

To resolve the issue where the InnoDB system data file 'ibdata1' must be writable, you can follow these steps:

1. Identify the ownership and permissions of the 'ibdata1' file:
- Open the terminal or command prompt.
- Navigate to the directory where the 'ibdata1' file is located.
- Execute the command `ls -l ibdata1` to view the ownership and permissions.

2. Ensure the file is owned by the correct user:
- If the ownership is incorrect, you can change it using the `chown` command. For example, if the correct user is 'mysql', run `sudo chown mysql ibdata1`.

3. Verify the file permissions:
- The correct permissions for the 'ibdata1' file should typically be 600 (read and write permissions for the owner only).
- If the permissions are incorrect, you can modify them using the `chmod` command. For example, `sudo chmod 600 ibdata1`.

4. Restart the MySQL or MariaDB service:
- After making ownership or permission changes, restart the MySQL or MariaDB service to apply the changes. Use the appropriate command for your system. For example, `sudo service mysql restart` or `sudo systemctl restart mariadb`.

By ensuring that the 'ibdata1' file is owned by the correct user and has the correct permissions, you should be able to resolve the issue.