• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    First installation -y option

    Scheduled Pinned Locked Moved
    Feature Request
    3
    4
    1.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Wayne WorkmanW
      Wayne Workman
      last edited by Wayne Workman

      The other day I tried to do a first-installation of the then-latest trunk version on a test server, I used ./installfog.sh -y just to see what would happen.

      It did automatically start and use all defaults which is fine, and when it got done, I browsed to x.x.x.x/fog/management and was presented with a db schema update page. I figured the -y argument would have taken care of this, but it’s probably something to do with a fresh brand-new installation.

      Just informing the @Developers about it. I don’t know if this is a bug or a feature request.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      W 1 Reply Last reply Reply Quote 0
      • W
        Wolfbane8653 Developer @Wayne Workman
        last edited by

        @Wayne-Workman

        This was a feature implemented in May-ish

        ./installfog.sh --help

        Usage: ./installfog.sh [-hdUuHSCKY] [-f <filename>] [-D </directory/to/document/root/>]
        [-W <webroot/to/fog/after/docroot/>] [-B </backup/path/>]
        [-s <192.168.1.10>] [-e 192.168.1.254] [-b <undionly.kpxe>]
        -h -? --help Display this info
        -d --no-defaults Don’t guess defaults
        -U --no-upgrade Don’t attempt to upgrade
        -H --no-htmldoc No htmldoc, means no PDFs
        -S --force-https Force HTTPS redirect
        -C --recreate-CA Recreate the CA Keys
        -K --recreate-keys Recreate the SSL Keys
        -Y -y --autoaccept Auto accept defaults and install
        -f --file Use different update file
        -D --docroot Specify the Apache Docroot for fog
        defaults to OS DocumentRoot
        -W --webroot Specify the web root url want fog to use
        (E.G. http://127.0.0.1/fog,
        http://127.0.0.1/)
        Defaults to /fog/
        -B --backuppath Specify the backup path
        –uninstall Uninstall FOG
        -s --startrange DHCP Start range
        -e --endrange DHCP End range
        -b --bootfile DHCP Boot file

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott
          last edited by

          Just guessing but did the database need to be updated? Was selinux enabled? Any error messages?

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          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)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          Wayne WorkmanW 1 Reply Last reply Reply Quote 0
          • Wayne WorkmanW
            Wayne Workman @Tom Elliott
            last edited by

            @Tom-Elliott I’ll reproduce and then let you know. I don’t think SELinux was on… This particular case is for a first-time installation on a new server build, I thought the -y option would auto update the DB for me, but it didn’t.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • First post
              Last post

            123

            Online

            12.1k

            Users

            17.3k

            Topics

            155.3k

            Posts
            Copyright © 2012-2024 FOG Project