@Sebastian-Roth Hi, big problem this morning, after upgrading to 1.5.7.89 yesterday, all computers tried to update fog client to 0.11.17, and it failed for all !
fog.log give me this :

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 07/01/2020 16:44 Client-Info Client Version: 0.11.16
 07/01/2020 16:44 Client-Info Client OS:      Windows
 07/01/2020 16:44 Client-Info Server Version: 1.5.7
 07/01/2020 16:44 Middleware::Response ERROR: Unable to get subsection
 07/01/2020 16:44 Middleware::Response ERROR: Object reference not set to an instance of an object.
 07/01/2020 16:44 Service Sleeping for 126 seconds
 07/01/2020 16:46 Middleware::Communication URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 07/01/2020 16:46 Middleware::Response Success
 07/01/2020 16:46 Middleware::Communication URL: http://192.168.10.60/fog/management/index.php?sub=requestClientInfo&mac=74:27:EA:6C:AA:0D&newService&json
 07/01/2020 16:46 Middleware::Authentication Waiting for authentication timeout to pass
 07/01/2020 16:46 Middleware::Communication Download: http://192.168.10.60/fog/management/other/ssl/srvpublic.crt
 07/01/2020 16:46 Data::RSA FOG Server CA cert found
 07/01/2020 16:46 Data::RSA ERROR: Certificate validation failed
 07/01/2020 16:46 Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: La signature du certificat ne peut pas être vérifiée. (NotSignatureValid)
 07/01/2020 16:46 Middleware::Authentication ERROR: Could not authenticate
 07/01/2020 16:46 Middleware::Authentication ERROR: Certificate is not from FOG CA
 07/01/2020 16:46 Middleware::Response Success
 07/01/2020 16:46 Middleware::Communication URL: http://192.168.10.60/fog/service/getversion.php?clientver&newService&json
 07/01/2020 16:46 Middleware::Communication URL: http://192.168.10.60/fog/service/getversion.php?newService&json

 07/01/2020 16:46 Service Creating user agent cache
 07/01/2020 16:46 Middleware::Response ERROR: Unable to get subsection
 07/01/2020 16:46 Middleware::Response ERROR: Object reference not set to an instance of an object.
 07/01/2020 16:46 Middleware::Response ERROR: Unable to get subsection
 07/01/2020 16:46 Middleware::Response ERROR: Object reference not set to an instance of an object.
 07/01/2020 16:46 Middleware::Response ERROR: Unable to get subsection
 07/01/2020 16:46 Middleware::Response ERROR: Object reference not set to an instance of an object.

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 07/01/2020 16:46 Client-Info Client Version: 0.11.16
 07/01/2020 16:46 Client-Info Client OS:      Windows
 07/01/2020 16:46 Client-Info Server Version: 1.5.7.89
 07/01/2020 16:46 Middleware::Response Success
 07/01/2020 16:46 Middleware::Communication Download: http://192.168.10.60/fog/client/SmartInstaller.exe
 07/01/2020 16:46 Data::RSA FOG Project cert found
 07/01/2020 16:46 ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 07/01/2020 16:46 Bus Emmiting message on channel: Update
 07/01/2020 16:46 Service-Update Spawning update helper
 07/01/2020 16:46 UpdaterHelper Shutting down service...
 07/01/2020 16:46 UpdaterHelper Killing remaining processes...
 07/01/2020 16:46 UpdaterHelper Applying update...
 07/01/2020 16:47 UpdaterHelper Starting service...

And nothing since more than 12 hours… Do I have to regenerate certificate ? With what consequences ?
Thanks

• For client, it’s a Windows installation, there is no older version on machine, same error with admin rights.
  But I think it could be related to a modification I made few weeks ago : I tried to run fog installer to activate https (./installfog.sh -S). It worked but I returned back because I’ve got another application on Fog server which was inaccessible with https activated…

• Lastlog command returns this (and I don’t have the fogproject user error anymore so that’s a very good point !!!):

