Post a Reply
1239 views

Random Cutoff

  1. 11 years ago

    David

    6 Sep 2013

    I'm getting reports of random cut offs from my agents.
    I am seeing Action:Hangup in the fop2 log files (when running logging with -X 2) in one of my groups.

    It's behaving as if the supervisor has clicked the HANGUP button, but they swear they haven't.

    I've disabled the hangup facility from the supervisor screen and restarted the fop2 server and it does seem to have fixed the issue, adding weight to the argument.

    My question is how can I see which supervisor screen (if any) pressed the hangup button? Anything to help identify would help - IP address or the like.

    Thanks,

  2. admin

    6 Sep 2013 Administrator

    You can use the audit log to see who pressed the hangup button. To turn on the audit log you have to pass the -a command line parameter to the fop2 server binary. You can edit the init script options file to do it, so check your /etc/sysconfig/fop2 file and add the parameter, so it looks something similar to this:

    OPTIONS="-d -a /var/log/fop2_audit.log"

    If you have any other extra arguments, like -i or -p, leave them as is, just add the -a /var/log/fop2_audit.log (orwhatever file/location you chose).

    Then you will be able to check the audit log and see from where the hangup originated.

    Best regards,

  3. David

    7 Sep 2013

    Thanks for getting back so quickly.
    I'll get this done shortly and report back the results.

  4. David

    9 Sep 2013

    I've not tried this yet, but since changing the password (and disabling the hangup feature) the problem has gone away.

    I'm reasonably sure this was human "error".

  5. admin

    9 Sep 2013 Administrator

    Thanks for reporting back. Most probably user error. FOP2 permissions should not be too liberal, it is a powerful tool.

or Sign Up to reply!