Posts made by Wolfbane8653

Is it a possibility that your firewall on your windows machine is blocking communication?

If so here is PART of my secret batch file. Pop this into a batch file and reboot. Then let us know what happens.
[CODE] ::Allow Fog Client Thru Firewall
netsh advfirewall firewall add rule name=“Fog Client” dir=in action=allow program=“C:\Program Files\FOG\FOGService.exe”
netsh advfirewall firewall add rule name=“Fog Service” dir=in action=allow program=“C:\Program Files\FOG\FOGServiceConfig.exe”
netsh advfirewall firewall add rule name=“Fog Tray” dir=in action=allow program=“C:\Program Files\FOG\FOGTray.exe”[/CODE]

Confirmed! Last entry in my logs were 2014-09-17. Don’t worry Tom’s on it!

Confirmed thanks Tom.

Any chance you can post your install log? File is located:[CODE]cd /var/log/foginstall.log[/CODE]

Do you just get a blank page or do you get anything at all when you go to the ip address?

That works too. Happy Imaging!

Update: I have updated to r2408 fixing all issues in r2403. The 32-bit is still an issue but its just not showing the status of part clone tom will work on this.

Your mysql is most likely stopped please do a

[CODE]sudo service mysql start
[/CODE]

Then try to login again.

This post is for bugs in r2403. THIS IS BLEEDING EDGE so don’t think it will be fixed in a day.

Issues:
1.) [B][COLOR=#ff0000]FIXED reapplied official r2403 [/COLOR][/B][S]Newly Imaged computers no longer attach to Active Directory. They where successful in r2389[/S]
[LIST]
[][S]Defaults are not being set under Service Configuration for Host Management[/S]
[][S]Under Host Management --> [Select NEW Host Registered] --> Service Settings All services are not ticked.[/S]
[][S]Yes, Services are Enabled as default under Service Config.[/S]
[][S]Yes, Active Directory info is enabled and filled out correctly. It filled in automatically from Fog Settings[/S]
[/LIST]
2.) [COLOR=#ff0000][B]FIXED after update to r2408[/B][/COLOR] [S]Seems to take a bit longer to process group tasks. (but to be expected from the update r2387)[/S]

3.) [COLOR=#ff0000][B]FIXED SEE EXPLAINATION OF GRAPH STATS BELOW [/B][/COLOR][S]Bandwidth- Transmit graph not showing any info during imaging. (worked in r236? I neglected to update for a time.) (Bandwidth- Recieved works when registering. I get a quick 2sec spike from the uploaded reg info)[/S]
[LIST]
[*]Turns our the Bandwidth- Transmit graph does work. It only shows the data transmitting from the selected node. I have a Fog server, and 2 storage nodes. So if I have the Server selected as the node for the info and the host uses the storage node nothing will show up on the graph. Thanks for the info Tom.
[/LIST]
4.) [COLOR=#ff0000][B]FIXED after update to r2410[/B][/COLOR] [S]3[/S][S]2-bit D610 not showing Partclone status info (blue screen) on screen during imaging. But 64-bit machines work just fine. Most likely a kernel issue. BUT image proceeds correctly. (work in r236?) --Tom is looking into this.[/S]

This post will be updated with more issues as they are come across or posted.

Please update to r2403 to remove this bug. However, this patch messed up a few other things so you may want to hold off for a bit.

Version 2389 (1.3)

When trying to schedule a cron style job from group management it fails.

Group Management ==> List All Groups ==> [Select Group] ==> Basic Tasks ==> [Select Advanced] --> [Select Donate] --> Schedule Cron-style Deployment --> [30] [17] [] [] [1-5] --> Click Donate Task

Here is the result.
[ATTACH]1405[/ATTACH]

With no task listed in [COLOR=#7baa0f][FONT=Ubuntu]Scheduled Tasks[/FONT][/COLOR].

[url=“/_imported_xf_attachments/1/1405_Untitled.png?:”]Untitled.png[/url]

It is NOT recommended to change the storage path. BUT…

Under Storage Management --> Select node <node you change the path on> and change the Image Path to /ivimages. Then you will need to make sure that directory exists. If not then do a mkdir and then change the permissions to a chmod 777

Then you will need to have copy the hidden files in /images and /images/dev. These files are both named .mntcheck.

meaning…
[CODE]sudo mkdir /ivimages
sudo mkdir /ivimages/dev
sudo cp /images/.mntcheck /ivimages
sudo cp /images/dev/.mntcheck /ivimages/dev
sudo chown -R fog /ivimages
sudo chmod -R 755 /ivimages
sudo chmod -R 777 /ivimages/dev
[/CODE]

This method forces the copy of the paths and files. But fog may do this automatically.

Edit:

ALSO looks like someone asked right before you did…
[url]http://fogproject.org/forum/threads/moved-images-folder-now-fatal-error-failed-to-mount-nfs-volume.11422/[/url]

It took 40 seconds to get a DHCP address that is and issue in itself.

updated Working Devices to include

[FONT=sans-serif][COLOR=#000000][SIZE=13px]HP ProBook 6450b ✓ Defualt bzImage undionly.kpxe 2014-06-13
HP Probook 645 ✓ Defualt bzImage undionly.kkpxe 2014-06-13 Disable UEFI-Bootdodus in BIOS. undionly.kkpxe is not a typo you need to use this file to boot properly.[/SIZE][/COLOR][/FONT]

[url]http://fogproject.org/wiki/index.php/Tftp_timeout[/url]…

Added Fedora 20 section and added the suggested line of “systemctl stop firewalld.service && systemctl disable firewalld.service”

[ATTACH=full]1245[/ATTACH]

Maybe something like?

Or at least a cut off time. If task does not start after [B]X[/B] number of hours/min, then cancel task.

[url=“/_imported_xf_attachments/1/1245_Untitled.png?:”]Untitled.png[/url]

fyi you can always post your install log. This log is located at /var/log/foginstall.log

It may give more insight than your quick copy paste.

• PXE Boot menu

1. background image location is–> /var/www/fog/service/ipxe/bg.png Just keep the pixel size and the name same. FYI you will need to replace the file [B]each and every time[/B] you update.
2. Does really matter were it is located on the Fog Boot Menu?
3. The steps to upgrade are very similar to what you want to do. You will need to copy the /images dir to the new server in location /images then you will need to create the image with the EXACT name of the dir’s in the /images dir. IF you were using 0.32 then you will need to change the image option to partImage from partClone. BUT if you were using 0.33b+ or 1.x.x then you keep the timage option to partClone. Yes then you may need to change the permissions to 777 on those dirs.

If I stated anything wrong here please correct me.

Yep issue confirmed in 2111. I will test latest revision in the morning.

If you get this issue please power cycle the host/client. The copying of data is complete but there was an issue exiting the download task so, the next boot the client will have the new image. Just continue as normal.