<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>after futher testing i now have the application performing well for my usecase. a few things to note:</div>
<div> </div>
<div>- NFS to store incoming and dropoffs folder</div>
<div>- mysql db</div>
<div>- large dropoffs >100GB, with large files ~60GB. this is likely pushing my system</div>
<div>- server is running behind haproxy loadbalancer</div>
<div>
<div> </div>
<div>firstly to answer your questions:</div>
<div>- virus scan was using "clamdscan --fdpass"</div>
<div>- SMTPdebug set to FALSE</div>
<div>- no checksumming</div>
<div> </div>
<div>once i had removed some issues:</div>
<div> </div>
<div>- increased server timeout in haproxy to very high</div>
<div>- increase number of CPUs for VM</div>
<div>- modified php.ini settings such as timeouts, max_upload, max_post etc</div>
<div> </div>
<div>the issue seemed to be due to the wait copying from incoming folder (local) to dropoffs (NFS). so i wondered why is the application waiting ? further tests led me to this: after i changed the mountpoints as follows</div>
<div>- NFS mounted to /var/zendto/incoming</div>
<div>- 'dropboxDirectory' => NSSDROPBOX_DATA_DIR."incoming/"</div>
<div> </div>
<div>thus the incoming and dropoffs are both on the same folder on NFS. and now it works perfectly! the data is written to NFS while it is being uploaded (which is the bottleneck anyway), then the move to "dropboxDirectory" is now very quick/instant as it is already on NFS.</div>
<div> </div>
<div>perhaps this is of use to someone else in future.</div>
<div> </div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Sent:</b> Monday, June 25, 2018 at 5:36 PM<br/>
<b>From:</b> "Jules Field" <Jules@Zend.To><br/>
<b>To:</b> "ZendTo Users" <zendto@zend.to><br/>
<b>Cc:</b> "Mr filesender" <jamesmm1@gmx.com><br/>
<b>Subject:</b> Re: [ZendTo] Error on File Upload</div>
<div>James,<br/>
<br/>
Please can you confirm that<br/>
a) as a virus scanner you are using "clamdscan" with at least the<br/>
"--fdpass" option, and *not* "clamscan"?<br/>
b) you have "SMTPdebug" set to FALSE.<br/>
<br/>
Also, try it with no checksumming or anything like that. And make sure<br/>
your /var/zendto/dropoffs is really on local storage and in the same<br/>
filesystem/partition/volume as /var/zendto/incoming.<br/>
<br/>
If you run "top" on the server while the upload of a huge file is<br/>
happening, what is occupying CPU time after the browser has sent the<br/>
whole file, but before the browser generates any error or returns the<br/>
success page?<br/>
And how long is that delay?<br/>
<br/>
Cheers,<br/>
Jules.<br/>
<br/>
On 25/06/2018 13:17, Mr filesender via ZendTo wrote:<br/>
> i would like to add more detail to this issue. After i have tested further, i am still consistently reproducing it. a few observations:<br/>
><br/>
> it is present when connecting directly to VM (although file size is larger to reproduce it. i notice 4-6GB). no firewall or loadbalancers in between client and zendto VM. the full file is sent to and present on the incoming folder. the problem occurs after the full file is transmitted. its the client browser that notices a problem, the server continues with the drop and after a time it is there and email is sent as expected<br/>
><br/>
> so i wonder, maybe it is a design issue with how the browser is waiting for a reply? i have solved the problem by adding more CPUs to the zendto VM (but perhaps will return with larger file/drop )<br/>
><br/>
> thank you<br/>
><br/>
><br/>
><br/>
> Sent: Wednesday, June 20, 2018 at 4:13 PM<br/>
> From: "Jules Field" <Jules@Zend.To><br/>
> To: "ZendTo Users" <zendto@zend.to><br/>
> Cc: "Mr filesender" <jamesmm1@gmx.com><br/>
> Subject: Re: [ZendTo] Error on File Upload<br/>
> That PHP output looks fine.<br/>
><br/>
> I will have to leave it to you to configure your load balancer.<br/>
><br/>
> Cheers,<br/>
> Jules.<br/>
><br/>
> On 20/06/2018 2:01 pm, Mr filesender via ZendTo wrote:<br/>
>> ah ok. i am running it behind haproxy/loadbalancer. i have tested directly to the zendto server and it works perfectly.<br/>
>><br/>
>> i will modify my loadbalancer timeouts to very high. in any case, i notice that when this error occurs, it is just the browser that is affected. the dropoff is still being processed on the server and eventually, after data has been moved to dropoff folder, is ready and email is sent<br/>
>><br/>
>> here are the details you asked for:<br/>
>><br/>
>> running over https. php -v:<br/>
>><br/>
>> PHP 7.2.6-1+0~20180611145758.22+stretch~1.gbpe20e8b (cli) (built: Jun 11 2018 14:58:01) ( NTS )<br/>
>> Copyright (c) 1997-2018 The PHP Group<br/>
>> Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies<br/>
>> with Zend OPcache v7.2.6-1+0~20180611145758.22+stretch~1.gbpe20e8b, Copyright (c) 1999-2018, by Zend Technologies<br/>
>><br/>
>> php -i | grep sodium<br/>
>><br/>
>> sodium<br/>
>> sodium support => enabled<br/>
>> libsodium headers version => 1.0.16<br/>
>> libsodium library version => 1.0.16<br/>
>><br/>
>> tjhank you for the prompt advice :)<br/>
>><br/>
>><br/>
>><br/>
>> Sent: Wednesday, June 20, 2018 at 10:18 AM<br/>
>> From: Jules <Jules@Zend.To><br/>
>> To: "ZendTo Users" <zendto@zend.to><br/>
>> Cc: "Mr filesender" <jamesmm1@gmx.com><br/>
>> Subject: Re: [ZendTo] Error on File Upload<br/>
>><br/>
>> Do you happen to have anything on your network which does any sort of content-scanning (e.g. virus scanning) of your network traffic?<br/>
>> A lot of modern firewalls have this sort of functionality built in.<br/>
>> In order to content-scan a file being sent over the network, it will need a complete copy of the file, and will have restrictions on the max file size it can cope with.<br/>
>><br/>
>> And are you using ZendTo over http or https?<br/>
>><br/>
>> Is the PC you are testing with running any anti-virus scanner that looks at network traffic?<br/>
>><br/>
>> Also, please run these 2 commands on your ZendTo server:<br/>
>> php -v<br/>
>> php -i | grep sodium<br/>
>> and tell us the output from each one.<br/>
>><br/>
>> Cheers,<br/>
>> Jules.<br/>
>><br/>
>> On 20/06/2018 8:54 am, Mr filesender via ZendTo wrote:<br/>
>><br/>
>> i am also experiencing this issue and it is blocking usage of the application. I was testing with v5.0.3 stable and noticed it.<br/>
>><br/>
>> now i reinstalled a completely fresh instance of beta 5.0.9 on debian 9 with php7 but it is still there. I use default config settings.<br/>
>><br/>
>> i notice it happens with a file ~>1GB . i get the exact same response from the system as kevin below "sorry i failed to dropoff your files.."<br/>
>><br/>
>> after i notice that the dropoff exists in database but with 0mb size. in dropoff folder, the data is there but only about half of the filesize.<br/>
>><br/>
>> i have tryed with mysql, sqlite3. i have tried turning clam off and on. nothing works.<br/>
>><br/>
>> thank you<br/>
>><br/>
>><br/>
>> On 01/06/2018 11:48, O'Connor, Kevin wrote:<br/>
>>> Jules,>> Disabling the clamdscan made no difference.>> I've done the upgrade to 5.03 and updated the config files. There was no zendto.conf.rpmnew I assume because there were no changes.>> The issue still exists. I can view and download the uploaded file from the outbox, using the resend mail option produces a blank page.>> This is not a production system, we still have an old 4.28-2 system running, so I'm thinking a complete rebuild from the ground up might be the best bet.>> Regards>> Kevin>>> -----Original Message----->> From: Jules Field [mailto:Jules at Zend.To[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]]>> Sent: 01 June 2018 10:31>> To: O'Connor, Kevin <KevinO'Connor at merseyfire.gov.uk[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]]>; ZendTo Users>> <zendto at zend.to[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]]>>> Subject: Re: [ZendTo] Error on File Upload>>>> Kevin,>>>> To rule out ClamAV permissions issues, edit preferences.php and set>> 'clamdscan' => 'DISABLED',>> Make sure you keep the old value, just comment it out.>>>> Does that make any difference?>>>> I would also advise a quick "yum update" to the latest release of 5.03.>> According to my ChangeLog, the changes from 5.01-5 and 5.03-1 are all>> security improvements or bug fixes.>>>> Cheers,>> Jules.>>>> On 01/06/2018 09:35, O'Connor, Kevin wrote:>>> Jules,>>>>>> Thanks for the quick response. Please see my responses below.>>>>>>> -----Original Message----->>>> From: Jules Field [mailto:Jules at Zend.To[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]]]>>>> Sent: 01 June 2018 09:23>>>> To: ZendTo Users <zendto at zend.to[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]]>>>>> Cc: O'Connor, Kevin <KevinO'Connor at merseyfire.gov.uk[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]]>>>>> Subject: Re: [ZendTo] Error on File Upload>>>>>>>> Kevin,>>>>>>>> Does anything show up in /var/zendto/zendto.log when this happens?>>> No there is nothing logged. All that the file contains as the logins>>> to the system>>>>>>>>>> How long are the uploads taking before this error appears?>>> It occurs even with small files that take seconds to upload.>>>>>>> It is caused by the PHP session failing/disappearing/timing-out>>>> during the upload process. It means the server received nothing of your>> files.>>> The files are present and as far as I can determine have completed upload.>>>>>>> The comment about files/directories is because that is one thing that>>>> will cause it, as in some browsers it is still impossible for me to>>>> check if what you've added to the list of files is a dir or a real file.>>>>>>>> Cheers,>>>> Jules.>>>>>>>> On 01/06/2018 08:52, O'Connor, Kevin via ZendTo wrote:>>>>> Morning,>>>>>>>>>> I've got a 5.01 clean install running on CentOS 7 with AD authentication.>>>>>>>>>> On completion of the file upload an error message pops up "Sorry I>>>>> failed to>>>> dropoff your files! Note that you cannot dropoff directories, only>>>> files" The file is successfully uploaded but this error seems to>>>> prevent the email being sent.>>>>> I noticed someone posted the same fault back in March but I can find>>>>> no>>>> response or resolution posted so was hoping someone could point me in>>>> the direction of a fix or a setting I might have got wrong.>>>>> TIA>>>>>>>>>> Kevin> This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.> If you have received this e-mail in error please notify the originator of the message.>> Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Merseyside Fire & Rescue Service, (MFRS).>> Incoming and outgoing emails may be monitored in line with current legislation.>> Steps have been taken to ensure that this email and attachments are free from any virus. In keeping with good computing practice the recipient should ensure they are actually virus free.>> <a href="http://www.merseyfire.gov.uk/" target="_blank">http://www.merseyfire.gov.uk/</a>[<a href="http://www.merseyfire.gov.uk/" target="_blank">http://www.merseyfire.gov.uk/</a>][<a href="http://www.merseyfire.gov.uk/" target="_blank">http://www.merseyfire.gov.uk/</a>[<a href="http://www.merseyfire.gov.uk/" target="_blank">http://www.merseyfire.gov.uk/</a>]]><br/>
>> _______________________________________________<br/>
>> ZendTo mailing listZendTo@zend.to[mailto:ZendTo@zend.to]<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>[<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>]<br/>
>><br/>
>> Jules<br/>
>><br/>
> Jules<br/>
><br/>
> --<br/>
> Julian Field MEng CEng CITP MBCS MIEEE MACM<br/>
><br/>
> 'No more impressive warning can be given to those who would confine<br/>
> knowledge and rsearch to what is apparently useful, than the<br/>
> reflection that conic sections were studied for eighteen hundred<br/>
> years merely as an abstract science, without regard to any utility<br/>
> other than to satisfy the craving for knowledge on the part of<br/>
> mathematicians, and that then at the end of this long period of<br/>
> abstract study, they were found to be the necessary key with which<br/>
> to attain the knowledge of the most important laws of nature.'<br/>
> - Alfred North Whitehead<br/>
><br/>
> <a href="http://www.Zend.To" target="_blank">www.Zend.To</a>[<a href="http://www.Zend.To" target="_blank">http://www.Zend.To</a>]<br/>
> Twitter: @JulesFM<br/>
> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br/>
><br/>
><br/>
><br/>
> _______________________________________________<br/>
> ZendTo mailing list<br/>
> ZendTo@zend.to<br/>
> <a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a><br/>
<br/>
Jules<br/>
<br/>
--<br/>
Julian Field MEng CEng CITP MBCS MIEEE MACM<br/>
<br/>
'The owls are not what they appear.' - David Lynch (indirectly)<br/>
<br/>
<a href="http://www.Zend.To" target="_blank">www.Zend.To</a><br/>
Twitter: @JulesFM<br/>
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br/>
<br/>
</div>
</div>
</div>
</div>
</div></div></body></html>