Re: [otrs] Upgrade to 3.2 - another little problem

2013-02-01 Thread Matthew Pulliam
The permissions issue trying to change anything in sysconfig, most likely means that for whatever reason you ZZZAuto.pm file is not writable by the user/group that you web server is running as. Based on your listing for the parameters you passed to the permissions script, check that the

Re: [otrs] Upgrade to 3.2 - another little problem

2013-02-01 Thread Martin Gruner
This is indeed a permission problem and could cause some of the other errors you mentioned. Make sure no SELinux or AppArmor policies are blocking things, if you executed otrs.SetPermissions.pl correctly. Regards, mg Am 31.01.13 19:04, schrieb Bianchi Massimo: > Hi all, > I think that I missed s

Re: [otrs] Upgrade to 3.2 - another little problem

2013-01-31 Thread Gerald Young
So run perms against the otrs-x.x.x folder. On Jan 31, 2013 11:44 PM, "Rainer Bendig" wrote: > Hm upgrade file says: > > --- snip ---8<--- > 5) Install the new release (tar or RPM) > > >With the tarball: > > shell> cd /opt > shell> tar -xzf otrs

Re: [otrs] Upgrade to 3.2 - another little problem

2013-01-31 Thread Rainer Bendig
Hm upgrade file says: --- snip ---8<--- 5) Install the new release (tar or RPM) With the tarball: shell> cd /opt shell> tar -xzf otrs-x.x.x.tar.gz shell> ln -s otrs-x.x.x otrs --- /snip --->8-- maybe this needs a patch ;( Am 31.01.2013 20:

Re: [otrs] Upgrade to 3.2 - another little problem

2013-01-31 Thread Gerald Young
make sure /opt/otrs isn't a symlink. Permissions may not apply correctly if it is. On Thu, Jan 31, 2013 at 1:04 PM, Bianchi Massimo < massimo.bian...@nposistemi.it> wrote: > Hi all, > > I think that I missed some step… > > ** ** > > Tryng to modify ANY item in sysconfig leads to an erro