Posts made by lebrun78

@Sebastian-Roth
I am on leave for 10 days
I’ll test the new installer when I get back.

Merry Christmas

@Sebastian-Roth
Hello
msi install works when passing https=0, so if I copy a settings.json file after installation, will the operation be sustainable ?

@Sebastian-Roth
I did not try with certificats and client 0.11.16.
Without certificat 0.11.16 was working

Hello
The client do not install with msi

I have add https install installing with this option: ./installfog.sh -W https://fogus.istic.univ-rennes1.fr -S

CustomActionSchedule(Action=InstallCert,ActionType=3073,Source=BinaryData,Target=InstallCert,CustomActionData=sHTTPS=1;sUSETRAY=1;sWEBADDRESS=fogus.istic.univ-rennes1.fr;sWEBROOT=/fog;sROOTLOG=1;sProductVersion=0.11.17;sINSTALLDIR=C:\Program Files (x86)\FOG\)
MSI (s) (58:C0) [16:30:10:887]: Invoking remote custom action. DLL: C:\windows\Installer\MSI2D78.tmp, Entrypoint: InstallCert
SFXCA: Extracting custom action to temporary directory: C:\windows\Installer\MSI2D78.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action SetupHelper!SetupHelper.CustomActions.InstallCert
MSI (s) (58!20) [16:30:11:809]: Note: 1: 2205 2:  3: Error 
MSI (s) (58!20) [16:30:11:809]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
MSI (s) (58!20) [16:30:11:809]: Product: FOG Service -- Unable to install CA certificate

Unable to install CA certificate
CustomAction InstallCert returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Here is the installfog generate by misexe:
installfog.log

installsation with SmartInstaller.exe works

Could you help me ?

@Sebastian-Roth
with your modification, the execution of the script goes to the end

Thank you

@Sebastian-Roth said in Auto-Installing FOG with HTTPS enabled issues:

https://github.com/ipxe/ipxe

wget https://github.com/ipxe/ipxe works on my centos 8.0 machine

I am on a Centos 8 server.
wget https://git.ipxe.org/ipxe.git/ gives :

--2019-12-09 15:51:41--  https://git.ipxe.org/ipxe.git/
Résolution de git.ipxe.org (git.ipxe.org)… 212.13.204.60
Connexion à git.ipxe.org (git.ipxe.org)|212.13.204.60|:443… connecté.
GnuTLS: A packet with illegal or unsupported version was received.
Incapable d’établir une connexion SSL.

On a centos 7, wget https://git.ipxe.org/ipxe.git/ works

No, we don’t have any proxy.

Works without -S option

@Sebastian-Roth said in Auto-Installing FOG with HTTPS enabled issues:

fogproject/bin/error_logs/fog_error

Hello Sebastian
Using ./installfog.sh -W http://cosinus/ -S
I get the same error:

* Compiling iPXE binaries that trust our SSL certificate......Failed!

Here is my error log file:
fog_error_1.5.7.56.log

Hello.

I have always the problem.
Can’t view Advanced menu command with Firefox 70.0.1 (64 bits).
No problem with chromium or opera.
Client os is ubuntu 18.04

@Quazz
Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions.
It’s clear for me now

Hello,
Working on 1.5.7.55 version, I have a problem using single disk -resible image.
Working from a 250Go master with 34.1Go C: partition.
Deploying on a 55Go VM for test, I get a full C: partition on deploy.
I di not see any error during capturing and deploying

Here are the defintion files of the image :

cat win10light-1903/d1.fixed_size_partitions
1

cat win10light-1903/d1.minimum.partitions 
label: dos
label-id: 0x17fda016
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1021952, type=7, bootable
/dev/sda2 : start=     1024000, size=    34329556, type=7
/dev/sda3 : start=    76800000, size=      112166, type=7

 cat win10light-1903/d1.original.fstypes 
/dev/sda2 ntfs
/dev/sda3 ntfs

cat win10light-1903/d1.partitions 
label: dos
label-id: 0x17fda016
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1021952, type=7, bootable
/dev/sda2 : start=     1024000, size=    71680000, type=7
/dev/sda3 : start=    76800000, size=    38541312, type=7

Hello
I set up a new fog server to replace an old one.
We have 1 vlan for the servers, 1 VLAN (2) for the pc (~ 500) which are in the rooms of TP, 1 VLAN for the positions of the personnel of administration, and other VLANs for the wifi, projects …
My predecessor had configured the current fog server with an interface and an interface and an IP for the management interface on the server VLAN and its storage node on the VLAN (2). I think it was to avoid broadcasting multicast streams across the router.

On the test server, for the moment I only have an interface on the server VLAN.
During the deployment tests on lots of 10 machines I did not see a drop in performance.

Which architecture do you recommend?

@Tom-Elliott said in FOG 1.6, identified problems:

I have identified a few more issues and been able to correct them.

1. Clicking on pages within the menu as opposed to full refresh on the same page, some elements such as list -> select items to delete, click delete, the modal not appearing requesting password to ensure you want to do this. On full refresh to link it worked. On clicking from the menu it didn’t. Fixed by causing reinitialization.

2. Import elements didn’t return proper notification items. Similarly warnings and info notifications always assumed error. This has been fixed

3. Added rudimentary file upload progress system. Will be working to implement a progress indicator.

4. Creating images when entering the name, the path didn’t auto populate. This has been re-implemented.

5. Snapin file uploads were already set to be operational, but did not work due to typo on the POST field to send up the files. Renamed and introduced.

6. Host export didn’t properly indicate the primac field. It didn’t even pull in the Mac at all and the values were improper. The host name appeared in description, and name field was the spot Mac was trying to populate. Added the primac field and properly pulling the data now.

