-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
PHP processes crashing when uploading files to Nextcloud server #1413
Comments
Anything in nextcloud logs? This should never really happen, so might be a php bug |
No, there is no errors in nextcloud logs. Very strange situation. I need to get core dump. |
Only android app returns 'server in maintenace mode' |
The only thing memories does on upload is index the file. Does it also crash if you do occ memories:index? Are you memory bound? OOM maybe? |
No, when I run command occ memories:index, all works fine. I have 16G memory on my server. Memory used mostly by ZFS ARC. Swap is emty |
When uploading files to server memories running script /lib/Service/Index.php? |
Yes it will index the file, but not "run the script" (gets called through nextcloud hooks) |
Good morning! I traced system calls with truss yesterday and find out that php craches happen in various places of code with various signals (sigsegv, sigabrt, sigbus) each time. But only when memories is enabled. I don't understand what's happening. Maybe it is incompatible versions of php extensions or incorrect build. My php installed from packages. |
Describe the bug
When Memories app is enabled and you uploading files to Nextocloud server (no matter webDAV or mobile app), PHP processes crashes:
php-fpm.log
When Memories app is disabled and you uploading files to server, all works fine. I tried to get core dump to solve this problem, but without success. I compiled PHP with --DEBUG option, but in this case Nextcloud server didn't worked at all (may be I did something wrong).
Steps To Reproduce
Platform
Screenshots
No response
Additional context
The text was updated successfully, but these errors were encountered: