Internal Server Error after update / check-code error #43

Closed
opened 2020-10-13 23:22:05 +02:00 by spreeni · 7 comments

Dear deblan,

today I got an error screen (Internal Server Error) which prevents me of accessing my Nextcloud instance. The support of my provider checked everything and after that they said, that the side_menu app caused the trouble. They deleted the app folder and after that everything was running fine again.

So I wondered, how this can be and went bug-hunting. I had updated the app to 1.16.1 a day before the trouble - can such a heavy error happen nearly 24 hours later?! I'm no IT-expert, just a user, but maybe you have an answer for that?

In the OCC-Web app I typed "app:check-code side_menu" and the result was

Analysing /data/www/mewe.owncube.cloud/apps/side_menu/lib/AppInfo/Application.php
1 errors
line   75: OC_App - private class must not be instantiated
Analysing /data/www/mewe.owncube.cloud/apps/side_menu/lib/Service/AppRepository.php
1 errors
line    5: OC_App - private class must not be imported with a use statement
App is not compliant

Unfortunately I cannot do more testing because I have no access to the root of the server. What do you think, could this have something to do with this server-error-trouble? "App is not compliant" sounds not good...

Regards, Frank

Dear deblan, today I got an error screen (Internal Server Error) which prevents me of accessing my Nextcloud instance. The support of my provider checked everything and after that they said, that the side_menu app caused the trouble. They deleted the app folder and after that everything was running fine again. So I wondered, how this can be and went bug-hunting. I had updated the app to 1.16.1 a day before the trouble - can such a heavy error happen nearly 24 hours later?! I'm no IT-expert, just a user, but maybe you have an answer for that? In the OCC-Web app I typed "app:check-code side_menu" and the result was ``` Analysing /data/www/mewe.owncube.cloud/apps/side_menu/lib/AppInfo/Application.php 1 errors line 75: OC_App - private class must not be instantiated Analysing /data/www/mewe.owncube.cloud/apps/side_menu/lib/Service/AppRepository.php 1 errors line 5: OC_App - private class must not be imported with a use statement App is not compliant ``` Unfortunately I cannot do more testing because I have no access to the root of the server. What do you think, could this have something to do with this server-error-trouble? "App is not compliant" sounds not good... Regards, Frank
Owner

Hello,

What is the version of Nextcloud and PHP please ?

Hello, What is the version of Nextcloud and PHP please ?
deblan added the
question
label 2020-10-14 07:48:32 +02:00
Author

sorry, I forgot to write that:
Nextcloud 19.0.3.1
PHP Version: 7.3.15

sorry, I forgot to write that: Nextcloud 19.0.3.1 PHP Version: 7.3.15
Owner

The check code is not a debugger but I will fix it anyway.

I can't reproduce the internal server error. I need your nextcloud log to understand what happened (data/nextcloud.log).

The check code is not a debugger but I will fix it anyway. I can't reproduce the internal server error. I need your nextcloud log to understand what happened (`data/nextcloud.log`).
Author

I'm using your app on a test system and there I cannot reproduce the error, too. Although the "app is not compliant" message is shown there it is running without any problems, there.
So maybe it's a fault of my provider - it's easy for him to show to the 3rd party addon and say, it's the fault of it.
That's why I decided to contact you for checking, if this can be a real bug. A server error 24h after updating an app sound a bit strange to me - I trust your judgement more than my provider :-)
I add the log of yesterday's backup by this message.

I'm using your app on a test system and there I cannot reproduce the error, too. Although the "app is not compliant" message is shown there it is running without any problems, there. So maybe it's a fault of my provider - it's easy for him to show to the 3rd party addon and say, it's the fault of it. That's why I decided to contact you for checking, if this can be a real bug. A server error 24h after updating an app sound a bit strange to me - I trust your judgement more than my provider :-) I add the log of yesterday's backup by this message.
Owner

I fixed errors thrown with app:check, see attachements for the preview.

I'm analyzing your logs.

I fixed errors thrown with app:check, see attachements for the preview. I'm analyzing your logs.
Owner

I see things.

Firstly, app.nextcloud.com occured access issues this week with many times out. That's why I have add a cache mechanism on the application to fix #42 (this fix is not your problem).

