FOG 1.6, identified problems
-
Hello
I tried by resetting the menu; but that does not work, the deploy menu runs in a loop.
The configuration on my test server was recovered by restoring the server’s mysql database in 1.4.4, so the boot menus are normally good
-
@lebrun78 said in FOG 1.6, identified problems:
The configuration on my test server was recovered by restoring the server’s mysql database in 1.4.4, so the boot menus are normally good
Uhhhhmmm, not a good idea. FOG 1.6 is quite different to 1.5.x and even more to 1.4.4!! I am pretty sure your setup is now totally messed up with a DB recovery form 1.4.4 state.
When you initially setup the 1.6 server, did you install plain from scratch or did you start from a copy of an old server? It’s very hard to help if we only know part of what exactly you did.
-
it’s a brand new server, (new hardware, new centos 8.0 distribution) except the fog database I restored.
I would like to keep machines, images, snapins configurations -
@Sebastian-Roth
with the restoration of the base, it seemed to work well.
Should I restart from scratched, installed and import from 1.4.4 export files for images, hosts, snapins? -
@lebrun78 said in FOG 1.6, identified problems:
Should I restart from scratched, installed and import from 1.4.4 export files for images, hosts, snapins
Definitely better to ex/import that stuff instead of using a complete DB dump from 1.4.4!!
-
@lebrun78 I’m not understanding here.
You made a change only to put it back in place and then test and found it’s still an issue?
This doesn’t make sense to me.
You have some customization going on. I don’t know where in the customization the issue is occurring.
By having it clean, you should be at what is needed for things when they’re working properly.
If you’re still getting error 500 from the boot.php, then chances are you will have an error in your php-fpm/www-error.log
You are trying to do too many things and we can’t help you if you’re doing that.
“I did that, but then I did this and it still isn’t working” doesn’t help because we don’t know at what point things stopped working.
If you started with a 100% clean database, do things work? I’d imagine if it were such a problem, i’d be seeing it too as I run working-1.6 for testing.
-
Trying to import from an 1.4.4 export unsuccessful for images,hosts and users .
Is there log for imports ? -
@lebrun78 Have you checked the apache and PHP-FPM logs yet? See my signature.
-
I guess what i’m trying to establish in this thread:
I cannot replicate the error you’re seeing. And from what I can tell this is an error that’s been custom made.
The thread starts: FOG 1.6 Identified Problems.
Nothing, so far, besides the advanced menu issue which was addressed, and added the Client link within the menu system, has been a problem specific to FOG 1.6
I don’t know how to help any further with this as the 2 things requested that were not due to custom modifications to the iPXE menu have been addressed.
Were these the only 2 things identified and solved? If so, can you branch out your specific problems into a new thread. I’m getting rather lost on where a problem is and how we’re supposed to help further.
Do things work as intended out of box (before copying your 1.4.4 database over it?)
-
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. -
@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.
I understand bringing up issues, but pushing everything here simply because you’re on 1.6 doesn’t mean it’s a problem 1.6 is causing, you know what I mean?
-
@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 okThe 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. -
@lebrun78 said in FOG 1.6, identified problems:
#login
params
param mac0 ${net0/mac}
param arch ${arch}
param hostname ${hostname}
goto host_${hostname} || goto autres
:host_bug
:host_win10-3
:host_i207m01
:host_i207m02
:host_i207m03
:host_i207m04
:host_i207m05
:host_i207m06
:host_i207m07
:host_i207m08
:host_i207m09
:host_i207m10
set username i207stud
set password coucou
params
param username i207stud
param password coucou
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
goto fin
:autres
login
params
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fin
param sysuuid ${uuid}I copied this into my menu and things worked perfectly fine. Of course I don’t have any hosts named host_win10-3 etc… but the point remains I’m not seeing any issues.
-
@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
-
@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.
Either way, “no image imported” means what? The definitions weren’t created? The physical image data didn’t import to the fog server?
We need clarity to help out.
-
@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
-
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…
(function($) { var importFile = $('#importfile'), importForm = $('#import-form'), importFormBtn = $('#import-send'); importForm.on('submit', function(e) { e.preventDefault(); }); importFormBtn.on('click', function() { importFormBtn.prop('disabled', true); // TODO: Start uploading file. // Send for processing. // complete data set and reset our layout. importFormBtn.prop('disabled', false); }); })(jQuery);
-
@Tom-Elliott said in FOG 1.6, identified problems:
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 ?
-
@lebrun78 The thing is I don’t know what is or isn’t.
For what it’s worth, I just updated the code base so you should be able to import images now.
I’ll be working throughout the day to get all the import elements functional. -
@lebrun78 All import elements should be functional now if you run a git pull and reinstall.