# Chown /var/spool/collector-sidecar/nxlog fails: no such file

**URL:** <https://community.graylog.org/t/chown-var-spool-collector-sidecar-nxlog-fails-no-such-file/11205>\
**Category:** Graylog Central (peer support)\
**Tags:** sidecar\
**Created:** [July 15, 2019, 3:31pm UTC](https://community.graylog.org/t/chown-var-spool-collector-sidecar-nxlog-fails-no-such-file/11205 "2019-07-15T15:31:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![oscarlo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/oscarlo/32/7006_2.png) [@oscarlo](https://community.graylog.org/u/oscarlo)\
**Post date:** [July 15, 2019, 3:31pm UTC](https://community.graylog.org/t/chown-var-spool-collector-sidecar-nxlog-fails-no-such-file/11205/1 "2019-07-15T15:31:57Z")

</div>

Hi, all,

Trying to follow the guide to install a Graylog Sidecar, I wind up getting stuck on [the step to “unconfigure the default system service” for NXlog](http://docs.graylog.org/en/3.0/pages/sidecar.html#nxlog-on-centos), specifically:

```auto
$ sudo chown -R nxlog.nxlog /var/spool/collector-sidecar/nxlog
chown: cannot access ‘/var/spool/collector-sidecar/nxlog’: No such file or directory

```

The `collector-sidecar` keyword (i.e. not `graylog-sidecar` as it seems to be properly called as of the new, baked-in version) makes me wonder if this is a leftover from the previous versions of the guide and so if it is still necessary to `chown -R nxlog.nxlog` some `.../nxlog` file or directory, only the updated path isn’t in the new guide?

Cheers,  
Oscar

(It seems like this might be a necessary step, as it is one of the steps meant to take `nxlog`out of the control of the system - my collector just failed, saying it “can’t restart since another instance is already running”.)

---

<div class="post-metadata">

**Author:** ![oscarlo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/oscarlo/32/7006_2.png) [@oscarlo](https://community.graylog.org/u/oscarlo)\
**Post date:** [July 16, 2019, 11:32am UTC](https://community.graylog.org/t/chown-var-spool-collector-sidecar-nxlog-fails-no-such-file/11205/2 "2019-07-16T11:32:12Z")

</div>

I’ve gotten it up and running again, after making sure that the service is started using `systemctl start graylog-sidecar` and not `graylog-sidecar -service start`, and it now seems like it’s working.

The /var/spool/collector-sidecar/nxlog directory appears to have contained the `configcache.dat` file, which according to the [NXLog reference manual](https://nxlog.co/docs/nxlog-ce/nxlog-reference-manual.html) should be located in the `/var/spool/nxlog` directory (which I think was “owned” by nxlog.nxlog from start).

Maybe the main issue for me was starting the service in a faulty way, causing it to not be recognized by the sidecar. I have opened a [GitHub issue](https://github.com/Graylog2/documentation/issues/642) to fix the [corresponding docs](https://docs.graylog.org/en/3.0/pages/sidecar.html#nxlog-on-centos) and remove the `$ sudo chown -R nxlog.nxlog /var/spool/collector-sidecar/nxlog` step to avoid future confusion for newcomers.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [July 30, 2019, 11:32am UTC](https://community.graylog.org/t/chown-var-spool-collector-sidecar-nxlog-fails-no-such-file/11205/3 "2019-07-30T11:32:13Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.