Standalone
-
Now, that part is working, I just copied over 1 image from the exteral hard drive onto the server into the images folder , what steps do I need to take in order for the new server to see the image ? Also what do I need to do in so that the clients can boot on the network and pickup an ip address?
-
The easiest way is to do the “Configuration Save” under “FOG Settings”
It exports every single thing inside the DB.
Then, take that file and import it into your new FOG server.
And, one thing at a time…
To test if network booting works, just try to network boot a computer. simple. After you try that and see what happens, we’ll go from there. Hopefully all is well. -
Well, the old server is dead, I only have the images copied over to the external hd. Is there anytning else I can try?
-
There’s a good thread on that: [url]http://fogproject.org/forum/threads/transfer-images-from-0-32-to-fresh-1-2-0-1-2-0-cant-see-images.11671/#post-36719[/url]
Basically, you just need to re-make them inside the Web-GUI, and the case and spacing and punctuation and all that jazz must EXACTLY match what the image paths are.
-
I did the check box but where to go next?
-
[quote=“fredlwal, post: 45831, member: 26766”]I did the check box but where to go next?[/quote]
I was sort of intending for you to read through that entire thread. I don’t believe you need the check-box for image-type.
Further in the thread, there is talk about what needs done to get the images to show up.
-
I wasn’t going from an old version of fog i’m coping images that are from 1.2.0 to the same version.
-
I ran the chmod 777, but how do I know its working when I can’t PXE into the server from a client?
-
This post is deleted! -
You just need to create those images inside Image Management using the correct paths.
[url=“/_imported_xf_attachments/1/1899_ImageNames.png?:”]ImageNames.png[/url]
-
You can troubleshoot PXE booting using this tutorial, it’s really through: [url]http://fogproject.org/wiki/index.php/Troubleshoot_TFTP[/url]
-
is there a log file that I can send about the pxe boot issue?
-
Sort of… there’s a script that’s still under development that you could try. It produces a log file that has lots of important configuration in it… It’s attached, along with sample output. The sample output is no use to you, it just shows what the output might look like.
Also, you might be better off just giving us screen-shots of the errors you’re seeing. Maybe a TCPDump of the communications, too: [url]http://fogproject.org/wiki/index.php/TCPDump[/url]
For more info on the troubleshooting script, look through this thread. And keep in mind, it’s still a very new thing.
This script doesn’t change anything, either. It just collects information. [url]http://fogproject.org/forum/threads/lets-make-scripts.12551/[/url][url=“/_imported_xf_attachments/1/1900_FogScript.zip?:”]FogScript.zip[/url]
-
this is what I get when I run the script.
t_tiger@fogsrv1:~/Downloads$ ./TroubleshootFog.sh
status: Unknown job: tftpd-hpa
status: Unknown job: isc-dhcp-server
status: Unknown job: rpcbind
status: Unknown job: vsftpd
modprobe: ERROR: could not insert ‘ip_tables’: Operation not permitted
iptables v1.4.21: can’t initialize iptables table `filter’: Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
./TroubleshootFog.sh: line 92: sestatus: command not found
cat: /etc/dnsmasq.d/ltsp.conf: No such file or directory -
Try this one, instead please.
It will create a text file in the location that it was run in. Post that file.
[url=“/_imported_xf_attachments/1/1905_troubleshoot.zip?:”]troubleshoot.zip[/url]
-
Where does it store the log file at, that you would need to look at?
-
This particular script stores the log in the place where the script is run from.
-
here u go
[url=“/_imported_xf_attachments/1/1908_DebianFog.txt?:”]DebianFog.txt[/url]
-
Can you post a screen shot of the error you’re seeing?
-
[quote=“Joseph Hales, post: 45708, member: 18131”]
[COLOR=#333333][FONT=Arial]/etc/default/isc-dhcp-server[/FONT][/COLOR]
[COLOR=#555555][FONT=Arial]We want to serve DHCP only on eth1 interface to we need to configure it that way. Edit the file and save it.[/FONT][/COLOR]
[COLOR=#555555][FONT=Courier New]sudo vim /etc/default/isc-dhcp-server[/FONT][/COLOR]
[COLOR=#555555][FONT=Arial]The line will look like this before you change it[/FONT][/COLOR]
[COLOR=#555555][FONT=Courier New]INTERFACES=“”[/FONT][/COLOR]
[COLOR=#555555][FONT=Arial]And after you change it, it will look like this:[/FONT][/COLOR]
[COLOR=#555555][FONT=Courier New]INTERFACES=“eth1”[/FONT][/COLOR]
[COLOR=#555555][FONT=Arial]Now you should stop and start the DHCP server.[/FONT][/COLOR]
[COLOR=#555555][FONT=Courier New]sudo service isc-dhcp-server stop[/FONT][/COLOR][COLOR=#555555][FONT=Arial] (if the service is already running; skip if it’s not running)[/FONT][/COLOR]
[COLOR=#555555][FONT=Courier New]sudo service isc-dhcp-server start[/FONT][/COLOR][/quote]Going off of what Mr. Hales posted, you might also want to restrict DHCP to your eth0 interface. I see in the log file you provided that there are several interfaces on this machine.
