Blank Install Page
-
@Sebastian-Roth I appreciate the community and open-source in general. Been using community driven products like CentOS and webmin/virtualmin for many years now. I’ve also come to expect a certain level of reliability in using them. not being able to install a product is usually a bad sign that things are not stable. Open source products work for folks when they work. I don’t want to debate or questions ones or a teams commitment or even diminish efforts, for that I am grateful. There is however a sense of reality in that one cant use and count on something if unstable. I get your all are now working on it. May I please make a valid suggestion based on the observation of a newcomer? Great thanks, perhaps say here… that Debin is (Recommended). I see 99% of most youtube videos on this app all using Debian and look at your own signature bloc where you say…
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
an there is no mention of CentOS. This confirms this community is in favor of Debian - which is totally fine. It sets expectations that Debian takes priority as its where most folks are at - hell I’d do the same too. My point here is I would not have spent so much time fighting something that is likely a bug and report it much sooner.Ill try the latest developer source. I don’t mind helping with testing at all and would be happy to. just trying to wrap my head around all of if. Plus I’m not a Linux admin normally - windows yes - for the record even with this bug herein ANYTHING has to be better than windows 10 stability. More and more I’m turning to Linux these days.
-
@dsoden Please re-read what you write…
I see 99% of most youtube videos on this app all using Debian and look at your own signature bloc where you say… Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log) an there is no mention of CentOS.
Just wrong!
My point here is I would not have spent so much time fighting something that is likely a bug and report it much sooner.
Not my problem.
-
@dsoden I just happen to see your mention of cent in the signature bock I saw debian/unbuntu: and stopped reading as I thought the rest was code for that platform. facepalm my bad… Debian is however IMO the most accepted and preferable platform for this system
-
@Sebastian-Roth wow - calm down man… apparently your one of those hyper sensitive folks with a massive ego made of glass! Your right its not your problem, it’s mine.
-
@Sebastian-Roth said in Blank Install Page:
latest developer source
latest developer source -> no go same outcome - and worse
LOG
[root@fogserver ~]# cat /var/log/httpd/error_log [Fri Nov 01 14:31:11.907383 2019] [core:notice] [pid 5797:tid 139840572270848] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0 [Fri Nov 01 14:31:11.909722 2019] [suexec:notice] [pid 5797:tid 139840572270848] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fe80::378d:ceba:514a:c75c. Set the 'ServerName' directive globally to suppress this message [Fri Nov 01 14:31:12.012179 2019] [lbmethod_heartbeat:notice] [pid 5797:tid 139840572270848] AH02282: No slotmem from mod_heartmonitor [Fri Nov 01 14:31:12.016303 2019] [mpm_event:notice] [pid 5797:tid 139840572270848] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1 configured -- resuming normal operations [Fri Nov 01 14:31:12.016340 2019] [core:notice] [pid 5797:tid 139840572270848] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' [root@fogserver ~]#
[root@fogserver ~]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: permissive Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 31 [root@fogserver ~]#
-**** NEW ****
one of the questions installer askes if you want to change host name - I said YES
changed to fogserver.local
never took…[root@fogserver ~]# hostname fogserver [root@fogserver ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 [root@fogserver ~]#
-
@dsoden @Sebastian-Roth @george1421
Please provide the error log from :
/var/log/php-fpm/www-error.log
This will provide the error causing your White Screen.
The issue with CentOS 8 is being addressed, but we need information.
You’re right that opensource works when it works, and believe me, we want to help and get this fixed.
Changing the hostname, for fog, does not change the hostname for the machine. This is more related to updating the SSL certificates based on the DNS Server.
The installer tries to do everything it can for you, but there are areas we try not to change, such as the physical machine hostname as there could be any number of reasons this is setup as such.
Can you explain how it’s things are worse?
I want to help, and I’m 100% sure we can get this fixed and running for you. I just need information to be able to do that. I actually have a CentOS 8 server running for testing at work.
No amount of bickering, backtalk, or anything (from anyone) is going to help that.
-
@Tom-Elliott said in Blank Install Page:
/var/log/php-fpm/www-error.log
[root@fogserver ~]# cat /var/log/php-fpm/www-error.log [01-Nov-2019 18:33:34 UTC] PHP Fatal error: Uncaught Error: Call to undefined function json_encode() in /var/www/html/fog/lib/db/pdodb.class.php:427 Stack trace: #0 /var/www/html/fog/lib/db/pdodb.class.php(230): PDODB->sqlerror() #1 /var/www/html/fog/lib/db/pdodb.class.php(171): PDODB::currentDb(Object(PDODB)) #2 /var/www/html/fog/lib/db/pdodb.class.php(180): PDODB->_connect(false) #3 /var/www/html/fog/lib/db/pdodb.class.php(103): PDODB->_connect() #4 /var/www/html/fog/lib/db/databasemanager.class.php(61): PDODB->__construct() #5 /var/www/html/fog/lib/fog/loadglobals.class.php(43): DatabaseManager::establish() #6 /var/www/html/fog/lib/fog/loadglobals.class.php(81): LoadGlobals::_init() #7 /var/www/html/fog/commons/base.inc.php(49): LoadGlobals->__construct() #8 /var/www/html/fog/management/index.php(22): require('/var/www/html/f...') #9 {main} thrown in /var/www/html/fog/lib/db/pdodb.class.php on line 427 [root@fogserver ~]#
worse because I assumed the question about changing the hostname… well changed the hostname of the system and app somehow, odd question if one does not have the context you provided above. That makes sense. Also I had not used that question till the last install round (like on #10 now) and when I did not see it work I figured more bugs.
-
@dsoden Please run: dnf -y install php-json
-
@Tom-Elliott said in Blank Install Page:
install php-json
I did a standard install and found a few things in the install script. I got to installing the schema and got the white screen of the OP. I went and check php-fpm error log and found the same error as the OP.
Installing php-json pushed the install forward. Then went back to web ui and installed the schema and the following error was thrown in the web ui.
Update ID: 16 Database Error: Failed to query: Error: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IDENTIFIED BY 'fs55548845957'' at line 1 Error Message: Error Code: "42000", Error Message: ["42000",1064,"You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IDENTIFIED BY 'fs55548845957'' at line 1"], Debug: SQL: [70] GRANT ALL ON `fog`.* TO 'fogstorage'@'%' IDENTIFIED BY 'fs55548845957' Params: 0 Variable contains: Array ( [0] => ALTER TABLE `tasks` ADD COLUMN `taskBPM` varchar(250) NOT NULL AFTER `taskPCT`, ADD COLUMN `taskTimeElapsed` varchar(250) NOT NULL AFTER `taskBPM`, ADD COLUMN `taskTimeRemaining` varchar(250) NOT NULL AFTER `taskTimeElapsed`, ADD COLUMN `taskDataCopied` varchar(250) NOT NULL AFTER `taskTimeRemaining`, ADD COLUMN `taskPercentText` varchar(250) NOT NULL AFTER `taskDataCopied`, ADD COLUMN `taskDataTotal` VARCHAR(250) NOT NULL AFTER `taskPercentText` [1] => CREATE TABLE `nfsGroups` (`ngID` integer NOT NULL AUTO_INCREMENT,`ngName` varchar(250) NOT NULL,`ngDesc` longtext NOT NULL,PRIMARY KEY (`ngID`)) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC [2] => CREATE TABLE `nfsGroupMembers` (`ngmID` integer NOT NULL AUTO_INCREMENT,`ngmMemberName` varchar(250) NOT NULL,`ngmMemberDescription` longtext NOT NULL,`ngmIsMasterNode` char NOT NULL,`ngmGroupID` integer NOT NULL,`ngmRootPath` longtext NOT NULL,`ngmIsEnabled` char NOT NULL,`ngmHostname` varchar(250) NOT NULL,`ngmMaxClients` integer NOT NULL,`ngmUser` varchar(250) NOT NULL,`ngmPass` varchar(250) NOT NULL,`ngmKey` varchar(250) NOT NULL, PRIMARY KEY (`ngmID`),INDEX `new_index`(`ngmMemberName`),INDEX `new_index2`(`ngmIsMasterNode`),INDEX `new_index3`(`ngmGroupID`),INDEX `new_index4`(`ngmIsEnabled`)) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC [3] => ALTER TABLE `images` ADD COLUMN `imageNFSGroupID` integer NOT NULL AFTER `imageDD`,ADD INDEX `new_index3`(`imageNFSGroupID`) [4] => ALTER TABLE `tasks` ADD COLUMN `taskNFSGroupID` integer NOT NULL AFTER `taskDataTotal`,ADD COLUMN `taskNFSMemberID` integer NOT NULL AFTER `taskNFSGroupID`,ADD COLUMN `taskNFSFailures` char NOT NULL AFTER `taskNFSMemberID`,ADD COLUMN `taskLastMemberID` integer NOT NULL AFTER `taskNFSFailures`,ADD INDEX `new_index5`(`taskNFSGroupID`),ADD INDEX `new_index6`(`taskNFSMemberID`),ADD INDEX `new_index7`(`taskNFSFailures`),ADD INDEX `new_index8`(`taskLastMemberID`) [5] => CREATE TABLE `nfsFailures` (`nfID` integer NOT NULL AUTO_INCREMENT,`nfNodeID` integer NOT NULL,`nfTaskID` integer NOT NULL,`nfHostID` integer NOT NULL,`nfGroupID` integer NOT NULL,`nfDateTime` integer NOT NULL,PRIMARY KEY (`nfID`),INDEX `new_index`(`nfNodeID`),INDEX `new_index1`(`nfTaskID`),INDEX `new_index2`(`nfHostID`),INDEX `new_index3`(`nfGroupID`)) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC [6] => ALTER TABLE `nfsFailures` MODIFY COLUMN `nfDateTime` datetime NOT NULL,ADD INDEX `new_index4`(`nfDateTime`) [7] => ALTER TABLE `multicastSessions` CHANGE `msAnon2` `msNFSGroupID` integer NOT NULL, ADD INDEX `new_index`(`msNFSGroupID`) [8] => INSERT IGNORE INTO `nfsGroups` (`ngName`,`ngDesc`) VALUES ('default','Auto generated fog nfs group') [9] => INSERT IGNORE INTO `nfsGroupMembers` (`ngmMemberName`,`ngmMemberDescription`,`ngmIsMasterNode`,`ngmGroupID`,`ngmRootPath`,`ngmIsEnabled`,`ngmHostname`,`ngmMaxClients`,`ngmUser`,`ngmPass`) VALUES ('DefaultMember','Auto generated fog nfs group member','1','1','/images/','1','10.96.151.182','10','fog','Jq2ddrAigb4iMEAjsg0Ez6U0nb5n52nZRBY5RyJ5CC0=') [10] => UPDATE `images` set imageNFSGroupID = '1' [11] => DELETE FROM `globalSettings` WHERE `settingKey` IN ('FOG_NFS_HOST','FOG_NFS_FTP_USERNAME','FOG_NFS_FTP_PASSWORD','FOG_NFS_DATADIR','FOG_NFS_DATADIR_CAPTURE') [12] => INSERT IGNORE INTO `globalSettings` (`settingKey`,`settingDesc`,`settingValue`,`settingCategory`) VALUES ('FOG_STORAGENODE_MYSQLUSER','This setting defines the username the storage nodes should use to connect to the fog server.','fogstorage','FOG Storage Nodes'),('FOG_STORAGENODE_MYSQLPASS','This setting defines the password the storage nodes should use to connect to the fog server.','fs55548845957','FOG Storage Nodes') [13] => GRANT ALL ON `fog`.* TO 'fogstorage'@'%' IDENTIFIED BY 'fs55548845957' [14] => UPDATE `schemaVersion` set `vValue`='16' ) Database SQL: GRANT ALL ON `fog`.* TO 'fogstorage'@'%' IDENTIFIED BY 'fs55548845957'
I’m currently working through this error.
-
@george1421 Can you run from MYSQL root user:
SHOW GRANTS FOR fogstorage;
-
@george1421 And this is from Master branch I take it? As this is what shows up, now, for the dev-branch and working-1.6
"DELETE FROM mysql.user WHERE user='$fogstoragenodeuser'", "CREATE USER '$fogstoragenodeuser'@'%' IDENTIFIED BY '$fogstoragenodepass'", "GRANT ALL PRIVILEGES ON `" . DATABASE_NAME . "`.* TO '$fogstoragenodeuser'@'%'",
Master is not as far forward as dev-branch is.
-
@Tom-Elliott I’m still pecking at it. But this is what I know so far.
This is failingGRANT USAGE ON 'fog'.* TO 'fogstorage'@'%' IDENTIFIED BY 'fs55548845957';
But I can get the same results with.
create user 'fogstorage'@'%' IDENTIFIED BY 'fs55548845957'; grant all on fog.* to 'fogstorage'@'%';
It was throwing an error on the grant all with single quotes around fog in fog.*
-
@george1421 Probably need to delete the user entirely.
-
@Tom-Elliott I switched to working is that not the right one?
-
@george1421 working-1.6 or dev-branch are the branches you should be on. I don’t think we have a branch named just working anymore.
-
@Tom-Elliott said in Blank Install Page:
SHOW GRANTS FOR fogstorage;
in catching up I got the same SQL errors
Running the show grants does this
mysql> SHOW GRANTS FOR fogstorage; ERROR 1141 (42000): There is no such grant defined for user 'fogstorage' on host '%'
in trying to re run the command in the browser
GRANT ALL ON `fog`.* TO 'fogstorage'@'%' IDENTIFIED BY 'fs94543688031'
I get this
mysql> GRANT ALL ON `fog`.* TO 'fogstorage'@'%' IDENTIFIED BY 'fs94543688031' -> ; ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IDENTIFIED BY 'fs94543688031'' at line 1 mysql>
My version is
mysql> select @@version -> ; +-----------+ | @@version | +-----------+ | 8.0.17 | +-----------+ 1 row in set (0.00 sec)
-
@dsoden hold on, we found something and fixed something else. Tom and I are chatting at the moment. The 1.6 beta installs (almost) correctly on centos 8 1905
-
@dsoden Mind ensuring your running on dev-branch?
The IDENTIFIED BY line has been moved from the GRANT line to it’s own line due to CentOS 8 having a version of Mysql that’s’ newer. We have to separate the generation of the user.
@george1421 and I are chatting in the background, we haven’t just left things alone, just need realtime assist.
-
@Tom-Elliott @george1421 all good then Ill check back after a period of time.
I’m using the public download version again because nothing was working.
kinda getting lost where I’m suppose to be. Once you have things sorted let me know and Ill run a full clean test on my side - thanks! -
@dsoden Where you are at right now exit out of the installer and open
mysql -u root -p
Then clean up the residue.
DROP USER IF EXISTS 'fogstorage'@'%'; DROP DATABASE fog;
Then switch back to the root of the fogproject that was downloaded.
and issue this commandgit checkout working-1.6
then change back to
bin
and rerun the fog installer. You will see an error message about the firewall, but just go past that for the moment.