Username         Port     From             Latest
root                                       **Never logged in**
daemon                                     **Never logged in**
bin                                        **Never logged in**
sys                                        **Never logged in**
sync                                       **Never logged in**
games                                      **Never logged in**
man                                        **Never logged in**
lp                                         **Never logged in**
mail                                       **Never logged in**
news                                       **Never logged in**
uucp                                       **Never logged in**
proxy                                      **Never logged in**
www-data                                   **Never logged in**
backup                                     **Never logged in**
list                                       **Never logged in**
irc                                        **Never logged in**
gnats                                      **Never logged in**
nobody                                     **Never logged in**
systemd-timesync                           **Never logged in**
systemd-network                            **Never logged in**
systemd-resolve                            **Never logged in**
systemd-bus-proxy                           **Never logged in**
_apt                                       **Never logged in**
messagebus                                 **Never logged in**
sshd                                       **Never logged in**
debian                                     **Never logged in**
mysql                                      **Never logged in**
statd                                      **Never logged in**
tftp                                       **Never logged in**
ftp                                        **Never logged in**
fog                                        **Never logged in**
fogproject                                 **Never logged in**

• And for updating database error I run fog installer once again from scratch (deleted .fogsettings), it asked me mysql password twice and now update is ok (1.5.7 and then 1.5.7.89). So I tested once again client installation after 1.5.7.89 update (client 0.11.17 available on web interface) but still same error…

Good news is that now I’ve just one problem to resolve : client installation !
See you tomorrow

Hi Sebastian,

Thanks for your reply.

• Concerning error with fog client, it’s exactly the same problem with 0.11.17 (and yes I was using 0.11.16 previously), here is the content of FOGService.install.log file :

 07/01/2020 14:59 Data::RSA FOG Server CA cert found
 07/01/2020 15:00 Data::RSA FOG Server CA cert found
 07/01/2020 15:00 Installer ERROR: Could not unpin FOG server CA cert
 07/01/2020 15:00 Installer ERROR: Access denied.
 07/01/2020 15:00 Installer ERROR: Could not pin server CA
 07/01/2020 15:00 Installer ERROR: Access denied.

• For lastlog file I absolutely don’t know why it’s missing, I recreated it (touch /var/log/lastlog) so know error message is :

 * Setting up fogproject user..................................Already exists

The account "fogproject" already exists but this seems to be a
fresh install. We highly recommend to NOT creating this account
beforehand as it is supposed to be a system account not meant
to be used to login and work on the machine!

Please remove the account "fogproject" manually before running
the installer again. Run: userdel fogproject

• And for updating database error, here is the end of fog_error_1.5.7.log (sorry some french words…)

To activate the new configuration, you need to run:
  systemctl reload apache2
Site 000-default disabled.
To activate the new configuration, you need to run:
  systemctl reload apache2
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-01-07 15:11:34 CET; 2s ago
  Process: 15930 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
 Main PID: 15935 (apache2)
    Tasks: 6 (limit: 4915)
   CGroup: /system.slice/apache2.service
           ├─15935 /usr/sbin/apache2 -k start
           ├─15942 /usr/sbin/apache2 -k start
           ├─15943 /usr/sbin/apache2 -k start
           ├─15944 /usr/sbin/apache2 -k start
           ├─15945 /usr/sbin/apache2 -k start
           └─15946 /usr/sbin/apache2 -k start

janv. 07 15:11:34 FOG systemd[1]: Starting The Apache HTTP Server...
janv. 07 15:11:34 FOG systemd[1]: Started The Apache HTTP Server.

● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-01-07 15:11:34 CET; 2s ago
     Docs: man:php-fpm7.0(8)
 Main PID: 15934 (php-fpm7.0)
   Status: "Ready to handle connections"
    Tasks: 6 (limit: 4915)
   CGroup: /system.slice/php7.0-fpm.service
           ├─15934 php-fpm: master process (/etc/php/7.0/fpm/php-fpm.conf)
           ├─15936 php-fpm: pool www
           ├─15937 php-fpm: pool www
           ├─15938 php-fpm: pool www
           ├─15939 php-fpm: pool www
           └─15940 php-fpm: pool www

