• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

BIND issues

K

kkropp

Guest
For some reason or another, named quits responding and I found the following interesting information in the messages log:

Apr 27 04:47:00 mcswb01 named[78172]: *** POKED TIMER ***
Apr 27 04:47:00 mcswb01 last message repeated 2 times

and then:

May 1 07:53:45 mcswb01 named[78172]: client {IP ADDRESS}#6192: no more recursive clients: quota reached
May 1 07:53:45 mcswb01 last message repeated 95 times

the thing that works is restarting named, but I don't think I should have to restart named every few days to make it work properly. Can anyone help with this? It is something I have never seen before.
 
If the IP address in the log is from outside your network, then you may want to reconfigure Bind/Named to turn off recursive lookups.

If you google on "no more recursive clients", you will find this to be more common with servers running Bind 9.2 and higher.

The other option would be to increase the limit on recursive clients to a higher number.

I also found at least one hit where it was related to Torrent doing too many lookups.

Here is one site with Bind/Named config info
Reconfig info
 
Back
Top