• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. mpmackenna
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 25
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by mpmackenna

    • mpmackennaM

      Unable to build FOS

      General Problems
      • • • mpmackenna
      16
      0
      Votes
      16
      Posts
      1.6k
      Views

      S

      @mpmackenna said in Unable to build FOS:

      Unfortunately, that is the only output I receive. The screen just hangs with the print statement displayed and never progresses past that statement.

      Well that’s a perfect start to get into debugging where exactly it hangs. Simply add more of those efi_printk further down that function and possibly as well in sub functions called by efi_main. In other models we often saw issues with PCI initialization. You’ll see that code a bit further down.

    • mpmackennaM

      Install hangs at "Ensuring node username and passwords match"

      FOG Problems
      • • • mpmackenna
      22
      0
      Votes
      22
      Posts
      3.0k
      Views

      mpmackennaM

      @george1421 I replicated my images using rsync and verified that all images are in both locations. I also have a backup of my images off of both of the nodes. I went in and I created a new Storage Group. I associated the Storage Node that is not the Master Server with the new Storage Group. I then associated a number of my images with that Storage Group. My goal is to have some images only reside on the node in the new Storage Group and some only reside on the other Storage Group. I set both servers to be the Master Node for their Storage Group. Based on the warning I read about setting a server to the Master Node I half-way expected for any images that were not associated with that Storage Group to be purged from the Master Node but that didn’t seem to happen, which is fine. Is it now safe to go back and purge images from servers via cli if they reside in an image store on a node that is not in the Storage Group that is associated with that image? Thank you!

    • mpmackennaM

      Failed to connect to database server, will try again in next iteration.

      FOG Problems
      • • • mpmackenna
      48
      0
      Votes
      48
      Posts
      43.4k
      Views

      C

      [quote=“mpmackenna, post: 893, member: 373”]
      [LEFT][COLOR=#333333]I have the below error over and over again in my FOG log viewer. I checked to see if my /var/www/fog/commons/config.php file had the correct settings and it does. I also was able to log in to the mysql db on the fog box without trouble. The db is on the same local machine as the FOG installation. Can someone please tell me how I can further troubleshoot this error?[/COLOR][/LEFT]
      [LEFT][COLOR=#333333]I am running FOG 0.32 on Debian 5.[/COLOR][/LEFT]
      [LEFT][COLOR=#333333]Thanks,[/COLOR][/LEFT]
      [LEFT][COLOR=#333333]Mike[/COLOR][/LEFT]
      [LEFT][COLOR=#333333][01-30-12 1:12:13 pm] Failed to connect to database server, will try again in next iteration.[/COLOR][/LEFT]
      [LEFT][COLOR=#333333][01-30-12 1:12:23 pm] Failed to connect to database server, will try again in next iteration.[/COLOR][/LEFT]
      [/quote]
      My problems with task hanging and getting [COLOR=#333333]“Failed to connect to database server” messages, [/COLOR]were solved by changing “WOL_INTERFACE”, “eth0” from 0 to “eth1” in both config files
      /var/www/fog/commons/config.php
      and
      /opt/fog/service/etc/config.php

    • 1 / 1