@Bristow-0 you may already do this. But you mentioned you clone the vm and not back it up. Would it not be best to run a proxmox backup of the fog server VM to another location like a Nas/share located elsewhere.
Posts made by falko
-
RE: Script for a backup ?
-
RE: windows 10 21H2 FOGService not starting
@george1421 @EduardoTSeoane thanks guys, picking up from Kallum here as he is not on site.
In this new Image Build, we are experiencing the same issue as discussed here where it seems the SetupComplete in Windows 10 21H2 runs but does not run as administrator so unable to change service settings.
Is anyone able to confirm this?
-
RE: Service status of FOGServcie cannot be changed after deployment
we are also experiencing this where it appears the SetupComplete is running but not being run as an Administrator so unable to make changes/start the service as my colleague has experienced. in the post below
https://forums.fogproject.org/topic/16327/windows-10-21h2-fogservice-not-starting/2
-
RE: Updating Issues from Dev-Branch 1.5.7.58
@Tom-Elliott Thanks Tom for checking this, I just updated (1.5.7.585) however and still spammed by the success boxes
-
RE: Updating Issues from Dev-Branch 1.5.7.58
Hi,
I have updated to Working-1.6 (1.5.7.853)
During Install on setting up and starting nfs server it reports [failed to get unit file state for nfs-server.service no such file or directory] but it does start OK.
As for imaging I am unable to image from the pxe menu
But I can deploy tasks from the web gui & when I do it returns maybe 20 or so success boxes. This issue also happens when on a Host Management page and I click Update (if I changed the image etc.)
Another issue is at the end of when the image is deployed I receive
I also seem unable to export the database from the Save Configuration page
Server is: Debian 8.11 Jessie
Version: Working-1.6 (1.5.7.853)
Kernel: 4.19.64 -
Does branch 1.6 not use the 0.11.17 client?
Does branch 1.6 not use the 0.11.17 client?
-
RE: Updating Issues from Dev-Branch 1.5.7.58
Hi,
Server is: Debian 8.11 Jessie
and yes I have jumped to 1.6 and back to Dev-Branch before (everything seemed to work OK, this was a few weeks ago maybe so no Database Upgrade).
This time however I used VM snapshot to roll back (instead of a downgrade), I’m back in work on Friday so I may be able to get more info then
-
Updating Issues from Dev-Branch 1.5.7.58
Hi,
Having Issues updating from Dev-Branch 1.5.7.58
-
Updating to latest Dev-Branch = Database failed to update
-
Updating to latest Working-1.6 = NFS Service failure
Have rolled back VM as we are currently imaging some new machines so unable to get any more info right now. but I can try the update again soon hopefully if more info is needed
-
-
RE: Anyone in UK have hardware from stone?
@Sebastian-Roth said in Anyone in UK have hardware from stone?:
@falko Do you know the specs of the machine yet? Mainboard, disk, network chip?
No not in detail, will hopefully get that info on Monday.
-
RE: Anyone in UK have hardware from stone?
Thanks @george1421 I wanted to know if anyone had them and was able to image with FOG. I don’t see it being an issue but we won’t get the test unit until after this coming week
-
Anyone in UK have hardware from stone?
Hi,
Does anyone here have hardware from stone, they make their own hardware ?
Usually go with Dell, but for this project (30 laptops) we are looking at competitive quotes from all.
Thanks
-
RE: Deploy associed image on boot menu
@lebrun78 it is possible to have only the assigned image in the deployment list via the menu. Can’t recall what setting it is right now.
EDIT: as George said item in FOG Settings under FOG Boot Settings will allow you to display the images as a list or not.Also how are your students able to access it, a username and password is needed to access the menu
-
RE: Creating group, members add themselves.
When I have experienced the issue in the past I have always found that the phantom hosts added to new groups were only the most recent hosts that were registered. Whether that be 2 hosts or 5 phantoms
Running the SQL maintenance commands from the wiki (as mentioned I think updates also helped) seemed to resolve
-
RE: upgrading from 1.5.0 to 1.5.1 fails at backup
@tom-elliott strangley my fog clients all reported Middleware::Response ERROR: so I reset encryption on my ‘all hosts’ group. Not sure if there was something else I needed/should have done but that sorted it.
-
RE: upgrading from 1.5.0 to 1.5.1 fails at backup
@tom-elliott that was quick! Upgrade seemed to go through fine.
-
upgrading from 1.5.0 to 1.5.1 fails at backup
Hi,
when I try to upgrade to 1.5.1 it fails at the database backup
(running Debian 8.10 & FOG 1.5.0)- Setting up Apache virtual host (no SSL)…OK
sed: can’t read /etc/php/5/fpm/pool.d/www.conf: No such file or directory - Starting and checking status of web services…OK
- Changing permissions on apache log files…OK
- Backing up database…Failed!,
- Setting up Apache virtual host (no SSL)…OK
-
RE: FOG 1.5.0 RC 13 and FOG Client v0.11.14 Released
@tom-elliott cool, not sure if it’s just me/my setup but since moving to rc12/13 the server UI seems more responsive
-
RE: FOG 1.5.0 RC 13 and FOG Client v0.11.14 Released
Tom, just upgraded (switched from working to dev) and the FOG_CLIENT_VERSION is still defined as 0.11.13 in system.class.php