从部署seafile服务器就开始报这个警告。。


#1

[11/15/17 20:35:50] http-server.c(161): fileserver: worker_threads = 10
[11/15/17 20:35:50] http-server.c(176): fileserver: fixed_block_size = 8388608
[11/15/17 20:35:50] http-server.c(191): fileserver: web_token_expire_time = 3600
[11/15/17 20:35:50] http-server.c(206): fileserver: max_indexing_threads = 1
[11/15/2017 08:35:51 PM] …/common/mq-mgr.c(54): [mq client] mq cilent is started
[11/15/2017 08:35:52 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 08:36:01 PM] Disconnected from daemon
[11/15/17 20:36:02] http-server.c(161): fileserver: worker_threads = 10
[11/15/17 20:36:02] http-server.c(176): fileserver: fixed_block_size = 8388608
[11/15/17 20:36:02] http-server.c(191): fileserver: web_token_expire_time = 3600
[11/15/17 20:36:02] http-server.c(206): fileserver: max_indexing_threads = 1
[11/15/2017 08:36:02 PM] …/common/mq-mgr.c(54): [mq client] mq cilent is started
[11/15/2017 08:36:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 08:41:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 08:46:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 08:51:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 08:56:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 09:01:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 09:06:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 09:11:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 09:16:03 PM] size-sched.c(96): Repo size compute queue size is 0
[11/15/2017 09:21:03 PM] size-sched.c(96): Repo size compute queue size is 0
省略了1年半的警告。。。。
[07/03/2019 11:07:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:12:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:17:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:22:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:27:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:32:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:37:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:42:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:47:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:52:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 11:57:40 AM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:02:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:07:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:12:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:17:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:22:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:27:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:32:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:37:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:42:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:47:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:52:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 12:57:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:02:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:07:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:12:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:17:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:22:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:27:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:32:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:37:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:42:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:47:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:52:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 01:57:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:02:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:07:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:12:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:17:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:22:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:27:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:32:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:37:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:42:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:47:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:52:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 02:57:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 03:02:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 03:07:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 03:12:40 PM] size-sched.c(96): Repo size compute queue size is 0
[07/03/2019 03:17:40 PM] size-sched.c(96): Repo size compute queue size is 0

一直不知道什么问题,看到其他人说没事,但是这一大堆日志看着很闹心,可以让它不报了不?
这是翻到类似案例,但是并没有解决。https://forum.seafile.com/t/django-request-log-full-of-warnings/2798/10


#2

最新的版本去掉这个警告了。


#3

因为changlog里没有涉及这个问题,所以没有急着尝鲜,既然您提到了,那有必要更新一下,谢谢!


#5

升级后7.0.2后,seahub.log里还有一个警告在继续:
2019-07-03 19:16:05,624 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:21:05,623 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:26:05,631 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:31:05,656 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:36:05,640 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:41:05,672 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:46:05,657 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:51:05,653 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 19:56:05,668 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:01:05,694 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:06:05,669 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:11:05,728 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:16:05,685 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:21:05,685 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:26:05,694 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:31:05,716 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:36:05,699 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:41:07,871 [WARNING] django.request:152 get_response Not Found: /api2/events/
2019-07-03 20:46:05,745 [WARNING] django.request:152 get_response Not Found: /api2/events/

这个不知道什么意思


#6

这个是因为旧版的客户端在访问一个新版中不存在的 api