-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recurring database entries to table 'activity' #34017
Comments
I guess you have 2 clients for contacts/addressbook syncing which back and forth change the contact again and again. Are you syncing your contacts with phones, laptops and computers? If so which programs are you using? |
Thank you for answer @nickvergessen - I am using DAVx5 on my Android smartphone and have sync clients for Thunderbird (TbSync). I cleaned the database and watched the logs for 5 minutes. No client made changes, but the activity table got new entries again. So I think I could confirm, that these entries occur just by processing "cron.php"! So 1st call after cleaning: 170 entries, 2nd call: 385 entries, 3rd call 590 entries. 4th call 725 entries... No client connected in this time, except "notification" and "heartbeat". I called like in crontab:
|
Could you do the same test but stop cron in the meantime to see what happens? |
@solracsf When I disable cron, no entries are added in the database. When I then manually call "cron.php" again, after 1st call: 210 more entries, after 2nd call 405, after 3rd call 615. |
Can you change the log level to 0, wait minutes and then check the nextcloud.log file for entries which cron jobs got executed? |
@nickvergessen - okay, I called cron.php while on loglevel 0. 200 lines in 'activity' were created this time. Here is the output:
|
OCA\DAV\Migration\BuildSocialSearchIndexBackgroundJob Seems to be the problematic one. |
Was added with 21 already #22222 |
I'm seeing something similar on another instance and database logs show DELETEs and INSERTs of Most probably called from |
#33813 potentially fixes the recurring contact updates |
Hi, please update to 24.0.9 or better 25.0.3 and report back if it fixes the issue. Thank you! My goal is to add a label like e.g. 25-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort! If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+ |
Dear Support,
Steps to reproduce
Expected behaviour
While no contact card change occured, no more entries get to the table
Actual behaviour
The table 'activity' grows ~200 entries every 5 minutes. I recognized this problem, because the database file was ~7GB in size with about 18.000.000 entries. Queries that involved this table took about 90sec. Randomly contacts get added to the table 'activity'. Always the same contacts. No effect if changing/saving the contacts. When deleting the contacts, other contacts occur here. I deleted all via the variable 'activity_expire_days'. The entries say subject='card_update_self' and then followed by all users that are member of the group with subject='card_update'.
Operating system:
Linux vm 5.10.0-18-amd64 nextcloud/activity#1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux
Web server:
apache2 2.4.54-1~deb11u1 amd64
Database:
mariadb-server-10.5 1:10.5.15-0+deb11u1
PHP version:
php7.4.30-1+deb11u1
Nextcloud version: (see Nextcloud admin page)
Nextcloud 24.0.5
Activity 2.16.0
Contacts 4.2.0
Where did you install Nextcloud from:
Channel Stable, web updated
Signing status:
List of activated apps:
Nextcloud configuration:
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no
Client configuration
Browser:
Firefox
Operating system:
Linux Mint
The text was updated successfully, but these errors were encountered: