Files 3.0.0 pre-final available
-
Hi Marty,
gettingPHP Fatal error: Bus::reset():
while parsing the directory structure (for both, owncloud- and smb-backends). When this error appears, the currently parsed subtree won’t expand in the GUI’s tree-pane (or doesn’t update any further) and the cursor stays in spinning-state.Response-time of webapp is generally degraded - the files-plugin is scanning the configured accounts in an endless-loop.
Please note:
I’m using an unsupported setup: CentOS 6, PHP 7.3, php-smbclient 1.0.0 (pear-build), memcachedfiles-2.1.6.334+227
working without serious issues.[11-Oct-2019 12:49:20] WARNING: [pool webmail.webapp.foo] child 25130 said into stderr: "PHP message: [DBG][FilesBrowserModule] [loadFilesTree]: getFolderContent took: 0.00065779685974121 seconds" [11-Oct-2019 12:49:20] WARNING: [pool webmail.webapp.foo] child 25131 said into stderr: "PHP message: PHP Fatal error: Bus::reset(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "FilesHierarchyNotifier" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition in /usr/share/kopano-webapp/server/includes/core/class.bus.php on line 314" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][AccountStore] Found 2 accounts." [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][BackendStore] Searching for external backends in /usr/share/kopano-webapp/plugins/" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][BackendStore] Registering backend: FTP" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][BackendStore] Registering backend: Webdav" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][BackendStore] Registering external backend: SMB" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][BackendStore] Registering external backend: Owncloud" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][FilesBrowserModule] [constructor]: executing the module as uid: brunzinger" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [BACKEND_WEBDAV]: Base path set to /remote.php/webdav" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [BACKEND_WEBDAV]: SSL extention was set to 1" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][FilesBrowserModule] Loading nodes for acc: b766b14e36c1621338f6b7c114c0e9f0 (Wolke Brunzinger)" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][FilesBrowserModule] Getting cache for node: b766b14e36c1621338f6b7c114c0e9f0/SAMBA home/aegaeon ## xar3c9dd8dd3caaa93a40d1d58a922fc282" [11-Oct-2019 12:49:21] WARNING: [pool webmail.webapp.foo] child 29804 said into stderr: "PHP message: [DBG][FilesBrowserModule] parsing: /SMB/foo/foo Kundendaten/ in base: #R#b766b14e36c1621338f6b7c114c0e9f0/SMB/foo/"
best regards,
++umgfoin. -
files-2.1.6.334+227 working without serious issues.
…after rolling back to 2.1.6, I noticed, the above PHP-error occurs even with
files-2.1.6
, but there it doesn’t cause any obvious problems.
So the observed issue is presumably unrelated to the DBG-message.++umgfoin.
-
installation now quite successful here.
a) installed files 3.0
b) restarted apache2 (Debian2)
c) I get a dialog box “An unexpected error has occurred”d) The files tab is completely empty (I use owncloud as a backend)
e) when I look in the apache2 log file I see this:
[Fri Oct 11 14:02:33.844215 2019] [:error] [pid 32698] [client 127.0.0.1:59604] [DBG][FilesListModule] Getting cache for node: f77026aa2ddb78d c14e582acc2545f11/PotentialProperties/Clacton ## mrc257a4fb6b9dc12f9090b713830662c47, referer: https://z.advanced-finance.com/webapp/ [Fri Oct 11 14:02:33.844341 2019] [:error] [pid 32698] [client 127.0.0.1:59604] [DBG][FilesListModule] Getting cache for node: f77026aa2ddb78d c14e582acc2545f11/PotentialProperties/Durham_unzipped ## mrc639df39636e5128255b50727d472da60, referer: https://z.advanced-finance.com/webapp/ [Fri Oct 11 14:02:33.844689 2019] [:error] [pid 32698] [client 127.0.0.1:59604] [BACKEND_WEBDAV]: [LS] start for dir: PotentialProperties/Durh am_unzipped/, referer: https://z.advanced-finance.com/webapp/
that is getting the directory structure I suppose
and then I can’t see anything wrong other than this:[Fri Oct 11 14:02:35.082018 2019] [:error] [pid 565] [client 127.0.0.1:59616] PHP Warning: include_once(): Failed opening 'plugins/htmleditor -quill/config.php' for inclusion (include_path=':/usr/share/kopano/php') in /usr/share/kopano-webapp/server/includes/core/class.pluginmanager. php on line 380, referer: https://z.advanced-finance.com/webapp/
If I however go under the settings / files I can see my cloud account setup correctly with a green status meaning it is connected correctly.
Present versions on my server
WebApp:
3.5.11.2456+1409.1
Kopano Core:
8.7.5
Z-Push:
2.5.1+0-0Summary: I have to rollback
Any ideas welcome.
-
FYI, rolled back and now it is fine.
Something is wrong with 3.0
-
Step d)
Files is probably creating the cache for your account, which takes a while.
We’re adding a loading mask in the next version.Could you give it another try, then wait a while for your account to load?
As for the “Unexpected error”
Could you dive in your logs and get the original error message? (If available) -
Thanks Marty, I’ll give it a try again over the weekend.
When I roll back to 2.1.6 the unexpected error goes away.
-
Hi Marty, I tried again…
a) The initial error still comes up
b) I can then wait forever, but the Files tab still displays nothing.
I looked at the log file but I can’t see anything obvious.
(apache2 log)However, I kept a copy of it and I would be happy to send it to you if you let me know how I can do that (it’s too big to post here)
Thank you.
-
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.
-
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.
-
yep… already it was.
Happy to send you the log files by email if you like.
-
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. -
Hi Marty,
I will try the process again today and report back.
And thank you very much for your help.
-
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.
-
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
toNORMAL
.++umgfoin.
-
not working for me though. Unless something has changed in the code from 3 days ago.
-
@mcostan Keep an eye on
https://jira.kopano.io/browse/KFP-412Should work way faster after this fix.
-
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.