[solved] Permissions won't set for some odd reason

Moderator: crythias

Locked
smurray
Znuny newbie
Posts: 12
Joined: 28 Mar 2012, 21:46
Znuny Version: 3.1.2
Real Name: Shaun
Company: PayFlex

[solved] Permissions won't set for some odd reason

Post by smurray »

Fresh OS build, and fresh install. I run the otrsSetPermissions.pl

Code: Select all

[shaun@otrs-test bin]$ sudo ./otrs.SetPermissions.pl /opt/otrs --otrs-user=otrs --web-user=apache --otrs-group=apache --web-group=apache
bin/otrs.SetPermissions.pl <1.4> - set OTRS file permissions
Copyright (C) 2001-2010 xxx, http://otrs.org/
Setting permissions on /opt/otrs
Setting permissions on /opt/otrs/var
Setting permissions on /opt/otrs/bin/*
Setting permissions on /opt/otrs/scripts/*.pl
Setting permissions on /opt/otrs/scripts/tools/*.pl
Setting permissions on Kernel/Config.pm
Setting owner rw and group ro permissions on /opt/otrs/
Setting owner rw and group ro permissions on /opt/otrs/.procmailrc
Setting owner rw and group ro permissions on /opt/otrs/.fetchmailrc
I delete the database, and do the check. Everything works great. Then when I click to the next screen. I get this error:

Warning
Message: Kernel/Config.pm isn't writable!
If you want to use the installer, set the Kernel/Config.pm writable for the webserver user!
Go back to the previous page

Checking the Config.pm permissions, I see:

Code: Select all

[shaun@otrs-test Kernel]$ ls -l Config.pm
-rw-rw-r--. 1 otrs apache 4035 Apr 19 10:10 Config.pm
Any thoughts? This is driving me bonkers!
smurray
Znuny newbie
Posts: 12
Joined: 28 Mar 2012, 21:46
Znuny Version: 3.1.2
Real Name: Shaun
Company: PayFlex

Re: [solved] Permissions won't set for some odd reason

Post by smurray »

sudo setenforce 0

I hope that doesn't do something baaaaad. But that got it working for me. Disregard, ty Google! LoL
Giulio Soleni
Znuny wizard
Posts: 392
Joined: 30 Dec 2010, 14:35
Znuny Version: 6.0.x and 5.0.x
Real Name: Giulio Soleni
Company: IKS srl

Re: [solved] Permissions won't set for some odd reason

Post by Giulio Soleni »

Hi,
I am almost sure that your issue was due to the fact that SELinux is *STILL* enforced for your system.

This setting should be relaxed to permissive or disabled at all (that's what sudo setenforce 0 command does just temporarily)

You should disable SELinux permanently or else you may have that issue again after a system reboot.

To disable SELinux permanently you have to edit the /selinux/enforce file and modify the line

Code: Select all

SELINUX=enabled
to

Code: Select all

SELINUX=disabled
and then reboot...

you may check then the SELinux status with the command:

Code: Select all

selinuxenabled && echo enabled || echo disabled
OTRS 6.0.x on CentOS 7.x with MariaDB 10.2.x database connected to an Active Directory for Agents and Customers.
ITSM and FAQ modules installed.
Locked