janv. 07 15:11:34 FOG systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
janv. 07 15:11:34 FOG systemd[1]: Started The PHP 7.0 FastCGI Process Manager.
--2020-01-07 15:11:36--  http://192.168.10.60//fog//maintenance/backup_db.php
Connexion à 192.168.10.60:80… connecté.
requête HTTP transmise, en attente de la réponse… 302 Found
Could not parse String-Transport-Security header
Emplacement : ?node=schema [suivant]
--2020-01-07 15:11:36--  http://192.168.10.60//fog//maintenance/backup_db.php?node=schema
Connexion à 192.168.10.60:80… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : non indiqué [text/html]
Sauvegarde en : « /home//fogDBbackups/fog_sql_1.5.7_20200107_031136.sql »

     0K                                                        1,58M=0s

2020-01-07 15:11:37 (1,58 MB/s) - « /home//fogDBbackups/fog_sql_1.5.7_20200107_031136.sql » sauvegardé [31]

Hi,

I have different problems with my fog server :

• Since few weeks it’s impossible to install fog client on computers, I tried with FOGService.msi and SmartInstaller.exe, using right Fog server IP but each time this message is displayed

unable to install CA certificate: access denied

• Each time I want to update Fog I have to run command userdel fogproject, if not this message is dispayed

Setting up fogproject user................................../var/log/lastlog: Aucun fichier ou dossier de ce type
Already exists
The account "fogproject" already exists and has been used to logon and work on this machine. We highly recommend you NOT use this account for your work as it is supposed to be a system account!
Please remove the account "fogproject" manually before running the installer again. Run: userdel fogproject

• I 'm actually on master branch (1.5.7), so I tried to use dev-branch (1.5.7.89) to see if it resolves these issues, but then installation failed with message

* Updating Database...........................................Failed!

Thanks for your help
Matthieu

@Sebastian-Roth Hi, thanks so much for your work and help, I’ll test as soon as I came back to work, after 19th August.

@Sebastian-Roth Hi, sorry for the delay but so much work and so little time…
here is the result from parted -l command with debug capture task, il it can help…

I’m on vacation in few minutes and I’ll be back in August 16th

Thanks

@Quazz Hi, first partition is Recover (500Mb), I don’t know why it’s not marked as fixed, I still can edit file ta add 1: at the beginning ? But sda1 size is not the on d1.partitions and d1.miminum.partitions

@Sebastian-Roth Hi, to speak about the same and only d1.mbr, d1.partitions and d1.miminumpartitions, I continue test and I made fresh win10 UEFI install and revert Fog to 1.5.5 version. But problem was the same, capture and deploy image on SSD 128GB is ok, but deploy on 50GB disk failed.
A colleague made some change on these 3 files (d1.mbr and the 2 d1 partitions files) to change dev/sda4 size from 248745984 to 104857600, and now it works great !!!
So I think it’s a Fog capture problem, here’s a link with 2 folders : Win10 for original capture which failed on smaller disk, and 50GB with working modified files
https://send.firefox.com/download/28dabd13930e0bc0/#BMGg3OazBC_kUld0vkPs6w

Thanks

@Sebastian-Roth Hi Seb, finally my trick resolve issue on some smaller disk (works now on 120GB disk with image created on 128GB disk), but some old computer with 60GB have still same error, can you take a look to d1.mbr file here ?
https://send.firefox.com/download/f8a134b57bdefad8/#lyrswaozWAFfuWTEcrYrNQ
Maybe some hex modification as in this topic is possible ? https://forums.fogproject.org/topic/13220/error-trying-to-restore-gpt-partition-deploying-an-image-to-smaller-disk/7

Thanks
Matthieu

@Sebastian-Roth Image was captured on 128GB SSD and failed to deploy on 120GB SSD, but I found an ugly solution that resolved my problem very well : thanks to you and @Quazz I did’nt notice that good layout contains 4 and not 3 partitions, so I just copy all files from a “good” image to a bad image folder, exept windows data partition that I renamed from d1p3.img to d1p4.img and everything works great !!!

