Hi,
since updating OTRS 3.1 to 3.2 (RPM installation on CentOS 5) I
regularly get permission error messages from the various cronjobs
(otrs.PostMasterMailbox.pl, otrs.DeleteCache.pl, otrs.LoaderCache.pl).
Examples:
*
Message: Can't remove file
/opt/otrs/var/tmp/CacheFileStorable/CacheInternalLoader/a/5/a5a7a46de71ce8a7f3f0961aecf5c8ba:
Permission denied
*
Message: Can't write
'/opt/otrs/var/tmp/CacheFileStorable/CacheInternalTicket/8/f/8fd2c543e3d23358aec0983fbda050cf':
Permission denied
*
mkdir /opt/otrs/var/tmp/CacheFileStorable/DynamicFieldValue/b/8:
Permission denied at /opt/otrs/Kernel/System/Cache/FileStorable.pm line 81
The directory in question is of course not always the same. Sometimes
the script finally succeeds or - in the case of
otrs.PostMasterMailbox.pl - I fetch the mail manually from the
administration panel. The failing otrs.PostMasterMailbox.pl creates
lots of nasty problems like multiple identical tickets or multiple empty
tickets etc.
In fact the permissions of some directories seem to be wrong. Example:
# ls -al /opt/otrs/var/tmp/CacheFileStorable/DynamicFieldValue
total 64
drwxrwsr-x 16 otrs apache 4096 Sep 17 19:13 .
drwxrwsr-x 26 otrs apache 4096 Sep 16 10:48 ..
drwxrwsr-x 4 otrs apache 4096 Sep 16 12:30 0
drwxrwsr-x 6 otrs apache 4096 Sep 17 14:40 1
drwxr-sr-x 3 apache apache 4096 Sep 10 19:47 2
drwxrwsr-x 4 otrs apache 4096 Sep 16 15:10 3
drwxr-sr-x 3 apache apache 4096 Sep 17 19:13 4
drwxr-sr-x 4 apache apache 4096 Sep 17 19:13 5
drwxrwsr-x 4 otrs apache 4096 Sep 17 19:13 6
drwxr-sr-x 3 apache apache 4096 Sep 9 18:53 8
drwxrwsr-x 5 otrs apache 4096 Sep 17 14:50 9
drwxrwsr-x 6 otrs apache 4096 Sep 17 19:13 a
drwxr-sr-x 4 apache apache 4096 Sep 17 19:13 b
drwxrwsr-x 4 otrs apache 4096 Sep 17 19:13 c
drwxrwsr-x 5 otrs apache 4096 Sep 17 14:50 d
drwxrwsr-x 5 otrs apache 4096 Sep 17 19:13 e
# ls -al /opt/otrs/var/tmp/CacheFileStorable/DynamicFieldValue/b
total 16
drwxr-sr-x 4 apache apache 4096 Sep 17 19:13 .
drwxrwsr-x 16 otrs apache 4096 Sep 17 19:13 ..
drwxr-sr-x 2 apache apache 4096 Sep 10 19:03 0
drwxr-sr-x 2 apache apache 4096 Sep 17 19:13 8
#
The involved accounts are 'otrs' and 'apache':
# id -a otrs
uid=500(otrs) gid=48(apache) groups=48(apache)
# id -a apache
uid=48(apache) gid=48(apache) groups=48(apache), [...and many others...]
#
Running `/opt/otrs/bin/otrs.SetPermissions.pl --otrs-user=otrs
--web-user=apache --otrs-group=apache --web-group=apache /opt/otrs` only
solved the problem temporarily (on existing directories).
The problem seems to be, that directories created by 'apache' (via the
web frontend) are missing write permission for the group, while
directories created by 'otrs' (through cronjobs) have correct
permissions. Any idea how to solve this problem? It's extremely
annoying and I didn't have this with OTRS 3.1.
Also I wonder, why this problem only appeared after the (rpm) update
from 3.1 to 3.2.
System: CentOS 5, OTRS installed with rpm install, SELinux is disabled.
frank
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
