I had the same error. I don’t remember exactly where the file is located. I can tell you tomorrow when I get into work but you need to disable SeLinux. Once you do that restart the fog server and then when it comes back up the image should finish almost immediately.
Posts
-
RE: Error received from TFTP serverposted in Linux Problems
-
RE: Can't get a HP machine to work upload or download an image.posted in FOG Problems
What version of FOG and can you get a screenshot
-
RE: Can't get a HP machine to work upload or download an image.posted in FOG Problems
What kind of errors do you get?
-
RE: Fog 1.0.1 image creationposted in FOG Problems
Try running this on your fogserver:
[CODE]sudo chown -R fog:root /images[/CODE]
-
RE: Downloading new kernel issueposted in FOG Problems
Resolved this issue.
Installed ftp (Not sure if this really did anything)
Disabled SeLinux -
Downloading new kernel issueposted in FOG Problems
When I go to download a new kernel it states: “Download Completed! Moving file to TFTP server…”. It will stay frozen at this screen.
-
RE: Host menu links not working on Firefoxposted in FOG Problems
I know one of my co-workers had to add <fogservername> into compatibility mode for some links to work in IE
-
RE: FOGFTP: Failed to connect. Host xxx.xxx.xxx.xxx, Error: Undefined Index CurrentUserposted in FOG Problems
I’m having this issue also. Receiving the “[COLOR=#333333]Error: Undefined Index: currentUser[/COLOR]” after uploading an image.
FOG_TFTP_PXE_KERNEL_DIR = /var/www/html/fog/service/ipxe/
FOG_TFTP_HOST = Server’s IP address
FOG_TFTP_FTP_USERNAME/PASSWORD = same login as fog user on server
vsftpd seems to be installed correctlyUnsure if this is related or not but under “Image Management” it’s not reading “Image Size:ON SERVER” like it did before on Ubuntu. The image files are there and they match the definitions. I can even deploy the images.
OS: CentOS 6.4
FOG Version: 1.0.1 -
RE: PXE permission deniedposted in FOG Problems
Resolved this issue by
[CODE]chown -R fog:root /tftpboot[/CODE]
-
PXE permission deniedposted in FOG Problems
I rebuilt my FOG server on CentOS everything on the web side seems fine and working properly. However, when i PXE boot any of my machines it gives me a PXE-T00: Permission denied error. I didn’t have this issue with Ubuntu.
I have FOG 1.0.1 and CentOS 6.4
-
Deploy fails after MBR no errorsposted in FOG Problems
I have a very similar issue with imaging as [URL=‘http://fogproject.org/forum/members/dislikeusernames.24301/’]dislikeusernames[/URL] had in his thread here:
[url]http://fogproject.org/forum/threads/deploy-stops-after-restoring-mbr.10549/[/url]Where an image will go through the deploy process up to the loading the MBR. Then it will say the task is completed and then restart. These images were working last week. In fact everything was working beside the 2 computer models in another post of mine. Also the image is set as Multiple Partition Image - Single Disk (Not Resizable).
The only thing that is different is we were having a 0x040ee119 error. Which im not sure what fixed it but I tried all 5 of the undionly.kpxe found here ([url]http://fogproject.org/forum/threads/ipxe-issue.10528/page-2[/url]). I also power cycled the fogserver a few times. Reset the switch the server is connected to and replaced it’s ethernet cable. Then I set the undionly.kpxe back to the original file and the pxe process started working but now the imaging process is broken.
-
RE: Uploading Image Issueposted in FOG Problems
Both models have an Intel
82567V-4 Gigabit Network Connection -
RE: Uploading Image Issueposted in FOG Problems
I’m heading out for the weekend. Thanks to all the devs that have helped me with some issues this week. I hope you guys have a good holiday weekend. I’ll continue to troubleshoot this issue Tuesday.
-
RE: Uploading Image Issueposted in FOG Problems
This is from the 4000
[url=“/_imported_xf_attachments/0/824_20140523_173654.jpg?:”]20140523_173654.jpg[/url]
-
RE: Uploading Image Issueposted in FOG Problems
Also both these models take a long time to get to that error page but I’m assuming that’s due to NIC drivers in the kernel. Which eventually i would like to make a custom kernel that only has the drivers we use.