7. Along with the reinitialization for the modal requesting passwords, this same reinitialization was causing table populating to be reinitialization and throw an error as it already existed. Set to retrieve so not to throw the error.

What a job, thank you very much !

When I edit a group, I can’t set module association in client module settings

@Tom-Elliott said in FOG 1.6, identified problems:

@lebrun78

Cool, thank you for that. This feature has not been implemented yet. Here’s the code behind the scenes, so it is a known thing and needs to be worked. I’m only one person though…

Could you tell me which features are not implemented todoy, so I will be able to test all the others ?

@Tom-Elliott said in FOG 1.6, identified problems:

@lebrun78 What do you mean no image imported?

There should be another log file that’s handling the php stuff. Usually called /var/log/php-fpm/www-error.log

The error.log from php-fpm is specifically error’s and processes starting dealing only with the php-fpm service. The www-error.log is the errors php-fpm is seeing from the php code passed by the browser.
The is only one line in www-error.log:

cat /var/log/php-fpm/www-error.log

[14-Nov-2019 10:03:13 UTC] PHP Warning:  socket_strerror() expects parameter 1 to be integer, string given in /var/www/html/fog/lib/router/route.class.php on line 570

Either way, “no image imported” means what? The definitions weren’t created? The physical image data didn’t import to the fog server?

No definition created

@Sebastian-Roth said in FOG 1.6, identified problems:

@lebrun78 Have you checked the apache and PHP-FPM logs yet? See my signature.

Here is the image import file

00-etudiant-rentree2019,,etudiant-rentree2019,,,,,1,,9
1903-ELEC,,1903-ELEC,,,,,2,,9
1903-INFO,,1903-INFO,,,,,2,,9
1903-VIRT,salles 204 et 206,1903-VIRT,,,,,2,,9
win10light-1903,,win10light-1903,,,,,1,,9

tail -20 /var/log/httpd/access_log

148.60.15.217 - - [14/Nov/2019:09:12:47 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:47 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:47 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:47 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:48 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:48 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:48 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:48 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:49 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:49 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:50 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:50 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:50 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:50 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:51 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:51 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:52 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:51 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"
148.60.15.217 - - [14/Nov/2019:09:12:52 +0100] "GET /fog/status/bandwidth.php?dev=eno1 HTTP/1.1" 200 28 "-" "-"
148.60.10.10 - - [14/Nov/2019:09:12:52 +0100] "POST /fog/management/index.php?node=home&sub=bandwidth HTTP/1.1" 200 53 "http://148.60.15.217/fog/management/index.php?node=image&sub=import" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:70.0) Gecko/20100101 Firefox/70.0"

tail -20 /var/log/httpd/error_log

[Wed Nov 13 15:12:59.336472 2019] [suexec:notice] [pid 8977:tid 139894213593344] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Nov 13 15:12:59.349238 2019] [lbmethod_heartbeat:notice] [pid 8977:tid 139894213593344] AH02282: No slotmem from mod_heartmonitor
[Wed Nov 13 15:12:59.351083 2019] [mpm_event:notice] [pid 8977:tid 139894213593344] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1 configured -- resuming normal operations
[Wed Nov 13 15:12:59.351099 2019] [core:notice] [pid 8977:tid 139894213593344] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Wed Nov 13 17:10:00.053054 2019] [mpm_event:notice] [pid 8977:tid 139894213593344] AH00492: caught SIGWINCH, shutting down gracefully
[Thu Nov 14 08:26:10.431342 2019] [suexec:notice] [pid 1209:tid 140320426273024] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using fogus2.istic.univ-rennes1.fr. Set the 'ServerName' directive globally to suppress this message
[Thu Nov 14 08:26:10.993453 2019] [lbmethod_heartbeat:notice] [pid 1209:tid 140320426273024] AH02282: No slotmem from mod_heartmonitor
[Thu Nov 14 08:26:10.996363 2019] [mpm_event:notice] [pid 1209:tid 140320426273024] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1 configured -- resuming normal operations
[Thu Nov 14 08:26:10.996388 2019] [core:notice] [pid 1209:tid 140320426273024] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

tail -20 /var/log/php-fpm/error.log

[13-Nov-2019 15:12:59] NOTICE: fpm is running, pid 8966
[13-Nov-2019 15:12:59] NOTICE: ready to handle connections
[13-Nov-2019 15:12:59] NOTICE: systemd monitor interval set to 10000ms
[13-Nov-2019 17:10:00] NOTICE: Terminating ...
[13-Nov-2019 17:10:00] NOTICE: exiting, bye-bye!
[14-Nov-2019 08:26:10] NOTICE: fpm is running, pid 1200
[14-Nov-2019 08:26:10] NOTICE: ready to handle connections
[14-Nov-2019 08:26:10] NOTICE: systemd monitor interval set to 10000ms

And no image imported :-(

@Tom-Elliott said in FOG 1.6, identified problems:

@lebrun78 I’m not saying you shouldn’t post issues here, I’m saying they should be specific to the issues of 1.6.

We addressed the 2 items that were related to issues in 1.6 - 1 being the advanced menu not having #!ipxe and then added the feature for the Client installer access on the menu.

The other items seem to be due to custom elements. Meaning, they’re not specific to 1.6 and not issues 1.6 is causing rather the custom things you’ve added.

these two features worked very well in version 1.4.4.
The start menus were identical under 1.4.4 and it was ok

The configuration obtained from the database seemed good, in the configuration interface and the generated files.
However, I will try again without starting from a restoration of the base. I will keep you informed on this thread.

I intended to move the draft version 1.6 forward by identifying errors as I progressed through the tests.
I’m going back to zero with the server’s operating system reinstallation.
I can create a thread for each error encountered if you prefer.