Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot create directory '/run/clamav': File exists #34

Open
Yamakasi opened this issue May 5, 2017 · 8 comments
Open

cannot create directory '/run/clamav': File exists #34

Yamakasi opened this issue May 5, 2017 · 8 comments

Comments

@Yamakasi
Copy link

Yamakasi commented May 5, 2017

The following happens on Ubuntu 17.04 after a successfull Puppetrun.

May 5 14:01:43 mailscan-02 mkdir[18384]: /bin/mkdir: cannot create directory '/run/clamav': File exists

@edestecd
Copy link
Owner

edestecd commented May 5, 2017

Are you getting this in a log? What is the path to the log?

@Yamakasi
Copy link
Author

Yamakasi commented May 5, 2017

I see this in /var/log/syslog

@edestecd
Copy link
Owner

edestecd commented May 5, 2017

I don't see that the module is managing that file anywhere.
Maybe were changing the default of something?
I'd do a diff on the deb provided default config vs the one this module makes... That may provide some insight

@Yamakasi
Copy link
Author

Yamakasi commented May 5, 2017

OK, nice, I'm just testing this out of the blue, module itself looks nice!

@edestecd
Copy link
Owner

Any word on this? Still having issue?

@emmenlau
Copy link

I have been affected by this issue even though I'm not sure this is the right place to report it? It seems the clamav-daemon startup script on Ubuntu 18.04 creates the directory without checking if it exists first. A possible solution was:

diff --git a/systemd/system/clamav-daemon.service.d/extend.conf b/systemd/system/clamav-daemon.service.d/extend.conf
index a8f64eb..49319d5 100644
--- a/systemd/system/clamav-daemon.service.d/extend.conf
+++ b/systemd/system/clamav-daemon.service.d/extend.conf
@@ -1,3 +1,3 @@
 [Service]
-ExecStartPre=-/bin/mkdir /run/clamav
+ExecStartPre=-/bin/mkdir -p /run/clamav
 ExecStartPre=/bin/chown clamav /run/clamav

@ubellavance
Copy link

I doubt this file is provided or modified by the module. Can you run dpkg -S on the extend.conf file (full path)?

@gomanuke
Copy link

Ju

I have been affected by this issue even though I'm not sure this is the right place to report it? It seems the clamav-daemon startup script on Ubuntu 18.04 creates the directory without checking if it exists first. A possible solution was:

Just the same still on Debian 10. extend.conf requires -p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants