Ok, answer will be fast :
If using the build 2018120800 ==> Not compatible with Debian 10
If using the latest build "under developement" ==> Compatible with Debian 10 but unstable and can't recommand for production use. Also, there is some known issue with the plugin system.
Let me call Jesus and God...
Follow the rules ==> Reporting rules - Reminder
(I could have deleted this post by now... so edit your initial post in accordance to the reporting rules)
(and use the "code" tag when you past logs or anything "long")
I'm pretty sure that, if you try to setup the latest released build, you use the same preseed file you posted which will explain the Fatal error.
https://github.com/i-MSCP/imsc…018120800/docs/preseed.pl
This is the preseed file for the 1.5.3 build 2018120800.
Also, there is no official support of Docker use, and like "tracer", I wonder why you attempt this ?
If you just want to test the panel, like he said, just do a Debian or Ubuntu VM, easier and working at least.
Did you git clone the latest unrealeased version ? (which is not "stable" by definition as all tests hasn't been done on it) or did you get the release packaged ? (1.5.3 build 2018120800)
If you take the first one, there "might" be some issues with the preseed way of setup.
If you take the package of the latest known good build, PHP.7.4 is not supported (7.1 at maximum).
Even, I'm not sure that the PHP7.4 is working for the "dev" build (preseed example stop at 7.3 after all).
I didn't recall myself about a Docker package for i-mscp, where did you get this ?
Little addition :
The error so, which is the patch is not applying... well, normal (see below)
For this attempt, I set the DebHelper level to 9 (max is 12, but I didn't tested with)...
Then, as this is working with PHP7.4.7 and no 7.4.8, I checked the changes in the "configure.ac" file, and... see by yourself:
PHP 7.4.7:
PHP 7.4.8:
The patch file now :
Well... they changed just this little line... why ? I don't know.
So for me, two/tree solutions :
1- We revert the change in the configure.ac file
2- We remove or "correct" the patch from the list
3- We manually edit the configure.ac file to reflect the "patch"
Edit :
Little info : We can simply "remove" the patch from the applicable list of patches too (comment in file : /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/patches/7.4/series)
Whichever solution you apply, the build should be fine after that.
Quick edit, two of the solutions you can use to build PHP 7.4.8 :
By using your prefered editor, open the files : /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/patches/7.4/0029-php-5.4.9-fixheader.patch*
(Yes, there is "two" files, one with a "~" at the end, don't know why, but it's there)
This file should look like this :
Save, then re-run the build process from PHP Switcher.
/!\ I'm not an expert, and maybe this patch is not needed anymore.
In fact, I don't know what will be the output of the "php_uname()" with this command passed in the config : PHP_UNAME=${PHP_UNAME:-$UNAME}
This patch, if I'm not wrong, is to obfuscate the output of some PHP variables, here, to prevent the leak of the system information through this function "php_uname()" (so that it display only "Linux" and not the whole "uname -a" result).
After I did compile with this modification, the "PHP_OS()" is empty, and "PHP_UNAME()" give the "full" details, so I don't know at the end...
We may revert this configure.ac file as the version 7.4.7 to check if the result is different or not on the webserver after compilation, but no more time for today (idea would be to remove "UNAME" and "PHP_UNAME" lines, and then, add back the "old modified" "PHP_UNAME" line.
Simply open this file : /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/patches/7.4/series
Then, found the line where the patch is noted : "0029-php-5.4.9-fixheader.patch"
Add a "#" at the start of the line, so that this patch will NOT be applied.
Save the file then re-run the build process from PHP Switcher.
For both solutions, if you get the error posted in the previous message, just set the system variable :
To set this variable :
export DH_COMPAT=9
and to remove it, simply :
unset DH_COMPAT
I get the same error as Speddy
which can be ignored with an environment variable that force the use of Level 9 for DebHelper:
To set this variable :
export DH_COMPAT=9
and to remove it, simply :
unset DH_COMPAT
Unfortunetely, there is some more errors on the way and the build keep failing, no solution so far.
As PHP7.4.8 is mostly a security fix for Windows users, I'll not bother with it and will wait next release (maybe they did something wrong with this build for Linux users ^^)
I know, english is difficult when it's not your main language, but to be honnest, it's hard to understand your issue at the moment.
Also, you didn't follow the rules in posting your request ==> Reporting rules - Reminder
Then, if your profile is up-to-date for your Linux environment, which is "Ubuntu Precise Pangolin", release 12.04 (which is out of support since April 2017), well, it's not officialy supported by the latest i-MSCP release available.
QuoteVersion 1.5.3 (build 2018120800)
Supported Ubuntu versionsUbuntu Trusty Thar 14.04
Ubuntu Xenial Xerus 16.04
Ubuntu Bionic Beaver 18.04
As this is "impacting" the entire community, I take the "responsibility" to allow english answers in this topic.
I don't see the point to open multiple threads in multiple languages for this particular subject, else... I move this in the General Discussion area...
If the server is still running Debian 7.0, not really great (in term of security and other stuff).
Last release of i-MSCP doesn't handle officialy this version of Debian (Debian Jessie 8.x and Stretch 9.x)
From my point of view, seeing this is either :
- An orphan entry in the DB which may "stop" some process going further untill fixed
- One or more services stopped.
Could you first clarify your setup (as the Reporting rules - Reminder state) ?
Else, check Nuxwin profile, you'll see his support plans prices.
Personnaly, I'm not confident at all on looking your broken system even if I'm "pretty good" at it.
