• 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.

Watchdog down after upgrading to 8.3

P

Panerai

Guest
I upgraded from 8.2.1 to 8.3

Via web controlpanel, when I try to activate Watchdog, I get:
"Wdcollect service does not respond. Refer to SWsoft technical support for help."
When I try to run an on-demand scan in the Watchdog module, I hit the green start button and I get this message: "Scanning is in progress. About 30 minutes left" and a progress bar that remains empty. When I hit update I get:
"The scanner has never been started."

Why is that?

In the email "success report" I see:

Get packages to installation from selected component watchdog
Warning: packages conflict by files detected: package gcc-g77-3.3.5-5.x86_64
conflict with package gcc-g77-32bit-9.3-7.x86_64
both have file /usr/lib/libfrtbegin.a with different md5 sum.
Warning: packages conflict by files detected: package gcc-objc-32bit-9.3-7.x86_64
conflict with package gcc-objc-3.3.5-5.x86_64
both have file /usr/lib/libobjc.a with different md5 sum.
Warning: packages conflict by files detected: package gcc-objc-3.3.5-5.x86_64
conflict with package gcc-objc-32bit-9.3-7.x86_64
both have file /usr/lib/libobjc.a with different md5 sum.
Warning: packages conflict by files detected: package gcc-g77-32bit-9.3-7.x86_64
conflict with package gcc-g77-3.3.5-5.x86_64
both have file /usr/lib/libfrtbegin.a with different md5 sum.
Check package set before installation

o.k. I reckon it didnt install Watchdog and thats why I cannot run it from the cp.


I try to install via commandline. I get:
>: rpm -i /srv/psa/PSA_8.3.0/dist-rpm-SuSE-9.3-x86_64/opt/modules/watchdog/psa-watchdog-2.0.3-suse9.3.build83071218.19.x86_64.rpm
package psa-watchdog-2.0.3-suse9.3.build83071218.19 is already installed

Next I run /usr/local/psa/admin/sbin/autoinstaller
watchdog has an (=) dunno what that means, cannot modify that, but I go for it. Process ends with:
Trying to establish test connection... connected
done

using /etc/init.d/xinetd
Reload INET services (xinetd)...done
done
The packages were installed successfully.

Sonds nice, but now the web-based updater now says:
Error! Failed to read product information from the file
Not all packages were installed.
Please, resolve the above problem and try installing the packages again.
If you cannot resolve the problem on your own, contact product technical support for assistance..

I try to start and stop PSA:
/etc/init.d/psa stop
/etc/init.d/psa start

Watchdog runs for some seconds, lets me edit settings but then again behaves as described above. On demand security scan never works.
Apparently the re-start of PSA at least fixed the cp updatemanager.

So how do I get that Watchdog running in a stable manner?

Thank you!
 
This has been reported, I will let you know what the fix is when I have the information.
 
@ sparkybarkalot

Yes, as long as problems are identical, they should run in a single thread. As my problem and the one reported in the thread you mention are both related to Watchdog, but differ in the kind of problem watchdog has, I found it reasonable to open a new thread.

Anyway it is surprising, that no solution has been offered to neither of the problems.

P.
 
For completeness:

This issue occurs due to a bug in PHP 5.2.3 used by Plesk control panel version 8.3.0.

Here is my PSA PHP version info:-

~# /usr/local/psa/admin/bin/php -v
PHP 5.2.3 (cli) (built: Dec 18 2007 20:44:09) Copyright (c) 1997-2007 The PHP Group Zend Engine v2.2.0, Copyright (c) 1998-2007 Zend Technologies with eAccelerator v0.9.5.1, Copyright (c) 2004-2006 eAccelerator, by eAccelerator ~#

Here is my workaround for the problem, disable the 'auto_globals_jit' option in Plesk PHP configuration /usr/local/psa/admin/conf/php.ini.

Restart the PSA Apache webserver /etc/init.d/psa restart (not your httpd Apache webserver).
 
Many thanks EBHAUK! After your modifications the on-demand scan finally runs. :)
 
Watchdog won't work - Wdcollect service does not respond.

When I try to enable services:

Wdcollect service does not respond. Refer to SWsoft technical support for help.

I have searched and tried the fixes by changing line in php.ini and restarting apache, still won't work. Does anyone have any idea what could be causing this? We have ping service locked down to specific ips, could this be it? Other settings in plesk firewall?

Thanks!
 
no response

does anyone know why this would happen??
 
Amazing

Can't get an answer in this forum or by trouble ticket....

what's the point of offering support and sending people to forums??




Wdcollect service does not respond. Refer to SWsoft technical support for help.

WHAT SWSOFT TECHNICAL SUPPORT??
 
I also have this problem, and the auto_globals_jit is switched off!!

Error: Wdcollect service does not respond. Refer to Parallels technical support for help.

Help???
 
Back
Top