Article ID: 9548, created on Jan 5, 2011, last review on Nov 20, 2014

  • Applies to:
  • Operations Automation

Symptoms

The periodic task 'Retrieve traffic usage data' fails in POA with the error message error while loading shared libraries: libboost_filesystem.so.1.41.0: cannot open shared object file: No such file or directory like in the following example:

Task ID          7361045  
Queue name       service 352      
Task name        Retrieve traffic usage data (service_id = 352)   
Task description Retrieve traffic usage data (service_id = 352)   
Queue status     Failed   
Start not earlier than  Aug-17-2010 15:45        
Method name      refreshUsage on OBJREF:proclog:0:getService:352  
Last execution output   Internal error:
/usr/local/pem/bin/logreporter /usr/local/pem/bin/logreporter /usr/local/pem/etc/logparser/traffic /usr/local/pem/etc/logparser/config.xml /usr/local/pem/etc/logparser/checkpoints.xml failed with code 127 saying:
STDOUT: '' STDERR '/usr/local/pem/bin/logreporter: error while loading shared libraries: libboost_filesystem.so.1.41.0: cannot open shared object file: No such file or directory

Cause

Shared library libboost_filesystem is absent on Linux server registered in POA.

Resolution

Make sure that POA Agent is installed properly on POA-managed host.

The shared library libboost_filesystem is a part of package boost-libs which is in turn a part of PVC application template:

  • EZ template: pa-pleskd or pa5x-pleskd in case of POA 5.x
  • Standard template: vzpem-pleskd If shared Linux server is PVC container-based - check that corresponding application template (EZ or standard) is installed in the container. Otherwise, install the RPM package boost-libs manually.

Search Words

libboost_filesystem

pa-pleskd

failed task

cannot open shared object file

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF