Содержание
- Issue results are valid but processing is incomplete
- Wikibear
- UFHH01
- Wikibear
- Resolved Problem php-fpm (70007)The timeout specified has expired: AH01075: Er
- sebgonzes
- UFHH01
- sebgonzes
- sebgonzes
- IgorG
- sebgonzes
- Trindex
- sebgonzes
- xernus
- Kingsley
- redcat
- sebgonzes
- lvalics
- sebgonzes
- sebgonzes
- Paddy
- Jonathan H
- Kingsley
- Balanca
- AaronMcH
- PHP-FPM- Error dispatching request to
- James.Simpson
- cPanelMichael
- James.Simpson
- Anoop P Alias
- James.Simpson
- Anoop P Alias
- cPanelMichael
- James.Simpson
- cPanelMichael
- James.Simpson
- cPanelMichael
- Issue (70007)The timeout specified has expired: AH01075: Error dispatching request to :, referer:
- yassi
- Attachments
- IgorG
- yassi
- Bitpalast
- yassi
- Bitpalast
- yassi
- Bitpalast
Issue results are valid but processing is incomplete
Wikibear
Regular Pleskian
I get this on my Ubuntu Webserver from apache this error:
(70008)Partial results are valid but processing is incomplete: AH01075: Error dispatching request to : (reading input brigade)
Any one now to fix this? I think that this maybe has todo with a bad request between php_fpm and mysql server.
UFHH01
Guest
even that the community really likes to help people with issues/errors/problems, you still have to provide essential informations , so that people willing to help you have some facts to investigate:
In YOUR case, you have to provide the following informations:
- YOUR current used Plesk version ( incl. #MU )
- YOUR current used operating system
Wikibear
Regular Pleskian
Sure you are right! Here more information about my system:
Product version: Plesk Onyx 17.0.17 Update #24
Update date: 2017/04/29 19:51
Build date: 2017/03/22 17:00
OS version: Ubuntu 16.04
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2
3. PHP 7.1.4 FPM -> Special Version by Plesk
4.
-rw——- 1 root www-data 375 Apr 29 19:56 httpd.conf
-rw——- 1 root www-data 375 Apr 29 19:56 httpd.conf.bak
-rw——- 1 root www-data 4334 Apr 29 19:56 httpd_ip_default.conf
-rw——- 1 root www-data 4113 Apr 29 19:56 httpd_ip_default.conf.bak
lrwxrwxrwx 1 root root 10 Apr 29 19:56 last_httpd.conf -> httpd.conf
lrwxrwxrwx 1 root root 21 Apr 29 19:56 last_ip_default.conf -> httpd_ip_default.conf
lrwxrwxrwx 1 root root 10 Feb 20 08:14 last_nginx.conf -> nginx.conf
-rw——- 1 root nginx 149 Feb 20 08:14 nginx.conf
-rw——- 1 root nginx 149 Feb 20 08:14 nginx.conf.bak
-rw——- 1 root nginx 2004 Feb 20 08:14 nginx_ip_default.conf
-rw——- 1 root nginx 2004 Feb 20 08:14 nginx_ip_default.conf.bak
-rw-r—r— 1 root root 2 Apr 29 06:25 stat_ttl.conf
-rw-r—r— 1 root root 1 Feb 16 17:51 vhost.conf
-rw-r—r— 1 root root 1 Feb 16 17:51 vhost_ssl.conf
Or you want all files?! For security reasons i feel bad to give my files out to public.
5. No CMS all content on this webspace is developed by myself.
Источник
Resolved Problem php-fpm (70007)The timeout specified has expired: AH01075: Er
sebgonzes
Silver Pleskian
I active 200 domains on one server with php-fpm 5.6, but have several problem :
[Mon Oct 19 17:53:31.969289 2015] [proxy_fcgi:error] [pid 10770:tid 140599495710464] (70007)The timeout specified has expired: [client xx.xx.xx.xx:54335] AH01075: Error dispatching request to :
[Mon Oct 19 17:54:19.939367 2015] [proxy_fcgi:error] [pid 11050:tid 140599462139648] (70007)The timeout specified has expired: [client xx.xx.xx.xx:54542] AH01075: Error dispatching request to :
It seem related to an timeout problem but don’t know for now, how to solve it.
UFHH01
Guest
the default value «Timeout 60» ( 60 seconds ) in your apache — webserver — configuration could be raised at «apache2.conf» or «httpd.conf» ( depending to your system ). Consider to raise it to 180 or 300 seconds.
sebgonzes
Silver Pleskian
I have these with «time» variable :
/etc/httpd/conf.d/fcgid.conf: FcgidIdleTimeout 40
/etc/httpd/conf.d/fcgid.conf: FcgidProcessLifeTime 30
/etc/httpd/conf.d/fcgid.conf: FcgidConnectTimeout 30
/etc/httpd/conf.d/fcgid.conf: FcgidIOTimeout 150
/etc/httpd/conf.d/httpd-includes.conf roxyTimeout 1800 (this one is an test to see if problem solve, but not solve nothing)
I use apache 2.4.6.
sebgonzes
Silver Pleskian
No one have similar problem? we solve it changing all domain from php-fpm to fastcgi, but it’s not seem the best solution.
We found similar problem in other system :
— https://forum.directadmin.com/showthread.php?t=50172
but solution not work for us.
IgorG
Forums Analyst
sebgonzes
Silver Pleskian
Trindex
New Pleskian
sebgonzes
Silver Pleskian
An update of this item. I still have no solution for this problem, I have put all our hosting with fastcgi, but when I test an wordpress website :
— with php 5.6 on fastcgi : 7.7 seg (very bad result)
— with php 5.6 on php-fpm : 2.2s (better result)
— with php 7 on php-fpm : 0.86s (acceptable result)
The problem is that, it’s ok with few website with this php mode, but if I put all 300 domains of server, I will reproduce the problem. Noone have an solution for this error??
xernus
New Pleskian
Kingsley
Silver Pleskian
redcat
New Pleskian
sebgonzes
Silver Pleskian
I never obtain an solution to this problem, in our case that is a litte diferent as your case (webhosting server), only have problem if a large number of domain have php-fpm, if a few number have this version, it’s works.
lvalics
Silver Pleskian
sebgonzes
Silver Pleskian
sebgonzes
Silver Pleskian
Paddy
New Pleskian
I had this error when I copied a site from a different server. My site was still trying to connect to a mysql database on the old server and the connection was blocked. Once I corrected the connection string, all was fine.
Hope this helps someone.
Jonathan H
New Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
Kingsley
Silver Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
Balanca
New Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
AaronMcH
New Pleskian
While I hate to resurrect an old thread, I didn’t see a clear answer here and this thread is still among the first Google results for this issue.
For those using PHP-FPM, there are two different timeouts that are configured within Apache. There is the plain «TimeOut» setting, and also the «ProxyTimeout» setting, mentioned by others. In order to avoid this error, both Apache and the proxy call to PHP-FPM need to keep the connection going for the required amount of time. The default value for TimeOut is 60, and the default value for ProxyTimeout is to match the TimeOut value.
So for example, if you wanted to double the timeout to 2 minutes, you could throw this into your httpd.conf (and then restart Apache):
TimeOut 120
ProxyTimeout 120
Just bear in mind that changing this means you’re willing to keep a request going for up to that long, so make sure you have the resources for it!
Thanks for the info, any idea if this can go in the «Additional Apache directives» per domain in Plesk, or does it have to be place in the global config?
In our case this issue doesn’t seem to be consistent, it happened earlier today but only for a few hours and only on one domain, then soon after everything went back to normal, but it seems to be an intermittent issue.
Источник
PHP-FPM- Error dispatching request to
James.Simpson
Member
I am trying everything I can think of to resolve these issues that i keep getting in the error_log
I see these all the time:
I have had a look at all the timeouts and they are all the same (php timeout, apache timeout, all set to 300s)
I’m not sure where to start with this error.
cPanelMichael
Administrator
I recommend searching the PHP-FPM error logs (/opt/cpanel/ea-php$$/root/usr/var/log/php-fpm/error.log) for any domain name’s reaching the max_children limit. You’d replace ea-php$$ with each specific version of PHP (e.g. ea-php70) that PHP-FPM is utilized with on your system. The offending entries will look like this:
If you find specific domain names are reaching the limit, you can increase the max_children value for them using the «Pool Options» feature in «WHM >> MultiPHP Manager».
James.Simpson
Member
I have checked in that file, and there are no errors being displayed at all, just the start up features.
I currently have:
PHP-FPM:
max-children: 100
Process Idle Timeout: 90
Max Requests: 1000
Apache:
Start Servers: 15
Min Spare: 20
Max Spare: 35
Server Limit: 300
Max Request Workers: 200
Keepalive: Off
Keepalive-timeout: 7
Max Keepalive requests: 150
Timeout: 300
Pre VirtualHost Include
Anoop P Alias
Well-Known Member
James.Simpson
Member
Anoop P Alias
Well-Known Member
cPanelMichael
Administrator
You can try increasing both of these values from «300» to a higher number such as «500» to see if the issue continues. Ensure to monitor Apache’s performance after making the change as sometimes a timeout is a good thing since it can prevent Apache from overloading the server.
James.Simpson
Member
I’m not sure if that may be the issue or not — it seems like a sometimes a process may get stuck, as it will wait till 300+ seconds sometimes for a user when they are just trying to load a page, as if somehthing is hogging all the connections? Even though other users can fly through the website without any issues.
I’m struggling to find out what it is at all, as a script shouldnt be running for more than 300 seconds to view a single page?
cPanelMichael
Administrator
You can open a support ticket if you’d like us to take a closer look to rule out any issues with cPanel & WHM itself or it’s integration of PHP-FPM. You can post the ticket number here and we will link this forums thread to the ticket.
James.Simpson
Member
I think it may be server configuration somehwere to be fair.
So what looks like is happening, sometimes when clicking on a link, it will load instantly as it should, but then randomly every now and then, it will just load the page until maximum execution time is hit, and then finally load the page.
So for example just now, i’ve been browsing the website fine, and then i clicked on one link, and it took 290 seconds to load the page. Now after its loaded all the rest of the site is fine again. Not sure what can cause this so randomly — server load isnt massive, and I can see idle processes in apache waiting for a connection. Mysql isnt processing anything either.
cPanelMichael
Administrator
We’d need access to the affected system to reproduce this behavior and determine if there are any obvious reasons for the increased page load time. Are you able to open a support ticket so we can take a closer look?
Источник
Issue (70007)The timeout specified has expired: AH01075: Error dispatching request to :, referer:
yassi
New Pleskian
In the error log I get the following:
(70007)The timeout specified has expired: AH01075: Error dispatching request to :, referer: http://domaine.com/auth/fen Erreur Apache
Already i see this link but nothing always i have this issue,how can i resolved that?
In my config i set application php servi by Apache
thanks in advance
Attachments
IgorG
Forums Analyst
yassi
New Pleskian
thanks for your answer already tested that but always i have the same issue ,so i don’t know why i have one time error apache and other time nginx
FYI I have plesk 12.5.30 linux ubutu 14.04.5 ,version php 5.5.9 ,exécute PHP:Application PHP servi by Apache.
Thanks in advance
Bitpalast
Plesk addicted!
The Nginx error is caused by an unresponsive Apache. Nginx forwards the incoming PHP request to Apache and waits on an answer. Apache does not respond to the request, for that reason Nginx is running into a timeout.
The reason for that Apache is not responding can be too low FPM configuration values as described in the above mentioned KB article, but it can also simply be script errors. If script execution is not finished and no error output (no HTML header) is returned, e.g. if error output is turned off and no page is generated, because script execution failed, the same timeout situation occurs. Normally, this is the main cause for the error.
yassi
New Pleskian
thanks for your answer ,so how can i just use nginx only without apache so i can display my configuration here if you want.
Thanks in advance
Bitpalast
Plesk addicted!
yassi
New Pleskian
Hi, I Have just this in plesk so here screenshot for the plesk configuration 2018 01 12 14 52 58 Param tres PHP pour webonline2018 com Plesk 12 5 30 ;
how can Disable Proxy Mode for Nginx in the Apache/Nginx configuration.
thanks in advance
Bitpalast
Plesk addicted!
This is not the correct page to disable proxy mode. On the PHP page you can only change to «PHP-FPM by Nginx only». Additionally you need to turn of Proxy mode of the Nginx web server.
This is the page you are looking for:
Then disable Proxy mode:
However, I suppose you think that you can solve your issue by bypassing Apache. Actually, the issue will persist, because your script still will not work properly.
Источник
-
#1
Hi All,
I am trying everything I can think of to resolve these issues that i keep getting in the error_log
I see these all the time:
Code:
[Mon Jul 23 14:21:49.265694 2018] [proxy_fcgi:error] [pid 10118:tid 140174646310656] (70007)The timeout specified has expired: [client xxx.xxx.29.224:40002] AH01075: Error dispatching request to : (polling)
[Mon Jul 23 14:21:56.362524 2018] [proxy_fcgi:error] [pid 10202:tid 140174739064576] (70007)The timeout specified has expired: [client xxx.xxx.29.224:38942] AH01075: Error dispatching request to : (polling)
[Mon Jul 23 14:22:28.515437 2018] [proxy_fcgi:error] [pid 10118:tid 140174551901952] (70014)End of file found: [client xxx.xxx.29.224:56734] AH01075: Error dispatching request to : (reading input brigade)
[Mon Jul 23 14:22:39.519789 2018] [proxy_fcgi:error] [pid 10118:tid 140174509942528] (70014)End of file found: [client xxx.xxx.29.224:56758] AH01075: Error dispatching request to : (reading input brigade)
[Mon Jul 23 14:22:41.134359 2018] [proxy_fcgi:error] [pid 10174:tid 140174614841088] (70014)End of file found: [client xxx.xxx.29.224:56766] AH01075: Error dispatching request to : (reading input brigade)
[Mon Jul 23 14:22:43.621452 2018] [proxy_fcgi:error] [pid 10202:tid 140174728574720] (70014)End of file found: [client xxx.xxx.29.224:56772] AH01075: Error dispatching request to : (reading input brigade)
[Mon Jul 23 14:23:04.080491 2018] [proxy_fcgi:error] [pid 10263:tid 140174530922240] (70014)End of file found: [client xxx.xxx.29.224:56792] AH01075: Error dispatching request to : (reading input brigade)
I have had a look at all the timeouts and they are all the same (php timeout, apache timeout, all set to 300s)
I’m not sure where to start with this error.
-
#2
Hello James,
I recommend searching the PHP-FPM error logs (/opt/cpanel/ea-php$$/root/usr/var/log/php-fpm/error.log) for any domain name’s reaching the max_children limit. You’d replace ea-php$$ with each specific version of PHP (e.g. ea-php70) that PHP-FPM is utilized with on your system. The offending entries will look like this:
Code:
ERROR: unable to read what child say: Bad file descriptor (9)
NOTICE: [pool domain_tld] child 1234 exited with code 0 after 25.12345 seconds from start
If you find specific domain names are reaching the limit, you can increase the max_children value for them using the «Pool Options» feature in «WHM >> MultiPHP Manager».
Thank you.
-
#3
Hi Michael,
I have checked in that file, and there are no errors being displayed at all, just the start up features.
I currently have:
PHP-FPM:
max-children: 100
Process Idle Timeout: 90
Max Requests: 1000
Apache:
Start Servers: 15
Min Spare: 20
Max Spare: 35
Server Limit: 300
Max Request Workers: 200
Keepalive: Off
Keepalive-timeout: 7
Max Keepalive requests: 150
Timeout: 300
Pre VirtualHost Include
Code:
<IfModule proxy_fcgi_module>
timeout 300
ProxyTimeout 300
</IfModule>
##Apache Event Default Settings (overrides main httpd.conf)
KeepAlive On
KeepAliveTimeout 2
MaxKeepAliveRequests 75
<IfModule event.c>
ThreadsPerChild 25
ServerLimit 16
MaxRequestWorkers 400
StartServers 6
MinSpareThreads 150
MaxSpareThreads 400
MaxRequestsPerChild 0
</IfModule>
<IfModule mod_fcgid.c>
FcgidMaxRequestsPerProcess 10000
FcgidMinProcessesPerClass 0
FcgidMaxProcessesPerClass 120
FcgidMaxProcesses 2000
FcgidProcessLifeTime 300
FcgidIOTimeout 300
FcgidIdleTimeout 60
FcgidIdleScanInterval 60
FcgidBusyTimeout 3600
FcgidConnectTimeout 10
FcgidBusyScanInterval 100
FcgidErrorScanInterval 3
FcgidZombieScanInterval 3
FcgidOutputBufferSize 0
FcgidZombieScanInterval 5
FcgidInitialEnv PHP_FCGI_MAX_REQUESTS 10000
FcgidMaxRequestLen 20468982
</IfModule>
It seems if processes seem to get stuck and just sits there loading until it times out.
-
#4
Please try changing the Apache httpd MPM from event to prefork. see if that helps
-
#5
Apache is currently running on mod_mpm_worker
-
#6
Do you get error in worker as well?. If yes switch to prefork
-
#7
<IfModule proxy_fcgi_module>
timeout 300
ProxyTimeout 300
</IfModule>
Hello James,
You can try increasing both of these values from «300» to a higher number such as «500» to see if the issue continues. Ensure to monitor Apache’s performance after making the change as sometimes a timeout is a good thing since it can prevent Apache from overloading the server.
Thank you.
-
#8
Hi Michael,
I’m not sure if that may be the issue or not — it seems like a sometimes a process may get stuck, as it will wait till 300+ seconds sometimes for a user when they are just trying to load a page, as if somehthing is hogging all the connections? Even though other users can fly through the website without any issues.
I’m struggling to find out what it is at all, as a script shouldnt be running for more than 300 seconds to view a single page?
-
#9
Hello James,
You can open a support ticket if you’d like us to take a closer look to rule out any issues with cPanel & WHM itself or it’s integration of PHP-FPM. You can post the ticket number here and we will link this forums thread to the ticket.
Thank you.
-
#10
I think it may be server configuration somehwere to be fair.
So what looks like is happening, sometimes when clicking on a link, it will load instantly as it should, but then randomly every now and then, it will just load the page until maximum execution time is hit, and then finally load the page.
So for example just now, i’ve been browsing the website fine, and then i clicked on one link, and it took 290 seconds to load the page. Now after its loaded all the rest of the site is fine again. Not sure what can cause this so randomly — server load isnt massive, and I can see idle processes in apache waiting for a connection. Mysql isnt processing anything either….
-
#11
So for example just now, i’ve been browsing the website fine, and then i clicked on one link, and it took 290 seconds to load the page. Now after its loaded all the rest of the site is fine again. Not sure what can cause this so randomly — server load isnt massive, and I can see idle processes in apache waiting for a connection. Mysql isnt processing anything either….
Hello James,
We’d need access to the affected system to reproduce this behavior and determine if there are any obvious reasons for the increased page load time. Are you able to open a support ticket so we can take a closer look?
Thank you.
-
#1
Hi,
I found many of this error message in error_log,
(70007)The timeout specified has expired: AH01075: Error dispatching request to : (reading input brigade), referer: https://…
system: Plesk Obsidian 18.0.26, Ubuntu 18.04
we use WordPress, Plesk-php-74 with php-fpm, mpm mode: event, Apache with disabled proxy mode.
the server do not return any error page while this error is raised
Thanks for advance.
-
#3
Thanks Igor for your reply
i added these directives to http and https to the subdomain https://subdomain.example.com
FcgidIdleTimeout 600
FcgidProcessLifeTime 600
FcgidConnectTimeout 600
FcgidIOTimeout 600
Timeout 600
ProxyTimeout 600
and restart apache2 but it does not resolve this issue, then i increase all Timeouts value to 1200, and i still got that error!
-
1.png
435.7 KB
· Views: 56 -
2.png
262.1 KB
· Views: 55
-
#4
Then I suspect that your code is trying to load something that is not reachable.
-
#5
i suspect a buggy plugin, thank you Arashi for you reply.
-
#6
i got a similar error.
Error dispatching request to : (polling)
We recently changed our Apache from worker mpm to event mpm and changed from mod_php to php-fpm. It seems running normally. However, we notice that there are a number of error messages in error_log- «AH01075: Error dispatching request to : (reading input brigade)» almost every day. According to online information, the cause should be the time for uploading large file exceeds the timeout.
We have tried to follow the workaround as the below and tried a number of adjustments on timeout values.
https://serverfault.com/questions/450628/apache-2-4-php-fpm-proxypassmatch
#Add the below in httpd-vhosts.conf, globally increase Timeout and ProxyTimeout value to 900
#Add the RequestReadTimeout directive
Timeout=900
ProxyTimeout=900
<IfModule reqtimeout_module>
RequestReadTimeout header=20-600,MinRate=500 body=20-60,MinRate=500
</IfModule>
#edit httpd.conf and change the timeout to 900
<Proxy «unix:/var/run/php-fpm.sock|fcgi://localhost»>
ProxySet connectiontimeout=5 timeout=900
</Proxy
Unfortunately, the error messages still occur. Please advise how to solve this problem.
Thank you very much.
I enabled debuging on the Server. Here is one of the famous errors:
Error downloading https://kumori.fosuta.org/remote.php/webdav/Music/Cat Stevens/The Very Best of Cat Stevens/16. Another Saturday Night.m4a-chunking-3152591687-4-2 - server replied: Bad Request (expected filesize 5242880 got 0)
And here is everything from the Server:
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Write lock requested for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:00+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"PASS: Write lock succeeded on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:00+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Incrementing lock type 2 count for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:00+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_antivirus","message":"Response :: stream: OKn","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Read lock requested for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"PASS: Acquired read lock for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Incrementing lock type 1 count for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Write lock requested for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"PASS: Write lock succeeded on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Incrementing lock type 2 count for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Releasing locks on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Released lock handle Resource id #52 on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"FREE: Released locks on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2","level":0,"time":"2015-09-30T20:58:38+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Read lock requested for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"PASS: Acquired read lock for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Incrementing lock type 1 count for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Incrementing lock type 2 count for /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Destroying locks on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Releasing locks on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"INFO: Released lock handle Resource id #48 on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"files_locking","message":"FREE: Released locks on /srv/owncloud-data/toni/cache/16. Another Saturday Night.m4a-chunking-3152591687-2.YymOFvO9fm4zMWSY.part","level":0,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
{"reqId":"SY9QhHWasR7+9ZiQGD9L","remoteAddr":"2a01:1e8:e100:8204:2e41:38ff:fe8c:5542","app":"webdav","message":"Exception: {"Message":"HTTP\/1.1 400 expected filesize 5242880 got 0","Code":0,"Trace":"#0 \/var\/www\/owncloud\/lib\/private\/connector\/sabre\/file.php(100): OC\\Connector\\Sabre\\File->createFileChunked(Resource id #37)\n#1 \/var\/www\/owncloud\/lib\/private\/connector\/sabre\/directory.php(113): OC\\Connector\\Sabre\\File->put(Resource id #37)\n#2 \/var\/www\/owncloud\/3rdparty\/sabre\/dav\/lib\/DAV\/Server.php(1053): OC\\Connector\\Sabre\\Directory->createFile('16. Another Sat...', Resource id #37)\n#3 \/var\/www\/owncloud\/3rdparty\/sabre\/dav\/lib\/DAV\/CorePlugin.php(513): Sabre\\DAV\\Server->createFile('Music\/Cat Steve...', Resource id #37, NULL)\n#4 [internal function]: Sabre\\DAV\\CorePlugin->httpPut(Object(Sabre\\HTTP\\Request), Object(Sabre\\HTTP\\Response))\n#5 \/var\/www\/owncloud\/3rdparty\/sabre\/event\/lib\/EventEmitterTrait.php(105): call_user_func_array(Array, Array)\n#6 \/var\/www\/owncloud\/3rdparty\/sabre\/dav\/lib\/DAV\/Server.php(469): Sabre\\Event\\EventEmitter->emit('method:PUT', Array)\n#7 \/var\/www\/owncloud\/3rdparty\/sabre\/dav\/lib\/DAV\/Server.php(254): Sabre\\DAV\\Server->invokeMethod(Object(Sabre\\HTTP\\Request), Object(Sabre\\HTTP\\Response))\n#8 \/var\/www\/owncloud\/apps\/files\/appinfo\/remote.php(83): Sabre\\DAV\\Server->exec()\n#9 \/var\/www\/owncloud\/remote.php(132): require_once('\/var\/www\/ownclo...')\n#10 {main}","File":"\/var\/www\/owncloud\/lib\/private\/connector\/sabre\/file.php","Line":346}","level":4,"time":"2015-09-30T20:58:39+02:00","method":"PUT","url":"/remote.php/webdav/Music/Cat%20Stevens/The%20Very%20Best%20of%20Cat%20Stevens/16.%20Another%20Saturday%20Night.m4a-chunking-3152591687-4-2"}
What I think, can clearly be seen is that the time between the first filelock 20:58:00
and the fail 20:58:39
is about the time a 5MB files takes with a 2.5Mbit Upstream. I took in consideration that a second file got transferred. So what I stated before seems to hold true, the chunk gets transferred but «vanishes». I think that this is not a client issue, rather a core «bug».