• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

mp3 transfer -- apache log analysis

Greg Sims

Basic Pleskian
We have been having some server HTTP alerts from our monitoring system. I did some research in the apache access_logs and see a behavior that I don't understand. I pulled some data this morning in hopes that you could help me understand what is happening here and how to potentially correct it.

http://raystedman.org/4204Ref.txt contains a log sequence that accesses one mp3 file by one user. The mp3 file is http://raystedman.org/mp3/4204.mp3 and is almost 7 MB large. Normally I will only see one record in the access_log for a transfer like this one. This transfer is really a mess. Why does it require this huge number of log records to transfer this one file?

The user is working on transferring a group of .mp3 files at the same time. This can be seen at http://raystedman.org/mp3Ref.txt. The server doesn't have much else going on which can be seen here http://raystedman.org/22Ref.txt. We can also see the side effects of all this in server-status http://raystedman.org/22Stat.txt.

Any ideas? Thanks! Greg
 
Just an idea, but...

He seems to be downloading several mp3 files not just one.

Could it be that this is a dial-up user using a download accelerator to split the files into multiple chunks? I've seen some accelerators splitting things into up to 16 chunks for no good reason.

And if he keeps losing the connection (or overloading the server or his pc or whatever), the download accelerator may then be coming back again over and over to re-start the download.

Like I say, just an idea. It may be nothing likr this at all.
 
Thanks for the reply feris!

I believe your scenario is likely correct -- this user has limited resources for some reson (modem connection, limited RAM, ...) and is downloaded in small blocks.

It doesn't seem correct that this one slow uses should be able to run on 10-20 apache processes at a time. This seems very unfair to other users. Is there a way to limit apache resources on the server by IP Address or something simular?

Thanks again!
 
Back
Top