• Help changing from pxelinux.0 to undionly.kpxe (Boot Menu)

    7
    0 Votes
    7 Posts
    7k Views
    Tom ElliottT

    I’ve now added the ability to add “individual” password login settings to menu items
    My current menu that is tested and working, although very minimal, is:
    [code]isset ${userID} && goto do_me || goto MENU
    :do_me
    kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
    imgfetch init.xz && boot || goto MENU
    :MENU
    menu
    item --gap Please Select one of the images below
    item fog.local Boot from hard disk
    item d101_64 D101 Base Image (64 bit load)
    item return Return to main menu
    choose --default fog.local target && goto ${target}
    :fog.local
    sanboot --no-describe --drive 0x80 || goto MENU
    :d101_64
    chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
    :return
    chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
    autoboot[/code]

    Notice the :d101_64 how it has the [B]chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU[/B] ?That’s all that’s needed to have a “login” for your menu item. Notice the top where it says :do_me? This is important to note that it’s ABOVE the menu generation part of the advanced menu setup.

    As I stated, this is very basic, but a method to :sort: the different functions could be:
    [code]isset ${userID} && iseq ${bootnum} 1 && goto do_me ||
    isset ${userID} && iseq ${butnum} 2 && goto do_me2 ||
    goto MENU
    :do_me
    kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=win7actsysprep ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
    imgfetch init.xz && boot || goto MENU
    :do_me2
    kernel bzImage root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.10.10.1 web=10.10.10.118/fog/ consoleblank=0 loglevel=4 type=down img=blahblah ftp=10.10.10.118 imgType=n osid=7 storage=10.10.10.118:/images capone=1 imgFormat=0
    imgfetch init.xz && boot || goto MENU
    :MENU
    menu
    item --gap Please Select one of the images below
    item fog.local Boot from hard disk
    item d101_64 D101 Base Image (64 bit load)
    item return Return to main menu
    choose --default fog.local target && goto ${target}
    :fog.local
    sanboot --no-describe --drive 0x80 || goto MENU
    :d101_64
    set bootnum 1
    chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
    :d102_64
    set bootnum 2
    chain -ar ${boot-url}/service/ipxe/advanced.php?login=1 || goto MENU
    :return
    chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} || goto MENU
    autoboot[/code]

  • CentOS sucking down RAM

    8
    0 Votes
    8 Posts
    4k Views
    B

    FWIW, I’ve found htop to be a lot more useful than top.

  • Download/Upload Performance Issues Since 1.1.2

    28
    0 Votes
    28 Posts
    9k Views
    JunkhackerJ

    i’ve heard of problems with some cards, that they have a power setting (configurable from windows) that will drop to 100m in low power mode, and may not come back out of it and into 1000m when booting into linux. but when booted into windows, they come back up to full speed. if you disable that setting in windows, the problem goes away completely.

  • Multicast interface binding issue

    12
    0 Votes
    12 Posts
    4k Views
    P

    Hi Tom,

    Thank you.

    I tried that and unfortunately, it doesn’t work for me. I checked the permissions for /etc/rc.local and tried using the full path name of service (/usr/sbin/service) to no avail. I would welcome your suggestions of what to try next.

    Would it be possible for future versions of the services to syslog something meaningful if they die and try to respawn themselves a couple of times with a delay for each please?

    Thanks,
    Paul.

  • Ubuntu or Centos / Physical or Virtual ?

    4
    0 Votes
    4 Posts
    3k Views
    V

    I run all my FOG servers as VMs, mainly in VMware ESXi or XenServer 6.2.

    for 0.32 I had all Ubuntu but for 1.x.x I’m now using Debian 7 and it’s not been a problem at all. My virtualbox test clients boot loop but none of the physicals do the same…

    You may be limited by your storage if you have lots of active VMs on the same SR/Datastore since disks only go so fast and aren’t the best performance for random IO. You may also get limitations on your network if you have active VMs on the same physical NIC… a 1gb link can be swallowed quickly while imaging.

    everything depends how much performance you need, what hardware you have and how often you are going to be imaging.

  • Missing LSB tags and Overrides

    2
    0 Votes
    2 Posts
    2k Views
    I

    There is something similar in the wiki: [url]http://www.fogproject.org/wiki/index.php?title=Error_Messages[/url]. Could you try what they suggest and see if it makes a difference? They are suggesting that there is a problem in the startup scripts for debian but that temporarily removing the fog startup scripts from /etc/init.d seemed to work.

  • What is /dev/mapper/vg_fog-lv_root and why is it so small?

    2
    0 Votes
    2 Posts
    2k Views
    Tom ElliottT

    I’m going to guess you named the system “fog” when you installed it?

    CentOS 6.5 defaults the filesystem type to lvm disk management. The root partition is usually defaulted to a maximum size of 50 GB.

    When FOG installs, it creates a directory in the root filesystem as /images which would be mounted on the root of the drive or / as you’re seeing.

    If you need it to load to a different disk you can very simply. Just mv the /images to a folder on a filesystem that has much more space. My guess is /home in your case is also on it’s own filesystem labeled as:
    /dev/mapper/vg_fog-lv-home.

  • Udpcast...Failed! Fog upgrade 0.34 to 1.1.1

    7
    0 Votes
    7 Posts
    3k Views
    M

    thanks for your hints. finaly i could fix the problem, i had to reinstall libc6-dev

    [FONT=Verdana][COLOR=#000000]apt-get install --reinstall libc6-dev[/COLOR][/FONT]

  • System startup script for ubuntu 12.04

    5
    0 Votes
    5 Posts
    2k Views
    K

    Yes editing fstab worked for exactly what i was trying to do.

  • Client not booting

    9
    0 Votes
    9 Posts
    4k Views
    I

    It sounds like the problem is with the DHCP service rather than Fog. Your Fog install could be fine, but if there is a problem with DHCP your clients won’t even try to talk to fog.

    One thing to try might be sniffing out some of the DHCP traffic on your network to confirm that it looks it should. Wireshark should help there. My hunch from what you say above is that your Citrix setup might have a DHCP service somewhere which is handing out DHCP leases in competition with your FreeBSD box. If that is the case, and your client gets it’s lease from that other DHCP server then it wont work.

  • Linux mint 17 deployment issue

    10
    0 Votes
    10 Posts
    4k Views
    I

    In case anyone else is interested in doing this I’ve updated my instructions on the fog wiki to describe
    [LIST]
    [*][URL=‘http://fogproject.org/wiki/index.php/Include_SystemRescueCD’]how to include SystemRescueCD [wiki][/URL]
    [/LIST]
    You [I]can[/I] do it by just booting from the CD instead, but we found it a really handy addition for resetting admin passwords, fscking filesystems, recovering broken systems etc. so we put it into fog.

  • Deploying Ubuntu 12.04 LTS image not working.

    14
    0 Votes
    14 Posts
    5k Views
    L

    Thanks for help.

    [url=https://www.gclub88.com/play-on-website/][color=#FFFFFF]gclub online ผ่านเว็บ[/color][/url]

  • TFTP Not Found

    6
    0 Votes
    6 Posts
    3k Views
    P

    Hi, I have the same problem.
    Ubuntu 12.04 with 0.32 is working fine, as soon as I put the upgrade 1.1.0 I have this error :

    [ATTACH]981[/ATTACH]

    I have double check the 066 and 067, 067 is undionly.kpxe.

    Here is my ipxe boot.php :
    #!ipxe
    cpuid --ext 29 && set arch x86_64 || set arch i386
    colour --rgb 0xff6600 2
    cpair --foreground 7 --background 2 2
    console --picture [url]http://10.6.2.102/fog/service/ipxe/bg.png[/url] --left 100 --right 80
    :MENU
    menu
    colour --rgb 0xff0000 0
    cpair --foreground 0 3
    item --gap Host is NOT registered!
    item --gap – -------------------------------------
    item fog.local Boot from hard disk
    item fog.memtest Run Memtest86+
    item fog.reginput Perform Full Host Registration and Inventory
    item fog.reg Quick Registration and Inventory
    item fog.sysinfo Client System Information (Compatibility)
    choose --default fog.local --timeout 60000 target && goto ${target}
    :fog.local
    sanboot --no-describe --drive 0x80 || goto MENU
    :fog.memtest
    kernel memdisk iso raw
    initrd memtest.bin
    boot || goto MENU
    :fog.reginput
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.6.0.12 keymap= web=10.6.2.102/fog/ consoleblank=0 loglevel=4 mode=manreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.reg
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.6.0.12 keymap= web=10.6.2.102/fog/ consoleblank=0 loglevel=4 mode=autoreg
    imgfetch init_32.xz
    boot || goto MENU
    :fog.sysinfo
    kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns=10.6.0.12 keymap= web=10.6.2.102/fog/ consoleblank=0 loglevel=4 mode=sysinfo
    imgfetch init_32.xz
    boot || goto MENU
    autoboot

    [url=“/_imported_xf_attachments/0/981_IMG_20140612_083144.jpg?:”]IMG_20140612_083144.jpg[/url]

  • MySQL problem continues

    6
    0 Votes
    6 Posts
    5k Views
    R

    Hi,
    Apparently a “no password” setting does fix this issue across the board, reliably, every time.

    I would much rather have a password in my situation, that is my goal.

    The strangest thing is how it happens randomly - my new FOG installations have been fine being up all weekend, but I’m guessing that sometime this week it will happen again…

    Thanks for any help and/or advice,
    D.L.

  • Xenclient with fog 0.32 on ubuntu 12.04

    17
    0 Votes
    17 Posts
    6k Views
    Tom ElliottT

    I’m not going to assist with this further.

    Why you ask yourself expectantly?

    You’re requesting we download files, but hosting through not necessarily good sources. This leads me to think you’re attempting to gain access to systems.

    I’m not saying this is WHAT you are actually trying to do, but I’m not going to download files from those links.

    Next reason,

    You’re making requests and saying, it’s not working. And the only “information” you can give is “you give it a try”?

    MMMMMMMMM sounds sketchy to me.

    If you want help, provide information in a more detailed nature such as “This error is happening.” Or upload screenshots of the problems your having.

    MOD’s, if you can Please remove the links from the posts (or David you can) as they are known “bad” sites.

  • Error received from TFTP server

    15
    0 Votes
    15 Posts
    5k Views
    S

    I also followed the wiki installation instructions Step-by-Step. FTP was missing from my install and SeLinux didn’t actually disable. I would verify the /etc/selinux/config has SELINUX=disable.

  • Tftpd-hpa not starting on reboot.

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • Custom Boot Image

    2
    0 Votes
    2 Posts
    2k Views
    B

    Update: I got it to work.

    The command to create the init.xz file is this:
    xz -C crc32 -z -c init > init.xz

    I found the answer right here in the forum: [url]http://fogproject.org/forum/threads/latest-fog-0-33b.6476/page-30[/url]
    Thanks Tom!

  • DNSMASQ kills DNS lookup on FOG server

    6
    0 Votes
    6 Posts
    4k Views
    D

    Ok, thanks for the post. It’s fixed now and it was the very last step that did it. A few notes on the instructions above. Like you requested, I did each step one at a time.

    [quote=“mecsr, post: 27208, member: 23886”]
    [B]Symlink method[/B]

    delete the current /etc/resolv.conf file with this command “sudo rm /etc/resolv.conf”[/quote]
    /etc/resolv.conf -> This is already a symlink to the master file /run/resolvconf/resolv.conf

    [quote=“mecsr, post: 27208, member: 23886”]
    2. edit the master resolv.conf file with the command “nano /run/resolvconf/resolv.conf”
    The format of the file is nameserver definitions…
    For a dns server definition, you use nameserver, you can define more than one, each has its own line
    nameserver [I]your.Network’s.DnsServer.Address [/I]
    For example, if you wanted the server to use google public dns, you would have one line say
    nameserver 8.8.8.8
    [/quote]
    /run/resolvconf/resolv.conf -> this file is modified automatically on resolvconf service restart

    [quote="mecsr, post: 27208, member: 23886
    If you are on a enterprise type network that has a domain name you use the search line and the supersede statement
    The “search” line syntax -
    search [I]your.appended.domainName[/I]

    The supersede statement, this is a multiple line statement with the second line indented with a space-
    supersede domain-name “[I]your.appended.domainName[/I]”; (Quotes are apart of the syntax)
    prepend domain-name-servers [I]your.primary.dnsServer.address[/I];

    (in case anyone hasn’t used nano before, to save and close the file, ctrl + x, then y )

    Create the symlink to the master file with the command “sudo ln -s /run/resolvconf/resolv.conf”

    Restart the resolvconf service and the dnsmasq service with “sudo service resolvconf restart” and “sudo service dnsmasq restart”
    [I]Note: If the “port=0” line in /etc/dnsmasq.d/ltsp.conf is still commented out, go uncomment it before your restart the dnsmasq[/I] [I]service[/I]

    Do a quick test with “sudo apt-get update” if it succeeds than hooray! otherwise try the next method.
    [/quote]

    This solution didn’t work. The files were automatically modified on service restart.

    [quote=“mecsr, post: 27208, member: 23886”]
    [B]resolvconf interfaces file[/B]
    [I]If the symlink method alone didn’t work, it may be necessary to edit the files specific to each network interface, these instructions assume you only have one ethernet device named eth0, but these steps can easily apply to any additional interfaces.[/I]

    Edit the eth0 dhclient file with “sudo nano /run/resolvconf/interfaces/eth0.dhclient”
    If you have a domain name, you need a domain line. It is the same as the “search” line in resolv.conf,
    except you domain instead of search. i.e. “domain your.appended.domainName” (without quotes)

    The only other lines you need are the nameserver lines which use the same syntax as the resolv.conf file shown above

    so just put in your nameserver definitions the same as before
    [/quote]

    I didn’t have an eth0.dhclient file.

    [quote=“mecsr, post: 27208, member: 23886”]
    2. Edit the eth0.inet file with “sudo nano /run/resolvconf/interfaces/eth0.inet”
    In this file you only need one line defining your primary dns server with a single nameserver line

    Restart the resolvconf service and the dnsmasq service with “sudo service resolvconf restart” & “sudo service dnsmasq restart”

    Do a quick test with “sudo apt-get update” if it succeeds than hooray! otherwise try the next method.
    [/quote]

    My eth0.inet file already had the correct info in it. I also had an lo.dnsmasq file with one line in it
    [CODE]nameserver 127.0.0.1[/CODE]
    So I modified this file with the correct details but, once again, on service restart the file reverted to the original values.

    [quote=“mecsr, post: 27208, member: 23886”]
    [B]resolvconf interface order and base config files[/B]
    [I]If the above 2 methods still didn’t do the trick, try editing these 2 more config files. You may try restarting the service after each file to see if you only needed to edit one of them rather than both.[/I]

    Edit the base file with “sudo nano /etc/resolvconf/resolv.conf.d/base”
    The syntax of this file is the same as the master resolv.conf file[/quote]

    I modified the base file with the values and restarted the service but the /etc/resolv.conf did not reflect the changes

    [quote=“mecsr, post: 27208, member: 23886”]
    2. Edit the interface order with “sudo nano /etc/resolvconf/interface-order”
    This file should already have lots of information in it. I edited so that the top two interfaces are
    eth0.dhcp
    eth*
    It is likely that you only need to have eth* at the top, but this is what I have working. Keep all the rest of the interface order
    as it is.

    Restart the resolvconf service and the dnsmasq service with “sudo service resolvconf restart” & “sudo service dnsmasq restart”

    Do a quick test with “sudo apt-get update” if it succeeds than hooray! otherwise, the problem is something different or the linux distro your using uses the resolvconf service completely differently than ubuntu 14.04 and would require additional research.

    I hope this helps. Good luck 🙂

    Thanks,
    -JJ[/quote]

    This final step was the one that worked. I only put eth* at the top of the interface-order file and restarted the service. Did a quick ping test… success! Checked the /etc/resolv.conf and it had pulled the details from eth0.inet

    So it seems the real problem is the lo.dnsmasq file which takes precedence in the interface-order
    [CODE]# interface-order(5)
    lo.inet*
    lo.dnsmasq
    lo.pdnsd
    lo.!(pdns|pdns-recursor)
    lo
    tun*
    tap*
    hso*
    em+([0-9])?(+([0-9]))*
    p+([0-9])p+([0-9])?(+([0-9]))*
    ath*
    eth*
    wlan*
    ppp*
    *
    [/CODE]
    The above was the original layout.

    Thanks for your help JJ. It was an interesting ride and probably wouldn’t have known the flow of these files from day to day usage.

  • Partimage: commit buffer cache to disk

    5
    0 Votes
    5 Posts
    2k Views
    X

    Hi all,

    I had the same problem. I fixed it checking the disk with gparted. No errors were found but the next time the image upload was fine.

    Xabi.

109

Online

12.2k

Users

17.4k

Topics

155.6k

Posts