Magento 2.2.3 Internal Server Error: Read timed out after 10 seconds
0
I have a magento 2.2.3 shop that is throwing me an internal server error every time I try to edit or create a new product. When I click save, it loads for about 10 seconds this shows internal server error. Try again later. I checked the system.log file and it shows the following error:
[2018-04-09 21:36:38] main.CRITICAL: Read timed out after 10 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/923d4f492fbf22029126adee53137102bd09deee49d3bdb1f83885e9ca3c4853/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
What would cause this issue and how can I fix it?
UPDATE:
I modified the file vendor/magento/module-cache-invalidate/Model/PurgeCache.php I changed the timeout to 90 seconds and I am now getting an error of timed out after 90 seconds. See below:
[2018-04-10 18:45:11] main.CRITICAL: Read timed out after 90 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:18] main.CRITICAL: A valid response status line was not found in the provided string {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:22] main.INFO: Broken reference: the 'product.reviews' element cannot be added as child to 'product_tabs', because the latter doesn't exist
magento2 php error zend-framework timeout
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
0
I have a magento 2.2.3 shop that is throwing me an internal server error every time I try to edit or create a new product. When I click save, it loads for about 10 seconds this shows internal server error. Try again later. I checked the system.log file and it shows the following error:
[2018-04-09 21:36:38] main.CRITICAL: Read timed out after 10 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/923d4f492fbf22029126adee53137102bd09deee49d3bdb1f83885e9ca3c4853/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
What would cause this issue and how can I fix it?
UPDATE:
I modified the file vendor/magento/module-cache-invalidate/Model/PurgeCache.php I changed the timeout to 90 seconds and I am now getting an error of timed out after 90 seconds. See below:
[2018-04-10 18:45:11] main.CRITICAL: Read timed out after 90 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:18] main.CRITICAL: A valid response status line was not found in the provided string {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:22] main.INFO: Broken reference: the 'product.reviews' element cannot be added as child to 'product_tabs', because the latter doesn't exist
magento2 php error zend-framework timeout
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Seem that you were using the curl to work with API. Your issue relates to the timeout issue. Try to increase the timeout for your curl. This will solve your timeout issue. The default timeout PHP is 13 seconds.
– Khoa TruongDinh
Apr 10 '18 at 1:57
I'm not using the API. The site is running varnish cache, so I'm thinking somehow that is involved.
– Kazpilot25
Apr 10 '18 at 15:35
Possibly a Zend timeout issue? I changed the value in the Client.php file for timeout from 10 to 90 and saw no difference.
– Kazpilot25
Apr 10 '18 at 16:35
add a comment |
0
0
0
I have a magento 2.2.3 shop that is throwing me an internal server error every time I try to edit or create a new product. When I click save, it loads for about 10 seconds this shows internal server error. Try again later. I checked the system.log file and it shows the following error:
[2018-04-09 21:36:38] main.CRITICAL: Read timed out after 10 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/923d4f492fbf22029126adee53137102bd09deee49d3bdb1f83885e9ca3c4853/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
What would cause this issue and how can I fix it?
UPDATE:
I modified the file vendor/magento/module-cache-invalidate/Model/PurgeCache.php I changed the timeout to 90 seconds and I am now getting an error of timed out after 90 seconds. See below:
[2018-04-10 18:45:11] main.CRITICAL: Read timed out after 90 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:18] main.CRITICAL: A valid response status line was not found in the provided string {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:22] main.INFO: Broken reference: the 'product.reviews' element cannot be added as child to 'product_tabs', because the latter doesn't exist
magento2 php error zend-framework timeout
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
I have a magento 2.2.3 shop that is throwing me an internal server error every time I try to edit or create a new product. When I click save, it loads for about 10 seconds this shows internal server error. Try again later. I checked the system.log file and it shows the following error:
[2018-04-09 21:36:38] main.CRITICAL: Read timed out after 10 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/923d4f492fbf22029126adee53137102bd09deee49d3bdb1f83885e9ca3c4853/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
What would cause this issue and how can I fix it?
UPDATE:
I modified the file vendor/magento/module-cache-invalidate/Model/PurgeCache.php I changed the timeout to 90 seconds and I am now getting an error of timed out after 90 seconds. See below:
[2018-04-10 18:45:11] main.CRITICAL: Read timed out after 90 seconds {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:18] main.CRITICAL: A valid response status line was not found in the provided string {"method":"POST","url":"https://custombuttons97.com/admin_cfytnh/catalog/product/save/id/5/type/simple/store/0/set/12/key/8937840148454054d5ff7ae2ff947a60b2b477567a535f0c1b649b69c06bdc23/back/edit","invalidateInfo":{"server":"[object] (Zend\Uri\Uri: http://127.0.0.1:6082/)","tagsPattern":"((^|,)cat_p_5(,|$))"}}
[2018-04-10 18:45:22] main.INFO: Broken reference: the 'product.reviews' element cannot be added as child to 'product_tabs', because the latter doesn't exist
magento2 php error zend-framework timeout
magento2 php error zend-framework timeout
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
edited Apr 10 '18 at 19:33
Kazpilot25
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
asked Apr 9 '18 at 22:12
Kazpilot25Kazpilot25
12
12
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Seem that you were using the curl to work with API. Your issue relates to the timeout issue. Try to increase the timeout for your curl. This will solve your timeout issue. The default timeout PHP is 13 seconds.
– Khoa TruongDinh
Apr 10 '18 at 1:57
I'm not using the API. The site is running varnish cache, so I'm thinking somehow that is involved.
– Kazpilot25
Apr 10 '18 at 15:35
Possibly a Zend timeout issue? I changed the value in the Client.php file for timeout from 10 to 90 and saw no difference.
– Kazpilot25
Apr 10 '18 at 16:35
add a comment |
Seem that you were using the curl to work with API. Your issue relates to the timeout issue. Try to increase the timeout for your curl. This will solve your timeout issue. The default timeout PHP is 13 seconds.
– Khoa TruongDinh
Apr 10 '18 at 1:57
I'm not using the API. The site is running varnish cache, so I'm thinking somehow that is involved.
– Kazpilot25
Apr 10 '18 at 15:35
Possibly a Zend timeout issue? I changed the value in the Client.php file for timeout from 10 to 90 and saw no difference.
– Kazpilot25
Apr 10 '18 at 16:35
Seem that you were using the curl to work with API. Your issue relates to the timeout issue. Try to increase the timeout for your curl. This will solve your timeout issue. The default timeout PHP is 13 seconds.
– Khoa TruongDinh
Apr 10 '18 at 1:57
Seem that you were using the curl to work with API. Your issue relates to the timeout issue. Try to increase the timeout for your curl. This will solve your timeout issue. The default timeout PHP is 13 seconds.
– Khoa TruongDinh
Apr 10 '18 at 1:57
I'm not using the API. The site is running varnish cache, so I'm thinking somehow that is involved.
– Kazpilot25
Apr 10 '18 at 15:35
I'm not using the API. The site is running varnish cache, so I'm thinking somehow that is involved.
– Kazpilot25
Apr 10 '18 at 15:35
Possibly a Zend timeout issue? I changed the value in the Client.php file for timeout from 10 to 90 and saw no difference.
– Kazpilot25
Apr 10 '18 at 16:35
Possibly a Zend timeout issue? I changed the value in the Client.php file for timeout from 10 to 90 and saw no difference.
– Kazpilot25
Apr 10 '18 at 16:35
add a comment |
1 Answer
1
active
oldest
votes
0
Cache problem.
Maybe you are using varnish cache, please check the concurrent connection setting or try to restart Varnish.
answered Apr 10 '18 at 4:20
leoleo
585521
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f221637%2fmagento-2-2-3-internal-server-error-read-timed-out-after-10-seconds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Cache problem.
Maybe you are using varnish cache, please check the concurrent connection setting or try to restart Varnish.
answered Apr 10 '18 at 4:20
leoleo
585521
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
add a comment |
0
Cache problem.
Maybe you are using varnish cache, please check the concurrent connection setting or try to restart Varnish.
answered Apr 10 '18 at 4:20
leoleo
585521
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
add a comment |
0
0
0
Cache problem.
Maybe you are using varnish cache, please check the concurrent connection setting or try to restart Varnish.
answered Apr 10 '18 at 4:20
leoleo
585521
Cache problem.
Maybe you are using varnish cache, please check the concurrent connection setting or try to restart Varnish.
answered Apr 10 '18 at 4:20
leoleo
585521
answered Apr 10 '18 at 4:20
leoleo
585521
answered Apr 10 '18 at 4:20
leoleo
585521
answered Apr 10 '18 at 4:20
leoleo
585521
585521
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
add a comment |
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
I think you're on the right track. The site is running varnish cache, and the log shows 3 attempts 5 seconds apart, which is a varnish setting for attempts. Now if I could just figure out what exactly is going on. I've restarted varnish with no luck. How do I check the concurrent connection setting?
– Kazpilot25
Apr 10 '18 at 15:37
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
Scratch that... It shows 2 attempts 10 seconds apart.
– Kazpilot25
Apr 10 '18 at 16:01
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
I ran varnishlog and there are no errors thrown in varnish when the internal server error occurs. I'm starting to think it's a Zend timeout somehow.
– Kazpilot25
Apr 10 '18 at 17:08
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f221637%2fmagento-2-2-3-internal-server-error-read-timed-out-after-10-seconds%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Seem that you were using the curl to work with API. Your issue relates to the timeout issue. Try to increase the timeout for your curl. This will solve your timeout issue. The default timeout PHP is 13 seconds.
– Khoa TruongDinh
Apr 10 '18 at 1:57
I'm not using the API. The site is running varnish cache, so I'm thinking somehow that is involved.
– Kazpilot25
Apr 10 '18 at 15:35
Possibly a Zend timeout issue? I changed the value in the Client.php file for timeout from 10 to 90 and saw no difference.
– Kazpilot25
Apr 10 '18 at 16:35