Installing Snipe-IT on CentOS 7 and MariaDB

JaredBusch

@DustinB3403 said in Installing Snipe-IT on CentOS 7 and MariaDB:

If the process is just a git pull that'd be one thing, but nothing in the documentation (as far as I could find) says that.

no. that is the process to update the code. only if you had originally checked out the code via git.

The script does not do that. It downloads the tar.gz file and extracts the code.

		echo -e "\n##  Downloading Snipe-IT from github and put it in the web directory.";

		log "wget -P $tmp/ https://github.com/snipe/snipe-it/archive/$file"
		log "unzip -qo $tmp/$file -d $tmp/"
		log "cp -R $tmp/$fileName $webdir/$name"

I have no idea why when the script pulls from git on debian.

		echo -e "\n* Cloning Snipeit, extracting to $webdir/$name..."
		log "git clone https://github.com/snipe/snipe-it $webdir/$name" & pid=$!

I mean FFS, they are already installed a ton of dependencies on CentOS 7 so just install git as well, FFS.

Yes a double FFS was needed.

DustinB3403

@JaredBusch I'm on centos as well for this install.

As for this part

@JaredBusch said in Installing Snipe-IT on CentOS 7 and MariaDB:

no. that is the process to update the code. only if you had originally checked out the code via git.

Yes, I understand.

Which is why I'm a bit confused on the update process.

JaredBusch

@DustinB3403 said in Installing Snipe-IT on CentOS 7 and MariaDB:

@JaredBusch I'm on centos as well for this install.

As for this part

@JaredBusch said in Installing Snipe-IT on CentOS 7 and MariaDB:

no. that is the process to update the code. only if you had originally checked out the code via git.

Yes, I understand.

Which is why I'm a bit confused on the update process.

You download the archive and extract it over the top of the current files.

Then you run the update commands, I assume as the apache user (not noted in the instructions).

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload
php artisan migrate
php artisan config:clear
php artisan config:cache

JaredBusch

They updated the installer to handle SELinux. I shoudl try again without setenforce 0 sometime.

          	#Check if SELinux is enforcing
	       	if [ "$(getenforce)" == "Enforcing" ]; then
	 	       #Add SELinux and firewall exception/rules.
		       #Required for ldap integration
	       	       setsebool -P httpd_can_connect_ldap on
	 	       #Sets SELinux context type so that scripts running in the web server process are allowed read/write access
	 	       chcon -R -h -t httpd_sys_script_rw_t $webdir/$name/
 	       	fi

JaredBusch

@JaredBusch said in Installing Snipe-IT on CentOS 7 and MariaDB:

I mean FFS, they are already installed a ton of dependencies on CentOS 7 so just install git as well, FFS.

Even more than a double FFS is needed because they ARE INSTALLING GIT

0_1499723000183_1c68eaa1-5f5c-4d16-ac60-472a6e7046c3-image.png

The level of WTF FFS is so high right now......

JaredBusch

Pull request submitted.. just holy WTF....
https://github.com/snipe/snipe-it/pull/3734

JaredBusch

In theory I could have modified the CentOS 6 section also, but I have no easy way to test that so I skipped it.

JaredBusch

@jaredbusch said in Installing Snipe-IT on CentOS 7 and MariaDB:

Pull request submitted.. just holy WTF....
https://github.com/snipe/snipe-it/pull/3734

And merged. so there we go.
0_1499837757306_76128643-d0bb-488e-b499-0abb88050463-image.png

BoardinJunky

I got Snipe-IT on CentOS 7 up and running using the above commands and scripts. I'm a bit stuck on getting ldap to work though. I get 'can't contact server' even though doing a manual ldapsearch query on the server works without a problem. 'Test LDAP' on Snipe-IT settings page fails with 'can't contact server'.

I tried looking for logs and such but the only one I could find was laravel log, which only logs login attempts.

Is there a trick to getting ldap to work? Any help would be hugely appreciated

black3dynamite

@boardinjunky said in Installing Snipe-IT on CentOS 7 and MariaDB:

I got Snipe-IT on CentOS 7 up and running using the above commands and scripts. I'm a bit stuck on getting ldap to work though. I get 'can't contact server' even though doing a manual ldapsearch query on the server works without a problem. 'Test LDAP' on Snipe-IT settings page fails with 'can't contact server'.

I tried looking for logs and such but the only one I could find was laravel log, which only logs login attempts.

Is there a trick to getting ldap to work? Any help would be hugely appreciated

You might have to turn on httpd_can_connect_ldap
setsebool -P httpd_can_connect_ldap on;

BoardinJunky

@black3dynamite said in Installing Snipe-IT on CentOS 7 and MariaDB:

setsebool -P httpd_can_connect_ldap on

You sir, are an absolute genius! I spent hours searching online but didn't see a single mention of that command. Did I miss it somewhere obvious??

I don't suppose you have another trick up your sleeve for getting mail to work? No matter what I try, I get a "Swift_TransportException in StreamBuffer.php line 269: Connection could not be established with host. Permission denied #13".

Tried using internal SMTP relay as well as 365 mail and same permission denied error.

JaredBusch

Same thing

setsebool -P httpd_can_sendmail on

BoardinJunky

@jaredbusch damn. I've not seen those commands mentioned anywhere. That did the trick to get around the permission thing. Could you point me in the direction of where the mail logs get created? laravel log doesn't show any.

~~I'm getting a 'Success! Link has been sent', but no email is actually received and not sure where to trace it down further.~~

Nevermind! It's up and running! Thank you!

stacksofplates

It's weird because their script has the SELinux stuff in it.

JaredBusch

@stacksofplates said in Installing Snipe-IT on CentOS 7 and MariaDB:

It's weird because their script has the SELinux stuff in it.

Well one of the earlier posts breaks that process because we said to setenforce 0 prior to running the script.

But yeah, that would work if you did not disable it first.

stacksofplates

@jaredbusch said in Installing Snipe-IT on CentOS 7 and MariaDB:

@stacksofplates said in Installing Snipe-IT on CentOS 7 and MariaDB:

It's weird because their script has the SELinux stuff in it.

Well one of the earlier posts breaks that process because we said to setenforce 0 prior to running the script.

But yeah, that would work if you did not disable it first.

Ah missed that ok.

BoardinJunky

Is it possible to restrict sign-in to only a specific group in AD? The ldap filter only seems to apply for ldap import. No matter what base DN I pick, every user is able to login and account gets created. Eg, only allow login for staff group and not students.

DustinB3403

@boardinjunky said in Installing Snipe-IT on CentOS 7 and MariaDB:

Is it possible to restrict sign-in to only a specific group in AD? The ldap filter only seems to apply for ldap import. No matter what base DN I pick, every user is able to login and account gets created. Eg, only allow login for staff group and not students.

Once you sync, can't you disable individual users per their Snipe-IT account settings?

DustinB3403

On another note, it might be worth creating a feature request to simply import only a specific OU.

BoardinJunky

@dustinb3403 I'm able to get a single group to import via LDAP but I can't restrict login to ONLY that group.

We have several thousand users, badly organized, so disabling them after a full import would be a pain.

Ideally I'm looking to import a specific group via LDAP, which works at the moment, and then ONLY allow that group to login, which doesn't work. Anyone from the base DN can also login. I could turn off LDAP integration after doing the initial sync I guess but that means the passwords won't match after they change their AD ones.

I feel like this SHOULD be possible but I'm not sure if I'm missing something obvious again in the settings.