{"reqId":"X4GhU0Wq@gLaKIO4NWUEkAAAAFs","level":2,"time":"2020-10-10T11:56:35+00:00","remoteAddr":"92.116.3.117","user":"admin","app":"appstoreFetcher","method":"GET","url":"/settings/apps","message":"Could not connect to appstore: cURL error 7: Failed to connect to apps.nextcloud.com port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.3.1"}

I don't see issue with Custom Menu:

$ grep SideMenu nextcloud_13.10.log # no result
$ grep side_menu nextcloud_13.10.log        
{"reqId":"XxCGu7csYlluv0ggqaaZzgAAABs","level":1,"time":"2020-07-16T16:56:34+00:00","remoteAddr":"92.116.59.153","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=QOA%2BnzwFb1g2OssuADZuuYfJK8XZncdJVY%2FzhJYML2M%3D%3AAqdW2lRgNQkODo1HZAY37vaqXfyx%2B5Ybbe2h6PtqXy8%3D","message":"\\OC\\Updater::checkAppStoreAppBefore: Checking for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0","version":"19.0.0.12"}
{"reqId":"XxCGu7csYlluv0ggqaaZzgAAABs","level":1,"time":"2020-07-16T16:56:34+00:00","remoteAddr":"92.116.59.153","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=QOA%2BnzwFb1g2OssuADZuuYfJK8XZncdJVY%2FzhJYML2M%3D%3AAqdW2lRgNQkODo1HZAY37vaqXfyx%2B5Ybbe2h6PtqXy8%3D","message":"\\OC\\Updater::checkAppStoreApp: Checked for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0","version":"19.0.0.12"}
{"reqId":"X3TjsH7Mj2csA-jXNZNVqgAAAC0","level":1,"time":"2020-09-30T19:59:52+00:00","remoteAddr":"92.116.38.40","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=tPYjVgRnOtmYOGupTcr%2Bgq9pihetlEhnvGJ7Fang%2B0o%3D%3AzbRoPlcTabb7CCXmIKnMzskZ%2F1TF%2BwwE2w4WZsKVrQ0%3D","message":"\\OC\\Updater::checkAppStoreAppBefore: Checking for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.1.1"}
{"reqId":"X3TjsH7Mj2csA-jXNZNVqgAAAC0","level":1,"time":"2020-09-30T19:59:52+00:00","remoteAddr":"92.116.38.40","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=tPYjVgRnOtmYOGupTcr%2Bgq9pihetlEhnvGJ7Fang%2B0o%3D%3AzbRoPlcTabb7CCXmIKnMzskZ%2F1TF%2BwwE2w4WZsKVrQ0%3D","message":"\\OC\\Updater::upgradeAppStoreApp: Update app \"side_menu\" from appstore","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.1.1"}
{"reqId":"X3TjsH7Mj2csA-jXNZNVqgAAAC0","level":1,"time":"2020-09-30T19:59:53+00:00","remoteAddr":"92.116.38.40","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=tPYjVgRnOtmYOGupTcr%2Bgq9pihetlEhnvGJ7Fang%2B0o%3D%3AzbRoPlcTabb7CCXmIKnMzskZ%2F1TF%2BwwE2w4WZsKVrQ0%3D","message":"\\OC\\Updater::checkAppStoreApp: Checked for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.1.1"}

Are calendar and tasks enabled? You seem to have a problem with them.

