After sending a POST request from the administrator module creation area, I receive a 'connection reset' error. The content is quite a large amount. Any ideas why this could be?
That sounds like a too much data or too much time problem. The related PHP settings are post_max_size or max_execution_time. You have to check yourself or ask your hosting provider.
Usually in the server log you can find the exact cause for the problem.
Related
I'm using Laravel Vapor for a project and I started getting this error today. It seems to happen randomly in different pages, it first take a minute trying to load and then I get one of this errors.
{"message": "Internal server error"}
{"message": "Endpoint request timed out"}
I'm not sure what the problem is since the error doesn’t show in my vapor-ui logs. Any idea what could be happening? Thanks
Your code is likely timing out due to the timeout and possibly the memory configs on your vapor.yml. Since you're receiving a timeout vs. a 500 or similar error, you're not seeing errors in the logs.
To verify I'd inspect the network requests coming through your browser and when it 'randomly' fails, see if it's always stopping its execution at 10 seconds (or whatever your timeout is in your vapor.yml file). Assuming you're reaching your timeout, I'd suggest doing the following:
Debug your code to understand why it's timing out and optimize any inefficiencies. Laravel Telescope provides some tooling for this: https://laravel.com/docs/8.x/telescope
Increase the timeout config on your vapor.yml file (default is 10 seconds) - Vapor docs: https://docs.vapor.build/1.0/projects/environments.html#timeout
Increase the memory config in your vapor.yml file (default is 1024). Per the docs: Vapor (via AWS Lambda) allocates CPU power to your Lambda function in proportion to the amount of memory configured for the application.. Vapor docs: https://docs.vapor.build/1.0/projects/environments.html#memory
Review the other performance tips Vapor provides: https://docs.vapor.build/1.0/projects/troubleshooting.html#performance-issues
Check your memory and timeout is increased.
I have had this problem often.
For this, I recommend you to examine the log file under storage/logs
Your query is probably timing out because the memory limit to php ini file is 128M. It will be fixed if you set the memory limit to 1024M in php ini file.
egg:
memory_limit =1024
I was downloading a file on my pc using my mobile hotspot from Sim_1 and 50% of the download was completed. When I changed the mobile data source to Sim_2, the download began from the beginning. :(
Is this problem caused by the change in ISP or maybe due to some other issues?
PS: Both Sim_1 and Sim_2 are of different networks.
I think in order to resume a download both the server that the resource is being fetched from and the client need to support this.
They would have to agree on the progress made and resume the download from the location in the byte stream that the client has reached. This might be achievable in HTTP using something like the partial requests using range headers like accept-range https://developer.mozilla.org/en-US/docs/Web/HTTP/Range_requests
Essentially, I think that the ability for your download manager client to be able to change network and resume from that point would depend on the end resource being requested as the server that is providing it would need to be able to do that. If that server is only capable of sending the total bytes from start to end then that is the best your client can hope for.
I've got my Web API interface working fine but after a fairly short period, like around 5 minutes, it gives a 500 Internal Server Error on the first call and then works fine again until it times out. I'm not getting any additional information on the error message and there's nothing going to the logs. I don't have the issue on my development machine, just on the live server. Any ideas what might be causing this? How can I get additional error information on a live server?
The simple answer to this was set Custom Errors Off within the Web.config file. That gave a very useful error that made it easy to track down the problem.
Interesting bug. When I try to subscribe to magento newsletter, I end you getting an internal server error 500. However on refresh via the url, it gives me the thank you for subscribing and adds to the database too!
Can anyone shed some light into this or faced similar problems?
Julian
PS: Thank you in advance
Please see your web servers log for errors. Usually the servers logs the occured php error which results in the 500 internal server error.
Many things could force this error. For example max_execution_time or memory overflow.
I see these kinds of messages on twitter and other places.... how do they work? Is it MySQL connections?
You can measure response time of each request (or a given fraction of the requests). If the response time goes up above a threshold you start rejecting requests.
If you measure SQL connection etc you need to know where your bottle necks are at a given moment. If your application is limited by bandwidth between your servers or something else counting SQL connections will not help you.
It might be shown if the database refused a connection or if the system load (read from /proc/loadavg) is too high. It could also be shown if too many users are logged in - but that's only likely for web applications where logged in users are expensive.. certain games for example where lots of state information must be kept while someone is logged in.