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]
Alright,
What errors is it giving you when you try to manually install mysql, if any?
The images are pigz’d as they’re uploaded. I don’t know of fog writing to /tmp, it’s to /tmp/pigz1 during the upload process, but that’s a pigz process which is writing to /images which is the mount of the nfs share.
If I’m wrong let me know, but you’re saying you’re having problems with the system actually picking up an IP Address when it goes thru PXE boot, or is it after this point that’s the problem?
It sounds like an issue with drivers. I’ve heard of some having success with different kernels. I have a very small kernel that might just fit the bill. It can be downloaded at: [url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
I don’t know if it has all the drivers for your particular system, and if it doesn’t just let me know and I’ll build a specialized kernel for you. Just tell me what hardware (driver types) you need and I’ll make it happen.
On the server, how much memory do you have? If the loads are taking that long, it seems that something is eating the RAM and php is taking forever. Are you running php thru fcgi?
Try manually installing mysql with yum -y install mysql-server, it should install the package. Check that mysql is installed then, and you should find /var/lib/mysql folder. Another way to find out if it’s installed is to run:
chkconfig mysqld on; service mysqld start
Then, try your install. I’ll need to check the install folder for redhat to see that it’s pointing to the right package for mysql.
Though its slightly aged have you gotten this figured out? I suppose a little research could be done but I think you could do:
apt-get build-dep build root
But don’t quote me as I don’t use Debian based OS.
If you need help I’ll try where I can.
If you know what kernel driver you need for your USB nic I can build the kernel but I don’t know that pxe will actually run from it as that’s typically an onboard option. Though, again I don’t have one of those tablets either.
Lol if only. Glad to be of help.