Activity notification loop - an email sent to all every 30 minutes

8.2.x
reported_bug
help

#1

Please help us by providing the following info. Before posting please also check the pinned "Known issues" threads and make sure that you're running the latest available version for your oC release: https://owncloud.org/changelog/

Steps to reproduce
1. The server is sending the activity email to all users every thirty minutes with teh same content
2. This happened after a share to all was set at a top level folder and then a share to all was set on a sub-level folder. This possibly led to a loop
3.

Expected behaviour
The activety email should only go out for new activities and not be repeated

Actual behaviour
The server is sending the activity email to all users every thirty minutes with teh same content

Server configuration
Operating system: ubuntu
Web server:apache
Database:
PHP version:
ownCloud version (see ownCloud admin page): 8.27
Updated from an older ownCloud or fresh install: fresh install
ownCloud log (data/owncloud.log, see https://central.owncloud.org/t/how-to-find-webserver-or-oc-logfile-enable-php-logfile/808):

Special configuration (external storage, external authentication, reverse proxy, server-side-encryption):

Integrity status for oC9+

Login as admin user into your ownCloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

#2

Hi,

that info for example was missing in your previous post (which was btw. tagged as 9.1.x).

Before reporting any issues please always use the latest available version. In your case this is 8.2.8: https://owncloud.org/changelog/#latest8.2


#3

I had the same issue in nextcloud version 10, so I dont think its a version issue. Any idea what could be causing such a loop? I checked the net but see no reference anywhere to such an issue


#4

If you think its not a version issue then just report a new bug to:

https://github.com/owncloud/core/issues

The people reading there have more insight into such internals.


#5

Thanks for reporting it at the issue tracker. Here is the reference: