Posts made by sarge_212

I’ve upgraded to latest FOG via trunk, and I can’t seem to get more than 2GB/min deploying an image. At one point it was at 6G/min which was beautiful. I’m only deploying one image and I can’t seem to speed it up. Do you have any recommendations to speed up the deploy time on the FOG server or things I can check. Also, it is noteworthy to mention that this is across various hardware, both the low and the high rate so I don’t think it’s the client hardware. I’ve upped the RAM to 16G on the server and the cores from 4 to 8 and still seeing slow deploy times. Any and all recommendations are appreciated. Thanks FOG Team!

Hey all,

I think this is a bug.

If I go to Task Management > List all hosts > click the Download arrow for that host, it downloads an image. However, if I go to host management > select the host > basic tasks > download > schedule the download, I get the error about optimal storage node. Just wanted to let you know after much hair pulling. Thanks.

No problem Wayne. This forum is awesome and you guys are all way responsive and helpful. Thanks!

I am attempting to do that, but I keep getting a (current password) prompt. After entering in all sorts and variations of passwords, I get authentication failure. I’ve tried userdel -uf fog to force remove the fog user and then add it again. It just doesn’t seem to be working. Also, I noticed in /var/www/html/fog/lib/fog/Config.class.php, that the STORAGE_FTP_PASSWORD wasn’t in this file. I added it there but still getting the error about Undefined index, optimal storage node.

Wayne,

Should users be created in /etc/shadow and /etc/passwd that are fog UI users? Just curious because none of those users I have created are in those files. I checked the log for vsftpd and it mentions that the user is unknown. I’m pretty sure it’s something in the environment where the user isn’t being recognized. Thoughts?

Further, I guess, now I get this:

I’m not using a NAS or anything, just another partition, /images where I’m storing the image. We’re only using one or two images in our environment.

AHHH!!! there is no password there…let me throw one in and see what happens. That’s probably it. I somehow neglected to get to this menu before. ./headslap

Weird,

I tried changing the password for fog in ssh and I keep getting authentication failures. So I check /etc/passwd and /etc/shadow and there is no fog in either of those. ???

Wayne,

I looked at all of those, and I tried to change the FOG password on the Linux server. However, I don’t know the current password so I get locked out of changing the FOG user’s password. Any quick way around that?

Hey Gents!

I’m seeing an issue here where after imaging, I can’t deploy an image to that machine. Here is the sequence I take to re-image:

FOG >> Host Management >> List all hosts >> select host >> basic tasks >> Download >> Create download task for host <host>

It seems on the older version of FOG, you wouldn’t have to upload the image to deploy, you could just deploy the image after having imaged it once. Am I correct in this thinking? Am I going about this the right way?

Let me know what to look at, thanks all!

Thanks Wayne! That is very helpful and what I needed to know! Very much appreciated!

I’m imaging using FOG 1.2.0 on CentOS 7 and our environment needs to be pretty locked down. It is working with SELinux enabled and I’m using IPtables as well. I opened the firewall using IPtables to accept any UDP and TCP on the entire subnet we’re using. Before I had done this, the imaging process was quite slow, now it happens in 8 minutes or so which is fantastic. The problem is, I’m trying to only allow it on certain ports only. I watched with netstat as it was imaging and saw port 2049 on the FOG server, but I wanted to be sure as to which port(s) the FOG server uses when deploying an image. Thanks all and I appreciate any and all feedback!

I get that, Wayne, and I don’t think that’s harsh. I should have commented on your suggestion. Better late than never: The weird thing I saw was when I did a download with debug, and then ran fdisk was I only saw one partition. I didn’t really understand that and still getting my feet wet with FOG decided to revert back to a snapshot before going any further. I really do appreciate the help and knowledge you guys have, I would be sunk without your help!! Thanks again. I’m going to try upgrading to the latest Trunk version and see what happens. Thanks!

Luckily I had a snapshot of the VM before I upgraded. I reverted back to stable 1.2.0 and now I can push images to machines. However, I’m seeing an incredible slow down on spinning disk vs SSD. Spinning disk is going very quickly, however SSDs are taking twice as long to image. I tried the upgrade trunk method and that kind of borked things. I’m thinking I might try that again but if you all have any suggestions for speeding up deployment to SSDs, that’d be appreciated.

So iPXE is now working. I did restorecon -Rv /tftpboot and that did it. The problem I’m seeing now is it doesn’t seem to be pushing the image down to the machine. Here are some cell phone shots of that:

Thanks again Wayne and Tom for your awesome feedback and help. I sure appreciate it!

Before I go re-installing FOG, I have tested TFTP and that hasn’t worked. I do tftp <IP> get undionly.kpxe and I get a timeout. To clarify: to re-install, can I just run the trunk upgrade in fog/bin/install.sh on my current install?

Also,

Thanks Wayne! I didn’t, don’t worry. The errors I’m seeing go something like this when I boot:

CLIENT MAC ADDR: <mac> GUID: <guid>
CLIENT IP <IP> MASK: <SUBNET MASK> DHCP IP: <DHCP SERVER>
GATEWAY IP: <GATEWAY IP>
TFTP.
PXE-MOF: Exiting Intel Boot Agent.
Selected boot device failed. Press any key to reboot the system.

I’ve tried this on 2 of our most common machines and I see the same on both. I’m testing on Dell Optiplex 9020 desktop and Dell Latitude 6430u laptop. Thanks all!

I tried undionly.kpxe. Should I be using a different boot file option?

I just upgraded to the latest FOG via trunk. I now can’t PXE boot any machines. I’ve checked and triple checked the TFTP username and password in /var/www/html/fog/lib/fog/Config.class.php, I’ve restarted NFS services, I’ve restarted vsftpd daemon. I am about to pull my hair out with this new version of FOG and roll back but I really don’t want to. I am running CentOS 7 with FOG revision 3451. Any help will prevent me from going bald early. Thanks all!

Thanks Wayne!