Clean controller related document

manual/administration/logs.md

@@ -3,7 +3,6 @@
 ### Log files of seafile server
 
 * seafile.log: logs of seaf-server
-* controller.log: logs of controller
 * seahub.log: logs from Django framework
 * fileserver.log: logs of the golang file server component
 * seafevents.log: logs for background tasks and office file conversion
@@ -13,7 +12,6 @@
 ### Log files for seafile background node in cluster mode
 
 * seafile.log: logs of seaf-server
-* controller.log: logs of controller
 * seafevents.log: Empty
 * seafile-background-tasks.log: logs for background tasks and office file convertion
 * seahub_email_sender.log: logs for periodically email sending of background tasks

manual/setup_binary/installation_ce.md

@@ -360,26 +360,6 @@ Now you can access Seafile via the web interface at the host address and port 80
     On CentOS, the firewall blocks traffic on port 8000 by default.
 
 
-### Troubleshooting
-
-If seafile.sh and/or seahub.sh fail to run successfully, use `pgrep` to check if seafile/seahub processes are still running:
-
-
-```
-pgrep -f seafile-controller # checks seafile processes
-pgrep -f "seahub" # checks seahub process
-
-```
-
-Use `pkill` to kill the processes:
-
-
-```
-pkill -f seafile-controller
-pkill -f "seahub"
-
-```
-
 ## Stopping and Restarting Seafile and Seahub
 
 ### Stopping

manual/setup_binary/using_logrotate.md

@@ -2,7 +2,7 @@
 
 ## How it works
 
-seaf-server and seafile-controller support reopenning logfiles by receiving a `SIGUR1` signal.
+seaf-server support reopenning logfiles by receiving a `SIGUR1` signal.
 
 This feature is very useful when you need cut logfiles while you don't want
 to shutdown the server. All you need to do now is cutting the logfile on the fly.