When I use "Recursive add..." on a folder with a large number of files and subfolders WebFM works for a while and then spits out the "Server unreachable" error message. When I then go deeper to add the folders one by one WebFM seems to have added almost all of the when it spit out the error message. Could the processing be terminated because of some server setting when it reaches some time limit?

Comments

robmilne’s picture

robmilne CreditAttribution: robmilne commented

Possible. I'll haven't run tests doing insertions of very large numbers of files for some time.

gjk’s picture

gjk CreditAttribution: gjk commented
Priority: Normal » Minor

Thank you very much. Note that I went through all my folders I entered the files manually (that is, folder by folder) so this issue is not critical to me. I changed the priority to minor to reflect this, although you (or somebody else) could have a different opinion.

marlutin’s picture

marlutin CreditAttribution: marlutin commented
Priority: Minor » Normal

I have the same error msg "server unreachable". With no other information, and no javascript error (enabled javascript debug from settings)

Uploaded 82 files in a folder managed by webfm, then added recursively theses files to the db via webfm interface, and get this msg.

- file system is public in Drupal, path set by default as specified, prior use (for 2 test files was ok)
- webfm_files table seems ok (path is relative to settings, 84 files are present)
- webfm_attach is empty.

files are downloadable publicly (i've removed the .htaccess for testing) otherwise I have an error 500 (normal)

For me this is critical, as the module is yet not fonctional, so I changed the status of priority as normal.

what can I do to find out what is going wrong?

cgmonroe’s picture

cgmonroe CreditAttribution: cgmonroe commented

I suspect it might be a PhP timeout problem. The recursive add to db makes a single Ajax call to the Drupal to "walk the tree".

The "server is unreachable" error is a general error that is returned if the Ajax call does not return a HTTP 200 (success) code.

If the recursive action talks too long because there are a lot of files, then PHP's execution time limits may be kicking in and killing the thread.

Check the logs for timeouts or requests to /webfm_js with non-200 return codes.

You might just try changing the PhP timeout setting in the php.ini file. Generally, the defaults are on the low side for Drupal.

nhck’s picture

nhck CreditAttribution: nhck commented

marlutin, thank you for taking the time to report reporting. Have you had time to check your logfiles for clues?

Maybe we have to introduce the batch API on this issue.

nhck’s picture

nhck CreditAttribution: nhck commented
Status: Active » Closed (cannot reproduce)