• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Watch dog module....

Spyder

Regular Pleskian
Hi Guys I have a dead watch dog :)

When I try enable i get this messages..

--------------
ERROR Nível SuperiorNível Superior

Unable to query: Unknown column 'connection_timeout' in 'field list'

--------------------------------------------------------------------------------

0: /usr/local/psa/admin/plib/common_func.php3:203 psaerror()
1: /usr/local/psa/admin/plib/modules/watchdog/common.php:173 db_query()
2: /usr/local/psa/admin/plib/modules/watchdog/common.php:503 wd_db_query()
3: /usr/local/psa/admin/plib/modules/watchdog/common.php:571 get_service_templates()
4: /usr/local/psa/admin/plib/modules/watchdog/common.php:669 get_all_templates()
5: /usr/local/psa/admin/plib/modules/watchdog/common.php:990 config_generate()
6: /usr/local/psa/admin/htdocs/modules/watchdog/services.php:34 generate_cfg_file()
----------

When using the beta this work.

FreeBSD version.

Some tips ??

TIA.
 
There are several problems with watchdog. After making a post a couple of days ago about watchdog crashing my qmail. An senior member advised me to disable it because of the amount of bugs still in it. I'll wait for a new release before running this on a production server.
 
Well i dont know where you are using plesk for but on a production server with customers you dont wanna have an beta releases or buggy versions running :)

But anywho, i cant say what the error is. I upgraded a couple of days ago and all worked fine till mailman was restarted after it was detecting a qmail stop. Maybe its fixed by just replacing the lines from mailman restart to qmail restart.

anywho.. first i'll wait for a fix. and if you 're running a production server with customers you should consider that as well :)
 
No, Never...

I have an "crash test dumie" machine .. live @ internet but without real users...

But thank´s ;;

Tia.
 
Back
Top