{"reqId":"X4DC@4AMW5n@vfDMDx4yhgAAAY8","level":3,"time":"2020-10-09T20:07:24+00:00","remoteAddr":"92.116.21.30","user":"Frank Spreen-Ledebur","app":"no app in context","method":"OPTIONS","url":"/remote.php/","message":{"Exception":"Symfony\\Component\\Routing\\Exception\\RouteNotFoundException","Message":"Unable to generate a URL for the named route \"calendar.view.index\" as such route does not exist.","Code":0, ...
$ grep -i exception nextcloud_13.10.log | egrep -o '"Unable to generate a URL for the named route .* does not exist."' -c # 147 results
$ grep -i exception nextcloud_13.10.log | egrep -o '"Unable to generate a URL for the named route .* does not exist."' | sort -u
"Unable to generate a URL for the named route \"calendar.view.index\" as such route does not exist."
"Unable to generate a URL for the named route \"mail.page.index\" as such route does not exist."
"Unable to generate a URL for the named route \"tasks.page.index\" as such route does not exist."
"Unable to generate a URL for the named route \"theming.Theming.getImage\" as such route does not exist."

You have several lines with this warning:

{"reqId":"nwPw74OWPFQSlOBDeJBx","level":3,"time":"2020-10-10T05:50:04+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"filesize(): stat failed for /data/www/mewe.owncube.cloud/data/admin/files_versions/XXXXXXXX at /data/www/mewe.owncube.cloud/lib/private/Files/Storage/Local.php#224","userAgent":"--","version":"19.0.3.1"}

And Finally, this all exceptions messages:

$ grep -i exception nextcloud_13.10.log | jq '.message.Message' | sort -u

""
"An exception occurred while executing 'UPDATE `oc_talk_participants` SET `session_id` = ?, `in_call` = ? WHERE (`user_id` = ?) AND (`room_id` = ?) AND (`participant_type` <> ?)' with params [\"0\", 0, \"Nils Dunsche\", 27, 5]:\n\nSQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction"
"Argument 6 passed to OCA\\BigBlueButton\\Controller\\RoomController::update() must be of the type string, null given, called in /data/www/mewe.owncube.cloud/lib/private/AppFramework/Http/Dispatcher.php on line 170"
"Backends provided no user object"
"Call to a member function getMountPoint() on null"
"Could not rename part file to final file"
"Could not save draft message"
"Der Dateiname enthält mindestens ein ungültiges Zeichen"
"Did expect one result but found none when executing: query \"SELECT * FROM `*PREFIX*bbb_rooms` WHERE `id` = :dcValue1\"; "
"Error when communicating with the mail server."
"Expected filesize of 10382658 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 57708 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10434498 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 90476 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 10304019 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 10333328 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 35620 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 38472 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 49152 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 6141876 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 8806764 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 96180 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 9934408 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 1212416 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 765072 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 1460862 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 14989098 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 4036168 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 15875156 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11485183 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 18442 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 188045 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 163839 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 18830741 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 7258110 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 189809 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 217572 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 22312506 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11376200 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 2273925880 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 317784064 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 231878 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 23469 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 24339786 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 6283628 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 259784 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 26148647 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11567103 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 2796736 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 32768 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 3032936921 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 633864192 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 4190462 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3366912 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 4323138 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1518736 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 44461612 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11583488 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 4783938 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3127220 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 4899138 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 93328 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 5181378 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 32768 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 5765658 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1011712 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 586298327 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 2826604 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 5882449 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3518464 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 5988876 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3096576 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 6874818 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 6234476 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 7187922 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 7686864 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3248128 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 7772837 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3416064 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 8072898 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1007980 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 9409218 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3452048 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 9539803 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 5881855 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 138395590 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 18300899 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 28803014 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 455409664 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 62136320 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side."
"Namespace prefix DAV on lastmodified is not defined\n on line 4, column 75"
"Node for share not found, fileid: 91806"
"strlen() expects parameter 1 to be string, null given"
"Sync failed for 7:Drafts: Error when communicating with the mail server."
"The input element to parse is empty. Do not attempt to parse"
"The start offset (1302) exceeded the size of the entity (1302)"
"The start offset (16536) exceeded the size of the entity (16536)"
"The start offset (258666) exceeded the size of the entity (258666)"
"The start offset (681290) exceeded the size of the entity (681290)"
"The start offset (8208) exceeded the size of the entity (8208)"
"Unable to generate a URL for the named route \"calendar.view.index\" as such route does not exist."
"Unable to generate a URL for the named route \"mail.page.index\" as such route does not exist."
"Unable to generate a URL for the named route \"tasks.page.index\" as such route does not exist."
"Unable to generate a URL for the named route \"theming.Theming.getImage\" as such route does not exist."

In my opinion, you should move from SQLite to MySQL because SQLite should be use only for development (as I do), you should take a look at your disabled apps (calendar, tasks, mail)…and this may be an issue with the apps.nextcloud.com connectivity.

I see things. Firstly, app.nextcloud.com occured access issues this week with many times out. That's why I have add a cache mechanism on the application to fix https://gitnet.fr/deblan/side_menu/issues/42 (this fix is not your problem). ``` {"reqId":"X4GhU0Wq@gLaKIO4NWUEkAAAAFs","level":2,"time":"2020-10-10T11:56:35+00:00","remoteAddr":"92.116.3.117","user":"admin","app":"appstoreFetcher","method":"GET","url":"/settings/apps","message":"Could not connect to appstore: cURL error 7: Failed to connect to apps.nextcloud.com port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.3.1"} ``` I don't see issue with Custom Menu: ``` $ grep SideMenu nextcloud_13.10.log # no result $ grep side_menu nextcloud_13.10.log {"reqId":"XxCGu7csYlluv0ggqaaZzgAAABs","level":1,"time":"2020-07-16T16:56:34+00:00","remoteAddr":"92.116.59.153","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=QOA%2BnzwFb1g2OssuADZuuYfJK8XZncdJVY%2FzhJYML2M%3D%3AAqdW2lRgNQkODo1HZAY37vaqXfyx%2B5Ybbe2h6PtqXy8%3D","message":"\\OC\\Updater::checkAppStoreAppBefore: Checking for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0","version":"19.0.0.12"} {"reqId":"XxCGu7csYlluv0ggqaaZzgAAABs","level":1,"time":"2020-07-16T16:56:34+00:00","remoteAddr":"92.116.59.153","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=QOA%2BnzwFb1g2OssuADZuuYfJK8XZncdJVY%2FzhJYML2M%3D%3AAqdW2lRgNQkODo1HZAY37vaqXfyx%2B5Ybbe2h6PtqXy8%3D","message":"\\OC\\Updater::checkAppStoreApp: Checked for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0","version":"19.0.0.12"} {"reqId":"X3TjsH7Mj2csA-jXNZNVqgAAAC0","level":1,"time":"2020-09-30T19:59:52+00:00","remoteAddr":"92.116.38.40","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=tPYjVgRnOtmYOGupTcr%2Bgq9pihetlEhnvGJ7Fang%2B0o%3D%3AzbRoPlcTabb7CCXmIKnMzskZ%2F1TF%2BwwE2w4WZsKVrQ0%3D","message":"\\OC\\Updater::checkAppStoreAppBefore: Checking for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.1.1"} {"reqId":"X3TjsH7Mj2csA-jXNZNVqgAAAC0","level":1,"time":"2020-09-30T19:59:52+00:00","remoteAddr":"92.116.38.40","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=tPYjVgRnOtmYOGupTcr%2Bgq9pihetlEhnvGJ7Fang%2B0o%3D%3AzbRoPlcTabb7CCXmIKnMzskZ%2F1TF%2BwwE2w4WZsKVrQ0%3D","message":"\\OC\\Updater::upgradeAppStoreApp: Update app \"side_menu\" from appstore","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.1.1"} {"reqId":"X3TjsH7Mj2csA-jXNZNVqgAAAC0","level":1,"time":"2020-09-30T19:59:53+00:00","remoteAddr":"92.116.38.40","user":"--","app":"updater","method":"GET","url":"/core/ajax/update.php?requesttoken=tPYjVgRnOtmYOGupTcr%2Bgq9pihetlEhnvGJ7Fang%2B0o%3D%3AzbRoPlcTabb7CCXmIKnMzskZ%2F1TF%2BwwE2w4WZsKVrQ0%3D","message":"\\OC\\Updater::checkAppStoreApp: Checked for update of app \"side_menu\" in appstore","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0","version":"19.0.1.1"} ``` Are calendar and tasks enabled? You seem to have a problem with them. ``` {"reqId":"X4DC@4AMW5n@vfDMDx4yhgAAAY8","level":3,"time":"2020-10-09T20:07:24+00:00","remoteAddr":"92.116.21.30","user":"Frank Spreen-Ledebur","app":"no app in context","method":"OPTIONS","url":"/remote.php/","message":{"Exception":"Symfony\\Component\\Routing\\Exception\\RouteNotFoundException","Message":"Unable to generate a URL for the named route \"calendar.view.index\" as such route does not exist.","Code":0, ... ``` ``` $ grep -i exception nextcloud_13.10.log | egrep -o '"Unable to generate a URL for the named route .* does not exist."' -c # 147 results $ grep -i exception nextcloud_13.10.log | egrep -o '"Unable to generate a URL for the named route .* does not exist."' | sort -u "Unable to generate a URL for the named route \"calendar.view.index\" as such route does not exist." "Unable to generate a URL for the named route \"mail.page.index\" as such route does not exist." "Unable to generate a URL for the named route \"tasks.page.index\" as such route does not exist." "Unable to generate a URL for the named route \"theming.Theming.getImage\" as such route does not exist." ``` You have several lines with this warning: ``` {"reqId":"nwPw74OWPFQSlOBDeJBx","level":3,"time":"2020-10-10T05:50:04+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"filesize(): stat failed for /data/www/mewe.owncube.cloud/data/admin/files_versions/XXXXXXXX at /data/www/mewe.owncube.cloud/lib/private/Files/Storage/Local.php#224","userAgent":"--","version":"19.0.3.1"} ``` And Finally, this all exceptions messages: ``` $ grep -i exception nextcloud_13.10.log | jq '.message.Message' | sort -u "" "An exception occurred while executing 'UPDATE `oc_talk_participants` SET `session_id` = ?, `in_call` = ? WHERE (`user_id` = ?) AND (`room_id` = ?) AND (`participant_type` <> ?)' with params [\"0\", 0, \"Nils Dunsche\", 27, 5]:\n\nSQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction" "Argument 6 passed to OCA\\BigBlueButton\\Controller\\RoomController::update() must be of the type string, null given, called in /data/www/mewe.owncube.cloud/lib/private/AppFramework/Http/Dispatcher.php on line 170" "Backends provided no user object" "Call to a member function getMountPoint() on null" "Could not rename part file to final file" "Could not save draft message" "Der Dateiname enthält mindestens ein ungültiges Zeichen" "Did expect one result but found none when executing: query \"SELECT * FROM `*PREFIX*bbb_rooms` WHERE `id` = :dcValue1\"; " "Error when communicating with the mail server." "Expected filesize of 10382658 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 57708 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10434498 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 90476 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 10304019 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 10333328 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 35620 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 38472 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 49152 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 6141876 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 8806764 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 96180 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 9934408 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 1212416 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 765072 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 1460862 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 14989098 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 4036168 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 15875156 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11485183 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 18442 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 188045 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 163839 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 18830741 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 7258110 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 189809 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 217572 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 22312506 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11376200 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 2273925880 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 317784064 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 231878 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 23469 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 24339786 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 6283628 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 259784 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 26148647 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11567103 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 2796736 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 32768 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 3032936921 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 633864192 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 4190462 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3366912 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 4323138 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1518736 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 44461612 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 11583488 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 4783938 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3127220 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 4899138 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 93328 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 5181378 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 32768 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 5765658 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1011712 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 586298327 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 2826604 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 5882449 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3518464 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 5988876 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3096576 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 6874818 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 6234476 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 7187922 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 7686864 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3248128 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 7772837 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3416064 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 8072898 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1007980 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 9409218 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 3452048 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 9539803 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 5881855 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 138395590 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 18300899 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 28803014 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 455409664 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Expected filesize of 957678605 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 62136320 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side." "Namespace prefix DAV on lastmodified is not defined\n on line 4, column 75" "Node for share not found, fileid: 91806" "strlen() expects parameter 1 to be string, null given" "Sync failed for 7:Drafts: Error when communicating with the mail server." "The input element to parse is empty. Do not attempt to parse" "The start offset (1302) exceeded the size of the entity (1302)" "The start offset (16536) exceeded the size of the entity (16536)" "The start offset (258666) exceeded the size of the entity (258666)" "The start offset (681290) exceeded the size of the entity (681290)" "The start offset (8208) exceeded the size of the entity (8208)" "Unable to generate a URL for the named route \"calendar.view.index\" as such route does not exist." "Unable to generate a URL for the named route \"mail.page.index\" as such route does not exist." "Unable to generate a URL for the named route \"tasks.page.index\" as such route does not exist." "Unable to generate a URL for the named route \"theming.Theming.getImage\" as such route does not exist." ``` In my opinion, you should move from SQLite to MySQL because SQLite should be use only for development (as I do), you should take a look at your disabled apps (calendar, tasks, mail)…and this may be an issue with the apps.nextcloud.com connectivity.
Author

Thank you for taking the time and have a look on the log. I will try to give the recommendations further to the provider. These SQLite warnings are strange because as far as I know the provider uses mysql. I will investigate that. I have a strong feeling, that your app is not the cause of the server error :-) .
So long, again, thank you very much!

Thank you for taking the time and have a look on the log. I will try to give the recommendations further to the provider. These SQLite warnings are strange because as far as I know the provider uses mysql. I will investigate that. I have a strong feeling, that your app is not the cause of the server error :-) . So long, again, thank you very much!
deblan removed the
question
label 2020-10-14 11:29:19 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: deblan/side_menu#43
No description provided.