• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Watchdog Error: The Wdcollect service is not responding.

tkalfaoglu

Silver Pleskian
I am getting a

Watchdog​

Error: The Wdcollect service is not responding. Refer to Plesk technical support for help.
when I try to star the service..

my curl version is old..
$ curl --version
curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.73.0-DEV OpenSSL/1.0.2k-fips zlib/1.2.7
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile NTLM NTLM_WB SSL libz unix-sockets
-bash-4.2$

I tried a:
/usr/local/psa/admin/bin/modules/watchdog/wd --start
and it waited for a long time then:
The Wdcollect service is not responding. Refer to Plesk technical support for help.

but yet:
# ps ax|grep wd
7040 ? Ss 0:00 /usr/bin/sw-engine -c /usr/local/psa/admin/conf/php.ini /usr/local/psa/admin/bin/modules/watchdog/wdcollect -c /usr/local/psa/etc/modules/watchdog/wdcollect.inc.php

I restarted the server.. and all these:

[root@jedi watchdog]# /usr/local/psa/admin/bin/modules/watchdog/wd --full-restart-wdcollect
The Wdcollect service is not responding. Refer to Plesk technical support for help.
[root@jedi watchdog]# /usr/local/psa/admin/bin/modules/watchdog/wd --regen-all
[root@jedi watchdog]# /usr/local/psa/admin/bin/modules/watchdog/wd --regen-all
[root@jedi watchdog]# /usr/local/psa/admin/bin/modules/watchdog/wd --adapt
[root@jedi watchdog]# /usr/local/psa/admin/bin/modules/watchdog/wd --start
The Wdcollect service is not responding. Refer to Plesk technical support for help.



did not help.. cant start watchdog.. help!
 
Last edited:
Hi,
is there any errors in /var/log/plesk/modules/wdcollect.log ?
Unfortunately nothing.. Here they are.. the latest entries:


# tail -f wdcollect.log
10800 Apr 12 22:28:49 [info] Server started.
10800 Apr 12 22:28:49 [info] Locale is activated for sending e-mail messages.
10800 Apr 12 22:28:49 [info] Server started.
10800 Apr 12 22:28:50 [info] Locale is activated for sending e-mail messages.
10800 Apr 12 22:28:50 [info] Server started.
10800 Apr 12 22:28:50 [info] Locale is activated for sending e-mail messages.
10800 Apr 12 22:28:50 [info] Server started.
10800 Apr 12 22:31:42 [info] Locale is activated for sending e-mail messages.
10800 Apr 12 22:31:42 [info] Server started.
10800 Apr 12 22:31:42 [info] Database server connection has been established.

# tail -f monit.log
[+03 Apr 12 22:13:15] Starting monit daemon with http interface at [127.0.0.1:2911]
[+03 Apr 12 22:13:15] Starting monit HTTP server at [127.0.0.1:2911]
[+03 Apr 12 22:13:15] monit HTTP server started
[+03 Apr 12 22:13:15] 'psa_spamassassin' failed, cannot open a connection to INET[localhost:783]
[+03 Apr 12 22:13:15] 'psa_spamassassin' trying to restart
[+03 Apr 12 22:13:15] 'psa_spamassassin' stop: /usr/local/psa/admin/bin/spammng
[+03 Apr 12 22:13:16] 'psa_spamassassin' start: /usr/local/psa/admin/bin/spammng
[+03 Apr 12 22:13:50] Shutting down monit HTTP server
[+03 Apr 12 22:13:50] monit HTTP server stopped
[+03 Apr 12 22:13:50] monit daemon with pid [63015] killed

I just clicked ENABLE from the plesk interface at 9 AM, and nothing new got added to these logs.. It still said
Error: The Wdcollect service is not responding. Refer to Plesk technical support for help.
 
You have already seen
What steps have you taken to update cURL? Why does the upgrade break Plesk?
 
You have already seen
What steps have you taken to update cURL? Why does the upgrade break Plesk?
Hello. I have not upgraded the cURL since I read that the new cURL is incompatible with wdcollect..
The current running cURL on that system is curl-7.29.0-59.el7_9.1.x86_64

Should I download and compile the new cURL?
 
O.k., more research shows that you are right, that with newer cURL versions, there is an issue with starting wdcollect service.

I see that there is a support article on the topic
It is not public anymore, but you can find it in Google cache (search for the full URL in Google, then click the down-arrow right to the search result headline entry and select "in cache" to view the previously public article).
The outcome of the article is: There is no solution.
I suggest to address the issue with official Plesk support. They might be able to give you further information.
 
thank you for your help, Peter. Indeed, there isn't much to do until the WdCollect is upgraded by PLESK..
 
Back
Top