Tom,
You are awesome. Worked like a charm. Feel free to move this to the Linux Problems forum if you feel appropriate. I couldn’t decide between the two.
Magnus
Tom,
You are awesome. Worked like a charm. Feel free to move this to the Linux Problems forum if you feel appropriate. I couldn’t decide between the two.
Magnus
Hi folks,
I’m seeing multiple errors pointing to fog in my terminal window when attempting to install various packages (xrdp and one other package). I’m a linux guppy and I have no idea why my package installs are failing. Would someone mind looking at the attached terminal output and explain what’s going on?
Thanks in advance for the replies. I’m running Debian 7.5 and fog v1.1.1.
[url=“/_imported_xf_attachments/1/1019_package_install_errors.txt?:”]package_install_errors.txt[/url]
[quote=“astrouga, post: 8526, member: 907”]BTW, the solution ullawolf1 suggested works really well:
"So tftpd-hpa starts “to early”. You can fix this by editing the /etc/rc.local and add the line
[CODE]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/CODE]
to restart the daemon after 30 seconds."
The thread is here:
[U][SIZE=2][COLOR=#0060e0][url]http://fogproject.org/forum/threads/tftp-stops-on-reboot-after-install.488/#post-5353[/url][/COLOR][/SIZE][/U]
[SIZE=2]astrouga[/SIZE][/quote]
Just wanted to add that I needed this fix on clean install of Debian 7.5 and fog 1.1.0 to get the TFTP server talking to my clients.
[quote=“Wolfbane8653, post: 29564, member: 3362”]Ubuntu 14.04 LTS is having serious issues with mysql. At this time it is[B] not recommended[/B] by anyone here to have your fog installation on Ubuntu 14.04.[/quote]
That’s great. I’ve lost count of how many times I’ve re-installed my linux server. What do you recommend for the most headache free fog experience? The latest version of Debian (I’d want to install a desktop environment)? Ubuntu 13.10?
I don’t need a bleeding edge Linux OS…just a stable environment for using fog.
[quote=“Tom Elliott, post: 29566, member: 7271”]All those having mysql problems on 14.04, what is the RAM amount on your systems?
What’s the mysql version installed?
[URL=‘https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1312936’]https://bugs.launchpad.net/ubuntu/ source/mysql-5.6/ bug/1312936[/URL][/quote]
I have 4GB of RAM and running mysql v5.5.37.
Update - restarting the mysql service and then clicking install/upgrade seems to have fixed the problem. It reported no upgrade was necessary and I’m no longer being prompted. Hope it doesn’t return.
Thanks.
HI fogsters,
I was having an issue with my fog v1.0.1 server and after a bit of unsuccessful troubleshooting and noticing v1.1.0 had dropped I decided to do a clean install (Ubuntu 14.04 LTS).
The install went fine and I was able to pull an issue from my client computer with no issues but now I’m being repeatedly prompted to update my database schema despite doing so successfully when asked during the fog server install. When I click the button to update the schema (again) I get an ‘Update/Install Failed’ message.
I attached a copy of my install log and a copy of the error log I received.
Can anyone point me to how to resolve this?
Thanks in advance for the help!
[url=“/_imported_xf_attachments/0/928_FOG 1.1.0 Database Schema Installer _ Updater.txt?:”]FOG 1.1.0 Database Schema Installer _ Updater.txt[/url][url=“/_imported_xf_attachments/0/929_v110_foginstall.txt?:”]v110_foginstall.txt[/url]
[quote=“Iulian Constantinescui, post: 27800, member: 24331”]Solved,
If you do a cleanup install or an upgrade you must change the config/settings in your linux/windows DHCP server.
On windows DHCP server make sure you put the 66 and 67 option.[/quote]
My option 66 and 67 settings were correct, otherwise the client wouldn’t have been able to talk to the fog server at all. What solved (and I use that term loosely) the problem was a clean install of Ubuntu 14.04. All is working beautifully now and I don’t need an rc.local edit either.
Thanks again to everyone that chimed in.
[quote=“Tom Elliott, post: 27249, member: 7271”][code]/bin/sleep 30 && /etc/init.d/htftpd-hpa restart[/code] Is that what’s really in your rc.local?
Try:
[code]/bin/sleep 30 && /etc/init.d/tftpd-hpa restart[/code][/quote]
No, I caught the error. My syntax is correct.
Tom,
Thanks for the reply. That command does work for me to get the TFTP server going. And there is a known bug with TFTP in 12.04…I’m just not sure why the rc.local hack worked with 0.32 isn’t working with 1.0.1.
Again, if I manually stop and start the TFTP service I’m able to access undionly.kxpe, whether it be via PXE boot or windows command line.
If I decide to go through the trouble to re-install Ubuntu (a very windows-esque fix, lol) do you recommend 14.04?
Thanks Jaymes.
I’m not sure if this is progress but now I’m getting a ‘PXE-E11: ARP TIMEOUT’ error after applying your change to the tftpd-hpa.conf file.
Hi Folks,
Back in v0.32 is where I first encountered this error and by following the steps below I resolved the issue. Now it’s back after a clean install of v1.01 and I’m not sure why. Here’s what I’ve done so far:
I followed this [URL=‘http://fogproject.org/wiki/index.php/Unable_to_connect_to_TFTP’]wiki[/URL] and made sure all the passwords in my config.php file matched that of my fog web ui login password. I also applied the same password to the FOG_TFTP_FTP_PASSWORD field in Fog System Settings.
I’m aware of the tftpd-hpa bug in Ubuntu 12.04 but I confirmed my rc.local file still includes the following line (per this [URL=‘http://fogproject.org/forum/threads/tftp-stops-on-reboot-after-install.488/’]thread[/URL]):
[CODE]/bin/sleep 30 && /etc/init.d/htftpd-hpa restart[/CODE]
[U]Luckily manually stopping and starting tftpd-hpa from a terminal prompt DOES fix the problem.[/U] I’d just rather not have to do it manually every time I reboot the server and find it peculiar that what worked for v0.32 isn’t working now that I’m on v1.01.
Anyone have any suggestions to fix this minor annoyance?
Thanks in advance for the replies.
Hi folks,
Whenever I schedule a task and enable the option to ‘Shutdown after Task Completion’ the client reboots, rather than shuts down. GreenFog and scheduled shutdowns also behave the same way.
This used to work just fine and the only thing that changed around the time it stopped working was an Ubuntu OS kernel update that I received automatically. I’m pretty sure the kernels fog uses to work with clients are isolated from the OS kernel updates.
Anyone know of a fix or a method to troubleshoot?
Thanks in advance for the help.
[quote=“Matthew Hood, post: 10086, member: 353”]The fix that I have found is to run a startup repair with the windows 7 cd then try reimaging.[/quote]
Just wanted to add that this fixed the problem for me. The log from the repair stated ‘Corrupted MBR’. I think this means the HD had itself confused with a toaster.
Are you saying localboot 0x80 may reboot the clients without installing the 4.04 syslinux kernels?
[quote=“Tom Elliott, post: 17948, member: 7271”]First things first. Chown the directory with sudo chown -R fog:root /tftpboot just so you know permissions are good throughout. Next, the default file can’t have extra spaces for lines. So anything with text on it should be fine. Remove the whitespace.
Change the local boot line to read as localboot 0x80 to ensure it finds the hard drive. Next all syslinux has the .c32 files they’re just in different places. Use du piped to grep to find them. Make sure you’ve got the fogboot directory in your web server. It should just be a link back to your /tftpboot/fog directory. I’ll clarify more when I get home.[/quote]
Tom,
I am also having issues getting the boot from local drive option to work (on Lenovo PC’s, not Dell). I may need to start a new thread but I wanted to clarify something…why do you recommend using ‘localboot 0x80’ over the ‘KERNEL chain.c32’ as recommended in the ‘Boot looping and Chainloading’ wiki?
Chris,
Another big thanks for your kernel. I was successfully able to get my clients (Lenovo Thinkcenter m83’s) to talk to the fog server and run an inventory and upload an image with your kernel. You saved me the pain of putting together a custom kernel myself or giving up on FOG all together.
Tom,
FYI I was unable to get either the kernel that was included with 0.32 or kernel v3.8.8 to load on my m83 client. Here’s the errors I observed with both:
tps65010: no chip?
acpi_ibm: ibm_acpihp_init: acpi_walk_namespace failed
Could not find Carillo Ranch MCH device.
uvesafb: failed to execute /sbin/v86d
uvesafb: make sure that the v86d helper is installed and executable.
uvesafb: Getting VBE info block failed (eax=0x4f00, err=2)
uvesafb: vbe_init() failed with -22
drm/i810 does not support SMP
Error: Driver 'mdio-gpio" is already registered, aborting…
cs89x0: request_region(0x320, 0x10) failed
Thanks,
Magnus
I’m still not sure of the cause but I’m back to working again after a re-install of the fog server. Luckily I didn’t have much of a configuration to lose as I’m still in a feeling out stage with FOG.
Hi Tom,
Thanks for the quick reply.
I confirmed both files are there and set permissions per your instructions. Unfortunately the client is still behaving the same.