upgraded to Ubuntu 18.04.1 LTS
-
@Boyan-Biandov said in upgraded to Ubuntu 18.04.1 LTS:
@Wayne-Workman Great link Wayne, I am actually going to do this myself very soon, one point of clarification if I may: section “Arranging Images”. Is it really necessary to copy the images to a folder, other than /images on the new fog server and then once they are copied there “rearrange” them by moving them again into the final destination of /images (assuming fog defaults)?
Imagine scenario A: You are busy capturing a new version of your image and someone attempts to deploy that image. They will get an incomplete and broken image and the install has failed.
Imagine scenario B: You are busy capturing a new version of your image but something goes wrong! The image is now in an incomplete/broken state and you have no way of knowing for how long that will be the case! Not very practical.
So yeah, there are legitimate reasons for using a ‘temporary directory’ if you will.
-
I did a new install on different machine and am having trouble with
Installing package: php-mysqlnd…Failed! (Will try later)
Started with Ubuntu 18.04.1 and fog 1.5.4.
I tried going back to ubunutu 16 and then 14 with fog 1.5.4 and 1.4.4 in all combinations. Still get the php-mysqulnd error. I currently have 18.04.1 back on the machine and am trying to install 1.5.4.
I am stuck. -
-
@bsalogga
Is this a clean FOG install attempt?just read the other posts, it’s an upgrade so below advice should work afaikAfaik, FOG should try to install php-mysql before php-mysqlnd which should make it return that it’s installed as a virtual package.
Instead there is no attempt to install php-mysql at all.
Does
/opt/fog/.fogsettings
exist? If so, delete thepackages=
line (in .fogsettings) and rerun the installer -
@bsalogga Just to be sure, this is NOT a brand new install of Ubuntu 18.04.1 LTS but rather there was a previous “clean” install of some older version and then it was UPGRADED to the current LTS of Ubuntu 18.04.1 LTS? Yes?
-
clean install
-
@Quazz
no .fogsettings, but tried removing packages= from installfog.sh. Same error. -
@bsalogga Try
sudo apt-get purge sysv-rc-conf
and then run the installer again. -
@bsalogga Are you using desktop or server Ubuntu 18.04.1 ? My daily tests use server edition, no GUI, 18.04
-
@Sebastian-Roth
Still not working. Error for the php-mysqlnd. -
@bsalogga said in upgraded to Ubuntu 18.04.1 LTS:
I did a new install on different machine
Just for everyone to notice. Initially this was a question about an upgraded Ubuntu installation but a fresh install was done now.
Please run
sudo add-apt-repository universe
and then re-run the FOG installer.If that still does not work you want to try out the latest working branch of FOG (either directly using git or ZIP download). We have addressed Ubuntu 18.04 issues there.
-
I agree with @Sebastian-Roth - a new install runs, in fact just recently I asked the same exact question just to be sure before I undertake a move since I’ve seen some prior issues but the discussion put that to rest, Ubuntu 18.04.1 LTS installs just fine:
-
@Boyan-Biandov Ubuntu 18.04 is not exactly like 18.04.1 - see my comment here https://github.com/FOGProject/fogproject/issues/261
I just figured what the difference is Ubuntu 18.04 server comes in two different flavors. One is the normal server ISO and the other one is the LIVE server. For 18.04 straight you could still download both versions. But seems like since 18.04.1 is out there is only the LIVE server image available anymore. I just installed 18.04.0 plain server and it has the mentioned universe section in sources.list
Here is a link for the non-live ISOs
http://www.cdimage.ubuntu.com/ubuntu/releases/18.04/release/ -
@Wayne-Workman
Using desktop. Since you mentioned server version, I gave it a try, but added gnome desktop. Same error. -
@bsalogga said in upgraded to Ubuntu 18.04.1 LTS:
Using desktop. Since you mentioned server version, I gave it a try, but added gnome desktop. Same error.
Was this a fresh clean install? Please provide the full logs again so we can have a look. It’s not helpful to just say “same error”.