We have updated our Terms of Service, Code of Conduct, and Addendum.

Troubleshooting file monitor permission issue

Options

Hello, While configuring cribl edge source of type file monitor and setting discovery mode to manual, it keeps on telling me permission denied(attached) and the *.log files are not monitored, although the user running cribl have access to this directory and the underneath *.log files. Attached the configuration of the source. Any idea what could be causing this issue?

Answers

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options

    can you share a listing of the directory in question? `ls -las`

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options
    1. Need to see the perms of the directory as well, not just the files 2. dataiku is the user that Cribl is running as?
  • Ryan Hennessy
    Ryan Hennessy Posts: 21 ✭✭
    Options

    attached the permissions of the directory, cribladm is the user running cribl, but this user is added to the dataiku group.

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options

    try putting Group=dataiku in the systemd config file

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options

    ```$ sudo systemctl edit cribl```

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options

    ```[Service] Group=dataiku```

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options

    then restart it ```$ sudo systemctl restart cribl```

  • Ryan Hennessy
    Ryan Hennessy Posts: 21 ✭✭
    Options

    cribl is not running as a systemd process

  • Jon Rust
    Jon Rust Posts: 439 mod
    Options

    since making the change to /etc/groups, did you log out or restart? How did you start cribl? (this is a linux perms issue, not a cribl issue)

  • Ryan Hennessy
    Ryan Hennessy Posts: 21 ✭✭
    Options

    No, cribl wasn't restarted. We are already able to list/read the intended files in the server using cribl user attached.

  • Ryan Hennessy
    Ryan Hennessy Posts: 21 ✭✭
    Options

    cribl is now restarted and the issue is solved, thanks <@ULBGHDPNY&gt;