securityonion-elsa-extras: cron.pl should check to see if it's already running

[dougburks]

Maybe add something like this to /opt/elsa/contrib/securityonion/contrib/securityonion-elsa-cron.sh:

# check to see if we're already running
for pid in $(pidof -x securityonion-elsa-cron.sh); do
    if [ $pid != $$ ]; then
        echo_error_msg 0 "Process is already running with PID $pid"
        exit 1
    fi
done

[dougburks]

original commit:
Security-Onion-Solutions/securityonion-elsa-extras@7736a2c

replaced by:
Security-Onion-Solutions/securityonion-elsa-extras@ab28446

[dougburks]

submitted for testing:
https://groups.google.com/d/topic/security-onion-testing/NX6x-AUoKhc/discussion

[dougburks]

Removing this fix, as cron.pl already has a lock where necessary and there are times when we need to run multiple cron jobs:

If cron.pl runs for a long time, it is probably performing index consolidation, which can indeed take an hour. However, two cron.pl's should be able to run alongside each other. Can you confirm that when cron.pl runs for a long time, the indexer program is also running, and the name of the index it is indexing has "perm_" at the beginning? You can also check /data/elsa/log/node.log to see what is happening.

https://groups.google.com/d/topic/enterprise-log-search-and-archive/LREhCLDgaUg/discussion

[dougburks]

removed fix:
Security-Onion-Solutions/securityonion-elsa-extras@7881f58

[dougburks]

closing this issue