Defective image

Fonctionnal image

New image by copy all files from fonctionnal image except d1p4.img from defective image

So for me this problem is resolved, big thanks to Fog team
Matthieu

@Quazz It’s fog 1.5.6.4 with latest kernel (4.19.36 and 4.19.48).
Indeed I’ve got 2 images with 4 partitions (one is hidden 16MB, not showed on disk manager but listed with diskpart) and no problem to deploy these ones, but on 2 other images there’s just 3 partitions (OEM, system and windows) and I’ve got trouble on different configuration…
So it may be related to mbr2gpt command I use to transform legacy to UEFI but I made it for my 4 images and 2 only are ok, I don’t know why and how to fix that…

@Sebastian-Roth Ok I have same issue on another computer with standard layout, I think it coul be related to Win10 1903 update ? If I upload image before sysprep and deploy on another configuration, it’s ok. But if I sysprep and then capture image, deploy failed

d1.fixed_size_partitions
:2:2

d1.minimum.partitions
label: gpt
label-id: 6A1C2439-885F-11E9-BB12-1866DA164C99
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=       24940, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=6A1C2436-885F-11E9-BB12-1866DA164C99, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda2 : start=     1979904, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=6A1C2437-885F-11E9-BB12-1866DA164C99, name="attrs=\x22GUID:63"
/dev/sda3 : start=     2182656, size=    46627670, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=6A1C2438-885F-11E9-BB12-1866DA164C99

d1.partitions
label: gpt
label-id: 6A1C2439-885F-11E9-BB12-1866DA164C99
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=     1977856, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=6A1C2436-885F-11E9-BB12-1866DA164C99, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda2 : start=     1979904, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=6A1C2437-885F-11E9-BB12-1866DA164C99, name="attrs=\x22GUID:63"
/dev/sda3 : start=     2182656, size=   247886848, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=6A1C2438-885F-11E9-BB12-1866DA164C99

I passed this script but same result

dism /online /cleanup-image /startcomponentcleanup
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /restorehealth
sfc /scannow
chkdsk C: /f

@Quazz yeah, strange layout I agree
Any way to restore a good layout (gparted or else) ?

@Sebastian-Roth Ok I continue test, upgrading image to 1903 but still same problem.
So these are results on PC I used to update masters, Dell Optiplex 3020 with SSD 128GB. I have no problem to upload and deploy image on this model, but all others models failed with “Error trying to restore GPT partition tables. Exit returned code 4”

d1.partitions :

label: gpt
label-id: 24A810B8-1662-11E9-AB92-B083FE947687
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=   248742296, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=24A810B5-1662-11E9-AB92-B083FE947687
/dev/sda2 : start=   248745984, size=     1116160, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=5F6E777F-5719-4379-A14B-0397E0C234B2, attrs="RequiredPartition GUID:63"
/dev/sda3 : start=   249862656, size=      206848, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=24A810B6-1662-11E9-AB92-B083FE947687

d1.minimum.partitions :

label: gpt
label-id: 24A810B8-1662-11E9-AB92-B083FE947687
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=    55035482, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=24A810B5-1662-11E9-AB92-B083FE947687
/dev/sda2 : start=   248745984, size=     1116160, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=5F6E777F-5719-4379-A14B-0397E0C234B2, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda3 : start=   249862656, size=      206848, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=24A810B6-1662-11E9-AB92-B083FE947687

d1.fixed_size_partitions :

:3:2:2:3

And for parted -l /dev/sda command :

Thanks
Matthieu

Hi,

I deployed image on a PC to update Win10 to 1903, no problem but when I tried to upload image I’ve got this error

I already have this problem in the past, resolved by these commands, but not this time…

dism /online /cleanup-image /startcomponentcleanup
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /restorehealth
sfc /scannow
chkdsk C: /f```

Thanks !
Matthieu

@Sebastian-Roth lastlog command is installed but doesn’t return any result for fogproject user, and same problem for fog and root account ! I just don’t understand, very strange…

For error deploying image, I tried to uplaod image on another computer and now I’ve got this…

Debug command parted -l /dev/sda give this

I don’t understand but I’m leaving office now for a big week-end until monday, I’ll chek this next week !

Thanks
Matthieu

@Sebastian-Roth said in Error trying to restore GPT partition tables. Exit returned code 4:

lastlog --user fogproject --clear

ok, for machine I capture image I’ll test tomorrow.

For lastlog command it returns an error : No such file or directory

@Sebastian-Roth first for fogproject account, I’ve got this message each time I run install.sh :

 * Configuring services

 * Setting up fogproject user................................../var/log/lastlog: Aucun fichier ou dossier de ce type
Already exists

The account "fogproject" already exists and has been used to
logon and work on this machine. We highly recommend you NOT
use this account for your work as it is supposed to be a
system account!

Please remove the account "fogproject" manually before running
the installer again. Run: userdel fogproject

So I delete this user I installer run fine, until next time…
fogproject account is created on Debian but doesn’t appear on fog web UI when I display all users (there’s just fog and root account)

In .fogsettings file I’ve got this username

username='fogproject'
password='xxxxxx'

I’ve just updated TFTP username name (it still was fog)

For partition layout, for the first one with debug task I’ve got this

I tried to deploy it removing “:4” but same error

@Sebastian-Roth Hi Seb, what I don’t understand with foguser account is that I have to delete it each time I run isntall.sh script, if not I’ve got an error message. Not a big deal but strange…

For text files, I’ve got this for first image I tested

d1.partitions :

label: gpt
label-id: 4C01BDD7-29D4-4B8C-99D8-987EEA909303
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=     1021952, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=081D3F0B-1B52-4643-8A24-684A7C1A8429, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/sda2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=607139A0-16C8-4261-BB87-253F40D707BD, name="EFI system partition", attrs="GUID:63"
/dev/sda3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=485F8027-C27D-4519-AA08-3980851152A7, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda4 : start=     1261568, size=   248807936, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=5BB64B2B-6646-419B-BE8A-13BB2269F0E8, name="Basic data partition"

d1.minimum.partitions

label: gpt
label-id: 4C01BDD7-29D4-4B8C-99D8-987EEA909303
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=       21394, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=081D3F0B-1B52-4643-8A24-684A7C1A8429, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/sda2 : start=     1024000, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=607139A0-16C8-4261-BB87-253F40D707BD, name="EFI system partition", attrs="GUID:63"
/dev/sda3 : start=     1228800, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=485F8027-C27D-4519-AA08-3980851152A7, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda4 : start=     1261568, size=   248807936, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=5BB64B2B-6646-419B-BE8A-13BB2269F0E8, name="Basic data partition"

d1.fixed_size_partitions

:2:3:4

and for the second one :

d1.partitions

label: gpt
label-id: 24A810B8-1662-11E9-AB92-B083FE947687
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=   249860608, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=24A810B5-1662-11E9-AB92-B083FE947687
/dev/sda2 : start=   249862656, size=      206848, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=24A810B6-1662-11E9-AB92-B083FE947687

d1.minimum.partitions

label: gpt
label-id: 24A810B8-1662-11E9-AB92-B083FE947687
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 250069646

/dev/sda1 : start=        2048, size=   249860608, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=24A810B5-1662-11E9-AB92-B083FE947687
/dev/sda2 : start=   249862656, size=      206848, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=24A810B6-1662-11E9-AB92-B083FE947687

d1.fixed_size_partitions
:2:2

Hi,

I try to deploy image on computer, each time I ahve this error :

Error trying to restore GPT partition tables
Exit returned code 4

I test on 2 different computers, 2 different images and 3 fog version (master, dev-branch and working), always same error…

Since few weeks when I upgrade fog (git pull then ./installfog.sh), I have error message about deleting fogproject account. But I never created fogproject user, just fog user, and I each fog installer create once again this fogproject account. Could it be related ? Acces right problem between fog and foguser account ?

Thanks for help !