• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. george1421
    3. Posts
    • Profile
    • Following 1
    • Followers 64
    • Topics 113
    • Posts 15,322
    • Best 2,772
    • Controversial 0
    • Groups 2

    Posts made by george1421

    • RE: Access control plugin in Git 5572 add page not displayed

      @Tom-Elliott said:

      It is a viable plug in it just is not usable via database.

      @Wayne-Workman Yeah, this has me a bit confused. I read what Tom said as: its fully functional but you can’t configure it. I checked and I can’t seem to find a wiki on how to set this up.

      posted in Bug Reports
      george1421G
      george1421
    • RE: Kernel Panic issue

      I would also suspect the hard drive. Using other image deployment tools, I’ve seen them get part of the way through the image deployment and then bomb out (like ghost). It is usually related to a bad hard drive. We would just swap a hard drive in the system from inventory and reimage. If the imaging process went through then we would tag and discard the old drive. Based on my experience 4-5 years on a consumer hard drive is typically where we start to see system errors.

      If that system is a normal business system and is 4-5 years old, that would also increase the chances the hard drive has some bad sectors.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Tftp and missing files on storage nodes

      Yes the files are there now, thank you. I did update everything this AM before posting and the tftp stuff wasn’t installed. This will save having to hack a full fog install into a storage node. Thanks again.

      I did capture an error during the update that didn’t seem to have an impact on the tftp install.

      * Setting up storage..........................................OK
       * Setting up and starting DHCP Server.........................../lib/common/functions.sh: line 1264: [: : integer expression expected
      Skipped
       * Setting up and starting TFTP and PXE Servers................OK
       * Setting up and starting VSFTP Server........................OK
      
      

      Now I’m off to test the installed tftp files…

      posted in Feature Request
      george1421G
      george1421
    • RE: Tftp and missing files on storage nodes

      @Tom-Elliott The missing files are the entire /tftboot folder as well as installing the tftp service and updating xinetd (rhel specific). I’ll update one of my storage nodes right away and see if all of the bits are in place now.

      Thank you!

      posted in Feature Request
      george1421G
      george1421
    • RE: Access control plugin in Git 5572 add page not displayed

      @Tom-Elliott So then do I understand this is not a viable plugin just yet?

      I need to limit certain deployment techs to specific storage locations so that techs from site A can’t deploy images or snapins to site B on accident (or intent).

      posted in Bug Reports
      george1421G
      george1421
    • RE: TFTP Problems

      @bacelo Again, what is 10.1.8.254 ?? Who owns it?

      That is the device you need to set dhcp options 66 and 67 in/on. Once you do that, the pxe client should boot into the fog menu. My intuition is telling me that 10.1.8.254 is your firewall/internet router.

      Once you get that working, you MUST make sure that the dhcp server in fog is not used or you will have IP address conflicts.

      posted in FOG Problems
      george1421G
      george1421
    • RE: TFTP Problems

      @bacelo said:

      well the fogserver ip is 10.1.8.1

      Interesting, I though I would have seen this address in the PXE header. What is host 10.1.8.254? That is the object that is managing your DHCP for your site. If your fog server is 10.1.8.1 and you have it setup for dhcp, but your addresses are being handed out by 10.1.8.254 then your bootp values are probably not getting to the pxe client.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Installation Problem

      Just for accuracy we can mark this solved?

      I hope your issue will not reoccur. If its something related to FOG or the installer again, please post back to a new thread. Cheers.

      posted in FOG Problems
      george1421G
      george1421
    • RE: TFTP Problems

      @bacelo The error indicates that the tftp process could not download the file that is defined. Can we safely assume that 10.1.8.254 is the IP address of the FOG server (one might think that the .254 may be a router address in some installations)?

      posted in FOG Problems
      george1421G
      george1421
    • RE: Fog server keeps going down

      Right now I’m not saying do or don’t start over. But this has been an issue for 11 days now. What is going on is not normal. There is something wrong with this build. It could be that you are using a NAS for storage for FOG (I simply don’t know since I have not setup this situation). All I’m saying at some time in the (near) future you will need to deiced to just “cut bait” and start over or continue on and spend more time on this and not on deployment.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Installation Problem

      @guille_elia I do see some timeout command line switches that may be useful, but the wget response is a bit confusing to me. It looks like it tries the 192.30… address then it transfers to the 54.231… address and then finally download the file. From start to finish it looks like it took 52 seconds to actually get the file once it was located.

      Here are the timeout options with wget. Its not clear in my mind which one is at fault, since I don’t know what the default settings are. But I’m suspecting it was near the 302 redirect message.

      -T,  --timeout=SECONDS         set all timeout values to SECONDS.
            --dns-timeout=SECS        set the DNS lookup timeout to SECS.
            --connect-timeout=SECS    set the connect timeout to SECS.
            --read-timeout=SECS       set the read timeout to SECS.
       -w,  --wait=SECONDS            wait SECONDS between retrievals.
            --waitretry=SECONDS       wait 1..SECONDS between retries of a retrieval.
            --random-wait             wait from 0.5*WAIT...1.5*WAIT secs between retrievals.
      
      
      posted in FOG Problems
      george1421G
      george1421
    • RE: Fog server keeps going down

      For better or worse here, I have to be the voice of reason: At some point (in the near future) you have to make a decision to continue down the path to try to fix this install, or just abandon it and spin up a new fog instance and manually copy the files across.

      IMO something is botched with this OS install. This system should not become unavailable like this. How much effort are you going to expend on trying to revive this system, where spinning up a new OS and fog install can be done in about 30 minutes.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Tftp and missing files on storage nodes

      @Wayne-Workman That’s what I thought. There is no need to do extra stuff (again, trying to stay out of the OS as much as possible) for the non-technical / wiki following FOG installers. Its a simple change (in my mind) to the installer script that would make the storage nodes a bit more versatile with little to no expense in time or effort. I’m not seeing a performance or security issue by installing the pxe boot files or tftp service (other than every service that is installed is a potential attack vector). Everything we do out of band (i.e. doing a full install then hacking it later) risks brining in errors and extra work to maintain: IMO)

      posted in Feature Request
      george1421G
      george1421
    • RE: Access control plugin in Git 5572 add page not displayed

      @Sebastian-Roth http://<for_server_dns_name>/fog/management/index.php?node=accesscontrol&sub=add

      posted in Bug Reports
      george1421G
      george1421
    • RE: TFTP Problems

      @bacelo said:

      yes, I think so 🙂

      That is not a reassuring answer. Where do your clients get their dhcp addresses from?
      Are the clients on the same subnet as the FOG server?

      posted in FOG Problems
      george1421G
      george1421
    • RE: Need ability to unpublish captured image

      @Wayne-Workman I’ll have to confirm that. The last time I checked all files in the /images folder was replicated to the storage nodes even if they were not specifically called out in an image or the database. The only exception was if the images were in */dev and */ca.

      I can test this today since I just rebuilt the POC system this AM with the latest build. But again, I want to avoid having to dive into the OS to move things around. While I have the necessary skills to do this, not everyone will or should have the access to do this.

      posted in Feature Request
      george1421G
      george1421
    • RE: Installation Problem

      @Wayne-Workman Just looking at drawing a connection here. All three files (kernel, inits, client) are downloaded via wget. If wget is in place then DNS resolution may be another issue. But starting with manually downloading the client agent will give us a better idea of the error.

      posted in FOG Problems
      george1421G
      george1421
    • RE: Installation Problem

      Is wget installed? The installer uses wget to pick up the files from the sourceforge servers. I might also expect the database backup to fail too if wget wasn’t installed.

      If wget is installed then see if you can use wget to download the client image. There should be a warning message during the installer script. Copy that out and run it manually from the command line. That may give you a better understanding of the error.

      I have seen proxy servers give issues if things are not setup correctly (I have one in my current environment). But you stated that there is no proxy server, so we won’t go down that rabbit hole.

      posted in FOG Problems
      george1421G
      george1421
    • Tftp and missing files on storage nodes

      Update the installer script to add the logic to automatically install the tftp boot files onto a storage node. I understand that not all storage nodes will be used for pxe booting. But add the required files just in case the node will be used for PXE booting. There is no risk to having the boot files or the tftp service installed if not used (xinetd managed the starting of the tftp process anyway). By adding this function to the storage node you can avoid having to enter into the host os to manage the files, or setup rsync to copy the files from a pxe boot server as new versions come out.

      posted in Feature Request
      george1421G
      george1421
    • RE: Need ability to unpublish captured image

      The other folder route might work, but I don’t think I can capture an image to a different folder (??). As for the replication (unless something has changed recently) if a file exists in the /images folder the replicator will copy it dutifully to all nodes in the storage group. If you have a multi site setup the link at HQ is typically pretty utilized already. Adding additional useless traffic to that link is something we want to avoid.

      We can proceduralize this today if we setup a development FOG master node where the images are developed. Once we have the golden image, we could rsync it to the production master node and then manually create the image information on the production master node. While it should work it does require host OS access and someone with the authority and skill to do this. I’m trying to avoid diving into the OS for a solution to this if at all possible.

      posted in Feature Request
      george1421G
      george1421
    • 1
    • 2
    • 753
    • 754
    • 755
    • 756
    • 757
    • 766
    • 767
    • 755 / 767