• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved log messages very huge

Jose Ruiz

New Pleskian
Hello.

I have installed Plesk Web Host Edition version 12.5.30 Update #48 on a CentOS Linux 6.5

The file log /var/log/messages increased his size about 140MB every day

I edited the log and found a lot of entries like those

Sep 29 11:24:02 ns3 named[30134]: client 67.93.217.243#24239: query (cache) 'sb.yz968.com/A/IN' denied

Sep 29 11:24:02 ns3 named[30134]: client 11.49.12.65#8355: query (cache) 'etydorwp.0011game.com/A/IN' denied

Sep 29 11:24:02 ns3 named[30134]: client 115.146.156.86#33148: query (cache) 'knizelkxmr.yz968.com/A/IN' denied

I think, I´m under attack

May anyone help me to fix this problem

Thank you
 
This is happening all the time.

1. You can ignore it, 140MB is not a lot, logrotate should solve it.
2. You can see where you get a lot of entries and solve it via Fail2Ban or firewall, if you think is an attack.
3. If is a DNS entry like in this case I see, you can eventually try to log only errors, not warnings. (dunno if work, never tried).
 
Back
Top