Apache/Perl/MySQL website hangs on local IP address but not on localhost

Hi,

We have an Apache webserver running Perl + Template Toolkit and a MySQL database for user access on a VM running Windows 2012 R2.

We have recently made some tweaks to the Perl code, nothing big, just a few edits and extra templates and some design changes (CSS etc). this was tested for several months on an identical dev server and we didn't see any issues.

We went live with the changes and everything was fine for about a week but now we are seeing an odd issue where the site hangs when navigating between pages then works fine for a bit and then hangs again. No pattern to this at all. Sometimes its fine for a few minutes, other times its seconds before it hangs again.

CPU usage is about 15%, Ram is at 80% but always as been as we only have 2GB on here. Neither of them peak or change when the browser hangs.

The issue we are seeing is if we browse the website using the local IP then we see this issue.

If we browse the site using localhost in the same browser (different tab) we never see this issue.

So we can be sat with the site hanging on the IP tab but still able to browse about in the other tab on localhost.

Our db is tiny (only about 200 users, the site isn't hugely busy and nothing else has changed.

Before we go rolling the system back, should we be looking anywhere in particular that could cause this disparity between browsing using the local IP and localhost?

We've:

Reset the IP stack, reinstalled VMtool drivers and reset up the interface.
Disabled anti virus, checked all over for issues.

EDIT
We have stopped Apache and replaced our code with the original files and it was fine. No hangs. So we put the new files back in place and it is still working ok.

Seems the restart of Apache has cleared the issue for now but we expect it to come back at some stage. Will continue to test.


Thanks.
LVL 1
LetterpartAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amitkumar PSr. ConsultantCommented:
How about the IP 127.0.0.1 ? Is it working fine ?
LetterpartAuthor Commented:
Hi,

Good question.

And no. 127.0.0.1 behaves the same as 10.149.1.11 and is intermittently slow while localhost is ok.
giltjrCommented:
When you issue the command "ping localhost" what is the IP address that shows?  Typically localhost is 127.0.0.1, unless you have IP6 running and then it may return the IPV6 local host address.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

LetterpartAuthor Commented:
Hi, Ping localhost gives me ::1

ping localhost

Pinging webserv1 [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

ping -4 localhost

Pinging webserv1 [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Open in new window

LetterpartAuthor Commented:
We have resolved the issue.

I noticed we were getting the following errors in the logs:


[Mon Jan 22 12:23:20 2018] [warn] (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.

Open in new window


Whether Apache had hung or was working fine. Looked into this in further details, and added:

Win32DisableAcceptEx

to the httpd.conf file, restarted Apache and we have been fine since.

Further details here: Article on Apache.org

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LetterpartAuthor Commented:
We resolved the issue ourselves and have updated this thread in case anyone else has the same issue.

While we appreciated the input provided by others, it didn't answer the question nor help us in the correct direction so this time I won't be marking any answers as assisted.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.