Testing SnipeIT on Fedora
-
Now I'm running into this issue:
https://github.com/snipe/snipe-it/issues/3787#issuecomment-325171989 -
@obsolesce said in Testing SnipeIT on Fedora:
Now I'm running into this issue:
https://github.com/snipe/snipe-it/issues/3787#issuecomment-325171989I think that's the issue they on their website too.
https://snipe-it.readme.io/v4.0/docs/upgrading-to-v4Known Issues Users running MariaDB 10.2.7 and later may have an issue upgrading or installing, due to a change in the way MariaDB stores null defaults. This issue will be fixed once the open pull request in the Doctrine repo is merged and a new version of Doctrine is released with these fixes. You can read more about that issue here. -
I found a way to get it going... steps incoming...
-
To install Snipe-IT on a fresh Fedora 28 minimal install:
- Install Fedora Server 28 minimal from NetISO.
- Okay to install the typical packages:
dnf install -y wget cockpit cockpit-storaged net-tools dnf-automatic - Download and run the Snipe-IT install script:
wget https://raw.githubusercontent.com/snipe/snipe-it/master/install.sh
chmod 744 install.sh
./install.sh - By default, the laravel log has bad permissions and needs to be fixed for Pre-Flight to work:
chmod 0755 /var/www/html/snipeit/storage/logs/laravel.log
chown apache:apache /var/www/html/snipeit/storage/logs/Laravel.log - By default, you won't be able to send mail with SELinux, allow it to:
setsebool -P httpd_can_network_connect 1
setsebool -P httpd_can_sendmail 1 - Pre-flight will now show and pass. Click the next button, it will fail. Then run this command to fix the DB issue:
reference: https://github.com/snipe/snipe-it/issues/5242#issue-307531010
mysql -u root -p
ALTER TABLE snipeit.assets CHANGE `_snipeit_mac_address` `_snipeit_mac_address_1` varchar(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL NULL ;
Now go back to the Pre-flight page, and it should continue on as normal.
-
What permissions should the .env file be set to?
As when I've done the manual git clone method the preflight keeps telling me to make sure it's protected from the outside world
-
@hobbit666 said in Testing SnipeIT on Fedora:
What permissions should the .env file be set to?
As when I've done the manual git clone method the preflight keeps telling me to make sure it's protected from the outside world
640 should be fine.
Are you able to browse to the .env file on your web browser? You should get a 404 when trying to.
-
@obsolesce it seemed to do that no matter what I set the permissions to
-
@obsolesce Gives me a oops something went wrong so guess it's alright.
-
@obsolesce Are you using MariaDB or MySQL? Also what versions.
I'm getting SQL Syntax errors on the pre-flight but looking on line i can see a post about version 10.2 causing issues.
-
Even the install script seem to be giving me jip as well.
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '''' at line 1 (SQL: ALTER TABLE assets CHANGE _snipeit_mac_address _snipeit_mac_address_1 VARCHAR(191) DEFAULT ''NULL'') -
@hobbit666 said in Testing SnipeIT on Fedora:
@obsolesce Are you using MariaDB or MySQL? Also what versions.
I'm getting SQL Syntax errors on the pre-flight but looking on line i can see a post about version 10.2 causing issues.
Even the install script seem to be giving me jip as well.
SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '''' at line 1 (SQL: ALTER TABLE assets CHANGE _snipeit_mac_address _snipeit_mac_address_1 VARCHAR(191) DEFAULT ''NULL'')
Oops should have looks up a bit can see @Obsolesce has already posted about this
-
@hobbit666 said in Testing SnipeIT on Fedora:
@obsolesce Are you using MariaDB or MySQL? Also what versions.
I'm getting SQL Syntax errors on the pre-flight but looking on line i can see a post about version 10.2 causing issues.
MariaDB, latest repo version... 10.2.
Look at #6 here:
@obsolesce said in Testing SnipeIT on Fedora:
To install Snipe-IT on a fresh Fedora 28 minimal install:
- Install Fedora Server 28 minimal from NetISO.
- Okay to install the typical packages:
dnf install -y wget cockpit cockpit-storaged net-tools dnf-automatic - Download and run the Snipe-IT install script:
wget https://raw.githubusercontent.com/snipe/snipe-it/master/install.sh
chmod 744 install.sh
./install.sh - By default, the laravel log has bad permissions and needs to be fixed for Pre-Flight to work:
chmod 0755 /var/www/html/snipeit/storage/logs/laravel.log
chown apache:apache /var/www/html/snipeit/storage/logs/Laravel.log - By default, you won't be able to send mail with SELinux, allow it to:
setsebool -P httpd_can_network_connect 1
setsebool -P httpd_can_sendmail 1 - Pre-flight will now show and pass. Click the next button, it will fail. Then run this command to fix the DB issue:
reference: https://github.com/snipe/snipe-it/issues/5242#issue-307531010
mysql -u root -p
ALTER TABLE snipeit.assets CHANGE `_snipeit_mac_address` `_snipeit_mac_address_1` varchar(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL NULL ;
Now go back to the Pre-flight page, and it should continue on as normal.
-
@obsolesce Yeah did your Alter table and i'm up and running and also imported my data from the old version.
Now to get it to work from behind a NGINX proxy
-
Now got issues adding machines, or doing anything add/edit wise. While in debug can see it all relating to the SQL stuff.
Guess its down to how i've exported and imported the database.
-
@hobbit666 said in Testing SnipeIT on Fedora:
Now got issues adding machines, or doing anything add/edit wise. While in debug can see it all relating to the SQL stuff.
Guess its down to how i've exported and imported the database.
Yeah probably due to that. I can add/edit fine using the instructions I provided.
-
@hobbit666 said in Testing SnipeIT on Fedora:
Now got issues adding machines, or doing anything add/edit wise. While in debug can see it all relating to the SQL stuff.
Guess its down to how i've exported and imported the database.
If oyu were not on the same version things will be bad.
because they update the database between versions for bugs or enhancemnts, etc. -
@obsolesce @JaredBusch
Yeah doing a clean install then will use the Export to CSV and re-import method so i can map the columns. -
@obsolesce said in Testing SnipeIT on Fedora:
To install Snipe-IT on a fresh Fedora 28 minimal install:
- Install Fedora Server 28 minimal from NetISO.
- Okay to install the typical packages:
dnf install -y wget cockpit cockpit-storaged net-tools dnf-automatic - Download and run the Snipe-IT install script:
wget https://raw.githubusercontent.com/snipe/snipe-it/master/install.sh
chmod 744 install.sh
./install.sh - By default, the laravel log has bad permissions and needs to be fixed for Pre-Flight to work:
chmod 0755 /var/www/html/snipeit/storage/logs/laravel.log
chown apache:apache /var/www/html/snipeit/storage/logs/Laravel.log - By default, you won't be able to send mail with SELinux, allow it to:
setsebool -P httpd_can_network_connect 1
setsebool -P httpd_can_sendmail 1 - Pre-flight will now show and pass. Click the next button, it will fail. Then run this command to fix the DB issue:
reference: https://github.com/snipe/snipe-it/issues/5242#issue-307531010
mysql -u root -p
ALTER TABLE snipeit.assets CHANGE `_snipeit_mac_address` `_snipeit_mac_address_1` varchar(191) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL NULL ;
Now go back to the Pre-flight page, and it should continue on as normal.
Backups via the SnipeIT Admin web interface won't work unless php-zip is installed:
dnf install php-zip -
New SnipeIT server all working with http://<Serverip>
But when i try and access through my proxy
https://nginx.domain.com i'm still getting:-
Do i need to configure the snipe server to be on https ??
-
@hobbit666 said in Testing SnipeIT on Fedora:
New SnipeIT server all working with http://<Serverip>
But when i try and access through my proxy
https://nginx.domain.com i'm still getting:-Do i need to configure the snipe server to be on https ??
What do you have set for
APP_URL=andAPP_TRUSTED_PROXIES=in the.envfile
