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

[7.0.3RC1] Repeated log message: touch() UTime failed permission denied #11678

Closed
PVince81 opened this issue Oct 20, 2014 · 4 comments · Fixed by #11924
Closed

[7.0.3RC1] Repeated log message: touch() UTime failed permission denied #11678

PVince81 opened this issue Oct 20, 2014 · 4 comments · Fixed by #11924
Assignees
Milestone

Comments

@PVince81
Copy link
Contributor

On OC 7.0.3 RC1 my log is full of:

{"reqId":"54456cf12cd77","app":"PHP","message":"touch(): Utime failed: Permission denied at \/srv\/www\/htdocs\/owncloud\/lib\/private\/config.php#141","level":3,"time":"2014-10-20T20:13:37+00:00","method":"PROPFIND","url":"\/remote.php\/webdav\/clientsync"}
{"reqId":"54456cf85008d","app":"PHP","message":"touch(): Utime failed: Permission denied at \/srv\/www\/htdocs\/owncloud\/lib\/private\/config.php#141","level":3,"time":"2014-10-20T20:13:44+00:00","method":"PROPFIND","url":"\/remote.php\/webdav\/"}
{"reqId":"54456d11f192e","app":"PHP","message":"touch(): Utime failed: Permission denied at \/srv\/www\/htdocs\/owncloud\/lib\/private\/config.php#141","level":3,"time":"2014-10-20T20:14:09+00:00","method":"PROPFIND","url":"\/remote.php\/webdav\/clientsync"}
{"reqId":"54456d16a346d","app":"PHP","message":"touch(): Utime failed: Permission denied at \/srv\/www\/htdocs\/owncloud\/lib\/private\/config.php#141","level":3,"time":"2014-10-20T20:14:14+00:00","method":"PROPFIND","url":"\/remote.php\/webdav\/"}

They appeared while the sync client was running.

The permissions seem to be correct:

-rw-rw---- 1 root www  541 Oct 20 22:16 config.php
drwxrwx---   2 wwwrun  www 4.0K Oct 20 10:40 config

Note: this is installed from the openSUSE 13.1 RPM, so the permissions should be correct.
If not, we need to find how to tweak them.

Discussed this with @LukasReschke and we can't explain why it is logging messages even though the @touch call is done with a @ which should eliminate such warnings.

Needs further research.

@craigpg @MTRichards @karlitscheck potential log filler

@PVince81
Copy link
Contributor Author

@karlitschek

@PVince81
Copy link
Contributor Author

This is the full listing of my config dir:

vincent-server:/srv/www/htdocs/owncloud # ls -l config
total 36K
-rw-r----- 1 root root 458 Nov 19  2013 config.debug.php
-rw-rw---- 1 root www  541 Oct 20 22:22 config.php
-rw-r----- 1 root www  23K Oct 16 08:46 config.sample.php
-rw-r----- 1 root www   55 Aug 20 12:54 noupdate.config.php

From what I saw in the code there's a loop that goes over all the config files, and it probably also looks at that file "config.debug.php" which has different permissions and tries to touch it.
This would explain the "permission denied" issue.
But doesn't explain why the message is still logged.

To make the messages disappear, I needed to set group writing permissions on ALL files in the config folder:

-rw-rw---- 1 root www 458 Nov 19  2013 config.debug.php
-rw-rw---- 1 root www 541 Oct 20 22:24 config.php
-rw-rw---- 1 root www 23K Oct 16 08:46 config.sample.php
-rw-rw---- 1 root www  55 Aug 20 12:54 noupdate.config.php

@LukasReschke should maybe the touch() be only applied to the actual config.php, not the other files ?

@PVince81 PVince81 added this to the 2014-sprint-07-next milestone Oct 22, 2014
@craigpg craigpg modified the milestones: 2014-sprint-08-next, 2014-sprint-07-current Oct 27, 2014
@PVince81
Copy link
Contributor Author

PVince81 commented Nov 2, 2014

Still getting this in 7.0.3RC2 on my server and it is annoying.
I hope it doesn't have any side effects...

@LukasReschke
Copy link
Member

I'll take a look tomorrow. Shouldn't have any side-effects except potentially spamming your logs ;)

@LukasReschke LukasReschke self-assigned this Nov 2, 2014
LukasReschke added a commit that referenced this issue Nov 3, 2014
@lock lock bot locked as resolved and limited conversation to collaborators Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants