Try: [url]http://fogproject.org/wiki/index.php/Upgrade_to_trunk#SVN[/url]
[CODE]cd /some/local/folder/
svn up
cd bin
./installfog.sh[/CODE]
[LIST]
[*][I]NOTE:[/I] You must run [B]svn up[/B] in the “/some/local/folder/” and not in “…/fog/bin” or in “…/fog”
[/LIST]
sry bad info. Tom says these are “normal” system accounts that should not be able to be removed. If i created test it was able to be deleted. See my test account![ATTACH=full]1616[/ATTACH]
[url=“/_imported_xf_attachments/1/1616_Untitled.png?:”]Untitled.png[/url]
fog/management/index.php?node=service&sub=edit#usercleanup
[LIST]
[]unable to remove users from usercleanup
[]no X’s for remove
[/LIST]
[ATTACH=full]1615[/ATTACH]
[url=“/_imported_xf_attachments/1/1615_Untitled.png?:”]Untitled.png[/url]
SO instant works but not delayed. have you tried cron-syle?
Sry currently testing the delayed on my configuration. I usually don’t use the delayed method. Just instant and cron-style.
Edit: delayed donate works for me. about 3 mins off from scheduled time thought. Most likely due to task check periods
I hate to throw this out there but did you disable windows firewall yet?
Server 1
Server 2
Storage 1 (same harddrive on a vm)
So you are saying that [Server 1] and [Server 2] both share /images on [Storage 1].
This will work without issues as long as you do not call the images the same name. so [Server 1] can have /images/image_dell] and [Server 2] can have /images/image_Dell. (yes they are different!).
If you do use the same name the last to upload will overwrite the original.
Odd some of the devs discussed this same issue earlier last week.
1.) Download the images to hardware and reupload. This way you don’t need to enable “legacy” images but you will not carry over the sql database and will need to re-register every host.
OR
2.) Mount the /images folder of the new server to /images2 and copy all contents. This way you will need to enable “legacy” images but if you follow the wiki I posted above you will keep all your hosts/group/ information. BUT see the Warning for importing the old database into the new install.
That would be best.
I do not now how far along you are with the FOG 1.2.0, (New images, registered hosts, etc) [url]http://fogproject.org/wiki/index.php/Upgrade_to_1.x.x[/url] migration upgrade would be a good reference if you 1.2.0 install has just been installed. (ie no images, no hosts, no groups)
I know its kind of confusing but the export of the old database would give you your old hosts info. But if you have already started registering on the new server, the import of the old database would do nothing but cause trouble.
So the real question is how much have you done with the new 1.2.0 server?
Thank you for upgrading!
We wanted to know what your server version was b/c there are may things you must do if you are moving from 0.32 to 1.x.x. So many things there is a nice wiki for it.
[LIST=1]
[*]I guess I haven’t as of yet. I keep rebuilding my images yearly and deploy soon after they are finished. You could always ftp them over to the “master” server before connecting the storage nodes. then just create the images in the web gui. as long as you drop the images in /images and name them exactly the same then you should be ok.
[/LIST]
You may also want to export your hosts and export you database. This will get you back in action faster.
This is good for the time zone.
However, for your error of “Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName.”
[SIZE=14px][quote][/quote][/SIZE][quote][SIZE=14px][FONT=UbuntuRegular][COLOR=#333333]If you insert a[/COLOR][/FONT][/SIZE]
[COLOR=#333333][FONT=Ubuntu Mono][SIZE=14px][COLOR=#222222]ServerName localhost[/COLOR][/SIZE][/FONT][/COLOR]
[FONT=UbuntuRegular][COLOR=#333333][SIZE=14px]in either [COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]httpd.conf[/SIZE][/FONT][/COLOR] or [COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]apache2.conf[/SIZE][/FONT][/COLOR] in [COLOR=#222222][FONT=Ubuntu Mono][SIZE=14px]/etc/apache2[/SIZE][/FONT][/COLOR] and restart apache the notice will disappear.[/SIZE][/COLOR][/FONT]
[/quote]
If both servers are still operational you could do either.
Why are you rebuilding the “master server”? Is this due to a hardware change or upgrade?
Also what versions of FOG are we looking at? Old server vs. New server?
[LIST=1]
[]In theory yes as long as you disable the fog server from being the master node at the instance of adding a storage node.
[]They will need to be on the same subnet mask. so 192.168.1.100 --> 10.0.0.100 will not talk to each other. you may want to look at [url]http://fogproject.org/wiki/index.php/Multiple_TFTP_servers[/url]
[*]You can increase the queue size as far as you wish but the more you add the slower the output of that node. If you queue and connect 100 hosts your speed may be 100mb/min but if you decrease to 20 then it may be 1GB/min (environment variable dependent). You can also have the node do all the nfs work and the server only house the mysql decreasing the demand of a large harddrive for the images to be stored.
[/LIST]
Interesting. Thank you for the update. Was there something different in-particular about these machines? Different OS?
[quote=“geoffpeters, post: 41043, member: 25329”]Yes, both php.ini files contain date.timezone=“America/Los_Angeles”. My path includes apache2, I assume that is OK.
I followed the steps you outlined and I restarted the FOG server.
When I restart the apache2 service I get a message:
“Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName.”
[/quote]
check this out you may want to look at those files again and change 127.0.1.1 to localhost
[url]http://askubuntu.com/questions/256013/could-not-reliably-determine-the-servers-fully-qualified-domain-name[/url]
Here is what I have used before. This is for a windows host but you’ll get the jist.
[url]http://www.addictivetips.com/windows-tips/convert-use-your-physical-machine-in-vmware-virtualbox-virtual-pc/[/url]
Just to back up Junkhacker here are the instructions to upgrade from 0.32 to 1.20:
[LIST]
[][url]http://fogproject.org/wiki/index.php/Upgrade_to_1.x.x[/url]
[]There you will notice [url]http://fogproject.org/wiki/index.php/Upgrade_to_1.x.x#Old_Images[/url]. Describing that partClone is the new method. partImage is no longer used since 0.33b. Due to this change your images will need to be set to “legacy”
[/LIST]
However, you state that unicast works and multicast does not. May I suggest to check the troubleshooting wiki:
[LIST]
[*][url]http://fogproject.org/wiki/index.php/Multicasting[/url]
[/LIST]
It [U]may,[/U] there are no guaranties. It depends on the OS and other configurations on that particular NAS.
[quote=“Jboun, post: 40989, member: 28157”]I try many things to resolv my problem but nothing works 
To isolate the NAS, I create a Windows storage node with NFS but always the same … (don’t have information disks in WEB FOG Interface)
I configured Windows NFS Server (ANSI code) with all the rights for all computers and the full access NTFS to evevryone and anonymous logon to my share c:/images.
I activate the GPO to permit the anonymous 's access in my share on Windows Server too
And Fillezilla with theses directory (and fog username/pwd used in management user) :
c:/
c:/images
c:/images/dev[/quote]
Windows will not report the bandwidth or the disk info. in the FOG Web GUI. Windows Nodes do not use the same communications as Linux. If you would like to set up a Windows Node see [url]http://fogproject.org/wiki/index.php/Windows_Storage_Node[/url]
The only way of really knowing if it is working is to check the replication logs to see if that node is successfully replicating the files. If it is then you can set up a download task for a client and remove queuing from the fog server and other nodes on the network.