Fog Installer - Distro check



  • These distributions have completed 73 successful clean installations in a row using their latest patches with the FOG master branch:

    • CentOS 7
    • Debian 8
    • Debian 9
    • Ubuntu 16

    We’re still waiting for a single winner to rise above the rest. The race for most-stable distribution continues.


  • Moderator

    @wayne-workman Thank you for keeping focus on these distro checks!!



  • @sebastian-roth Looks like you fixed it, good job man.


  • Senior Developer

    @Wayne-Workman Ok, I just pushed a fix (hope I got that right) to the working branch. Let’s see if that’s doing the job. If so I might push it to dev-branch soon as well.



  • @sebastian-roth said in Fog Installer - Distro check:

    As we don’t backport fixes to the master branch this one will be screwed with Arch for a long time I am afraid.

    That’s how it should be. Also, looks like working branch failed again today.


  • Senior Developer

    @Wayne-Workman Thanks for that. Looking through it I found --with-gettext=shared in the compile options. So enabling the shared module still needs to be done. As Tom said this should be done by the installer. Ahhh, I think I know what’s up. The installer does regex-matching to enable the modules - see here:

    ...
    sed -i 's/;extension=gettext.so/extension=gettext.so/g' $phpini ...
    ...
    

    Now what changed in Arch is that they don’t use the .so extension in the configuration anymore. See here. I’ll fix our regex today.

    As we don’t backport fixes to the master branch this one will be screwed with Arch for a long time I am afraid.



  • @sebastian-roth Arch’s default apache root dir is very interesting: /srv/http
    Anyways, I added that file to there and when viewing it via browser, I don’t see any indicators that gettext is on. Here’s a copy of the page:
    https://mega.nz/#!EskiSSwT!Aj2px-ZMpwcDj90TBbpJRdB6G04AcBhrMR5WcPwlj6g


  • Senior Developer

    @sebastian-roth get text must be enabled in arch though I’m pretty sure we do this already.

    I am aware 7.2 removes native mcrypt functions though which will impact things such as the client authentication. I haven’t had time to figure out a better alternative to replace these calls yet sorry.


  • Senior Developer

    @Wayne-Workman Thanks for letting us know. Your tests distro tests are awesome man!

    Arch has gone from PHP 7.1.12 to 7.2 lately - see here. The function call _(...) is an alias for gettext(...) which is used for translation strings. But I haven’t found why there should be an issue with that yet.

    Can you do me a favor? On one of the Arch installations - if you still have one around - please create a file info.php in FOG web root directory with the following content:

    <?php
    phpinfo();
    ?>
    

    Save and open in browser http://x.x.x.x/fog/info.php to see if you can figure if gettext extension is on or not. On my server I see “GetText Support enabled”



  • Got a error on Arch across all branches this morning from apache:

    [Mon Dec 04 07:43:13.301115 2017] [proxy_fcgi:error] [pid 2547:tid 140160016578304] [client 10.0.0.26:34968] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught Error: Call to undefined function _() in /srv/http/fog/commons/text.php:22\nStack trace:\n#0 /srv/http/fog/commons/base.inc.php(41): require()\n#1 /srv/http/fog/management/index.php(22): require('/srv/http/fog/c...')\n#2 {main}\n  thrown in /srv/http/fog/commons/text.php on line 22\n'
    

    Looks like something in Arch’s repo broke this since it was in all branches. Other distributions are fine.


  • Moderator

    @wayne-workman Well done on the stats. I think we have a good bunch of winners already.



  • Wanted to post a quick status of the testing’s streaks. You can see them in the link in my signature.

    Currently, we have 4 Linux distributions that are neck & neck for the title of ultimate stability on the FOG Master branch.

    We have a current streak of 40 for these Linux distributions:

    • CentOS 7
    • Debian 8
    • Debian 9
    • Ubuntu 16

    We will see which Linux distribution pulls ahead in the long haul these coming months (and years). The race is ON!



  • FYI, lots of failures last night. On master branch, all Fedoras and Ubuntus failed, and then Ubuntu 17 failed on Dev branch - this is the only one that returned a log, it’s the ‘alter user’ mysql issue.

    I am re-running the tests for the master branch to see if the same results happen or not.



  • Between 1:40 AM and 2:44 AM CST, the Arch team likes to make changes. I can tell because working branch runs first, and succeeded with Arch, but later dev-branch and master failed with the same error.



  • Arch bombed out this morning on all branches - something to do with NFS. This is typical for Arch - one day it’ll just bomb out hard across the board on the same item, a couple days later it’s fixed. Once it was related to mariadb problems, today it’s NFS.

    Not trying to bash Arch here, there is a very small team working on Arch and they overall do a good job when you take into account their team size. Also stuff is going to break occasionally when you’re always making stuff better.

    On a side note, the streak counts seem to be working.



  • @george1421 I think I already know which ones will be most stable. ;-) I’ll keep quiet though and we’ll see how it goes.


  • Moderator

    Very nice job!! After some time we should be able to identify the most stable OS for FOG installs. This will really come in handy when thinking about which OS we might support in the future.



  • Streak counts are now public.



  • Soon, the fog installer dashboard (see my signature) will have streak counts for each item. There will be a current success streak and a record success streak.

    I’ve been wanting to do this for a while, I think it’ll be fun to watch the counts stack up. I’m monitoring the files for a couple days to be sure everything is working right before I put the values into the tables.

    0_1506691248592_streaks.png



  • The issues appear to have been non-issues in the latest tests. SELinux was not set to permissive (my fault).


Log in to reply
 

278
Online

7.1k
Users

14.3k
Topics

135.1k
Posts