Search Engine: Elastic

Article ID: 119912, created on Jan 31, 2014, last review on May 10, 2014

  • Applies to:
  • Odin Business Automation Standard 4.5
  • Odin Business Automation Standard 4.3

Symptoms

There is a number of failed tasks like "Plesk Node #N events process" shown in Task Queue:

Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue

The following errors are shown in the logs:

  1. /var/log/taskman.log

    [2014/01/27 14:39:30] [INFO] [833] [HSPC::Taskman::call_task] ===> Executing task #36151 [HSPC::MT::Plesk::Events->process_nodes] [undef]
    [2014/01/27 14:39:30] [ERROR] [833] [HSPC::Taskman::call_task] <=== Task #36151 failed locally: 404 Not Found at /usr/lib/perl5/site_perl/5.8.8/HSPC/Taskman.pm line 288
    
  2. /var/log/httpd/hspc_frontend_proxy_error_log

    [Mon Jan 27 14:39:11 2014] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 123.123.123.123:8080 (*) failed
    [Mon Jan 27 14:39:19 2014] [error] (111)Connection refused: proxy: HTTP: attempt to connect to 123.123.123.123:8080 (*) failed
    [Mon Jan 27 14:39:20 2014] [error] [client 127.0.0.1] File does not exist: /var/www/html/frontend
    [Mon Jan 27 14:39:20 2014] [error] [client 127.0.0.1] File does not exist: /var/www/html/frontend
    

Cause

Stopped Task Manager and hung http process.

Resolution

Verify Task Manager is running on PBA-S node and start it. Login to PBA-S node as root and restart httpd service:

~# /etc/init.d/httpd restart

For clustered PBA-S installation: start Task Manager and restart httpd service in all backend nodes.

Additional information

Stopped Task Manager service: no new Actions in the Action log

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 807e9c1dc97aefd951b912a17e50c428 70a5401e8b9354cd1d64d0346f2c4a3e 624ca542e40215e6f1d39170d8e7ec75

Email subscription for changes to this article
Save as PDF