Skip to main content
Question

Cribl is stopped, but pid file exists

  • March 11, 2025
  • 4 replies
  • 64 views
T

HiI have 2 cribl workers (cribl worker 1 and cribl worker 2 )managed by the same manager; cribl worker 1 goes down every now and then and has to be started manually. Status checks return the following: 'Cribl is stopped, but pid file exists'; can any of you please help me troubleshoot or point me in the right direction

    4 replies

    T
    • Tony R
    • Employee
    • March 11, 2025

    Hi Dalwin, are you running the command using user Cribl ?

    T
    • tpeveler
    • Author
    • Employee
    • March 11, 2025

    yes i running cribl status command as cribl useri am also able to start cribl worker manually using cribl startI would like to know why its keeps going down even though i have enabled boot-start

    B

    Boot-start won't keep it from going down; nothing can prevent it. Boot-start ensures it will be restarted if it does go down because systemd monitors it. However systemd won't monitor it if you aren't starting it with systemd. You mentioned you use "cribl start" to start it but that bypasses using systemd thereby defeating the use of the boot-start command. You should be using "systemctl start cribl" as root. As for the issue, you'll need to give us something to go on. Please look for relevant errors in the API log from the affected worker.

    S

    I faced the same issue.
    Even after shutting down the file named cribl.pid under $CRIBL_HOME/pid has not been removed. Ideally, it has to be removed. Once i delete and start, it worked for me

    Terms & ConditionsAccessibility statement