fog problem ?
-
So it work now but i have a problem with the upload of the image.
i try to upload an image and it copy the entire disk (even the space not used)
I’d like know if it’s normal or not and if their is a solution if it’s a problem from me.
i try to upload a debian 7.3
thanks guys
edit:
-
@Varion Keep going like what?
What did you do that got it operational for you? What changed, how did it get fixed?
Why would your fog server need to handle DHCP? You just edit the boot file that your dhcp server is currently handing out and you should be operational. Of course, that all aside, you would need to make sure that the switches you’re using are not in STP - Plain mode. If you MUST use STP, make sure it’s possible to use Rapid STP or PortFast (or the equivalent setting as defined for your network switches/routers).
No such file or directory as described only a few posts earlier would indicate, to me, that it cannot find the FOG Server by the IP Address (192.168.3.79). If FOG is handling the DHCP at that point, what’s giving FOG the IP address? Even if it’s statically defined it does not automatically mean it will operate.
What is your supervisor’s system doing? Is it handling DHCP (AKA proxy dhcp or a rogue dhcp server?)
-
@Tom-Elliott
keep going like that --> keep working
I have just install the fog server on a physical computer not a VM (with virtualbox) i have change nothing during the installation or anything else.
We have a switch that use STP but it’s not the problem (we have the server on the physical computer which work)
We have DHCP server but looks like it’s not the problem because our server work now.The only problem we have right now is that when we want to upload an image it take the full disk instead of just the occupied space.
My supervisor have a question, does the fog version 1.2.0 support LVM and did the upload take just the disk space occupied or the entire disk? -
@Varion said:
The only problem we have right now is that when we want to upload an image it take the full disk instead of just the occupied space.
My supervisor have a question, does the fog version 1.2.0 support LVM and did the upload take just the disk space occupied or the entire disk?FOG supports LVM disks, but only as non-resizable. That said, the free space on the disk compresses down to almost nothing. FOG currently supports resizing for Ext4 and NTFS.
-
@Wayne-Workman okay thank’s
Does the version of FOG 1.2.0 allow to choose the partition that we want to upload or not ?
Or how did we can upload an debian os install on lvm with some logic volume like swap of 4g, logic volume home of 300g (1% used)… or we have an other solution (like an other os or things like that), how can we make an efficient save with fog ( just the disk space used, without copy the 300g from the volume home which are useless for us). We just want to copy the OS for deploying it to new computer. -
i have "fatal error: failed to mount nfs volume when i want to upload
-
@Varion For the NFS issue, we need more details. What’s the image path inside that node’s storage management? What’s the contents of
/etc/exports? Have you ran through the Troubleshoot NFS article? -
@Wayne-Workman
/images
the server try to mount the nfs volume with the old server address. Where can we change that if it’s possible ?
mounting file system … mount: mounting 192.168.3.79:/images/dev/ on /images failed: No route to host
and the ip address of the fog server is 3.95
-
@Varion Changing a FOG server’s IP is not as easy as it might seam. Here are instructions on this: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
The error (wrong IP) you are seeing at this stage is caused the storage management settings in the web gui (Storage Management -> DefaultMember -> IP Address). But please make sure to follow the instructions in that wiki article and get it all corrected!
-
The default storage ip address is good, i’ve checked all the instructins in your link but nothing happen. The error message is still here
-
@Varion said:
@Wayne-Workman
/images
the server try to mount the nfs volume with the old server address. Where can we change that if it’s possible ?
mounting file system … mount: mounting 192.168.3.79:/images/dev/ on /images failed: No route to host
and the ip address of the fog server is 3.95What do you mean by:
@Varion said:
The default storage ip address is good, i’ve checked all the instructins in your link but nothing happen. The error message is still here
THe first picture doesn’t show anything the a directory contents of what appears to be the home folder of the user currently signed in.
What Sebastian is talking about is the IP Address within the Storage nodes under Storage Management Page. If your fog server is still looking at the “old” IP address for handling NFS this would explain the IP Address issue you’re describing. That OR your “old” fog server is still up and running under 192.168.3.79, and all of your bootup settings (TFTP Option 66/67) are still looking at the “old” fog server.
-
he look at the good IP address.
I have install once fog on a new computer and i have a “tsc: fast tsc calibration failed”
the other error are gone for now >_< -
“tsc: fast tsc calibration failed” is not a problem! Just ignore the message…
-
@Sebastian-Roth
maybe sometimes but in my case the computer start a normal boot and cancel the task of upload the image -
@Varion I am pretty sure this is not causing your problem. Possibly this is the last message you see but I doubt it’s the cause. Please try updating the kernel (Web GUI -> FOG Configuration -> Kernel Update) and see if you still run into the same problem.
Please let us know which computer (exact model!) you are seeing this problem on and best if you could take a (slow motion - iPhone can do this) video of the screen when this is happening!!
My guess is that this is caused by a hardware issue. Memory (memtest) or damaged hard drive?
-
I’ll give you that soon.
And i have an other strange thing, i’ve upgrade my fog 1.2.0 to trunk but the website is still 1.2.0 is it normal ? (i have follow the tuto with git https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk i need to update the kernel or something like this ? )
-
I’ve test it on a new computer we have received, a hp probook (they are all hp probook) i think it’s this model http://store.hp.com/FranceStore/Merch/Product.aspx?id=P4P61EA&opt=ABF&sel=NTB
-
@Varion About the web interface: See what you get from those commands and post the output here:
grep DocumentRoot /etc/apache2/sites-enabled/001-fog.confandls -al /var/wwwWhat did you mean by “the computer start a normal boot and cancel the task of upload the image”?? Please let us know where exactly the task is canceled!! Error messages you see? Or just reboot or hang? Best if you can upload a picture or video so we know what exactly you see. Otherwise we’re just guessing.
-
“the computer start a normal boot and cancel the task of upload the image” --> reboot yes sorry
For the commands:
grep DocumentRoot /etc/apache2/sites-enabled/001-fog.conf --> no result
ls -al /var/www
-
@Sebastian-Roth
Entrez le nouveau mot de passe UNIX : Retapez le nouveau mot de passe UNIX : passwd : le mot de passe a été mis à jour avec succès
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Synchronizing state for mysql.service with sysvinit using update-rc.d…
Executing /usr/sbin/update-rc.d mysql defaults
Executing /usr/sbin/update-rc.d mysql enable
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Operation failed: Aucun fichier ou dossier de ce type
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Operation failed: Aucun fichier ou dossier de ce type
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
Failed to get D-Bus connection: Erreur inconnue -1
