Installing Snipe-IT on CentOS 7 and MariaDB
-
@JaredBusch I left anonymous users and allowed root login remotely. Those are the only other changes I made other than FQDN name
-
@Robblehead said in Installing Snipe-IT on CentOS 7 and MariaDB:
@JaredBusch I left anonymous users and allowed root login remotely. Those are the only other changes I made other than FQDN name
Those should never be allowed. That is database access not the CentOS access.
-
@JaredBusch ok
-
-
-
@JaredBusch You have made fire! https://rockloveaustin.files.wordpress.com/2014/11/castaway.gif
-
@Robblehead You will want to properly get that DNS entry in your router or something so that all your devices work.
Editing your hosts file should only be a quick workaround that is used temporarily.
-
@JaredBusch One last question, this is a test environment. When I move into production it will have a new IP address which shouldn't be a big deal but I am wondering if I will have to modify host file of every system that will be using snipe?
-
@JaredBusch answered my question for me. The production environment is running a sonicwall so I am pretty sure I can handle that side with Dell's help. (I know it's capable)
-
@Robblehead said in Installing Snipe-IT on CentOS 7 and MariaDB:
@JaredBusch One last question, this is a test environment. When I move into production it will have a new IP address which shouldn't be a big deal but I am wondering if I will have to modify host file of every system that will be using snipe?
Don't modify the local host file, use a proper DNS entry on your router (or DNS server if you have one)
-
@DustinB3403 said in Installing Snipe-IT on CentOS 7 and MariaDB:
@Robblehead said in Installing Snipe-IT on CentOS 7 and MariaDB:
@JaredBusch One last question, this is a test environment. When I move into production it will have a new IP address which shouldn't be a big deal but I am wondering if I will have to modify host file of every system that will be using snipe?
Don't modify the local host file, use a proper DNS entry on your router (or DNS server if you have one)
I already answered that as he posted in his next post.
-
@Robblehead said in Installing Snipe-IT on CentOS 7 and MariaDB:
@JaredBusch answered my question for me. The production environment is running a sonicwall so I am pretty sure I can handle that side with Dell's help. (I know it's capable)
Your problem is you will not be able to use DNS like you need because of this.
@Robblehead said in Installing Snipe-IT on CentOS 7 and MariaDB:
@DustinB3403 my router is pushing OpenDNS to all devices, would this be part of the issue? My laptop maybe not using same DNS?
You have no local DNS. So you are going to have to change your entire network or be stuck changing the hosts file on every single device that needs to use Snipe-IT.
You should never be pushing out a non local DNS source to your machines.
If you want to use OpenDNS, then you set your router to use OpenDNS and then you set your clients to use your router.
-
Jared is correct, even if it is only a cache (effectively) you want a local DNS server in all cases, even at home.
-
@Robblehead
Your fqdn should be like snipeit.abc.new
in your router or host file write a custom dns as
192.168.1.10 snipeit.abc.new
Now from your browser http://snipeit.abc.new
it will work. -
@brandon.hay
ignore this error,go to your browser http://your fqdn
and complete the remaining process via snipeit
it will work.
Tested. -
@Amit-Shrestha thanks for hopping in.
-
Just trying this myself again and i'm getting the below error after running
setenforce 0 && mkdir -p /var/www/html; cd /var/www/html/; wget https://raw.githubusercontent.com/snipe/snipe-it/master/install.sh && chmod 744 install.sh && ./install.sh && cd snipeit; sed -i "s/'timezone' => '',/'timezone' => 'UTC',/" app/config/app.php; php artisan app:install [Symfony\Component\Console\Exception\CommandNotFoundException] Command "app:install" is not defined. Did you mean one of these? migrate:install app:name -
@DustinB3403 said in Installing Snipe-IT on CentOS 7 and MariaDB:
Just trying this myself again and i'm getting the below error after running
setenforce 0 && mkdir -p /var/www/html; cd /var/www/html/; wget https://raw.githubusercontent.com/snipe/snipe-it/master/install.sh && chmod 744 install.sh && ./install.sh && cd snipeit; sed -i "s/'timezone' => '',/'timezone' => 'UTC',/" app/config/app.php; php artisan app:install [Symfony\Component\Console\Exception\CommandNotFoundException] Command "app:install" is not defined. Did you mean one of these? migrate:install app:nameThe
snipeit.shfile was updated recently. -
I attempted to install via the install.sh script and it got most of the way through without error. Then, toward the end of the script, I get this:
----Begin Paste----Setting up hosts file.
Starting the apache server.
Created symlink from /etc/systemd/system/multi-user.target.wants/httpd.service to /usr/lib/systemd/system/httpd.service.
Configuring .env file.
All settings correct for using Composer
Downloading...Composer (version 1.4.2) successfully installed to: /var/www/html/snipeit/composer.phar
Use it: php composer.pharDo not run Composer as root/super user! See https://getcomposer.org/root for details
Loading composer repositories with package information
Installing dependencies from lock file
Your requirements could not be resolved to an installable set of packages.Problem 1
- This package requires php >=5.5.9 but your PHP version (5.4.16) does not satisfy that requirement.
Problem 2
- Installation request for aws/aws-sdk-php 3.19.2 -> satisfiable by aws/aws-sdk-php[3.19.2].
- aws/aws-sdk-php 3.19.2 requires php >=5.5 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 3
- Installation request for aws/aws-sdk-php-laravel 3.1.0 -> satisfiable by aws/aws-sdk-php-laravel[3.1.0].
- aws/aws-sdk-php-laravel 3.1.0 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 4
- Installation request for barryvdh/laravel-debugbar V2.2.3 -> satisfiable by barryvdh/laravel-debugbar[V2.2.3].
- barryvdh/laravel-debugbar V2.2.3 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 5
- Installation request for classpreloader/classpreloader 3.0.0 -> satisfiable by classpreloader/classpreloader[3.0.0].
- classpreloader/classpreloader 3.0.0 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 6
- Installation request for guzzlehttp/guzzle 6.2.1 -> satisfiable by guzzlehttp/guzzle[6.2.1].
- guzzlehttp/guzzle 6.2.1 requires php >=5.5 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 7
- Installation request for guzzlehttp/promises 1.2.0 -> satisfiable by guzzlehttp/promises[1.2.0].
- guzzlehttp/promises 1.2.0 requires php >=5.5.0 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 8
- Installation request for laravel/framework v5.2.45 -> satisfiable by laravel/framework[v5.2.45].
- laravel/framework v5.2.45 requires ext-mbstring * -> the requested PHP extension mbstring is missing from your system.
Problem 9
- Installation request for laravelcollective/html v5.2.4 -> satisfiable by laravelcollective/html[v5.2.4].
- laravelcollective/html v5.2.4 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 10
- Installation request for league/csv 7.2.0 -> satisfiable by league/csv[7.2.0].
- league/csv 7.2.0 requires ext-mbstring * -> the requested PHP extension mbstring is missing from your system.
Problem 11
- Installation request for maknz/slack dev-master -> satisfiable by maknz/slack[dev-master].
- maknz/slack dev-master requires ext-mbstring * -> the requested PHP extension mbstring is missing from your system.
Problem 12
- Installation request for spatie/db-dumper 1.5.1 -> satisfiable by spatie/db-dumper[1.5.1].
- spatie/db-dumper 1.5.1 requires php ^5.5|^7.0 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 13
- Installation request for spatie/laravel-backup 3.8.1 -> satisfiable by spatie/laravel-backup[3.8.1].
- spatie/laravel-backup 3.8.1 requires php ^5.5|^7.0 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 14
- Installation request for symfony/console v3.0.9 -> satisfiable by symfony/console[v3.0.9].
- symfony/console v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 15
- Installation request for symfony/debug v3.0.9 -> satisfiable by symfony/debug[v3.0.9].
- symfony/debug v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 16
- Installation request for symfony/event-dispatcher v3.1.3 -> satisfiable by symfony/event-dispatcher[v3.1.3].
- symfony/event-dispatcher v3.1.3 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 17
- Installation request for symfony/finder v3.0.9 -> satisfiable by symfony/finder[v3.0.9].
- symfony/finder v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 18
- Installation request for symfony/http-foundation v3.0.9 -> satisfiable by symfony/http-foundation[v3.0.9].
- symfony/http-foundation v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 19
- Installation request for symfony/http-kernel v3.0.9 -> satisfiable by symfony/http-kernel[v3.0.9].
- symfony/http-kernel v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 20
- Installation request for symfony/process v3.0.9 -> satisfiable by symfony/process[v3.0.9].
- symfony/process v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 21
- Installation request for symfony/routing v3.0.9 -> satisfiable by symfony/routing[v3.0.9].
- symfony/routing v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 22
- Installation request for symfony/translation v3.0.9 -> satisfiable by symfony/translation[v3.0.9].
- symfony/translation v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 23
- Installation request for symfony/var-dumper v3.0.9 -> satisfiable by symfony/var-dumper[v3.0.9].
- symfony/var-dumper v3.0.9 requires php >=5.5.9 -> your PHP version (5.4.16) does not satisfy that requirement.
Problem 24
- laravel/framework v5.2.45 requires ext-mbstring * -> the requested PHP extension mbstring is missing from your system.
- watson/validating 2.2.2 requires illuminate/contracts ~5.0 <5.3 -> satisfiable by laravel/framework[v5.2.45].
- Installation request for watson/validating 2.2.2 -> satisfiable by watson/validating[2.2.2].To enable extensions, verify that they are enabled in your .ini files:
- /etc/php.ini
- /etc/php.d/curl.ini
- /etc/php.d/dom.ini
- /etc/php.d/fileinfo.ini
- /etc/php.d/gd.ini
- /etc/php.d/json.ini
- /etc/php.d/pdo.ini
- /etc/php.d/pdo_sqlite.ini
- /etc/php.d/phar.ini
- /etc/php.d/posix.ini
- /etc/php.d/sqlite3.ini
- /etc/php.d/sysvmsg.ini
- /etc/php.d/sysvsem.ini
- /etc/php.d/sysvshm.ini
- /etc/php.d/wddx.ini
- /etc/php.d/xmlreader.ini
- /etc/php.d/xmlwriter.ini
- /etc/php.d/xsl.ini
- /etc/php.d/zip.ini
You can also runphp --iniinside terminal to see which files are used by PHP in CLI mode.If you want mail capabilities, edit /var/www/html/snipeit/.env and edit based on .env.example
Open http://monitor.alaska.lan to login to Snipe-IT.
- Cleaning up...
- Finished!
----End Paste----
So, in short, it appears that the script relies on PHP being at a version higher than the one that ships with CentOS 7.3. Has anyone found a way around this yet? I've seen a few different HOWTO's where it's mentioned to install the remi or webtatic repo's to get the higher versions of PHP, but composer continues to complain. Thankfully, this was a VM and I was able to create a snapshot before making changes from the baseline.
-
@lmindnix said in Installing Snipe-IT on CentOS 7 and MariaDB:
I attempted to install via the install.sh script and it got most of the way through without error. Then, toward the end of the script, I get this:
----Begin Paste----
----End Paste----So, in short, it appears that the script relies on PHP being at a version higher than the one that ships with CentOS 7.3. Has anyone found a way around this yet? I've seen a few different HOWTO's where it's mentioned to install the remi or webtatic repo's to get the higher versions of PHP, but composer continues to complain. Thankfully, this was a VM and I was able to create a snapshot before making changes from the baseline.
The script installs the correct version of PHP. It adds the IUS repo specifically for that.
