I'm using Apache 2.4.4 as a part of WAMP in Windows 2008 server. If I try to send a request while on the fringe of a wifi network using a smart phone and the phone transitions from wifi to 4g, my entire Apache service will freeze until it is restarted. Nothing is written to the access log or error log after the service stops working.
Is there a way to protect my server against this?
Edit:
I did some more testing. This only occurs if I'm using the external IP to connect to the server ie. 60.60.60.60:8080, but not 192.168.0.5:8080.
I am able to recreate the issue 100% if I stand somewhere with slight packet loss (2%), send a request, and disconnect from wifi before a response is received.
The only thing that locks up is Apache. Everything else on the server works fine.
It seems this is an issue with Apache, Windows, and my network card. I tried the solution to this question which is a general solution for buggy Windows/Apache interactions. I'll try updating my network card drivers when I get that chance and that may also solve the issue without needing the above fix.
Related
I’m using Jetbrains Gateway to use IntelliJ to work on the code in a remote Linux machine.
I connect via SSH. I connect and work fine initially, the latency is around 150 ms but it keeps disconnecting. I realized it disconnects when I stop coding and spend some time on other things (browser etc.). When I want to re-connect it asks for SSH key passphrase, I need to enter it multiple times and the 'Save Permanently' option won't work.
Is there a setting I can do to keep it connected?
Could this be related to my company's network, in which case again can I increase timeout or retry on fail by some settings?
This is Max from the remote development team at JetBrains.
I'm sorry to hear you are having trouble with Gateway. Please create a ticket here https://youtrack.jetbrains.com/newIssue?project=GTW describing your issue and attaching your logs. This will help us understand whats going on and resolve your issue.
Thanks!
I started using Remote Development feature of IntelliJ connecting to the same remote machine as described here https://www.jetbrains.com/help/idea/remote-development-starting-page.html
It does not disconnect, I can work whole day (tested 12+ hours) without any connection issues.
I am trying out the WebRTC examples of MuazKhan. It is working perfectly fine when the broadcaster is on AWS/Azure(or any other network) and the receiver is through my phones 4G network. But as soon as I switch to my broadband from 4G, the video stream is unable to connect and I the video player keeps on trying. Therefore I assumed that the problem is of the router NATting and will be resolved if I use a tried-n-tested TURN service such as Xirsys.
Sadly, even after using their TURN servers, I still am blocked with my broadband connection issue as mentioned above. Here are a few queries that I wanted to discuss:-
This issue seems to be due to NATting through my broadbands routers. Shouldn't using the TURN server solve it?
How can I verify if even the TURN servers are getting used and its not just the STUN servers.
Can this issue be due to the Signalling Server?
Do i need to enable some specific protocols in my router to make this work?
What else could be responsible for the issue that I should debug?
I have been trying to get Raknet up and running on my Raspberry Pi (2).
I am using a simple client server test program to connect from my windows machine to my raspberry pi. Using tshark on the Pi I can see that all message are arriving on the Pi. However, the server application does not seem to pick those up. As far as I can deduce all ports are open, the machines are on the same network, the code is correct (taken from some github repo with examples for raknet).
The frustrating thing is that a while back I though I solved this communication by starting my server app as root (sudo). However, in the meantime something has been changed in my setup which makes this no longer the case. Any help is appreciated.
I completely forgot about my question here. It actually had to do with privileges on the networks we use here. I had been testing on two different networks without realizing. Problem has been solved.
I am currently in the beginnings of developing an integrated Sonos app, and to get a better understanding of what needs to happen, I downloaded Sonos's provided sample server for the "Acme" service.
On first use, I was able to get it working and was able to play songs from the static directory that was provided within the package. However, after closing the server, leaving my computer for some time, and booting it back up again with ./gradlew bootRun, I noticed that I was not able to use the sample service anymore. On the window to link the sample account, it said that there was an error in authenticating and that it might be an issue with the connection.
First things first, I rebooted everything I could reboot. Turned the gradle server on then off. Removed the service and created it again. I even did a factory reset and put the Sonos device (PLAY:1 variety) on a different network at the office. The sample service still won't authenticate.
What could be causing the authentication for the sample Acme service to stop working just like that on every network? I should mention that I have been using the same config settings ever since I got it to work the first time, so it should not be a problem with my configurations in the customSD page. Also, I have not changed any code within the sample server.
TL;DR: The Sonos sample server worked one time for me, and hasn't worked since on multiple networks and devices, even after a factory reset. What could be causing this issue?
It sounds like the player possibly can't find the sample server any more. When you set up the service via customsd, you used an ip address for the endpoint. Is it possible that ip address has changed?
When I click the send button for sending my app in Application Loader, it is waiting for a response (sent API usage to iTunes Connect, waiting for response) and waiting without error. I am getting a message "the network connection was lost" after a couple minutes. I tried another network connection but the issue was not resolved. Could the issue be on iTunes network?
It should just work if you quit Application Loader, then re-open it.
To submit an application to iTunes Connect, your Mac always need to be up to date, or you will be able to get errors. To do this click on Apple's logo > Software Update. I was having the same problem, and it solved for me. Cheers =)
I had to force quit and the re-open to make it work.
A normal restart did not work, nor did a restart of my Mac. Very weird.
Make sure your iTunes Connect user has admin privileges. I had it set at Technician and everything looked like it was working but it would hang on the "Sending API Usage to iTunes".
None of the above suggestions work for me. Likely the real cause is physical and related how Application Loader is using the internet. I have ADSL connection with a Netgear modem/router assigning each device at home a fixed IP address according to the mac address of the network interface of each device. I had noticed that when Application Loader is uploading, my Windows PC could not connect to the internet. However, if in Mac mini I use Safari doing various things like watching video, my Windows PC can access internet.
Even stranger, when Application Loader is uploading, the modem/router could easily lost connection to the internet, as I could see from the LED lights of the modem. The connection is lost randomly at any progress of uploading the 20 MB file.
So I had turned off Windows PCs, iPads, iPhones and Android device at home, so Mac mini is the only device using the Internet, the Application Loading has finally been able to upload the app successfully in one go.
My guess is, my home phone line has some noise, and Application Loader is using the internet aggressively particularly the up link, so stressing out the modem, then causing other devices like my Windows PC lost connection, not even able to resolve host.
So my working solution is to make Mac be the only device using the Internet, given that the internet connection is already in poor condition with noise, near the edge of losing connection.