I am installing Magento 2. There is no problem till the installation reaches 70% but after that, a popup appears stating Apache HTTP server has stopped working. It pops up on the screen again and again. Not able to complete the installation process. What should be done?
Related
I start my vite dev server for my react typescript project.
After working for some time the browser is unable to serve the website and it keeps loading fore ever.
This also slows down my syatem internet speed
After i close the browser and server. The issue is resolved but it again appears after i work sometime on the server.
I am using linux mint as my OS
I have also tried upgrading the u limit as described in the vite js troubleshoot page but no help
Trying to use this project: https://github.com/blueimp/jQuery-File-Upload/
Our application server is a FreeBSD 11.2 with Apache 2.4.39 and PHP 7.2.17. I've downloaded their demo and receive the error net::ERR_CONNECTION_RESET in the browser console when trying to upload anything large enough to exceed 22 seconds exactly. It does appear to be server related as I've downloaded the same demo to another CentOS7 server where same file upload succeeds.
Although I have checked all my PHP variables for max upload size and memory limit, etc., would this demo be subject to PHP variables? I found the RequestReadTimeout Apache setting in the server that fails, not present in the working server, so I thought it could be the culprit, but I changed this setting from...
RequestReadTimeout header=20-40,MinRate=500 body=20,MinRate=500
To this...
RequestReadTimeout header=60-120,MinRate=500 body=120,MinRate=500
...and restarted Apache, but the same result. The developers on this server believe this issue only started after recent updates to the server were done that included Apache 2.4.33 upgraded to Apache 2.4.39. The PHP version did not change, however, there were many other packages updated as well as security patches to the FreeBSD OS. Can someone suggest what could fix this issue?
--UPDATE--
Okay, this is easily duplicated. I spun up a VM with a fresh install of FreeBSD 11.2, installed Apache 2.4.39 and the demo of this project. I adjusted these settings in the demo app to allow a large mp4 video to be uploaded...
acceptFileTypes: /(\.|\/)(gif|jpe?g|png|mp4)$/i,
maxFileSize: 999000000,
...and receive the same Unknown error at exactly 22 seconds into the download progress of an mp4 file of ~493MB. There must be a setting in Apache that needs to allow more time or other limit. And perhaps a change to the FreeBSD Apache 2.4 port somewhere between 2.4.33 and 2.4.39. My developers say this all started after that update.
Well, the RequestReadTimeout setting in Apache was the culprit. I had to completely disable, now it works.
same issue here - to fix, on a Centos 7 system, comment out this line:
LoadModule reqtimeout_module modules/mod_reqtimeout.so
from the 00-base.conf file, then restart httpd
Im running on the latest Mac OS. I installed wildly and it is starting up with no errors. Im trying to deploy a small enterprise application, I exported it as jar file from eclipse. Im following a online course, I double checked the code it looks exactly like in the videos.
The problem is: When I deploy from the admin console, it just tells me: Your request is being processed ... waiting more then 20 minutes, no errors not even a warning, it just won't deploy and I have no clue what is the problem....
I am installing Magento 2 and getting the following error when trying to run the setup. What am I missing?
{{$state.current.noMenu ? $state.current.title : titles[$state.current.type]}}
I have received this even on Magento 2.3. Two things I have seen that cause this:
Running magento in a multi-docker/container environment where all the containers aren't synced up in terms of magento files.
Possibly some type of browser caching issue. The last time it happened, I opened the same site in an incognito window and the site loaded up properly.
I'm actually in a nightmare. My webapp uses websockets for the chat and here comes the problem:
Using Glassfish 4.1u13 everything worked fine, until I activated the Access Log Monitoring. since that, every ws request was made 2 times and the web socket couldn't did the handshake.
https://java.net/jira/browse/GLASSFISH-21007
Tried to update to glass fish 4.1.1 -> problem PERSIST
Tried to switch to Payara 4.1.1.115 (which is a patched version of glassfish) and everything went smooth. I could now have websockets AND access logging in my Glassfish instance.
Some minutes after noticed that when I reload the page, not always the communication between client app and server were done.
Inspect network -> handshakes correctly but can't exchange data.
On server side then, I made 2 system out: one in the filter of the request servlet and one in the websocket endpoint.
Every request arrives to the server and do the handshake BUT sometimes #OnOpen will not be called, even if the wss is upgraded to 101. How's that possible? tried to update to Tyrus 1.12 (payara uses 1.11) and also downgrade it to 1.8.1 (which is the version used by functioning Glassfish 4.1u13) but nothing happens.
How I can debug this behaviour?
This was a bug which was raised against Payara (Github issue #536) and has now been fixed.
The fix has been released in Payara version 4.1.1.161, which is available for download.