kopano files_plugin errors out

fbartels

Hi @ckruijntjens,

I am not really involved in webapp development so I would not know. @marty is the once that is closer to the material.

But I am wondering if you really do not get an error message. Error 500 is an “internal server” error and usually always gets logged on the server (as its happening there).

@fbartels

no errors. but could be i dont have debu on. I will enable debug to see what happens

This post is deleted!

@fbartels @marty

With the yust newly deployed files-plugin the issue is resolved.

With version kopano-webapp-plugin-files_3.0.0.39+359.1_all still the same error.

Looks like there is a cache in kopano with old not existent folders from my nextcloud.
How can I reset the cache?

Best regards,

Frank

marty

@sauserdauser

Could you check the log for an error message, so we have an idea where it fails.

Sure, part of php7.2-fpm:

[13-May-2020 10:41:36] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [BACKEND_WEBDAV]: [LS] start for dir: AAA-Barkasse/”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [BACKEND_WEBDAV]: [LS] backend fetched in: 1.8994901180267 seconds.”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [BACKEND_WEBDAV]: [LS] done in 1.8995430469513 seconds”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [DBG][FilesListModule] Setting cache for node: 8a3105f9479fa2ea850415b5c6c50c1e/AAA-Barkasse ## HansMeyserad8a699aa81ef66ae6902198e5141764”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [DBG][FilesListModule] Getting cache for node: 8a3105f9479fa2ea850415b5c6c50c1e/ ## HansMeyser6fb10150fa2d75193763ace1ff430c48”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [DBG][FilesListModule] Getting cache for node: 8a3105f9479fa2ea850415b5c6c50c1e/AAA-Barkasse ## HansMeysere78585cff1b1e391e00636f30a03f77b”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [BACKEND_WEBDAV]: [LS] start for dir: BBB-Barkasse/”
[13-May-2020 10:41:40] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [BACKEND_WEBDAV]: ls general exception: HTTP error response. (errorcode 503) [500]”
[13-May-2020 10:41:41] WARNING: [pool zpool72] child 18007 said into stderr: “NOTICE: PHP message: [DBG][BackendStore] Searching for external backends in /usr/share/kopano-webapp/plugins/”
[13-May-2020 10:41:41] WARNING: [pool zpool72] child 18007 said into stderr: “NOTICE: PHP message: [DBG][BackendStore] Registering backend: Webdav”
[13-May-2020 10:41:41] WARNING: [pool zpool72] child 18007 said into stderr: “NOTICE: PHP message: [DBG][BackendStore] Registering backend: FTP”
[13-May-2020 10:41:41] WARNING: [pool zpool72] child 18007 said into stderr: “NOTICE: PHP message: [DBG][BackendStore] Registering external backend: Owncloud”

marty

@sauserdauser

Unsure if this 503 error is related to the caching.

You can rebuild the cache by reloading the files hierarchy.

This is the result of rebuild the cache with F5:

marty

@sauserdauser Yeah it takes some time.

after ~2 hours the same result. In the NextCloud I found that Kopano try to read already deleted folders.

marty

Could you give us some more information,
such as the version you upgraded from?

Does it also occur with the plugin kopano-webapp-plugin-owncloud?

I use the latest versions.
kopano-webapp-plugin-filesbackend-owncloud 3.0.0.15+115.1

It occur with the Owncloud and WebDav plugin. I also recreated the account. Same issue.

marty

@sauserdauser

If it happens on new accounts than it seems a different issue than files tries to read already deleted folders.

Humor me: how does files 2.x (last final) behaves with your account?

Are you sure your fileserver is setup correctly? After all it’s a 503 error.

And if so, could you check if this is related to the content of BBB-Barkasse/or if it also occurs with different folders?

I meant a new user connection with the same username.
All kopano user have the problem that kopano try to read the delete main folders on the nextcloud. Looks like kopano has a cache with the old information. If I create an new testuser with the same authrization all ist Okay

marty

@sauserdauser

If it does it would throw a 404, which is does on my machine. Not a 503.

Please check the questions in my previous post.
And try to reproduce this issue with a new user as well.

Btw your log it shows:

[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [DBG][FilesListModule] Getting cache for node: 8a3105f9479fa2ea850415b5c6c50c1e/AAA-Barkasse ## HansMeysere78585cff1b1e391e00636f30a03f77b”
[13-May-2020 10:41:38] WARNING: [pool zpool72] child 17903 said into stderr: “NOTICE: PHP message: [BACKEND_WEBDAV]: [LS] start for dir: BBB-Barkasse/”

There is no request made for the cache for “BBB-Barkasse” or you changed the names in the log?

I found now the error on the nextcloud. We use groupfolders and there is a problem with the trash.

I fixed the issue with delete the database entries “DELETE from oc_filecache WHERE path LIKE “__groupfolders/trash/%”” and the related files on os level.

Thank you for your support

Martin

@plzk-de said in kopano files_plugin errors out:

I just signed up again here to report, that kopano through UCS have delivery again faulty plugins.

Hello @plzk-de , please take a look at here

fbartels

@Martin thanks for pointing him in the right direction. I move his post into the linked topic.