Files 3.0.0 pre-final available

mcostan

now rolled back and everything is back to normal.

My guess is that the issue is the first initial unexpected error which however I am unclear how to identify.

umgfoin

Hi mcostan,

I looked at the log file but I can’t see anything obvious.

Did you raise the log-verbosity for the files plugin?
/etc/kopano/webapp/config-files.php

define('PLUGIN_FILESBROWSER_LOGLEVEL', "DEBUG");

++umgfoin.

mcostan

yep… already it was.

Happy to send you the log files by email if you like.

marty

@mcostan

Thanks for the try.
We’ve added some better logging (webapp) for this unexpected error (already in master)
If an error is logged you should be able to find it by searching for:

JSON ERROR

In the meantime we’re working on some performance for the files plugin.
Most likely the requests had a time out on your machine.

mcostan

@marty

Hi Marty,

I will try the process again today and report back.

And thank you very much for your help.

mcostan

I just tried again.

I searched the entire log file and I cannot see JSON ERROR.

However when I now log in, I get the following error message instead:

Server encountered some problem, so it was not able to handle the request.

After that, the files area is still completely empty.

Rolled back and everything back to normal.

Note that the error message occurs immediately after logging into webapp (pretty much instantly)

Thanks for your help.

I have taken a copy of the log file which I can send you if you would like to.

umgfoin

Update:
Files-3.0 - git master 67cd8a32846 with webapp
3.5.11.24-g059d608p on CentOS 6, PHP 7.3, memcached:

Problems gone - working for nextcloud and smb.

The long periods of unresponsiveness while loading/updating folder contents disappeared after setting log-level from DEBUG to NORMAL.

++umgfoin.

mcostan

not working for me though. Unless something has changed in the code from 3 days ago.

marty

@mcostan Keep an eye on
https://jira.kopano.io/browse/KFP-412

Should work way faster after this fix.

mcostan

My error was that I get an unexpected error to start with… I really don’t think my error was due to the caching…

But hey… who am I to say.