diff --git a/manual/administration/logs.md b/manual/administration/logs.md index 0020df76b..3110706f4 100644 --- a/manual/administration/logs.md +++ b/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 diff --git a/manual/outdate/using_syslog.md b/manual/outdate/using_syslog.md deleted file mode 100644 index 1e741b3b0..000000000 --- a/manual/outdate/using_syslog.md +++ /dev/null @@ -1,94 +0,0 @@ -## Configure Seafile to Use Syslog - -Since community edition 5.1.2 and professional edition 5.1.4, Seafile support using Syslog. - -### Configure Syslog for Seafile Controller and Server - -Add following configuration to `general` section in `seafile.conf`: -``` -[general] -enable_syslog = true -``` - -Restart seafile server, you will find follow logs in `/var/log/syslog`: -``` -May 10 23:45:19 ubuntu seafile-controller[16385]: seafile-controller.c(154): starting ccnet-server ... -May 10 23:45:19 ubuntu seafile-controller[16385]: seafile-controller.c(73): spawn_process: ccnet-server -F /home/plt/haiwen/conf -c /home/plt/haiwen/ccnet -f /home/plt/haiwen/logs/ccnet.log -d -P /home/plt/haiwen/pids/ccnet.pid -``` -``` -May 12 01:00:51 ubuntu seaf-server[21552]: ../common/mq-mgr.c(60): [mq client] mq cilent is started -May 12 01:00:51 ubuntu seaf-server[21552]: ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seaf_server.heartbeat -``` - -### Configure Syslog For Seafevents (Professional Edition only) - -Add following configuration to `seafevents.conf`: -``` -[Syslog] -enabled = true -``` - -Restart seafile server, you will find follow logs in `/var/log/syslog` -``` -May 12 01:00:52 ubuntu seafevents[21542]: [seafevents] database: mysql, name: seahub-pro -May 12 01:00:52 ubuntu seafevents[21542]: seafes enabled: True -May 12 01:00:52 ubuntu seafevents[21542]: seafes dir: /home/plt/pro-haiwen/seafile-pro-server-5.1.4/pro/python/seafes -``` - -### Configure Syslog For Seahub - -Add following configurations to `seahub_settings.py`: - -``` -LOGGING = { - 'version': 1, - 'disable_existing_loggers': True, - 'formatters': { - 'verbose': { - 'format': '%(process)-5d %(thread)d %(name)-50s %(levelname)-8s %(message)s' - }, - 'standard': { - 'format': '%(asctime)s [%(levelname)s] %(name)s:%(lineno)s %(funcName)s %(message)s' - }, - 'simple': { - 'format': '[%(asctime)s] %(name)s %(levelname)s %(message)s', - 'datefmt': '%d/%b/%Y %H:%M:%S' - }, - }, - 'filters': { - 'require_debug_false': { - '()': 'django.utils.log.RequireDebugFalse', - }, - 'require_debug_true': { - '()': 'django.utils.log.RequireDebugTrue', - }, - }, - 'handlers': { - 'console': { - 'filters': ['require_debug_true'], - 'class': 'logging.StreamHandler', - 'formatter': 'simple' - }, - 'syslog': { - 'class': 'logging.handlers.SysLogHandler', - 'address': '/dev/log', - 'formatter': 'standard' - }, - }, - 'loggers': { - # root logger -        # All logs printed by Seahub and any third party libraries will be handled by this logger. -        '': { - 'handlers': ['console', 'syslog'], - 'level': 'INFO', # Logs when log level is higher than info. Level can be any one of DEBUG, INFO, WARNING, ERROR, CRITICAL. - 'disabled': False - }, - # This logger recorded logs printed by Django Framework. For example, when you see 5xx page error, you should check the logs recorded by this logger. - 'django.request': { - 'handlers': ['console', 'syslog'], - 'level': 'INFO', - 'propagate': False, - }, - }, -} -``` diff --git a/manual/setup_binary/installation_ce.md b/manual/setup_binary/installation_ce.md index 72264573d..f1099276c 100644 --- a/manual/setup_binary/installation_ce.md +++ b/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 diff --git a/manual/setup_binary/using_logrotate.md b/manual/setup_binary/using_logrotate.md index 73d30b08b..b254033f2 100644 --- a/manual/setup_binary/using_logrotate.md +++ b/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.