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

    Feedbacks after FOG dev-branch Install on Virtualized Debian 7.9

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    2
    670
    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.
    • GreenItSolutionsG
      GreenItSolutions
      last edited by

      Hi all,
      After 3 days to resolve all bugs and misconfigurations, the system works fine now.

      We have encountered three majors problems :

      • DHCP starting error at installation
      • Password of fog user
      • Permissions on /images directory

      First : DHCP won’t start at installation

      • I don’t know why, but resolve by launching the install script a second time

      Second : Password of fog user

      • Because we launch the install script twice to solve first problem

      Third : Permissions on /images directory

      • Because the /images directory is a second disk mount by /etc/fstab AFTER script install
      • Change permissions to fog.root and chmod 777

      If i have more time, i will search for debug the DHCP install problem
      I think it will be a good idea if developer can add in the install script a verify permissions routine on /images and force if necessary.

      Thanks for this great project.

      Green IT Solutions - Linux & Open Source Solutions - Virtualization - IP Networks
      43, rue du 24 Fevrier - 79000 Niort (FR)

      1 Reply Last reply Reply Quote 1
      • george1421G
        george1421 Moderator
        last edited by george1421

        Thank you for your feedback. This is all good information for the Devs. I noticed you didn’t mention the version of FOG you installed. Did you install 1.2.0 stable, or a trunk build of 1.2.0 (i.e. 1.3.0 beta). I see that you stated you installed the dev branch (which is not a term we used). Could you reply with the numbers that are listed on the cloud from the management interface gui?

        I can’t speak to issue 1 of yours.

        As for 2, I’ve experienced this my self where the second time you run the script the OS password for the fog user gets updated but the information stored in the database is not, creating an inconsistent (i.e. broken) install.

        For 3, I wrote a kb article [ https://forums.fogproject.org/topic/6642/moving-fog-s-images-files-off-the-root-partition ] on how to create a similar setup as you have. The issue I see is that the /images and /opt/fog/snapins folder could potentially grow out of control unless you are managing the disk space properly.

        Thank you for taking the time to give the dev members great feedback and for taking the time to work with and use FOG. Its a great solution.

        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!

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

        146

        Online

        12.1k

        Users

        17.3k

        Topics

        155.3k

        Posts
        Copyright © 2012-2024 FOG Project