You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in comment nextcloud/server#45682 (comment)
I kept getting these errors in NC log after upgrade to NC 29.0.9 + Maps 1.4.0
Warning | cron | Cron job used more than 300 MB of ram after executing job OCA\Maps\BackgroundJob\AddPhotoJob (id: 622614, arguments: {"photoId":30578,"userId":"luka"}): 296.4 MB (before: 283.7 MB) | "19. stu 2024. 21:55:04"
Warning | cron | Cron job used more than 300 MB of ram after executing job OCA\Maps\BackgroundJob\AddPhotoJob (id: 600786, arguments: {"photoId":83819,"userId":"luka"}): 286.5 MB (before: 280.5 MB) | "19. stu 2024. 21:41:34"
Warning | cron | Cron job used more than 300 MB of ram after executing job OCA\Maps\BackgroundJob\AddPhotoJob (id: 571892, arguments: {"photoId":47767,"userId":"luka"}): 287.9 MB (before: 284.6 MB) | "19. stu 2024. 21:25:12"
Warning | cron | Cron job used more than 300 MB of ram after executing job OCA\Maps\BackgroundJob\AddPhotoJob (id: 561832, arguments: {"photoId":25830,"userId":"luka"}): 287.9 MB (before: 285 MB) | "19. stu 2024. 21:16:33"
As I was informed this is new feature of NC29 to monitor background jobs for memory usage. And it seems that AddPhotoJob in Maps is using more memory than expected.
I got around it by moving these messages from warning to debug log by editing line 200 in /var/www/nextcloud/cron.php which says $logger->warning($message, ['app' => 'cron']);, but I was asked if I could open issue here as well.
Steps to reproduce
Upgrade to NC29 with Maps, and wait for background job to start scanning photos to add them to map. Eventually it should trigger 300MB warning. Large photo library might be required.
Expected behavior
Job to use less memory and not trigger constant warnings.
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install of the server?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Is this bug present after an update or on a fresh install of the app?
Updated from a minor version
Are you using the Nextcloud Server Encryption module?
{"reqId":"G7XPPZqHMfmIfOhg4Xbr","level":2,"time":"2024-11-19T20:55:04+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Cron job used more than 300 MB of ram after executing job OCA\\Maps\\BackgroundJob\\AddPhotoJob (id: 622614, arguments: {\"photoId\":30578,\"userId\":\"luka\"}): 296.4 MB (before: 283.7 MB)","userAgent":"--","version":"29.0.9.2","data":{"app":"cron"},"id":"673d95c222672"}
{"reqId":"EZUYTP4Bni7A3ABBaA1l","level":2,"time":"2024-11-19T20:41:34+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Cron job used more than 300 MB of ram after executing job OCA\\Maps\\BackgroundJob\\AddPhotoJob (id: 600786, arguments: {\"photoId\":83819,\"userId\":\"luka\"}): 286.5 MB (before: 280.5 MB)","userAgent":"--","version":"29.0.9.2","data":{"app":"cron"},"id":"673d95c222677"}
{"reqId":"m8AZloar8nnKf96cyTT4","level":2,"time":"2024-11-19T20:25:12+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Cron job used more than 300 MB of ram after executing job OCA\\Maps\\BackgroundJob\\AddPhotoJob (id: 571892, arguments: {\"photoId\":47767,\"userId\":\"luka\"}): 287.9 MB (before: 284.6 MB)","userAgent":"--","version":"29.0.9.2","data":{"app":"cron"},"id":"673d95c22267b"}
{"reqId":"oF8LvUyhLUlohM0n2Y34","level":2,"time":"2024-11-19T20:16:33+00:00","remoteAddr":"","user":"--","app":"cron","method":"","url":"--","message":"Cron job used more than 300 MB of ram after executing job OCA\\Maps\\BackgroundJob\\AddPhotoJob (id: 561832, arguments: {\"photoId\":25830,\"userId\":\"luka\"}): 287.9 MB (before: 285 MB)","userAgent":"--","version":"29.0.9.2","data":{"app":"cron"},"id":"673d95c22267f"}
Browser Console
Additional info
No response
The text was updated successfully, but these errors were encountered:
Bug description
As mentioned in comment nextcloud/server#45682 (comment)
I kept getting these errors in NC log after upgrade to NC 29.0.9 + Maps 1.4.0
As I was informed this is new feature of NC29 to monitor background jobs for memory usage. And it seems that
AddPhotoJob
in Maps is using more memory than expected.I got around it by moving these messages from warning to debug log by editing line 200 in
/var/www/nextcloud/cron.php
which says$logger->warning($message, ['app' => 'cron']);
, but I was asked if I could open issue here as well.Steps to reproduce
Upgrade to NC29 with Maps, and wait for background job to start scanning photos to add them to map. Eventually it should trigger 300MB warning. Large photo library might be required.
Expected behavior
Job to use less memory and not trigger constant warnings.
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install of the server?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Is this bug present after an update or on a fresh install of the app?
Updated from a minor version
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Browser Console
Additional info
No response
The text was updated successfully, but these errors were encountered: