Search Engine: Elastic

Article ID: 130994, created on Jun 13, 2017, last review on Jun 13, 2017

  • Applies to:
  • Operations Automation 6.0
  • Business Automation 6.0

Symptoms

Billing is not available. Output of service pba restart command shows following:

[root@billing ~]# service pba restart
Checking Stellart Service Manager:                         [RUNNING]
Stopping Parallels Business Automation:                    [STOPPED]
Stopping Stellart Service Manager:                         [  OK  ]
Starting Stellart Service Manager:                         [RUNNING]
Starting Stellart Log Server:                              [FAILED]
Starting Parallels Business Automation dependencies:       [FAILED]

The following entries can be observed in logsrv.out.log:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'what():  Connection refused

Cause

Logging to a rsyslog server is enabled in /usr/local/bm/etc/ssm.conf.d/global.conf, however the remote server is not responding.

According to OA Billing Deployment Guide:

If OA Billing is configured to write logs on a remote server, but it is not able to connect to the log server, or there is some other issue with writing logs there, OA Billing will not be started at all.

Resolution

  1. Please either make sure that a remote rsyslog server is available or disable logging to a remote server;
  2. Restart Billing:

    service pba restart 
    

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 5356b422f65bdad1c3e9edca5d74a1ae 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF