Are you trying to do this install from your home system?

Give me a minute or two and I’ll post the latest and greatest that I’ve created.

I don’t know if it will work, but it will contain many of the Fixes I’ve already implemented.

[quote=“mlb2009, post: 15451, member: 13741”]in fog 0.33 it will be installing and working for fedora,right[/quote]

From my knowledge it is all set and should work for all the Distro’s it nativally supports (Redhat/Centos/Fedora)([X]Ubuntu Based)

For non-standard distro’s you could get it to work, though it might take a little extra work.

I was able to correct for the issue with Quickimage, but it did require me to do two things.

First thing I had to do was edit
{fogwebdir}/service/hostlookupbymac.php
Here’s what I did/changed to this file:
From:
53 $tmp;
54 if( createImagePackage( $conn, $imageMember, “”, $tmp, false ) )
To:
53 $tmp;
54 $Host = new Host($hid);
55 if ( $Host->createImagePackage(1,“AutoRegTask”,true,true,true) )
56 //if( createImagePackage( $conn, $imageMember, “”, $tmp, false ) )
Then in file:
{fogwebdir}/lib/fog/Host.class.php
Go to and comment out Line 528.
Then all worked well. Including the Main GUI.
I don’t like commenting lines within a class that was, for the most part, working already, but I had to for quickimage as it’s trying to assign, for logging purposes I guess, the username to create the task. When it’s quick image, it doesn’t know who the user is so it spits out an error and will not create the task, the PXE File for the host will get created, but no database task gets created.
I’m guessing a similar change will need to be made in the Full Host registration script.

[quote=“mlb2009, post: 15450, member: 13741”]Windows 7 support will also be good[/quote]
Windows 7 is already supported in 0.32, and as such would be supported in 0.33

Okay,

Is there any way you’d be able to allow remote access that I could actually take a look at the file/install process?

There shouldn’t be any problem with installing, so it seems there’s a borked command in the installer somewhere, I just don’t know where. I’m running on CentOS 6.4 and I haven’t run into any issues. I’m also running/testing 0.33 so I’m not a good example.

Also,

When giving information, please try to provide as much information as possible. It’s not easy to troubleshoot something when not being directly in front of it. It makes it much more difficult to help out when there isn’t any information to go off of.

Responses such as:
“didn’t work.”,“Didn’t help”

Doesn’t give us anything to work off. We don’t know what you’ve tried, or how you know certain things.

How do you know that mysql is working?
What have you tried beyond the help I’ve tried giving?
What kinds of error messages is the system telling you? Fog tells you information, but we don’t know your systems particular setup.

Okay,

Is your FOG Server behind a router that then connects to a modem or directly connected to the modem?

If you’re connected directly to the modem, then how did you get the DHCP Server and the DNS Server IP Address?

You’re sure mysql is actually running on your system then?

Is selinux running or disabled?
To check:
cat /etc/sysconfig/selinux

Look for:
SELINUX=disabled
If it doesn’t say disabled change it and reboot your machine.
Then check that iptables is disabled <- DONT DO THIS IF YOU’RE CONNECTED DIRECTLY TO THE MODEM
service iptables stop; chkconfig iptables off
Once done, retry the install process.
Can you post a reading of:
/var/log/messages
Directly after you’ve tried installing fog.
Thank you,

While testing my custom init.gz, I found an issue in the Quick Image system. This, from what I can tell right now, affects all of the PXE options to perform the Quick Image (Full host registration, quick image, etc…) as the function it calls does not exist. I see a function called createImagePackage(…) but the function performed within the files is not relative and it’s not pointing to the class. I’m going to play a bit until I figure this part out, but until then, just wanted to post this issue.

Is your fog server connected directly to the internet? You understand linux and the command line?

The way to obtain your systems IP (which you should have setup statically) is to run:
ifconfig
If you have multiple interfaces, you’ll need to figure out which interface you’re trying to use and use the IP associated with that.

I assume your IP is going to be in the range of 192.168.1.2 thru 192.168.1.254 as you put your router and dns server as 192.168.1.1

Your files to be edited should be located in:
<locationOfFogInstallFolder>/lib/redhat

There are two files in there which I forget the names of.

However, if my memory serves me correctly, when you do the install, it should ask you what you want to set your IP up as, and it defaults to your systems IP, so unless your FOG server is directly connected to the Modem, it should have a private IP address assigned to it already. I’d recommend, until you understand what this software is doing, sticking with the defaults.

I do the symbolic link on my system as it seems to work the best for my setup.

You can change the information by changing the values in the Storage Management part of the Web gui and you’ll also have to make the changes under fog configuration->fog settings within the GUI as well.

To add to the above,

My upload process with using Sectors works beautifully. However, the deploy process (which I have trouble with in both the original and my custom builds) does not work with single partition resizeable. However, it’s also not working with MPS, but that might be because I created the images using my custom build as that’s what I’ve been testing most frequently. I’ll find out later on. Still making progress and it’s a slow right. If you all can’t tell, I’ve not worked too much on the web interface in quite some time due to this. I will, however, try to get work done on it once I got this all figured out. In the mean time, I’ll work on tweaking the OS portion so it can be as small as possible, while still giving all of the needed elements a chance for us. I’m contemplating removing the partclone parts for now as it doesn’t build all the needed modules any what. It only creates:
partclone.restore
partclone.ntfsfixboot
partclone.info
partclone.chkimg
partclone.dd
fail-mbr.bin

I don’t know how to get it to build the [fstypes] of partclone executables, but I’ll work that out, hopefully in the future as well. Though we’re not using it right now anyway, so it’s not a huge thing.

Okay, looking into this, I don’t think there’s an issue with the default installation files for redhat. Fedora 19 should use the yum install mysql mysql-server and the configuration is chkconfig mysqld on; service mysqld restart which, you stated, works fine for your system.

However, it may have an issue because it’s trying to restart the service from your public IP address, which would cause a failure as it, theoretically, can’t access from that point.

Try not using your public IP address and use your server’s internal IP address during the setup. Hopefully this helps out.

I think you’re misunderstanding the system. When you boot a system thru pxe and it loads bzImage and init.gz, it’s not the same filesystem as your server.

init.gz is what loads the file system fog uses on the clients. It’s that /tmp directory that’s being used to have the fifo file created that pigz{1-3} uses when it’s uploading an image. /images is also created on the init.gz system during this same process. That /images directory is the mount point for your storage server (/images typically) on your FOG server which would, ideally, be a large filesystem. Essentially, the /images you see on the client when uploading an image is the storage node you’ve setup for FOG to store the images to. If you’ve setup the storage node to write to /tmp on your fog server, then it’s really easy, but I don’t think that’s what you’ve done here.

Basically,

What you’re seeing FOG do during the upload process is not the same /tmp as your server system.

So you’re not running thru a mod_fcgi process if it’s all defaults. I’d find out what’s eating your memory on the server then. You mean that there’s 11+GB of RAM in use on your fog server? That’s crazy, and definitely would be the cause of slowness as that much used RAM would also mean your CPU is constantly in use.

Your public IP is not what should be used. You would use the IP address your fog server is setup for within your internal network (the network you’re trying to image from).

Can you do me a favor and check the install. I’ll download a copy of the tar file and see what it’s doing as well, but I’ve never seen any issues with it before. Maybe it’s forgetting a part for Fedora 19 which is RH Based.

I’ll double check, but do you know how to edit the files?

From the install folder, look within for a folder that contains redhat and which files do the install process. I will get back here with the info, but it’s going to be a little bit.

I think you’d want something along the lines of a menu entry as:
LABEL fog.sccm
KERNEL fog/kernel/memdisk
APPEND iso initrd=fog/images/sccm.iso raw
MENU LABEL SCCM
TEXT HELP
Useful Information about SCCM here!
ENDTEXT

Okay,

So now that we know mysql is installed and working (how btw?) what’s the error’s you’re getting with installing fog?

So is your fog setup now installed?

If it is, what did you end up having to do?

If it isn’t, I’ll take a look at the 0.32 Redhat install portion to find out why it didn’t install for you.

Thanks,

Yes it is possible. If you know the kernel and the initrd (or iso) you’ll need, you just open up the /tftpboot/pxelinux.cfg/default file and create a new menu entry.

I don’t know all your info needed for SCCM so I’m sorry I can’t break it down any easier for you.

[quote=“mlnancejr8808, post: 15414, member: 654”]Yes, when the PCs boot to PXE initially they will try to pull DHCP go about 4 dots whatever you want to call them then say PXE-E51- DHCP or proxyDHCP offered…other PCs we have (Dell Optiplex 740 and 755) have no issue. Just dealing with this on the HP Compaq 6300 Pro and I have 6 labs to image by next Wednesday when school starts.[/quote]
Found this on website:
[url]http://www.symantec.com/business/support/index?page=content&id=TECH12323[/url]
[SIZE=4][B][FONT=Arial][SIZE=18px][COLOR=#444444] [/COLOR][/SIZE][/FONT][/B][/SIZE]

[SIZE=4][B][FONT=Arial][SIZE=18px][COLOR=#444444]Solution[/COLOR][/SIZE][/FONT][/B][/SIZE]

[SIZE=16px][FONT=Arial][COLOR=#444444]
This error is usually received when the client booting up via PXE is having difficulty communicating with the DHCP/PXE server. The common troubleshooting steps and/or causes of this problem are as follows:

1-The PXE client is connected to a managed switch that does not have portfast enabled and/or is running spanning-tree. Portfast will need to be enabled. To read more about what spanning-tree and portfast are, see article 3096, “What is Spanning Tree? What is PortFast?”
2-The DHCP/PXE servers reside on a different subnet than the PXE client. IP helpers need to be in place. See article 1331, “Configuring PXE to work across VLANs.”
3-Check the DHCP server and verify that the DHCP scope has free IP addresses to lease out (make sure they are not all used up).
4-If the above steps do not correct the issue, place the DHCP Server, PXE server and a client computer on a hub. Test PXE to see if the same message is received. If the same error message is not received, this is a good indication that there is some factor on the network not permitting the DHCP/PXE protocols to be passed down to the client computer.
Place a hub between the PXE client and the switch the client is connecting to. If at this point the PXE client works successfully, please review step 1 of this article.
5-Use TCPView to verify the DHCP ports 67 and 68 ([URL=‘http://www.microsoft.com/technet/sysinternals/utilities/TcpView.mspx’][SIZE=12px][COLOR=#72a826]http://www.microsoft.com/technet/sysinternals/utilities/TcpView.mspx[/COLOR][/SIZE][/URL]). MTFTP Port 69 are showing.
6-If this problem is still occurring after testing out the above, collect sniffer traces from the DHCP/PXE server(s) and contact Altiris Support Services.
7-If DHCP server is on the same box as PXE server follow the option to enable 060 scope option. Article ID: 17347 Creating and setting option 060 on a DHCP server
8-The NIC could be disabled on the Client machine.[/COLOR][/FONT][/SIZE]