@george1421 said in Database connection unavailable:
botched uploads
Nice thanks for the tips, worked
@george1421 said in Database connection unavailable:
botched uploads
Nice thanks for the tips, worked
@george1421 My fogserver is a VM
Deleting the “/var/lib/mysql/tc.log” file resolved the issue.
My disk was probably full but the DB could not restart until i delete the tc.log file
But my VM have 150Gb allocated. I don’t know why i have only 85Gb available. I will check that.
Thanks !
The result of df -h command :
By the way, i suspected to be out of disk space too before the post and deleted 1 image from the /images folder but nothing changed. I still can’t start the database
Hello,
My web interface of fog is suddenly no longer accessible. Everything was wirking fine yesterday, i uploaded an image and today i got MariaDB error. I recently Updated/Compiled the latest version of iPXE with the fog tutorial, maybe its related ?
My fog is version 1.5.9 installed on ubuntu 18.04.4
The command “systemctl status mariadb.service” result :
When i rerun the installer i get this :
Got no idea what to do with that.
Thanks!
Nice, working!
Thanks a lot for the tutorial and all the work!
Hello,
My fog is version 1.5.9 with kernel bzImage version 5.15.19.
I’m trying to boot a laptop ACER A515-56 on PXE IPV4 but i’m receiving this error :
“No configuration methods succeeded”.
My W2016 server DHCP boot filname configuration (067) is “ipxe.efi”.
What am i missing ? Do i have to configure anything else to be able to boot on UEFI ?
Thanks
the error :
Hello,
I’m running fog version 1.5.9-RC2.
I can’t deploy image anymore on my computers i got the following errors "image failed to restore and exited with exit code 1 (writheimage):
I can upload correctly but when i’m looking on the web interface the image appears to be at 0Go with invalid data :
The image seems to be uploaded correctly in /images :
Where should i look ?
Thanks
@Sebastian-Roth No, i didnnt change anything on the bios. I’m not at work so i can’t take a picture of it but the disk is still first on boot order. I already verified that. If i disabled PXE it’s correctly booting on disk but i don’t want that.
Maybe there is task scheduled stuck somewhere ? On the interface i can’t see any task running. Maybe i should do something on the server to clean all task ?
How Can i do that ?
Thanks
(I marked this post as resolved but it’s a missclick , sorry)
Hello,
I recently installed a fog server. I deployed an image on severals computers and since, they keep first booting on the fog PXE. There is no tasks anymore.
However the boot order is on the disk first, not on the network. It act like this on every PC i deployed.
Any Idea where the problem is ?
Thanks
well, what i needed was the french keyboard for the registration/capture/deploy.
I followed Quazz advice (General settings / keymap : azerty) and all is good now !
thanks
French, won’t be easy to use the boot menu with the wrong keyboard…
Hello, i would like to change the boot menu keyboard language. I can’t find any option for that.
There is an option in general fog settings / general settings / default locale = xxx but it’s not changing the boot menu keyboard. Is it possible to do that with fog 1.5.4 ?
Thanks
I don’t know why but its now working fine …
I still have an error in my fog client log but the computer joined the domain and get rename correctly.
There is all my fog client log :
20/12/2017 15:26 Service Starting service
20/12/2017 15:26 Bus Became bus client
20/12/2017 15:26 Middleware::Response Success
20/12/2017 15:26 Service Initializing modules
20/12/2017 15:26 Service Sleeping for 90 seconds
Hello,
i’m trying to join my computer automatically to the domain and to rename it with the fog client.
My fog client version is v0.11.12 and my fog server is on 1.4.4 .
I got this error i my logs (sorry it’s in french):
20/12/2017 11:46 Service ERROR: Unable to parse sleep time
20/12/2017 11:46 Service ERROR: Le format de la chaîne d’entrée est incorrect.
20/12/2017 11:46 Service Sleeping for 60 seconds
20/12/2017 11:46 Bus::Client ERROR: Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée
@x23piracy Well for windows 7 it wasn’t needed to sysprep to activate windows 7 licence and since we don’t have a microsoft domain it wasn’t necessary to use sysprep anyway… i think… It was working at least… xD
@x23piracy I think this is the problem, i have to sysprep before imaging if i want to activate a cloned windows 10 (for OEM w10 key).
If i don’t sysprep, he don’t want to activate it and say something like: “the previous windows, before the upgrade to windows 10, wasn’t activate”.
@x23piracy In the past we had some problems with sysprep and our anitivirus, so we are not using it. We don’t have a windows domain so it’s not a problem.
I still would like to see ur unattend.xml to see how you make it work!
Hello
I got poblem to rename and integrate computers to domaine with fog.
I’ve an error on my fog.log ;:
18/09/2017 14:54 Data::RSA FOG Server CA cert found
18/09/2017 14:54 Middleware::Authentication Cert OK
18/09/2017 14:54 Middleware::Authentication ERROR: Could not get security token
18/09/2017 14:54 Middleware::Authentication ERROR: Le fichier ‘C:\Program Files (x86)\FOG\token.dat’ est introuvable.
18/09/2017 14:48 Middleware::Communication POST URL: http://xx.xx.xx.xx/fog/management/index.php?sub=requestClientInfo&authorize&newService
18/09/2017 14:48 Middleware::Response Invalid security token
thanks