Pydio Cells: Too many logs in services/pydio.grpc.log

Pydio Cells
1

Describe your issue in detail

After updating Pydio Cells from 4.2.7 to 4.3.2, the disk usage of services/pydio.grpc.log got out of control.

  jkirk@ganymed ~ % sudo du -ch --max-depth 1 /srv/pydio-cells/cells/services
  416K    /srv/pydio-cells/cells/services/pydio.grpc.docstore
  8.0K    /srv/pydio-cells/cells/services/pydio.grpc.data.index
  20K     /srv/pydio-cells/cells/services/pydio.grpc.data.objects
  106M    /srv/pydio-cells/cells/services/pydio.grpc.jobs
  656M    /srv/pydio-cells/cells/services/pydio.grpc.activity
  156K    /srv/pydio-cells/cells/services/pydio.grpc.chat
  8.0K    /srv/pydio-cells/cells/services/pydio.gateway.grpc.clear
  101M    /srv/pydio-cells/cells/services/pydio.grpc.search
  8.0K    /srv/pydio-cells/cells/services/pydio.rest.install
  6.2M    /srv/pydio-cells/cells/services/pydio.grpc.tasks
  24G     /srv/pydio-cells/cells/services/pydio.grpc.log
  8.0K    /srv/pydio-cells/cells/services/pydio.test.objects
  8.0K    /srv/pydio-cells/cells/services/pydio.grpc.timer
  19M     /srv/pydio-cells/cells/services/pydio.grpc.versions
  8.0K    /srv/pydio-cells/cells/services/pydio.gateway.rest
  44K     /srv/pydio-cells/cells/services/pydio.grpc.mailer
  25G     /srv/pydio-cells/cells/services
  25G     total

  jkirk@ganymed ~ % ls -lt /srv/pydio-cells/cells/services/pydio.grpc.log | head
  total 480
  drwx------ 3 root root 4096 Jan 15 03:50 syslog.bleve.0119
  drwx------ 3 root root 4096 Jan 14 22:55 syslog.bleve.0118
  drwx------ 3 root root 4096 Jan 14 18:05 syslog.bleve.0117
  drwx------ 3 root root 4096 Jan 14 13:15 syslog.bleve.0116
  drwx------ 3 root root 4096 Jan 14 08:15 syslog.bleve.0115
  drwx------ 3 root root 4096 Jan 14 03:30 syslog.bleve.0114
  drwx------ 3 root root 4096 Jan 13 22:20 syslog.bleve.0113
  drwx------ 3 root root 4096 Jan 13 17:45 syslog.bleve.0112
  drwx------ 3 root root 4096 Jan 13 12:50 syslog.bleve.0111

  jkirk@ganymed ~ % ls -lt /srv/pydio-cells/cells/services/pydio.grpc.log | tail
  drwx------ 3 root root 4096 Jan  7  2023 syslog.bleve.0009
  drwx------ 3 root root 4096 Nov 14  2022 syslog.bleve.0008
  drwx------ 3 root root 4096 Nov  3  2022 syslog.bleve.0007
  drwx------ 3 root root 4096 Sep 12  2022 syslog.bleve.0006
  drwx------ 3 root root 4096 Jul 18  2022 syslog.bleve.0005
  drwx------ 3 root root 4096 May 26  2022 syslog.bleve.0004
  drwx------ 3 root root 4096 Apr 11  2022 syslog.bleve.0003
  drwx------ 3 root root 4096 Feb 24  2022 syslog.bleve.0002
  drwx------ 3 root root 4096 Jan  3  2022 syslog.bleve.0001
  drwx------ 3 root root 4096 Nov  9  2021 syslog.bleve

So after the last update, we got a total of 24GB of logs.

More than 18 million(!) lines of dispatcher-worker could not update activeChan value in 14 days.

  jkirk@ganymed /srv/pydio-cells % sudo docker-compose logs | grep "dispatcher-worker could not update activeChan value" | wc -l
  18464219

  jkirk@ganymed /srv/pydio-cells % sudo docker-compose logs | grep "dispatcher-worker could not update activeChan value" | head
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value +1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value -1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value +1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value -1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value +1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value -1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value +1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value -1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value +1
  cells_1    | 2024-01-03T18:34:30.693Z   INFO    pydio.grpc.tasks        [debug] dispatcher-worker could not update activeChan value -1

What version of Cells are you using?

v4.3.2 via docker image from Docker

What is the server OS? Database name/version? Browser name or mobile device description (if issue appears client-side)?

Debian/bullseye

What steps have you taken to resolve this issue already?

None, so far. I am about to update the docker image and delete the logs.

2

Hi,
This log is in fact not so important, but … it should not appear so frequently :slight_smile:
Do you have a very high usage of your platform? This probably indicates that you do not have enough resources (cpu/mem) to fit your needs.
Anyway, we’ll make sure to remove this log in the next version.
-c

3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.