Search Engine: Elastic

Article ID: 127015, created on Sep 26, 2015, last review on Jul 14, 2018

  • Applies to:
  • Odin Business Automation Standard 4.5


Is it possible to find out who launched a certain task in OBAS?

For instance, there was a customer with Account ID #1001 that was put on hold although the account had its billing balance equal to 0. It was done by the task #1000001 Hold subscriptions owned by account #1000 at 12:00 on September 1st.

How to find out by whom it was put on hold?


  1. Check the database record regarding the task:

    # hspc-sql
    mysql> select * from task_queue where task_id=1000001  \G;
    *************************** 1. row ***************************
          task_id: 1000001
    action_log_id: NULL
         priority: 129
    base_priority: 128
           repeat: 0
      repeat_type: 0
               at: 2015-09-01 12:00:00
            added: 2015-09-01 12:00:00
          started: 2015-09-01 12:00:00
         finished: 2015-09-01 12:00:01
              pid: 4947
            class: HSPC::MT::Billing
           method: _execute_task_hold_account_subscriptions
            param: [
             redo: 1
          timeout: 0
           status: 0
      description: Hold subscriptions owned by account #1000

    From the args field we can see that task was scheduled by a Reseller. Note also the started and finished dates of the task.

  2. Check /var/log/hspcd/access_log for the period between started and finished dates for entries like - - [01/Sep/2015:12:00:00 +0100] "POST /hspc/rcc/01.01.14/tab,def/id,1000/act,com HTTP/1.1" 302 283 ",def/id,1000/act,edt" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0"

    The one above shows that the customer account #1000 was edited from RCC ( is the OBAS node hostname) by someone who logged in from the IP address

See also

Is it possible to track down when and by whom customer contacts were changed?

How to track customer actions?

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF