• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

***poked timer*** error

U

UmitO

Guest
hi,
my server(win 2008r2 plesk 10) was too much down last week.i checked my log files and found that there is poked time errors first and than it gives bind errors?Have any solutions?my errors was

The description for Event ID 2 from source named cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

*** POKED TIMER ***

the message resource is present but the message is not found in the string/message table


/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////


The description for Event ID 1 from source named cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

zone 0.0.127.in-addr.arpa/IN: loading from master file C:\Program Files (x86)\Parallels\Plesk\dns\var\0.0.127.in-addr.arpa failed: bad name (check-names)

the message resource is present but the message is not found in the string/message table


//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////


The description for Event ID 1 from source named cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

zone 0.0.127.in-addr.arpa/IN: not loaded due to errors.

the message resource is present but the message is not found in the string/message table


///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////


The description for Event ID 1 from source named cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found

the message resource is present but the message is not found in the string/message table


///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////


The description for Event ID 1 from source named cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

dns_rdata_fromtext: C:\Program Files (x86)\Parallels\Plesk\dns\var\0.0.127.in-addr.arpa:2: near '[email protected]': bad name (check-names)

the message resource is present but the message is not found in the string/message table
 
Back
Top