Skip to main content
Question

Troubleshooting file monitor permission issue

  • Mar 11, 2025 3:13 AM UTC
  • 11 replies
  • 219 views

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?

11 replies

Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC

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


Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC
  1. Need to see the perms of the directory as well, not just the files2. dataiku is the user that Cribl is running as?

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


Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC

try putting Group=dataiku in the systemd config file


Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC

```$ sudo systemctl edit cribl```


Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC

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


Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC

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


cribl is not running as a systemd process


Jon Rust
Forum|alt.badge.img
  • Employee
  • Mar 11, 2025 4:44 AM UTC

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)


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


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