• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tom Elliott
    3. Posts
    • Profile
    • Following 27
    • Followers 80
    • Topics 116
    • Posts 18,782
    • Best 2,568
    • Controversial 0
    • Groups 0

    Posts made by Tom Elliott

    • RE: Bugs in FOG 0.33

      Another minor issue that I’ve so far noticed is:

      Reports, all of the pages will not work and it appears it’s because it has to communicate with the database. This communication is lost because the mysql_query statements within this pages look to be sending to a variable $conn that doesn’t exist for those pages. Also, as it needs to communicate with the database, the base configuration files are not existing either. My best suggestion would be to make a configuration file that stores the references needed within a file called something like base.inc.php that includes the base required files of commons/init.php commons/init.database.php. For the $conn variable, suggest an include statement of the base.inc.php so that the $conn system can be accessed even though it’s not directly defined in the file. So, basically, all main files should have an include BASEPATH . ‘commons/base.inc.php’; statement in them. This would also work for all other file that request this same information.

      Found out that Pending MACs.php file the reference to class HostManager works if called like this:

      $hostMan = new HostManager(); Rather than
      $hostMan = $FOGCore->getClass(‘HostManager’);

      Fixed and working on my side.

      My base.inc.php file is:

      <?php
      /* This file just stores the heading information for including *

      • In the FOG System. This should minimize code lines. *
      •                                                         */      
        

      if (!defined(‘BASEBATH’))
      require_once(‘system.php’);
      require_once(BASEPATH . ‘/commons/config.php’);
      require_once(BASEPATH . ‘/commons/init.php’);
      require_once(BASEPATH . ‘/commons/init.database.php’);
      $conn = @mysql_connect( DATABASE_HOST, DATABASE_USERNAME, DATABASE_PASSWORD);
      ?>

      and is located in commons.

      Then added the line to the files needed. Though I guess in the management/index.php all you should need is the reference :

      include ‘…/commons/base.inc.php’;
      In the reports *.php files.
      include BASEPATH . ‘/commons/base.inc.php’;

      posted in Bug Reports
      Tom ElliottT
      Tom Elliott
    • RE: Bugs in FOG 0.33

      Found out a few things.

      The init.gz fog.man.reg script for full host registration is broken. (EDIT: Not broken just not appropriate as OSID is now based on Image rather than per system.)

      This is because, your mysql database for fog removes the table from hosts hostOS. This itself isn’t a huge deal as I think your method of assigning the OSID to the image file rather than each system is more appropriate. But your scripts need to be adjusted to make this modification. fog.man.reg doesn’t need to get the host osid and should be removed. I’ve updated the file and will post it as soon as I can.

      Also, under this same issue, the /var/www/html/fog/service/auto.register.php file needs to stop trying to put in the hostOS field as it will fail due to the table not existing in the first place. Removing all references for osid realosid and hostOS seems to have corrected this issue, I will post this file as well when i have more time. I’ve modified them to help out in my little way. I’ve also modified the /var/www/html/fog/management/reports/Inventory.php file to work more appropriately as well so it pulls it imageOSID rather than trying to pull information from a non-existent table which will cause failure.

      I hope I’m not stepping on anyone’s shoes here and have helped out in my little way.

      Also, if anyone’s interested, I’ve created my own init.gz and bzImage to work off of the most current kernels (3.10.5). The init.gz file has bash included with it as well.

      EDIT:

      Got the files and they are now attached.

      auto.register.php should be a simple placement into {fogwebdir}/service/ , and I’m sure you could leave the original fog.man.reg file in place with osid inputs because the auto.register.php ultimately is in charge of writing the data to the database.

      For nice housekeeping, the fog.man.txt just needs to be renamed (as the forums won’t allow an upload of a file ending in extension .reg) and chmod’ed as necessary within the init.gz /bin directory.

      Hopefully this helps. Thank you,

      [url=“/_imported_xf_attachments/0/359_auto.register.php?:”]auto.register.php[/url][url=“/_imported_xf_attachments/0/360_fog.man.txt?:”]fog.man.txt[/url]

      posted in Bug Reports
      Tom ElliottT
      Tom Elliott
    • 1 / 1