Search Engine: Elastic

Article ID: 117878, created on Oct 11, 2013, last review on Apr 30, 2016

  • Applies to:
  • Odin Business Automation Standard


There is an error in the Tasks Queue log of OBAS :

task_id: 38762
Status : Error  
description: Payment Processing: Update Billing Info for Document #74

Task Manager log provides more details of the error greppable by the task id:

[root@pbas ~]# grep 38762 /var/log/taskman.log
[2013/08/14 11:19:08] [INFO] [15768] [HSPC::Taskman::call_task] ===> Executing task #38762 [HSPC::MT::PP::PluginEngine::OP->_map_update_billing] [undef]
[2013/08/14 11:19:08] [WARN] [15768] [HSPC::Taskman::call_task] <=== Task #38762 failed remotely: #p2013-08-14_11-19-08.1 [undef]

Error-TEXT: 19:08] [ERROR] [15892] [HSPC::Taskman::Comm::backend_execute_task] Task #38762 HSPC::MT::PP::PluginEngine::OP -&gt; _map_update_billing failed miserably: ERROR: Date::Manip unable to determine TimeZone.

The issue can also take a form of failed Plesk node events process tasks that complete successfully if re-run by hand. In that case hspc.log shows

at /usr/local/share/perl5/LWP/Protocol/ line 31
[Mon Jul  7 02:24:01 2014] [error] (12)Cannot allocate memory: fork: Unable to fork new process
[Mon Jul  7 02:46:04 2014] [error] (12)Cannot allocate memory: fork: Unable to fork new process

With the following error in taskman.log:

# less /var/log/taskman.log | grep 6352683
[2014/07/07 02:24:00] [INFO] [6740] [HSPC::Taskman::call_task] ===> Executing task #6352683 [HSPC::MT::Plesk::Events->process_node_events] [undef]
[2014/07/07 02:24:01] [ERROR] [6740] [HSPC::Taskman::call_task] <=== Task #6352683 failed locally: Can't locate SOAP/Lite/Deserializer/ in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at (eval 136) line 3.


This error is caused by the lack of resources:

[root@pbas ~]# cat /proc/user_beancounters | grep -v 0$
Version: 2.5
       uid  resource           held    maxheld    barrier      limit    failcnt
            privvmpages      767326     767652    1048576    1048576          3


Increase the 'privvmpages' limit for this container (OBAS Management Node). Run the following command on the node where OBAS container resides to increase the resource:

[root@hw_node ~]# vzctl set CTID --save --privvmpages NEW_BARRIER:NEW_LIMIT 

Where CTID is the id of the OBAS container.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF