drupal site db connection error about isle HOT 12 CLOSED

Ok Thanks.. this is what I'm starting to think about so you're one step ahead of me ;-). The default site did come up after fixing my /etc/hosts on my laptop (virtual box has it as 192.168.56.102) so I needed to map that in /etc/hosts and then everything started working properly. So while it is working and I'm starting to think how to import some data and maybe some sites we use to try out that process of getting data into this setup.
It does make me wonder though why it's not working automatically (I have to copy in the default settings.php with the isle db info set) whereas I think by the sounds of it, it is working automatically for others (on MacOS and Ubuntu)? So have I found a bug that's only specific to CentOS or something? Maybe we should rm -f /tmp/drupal_install/sites/default/settings.php in make_site.sh before we copy it and then the one that's already in the container with the db info set would still be in place? Not sure what to do to address it not working out of the box.

from isle.

@hamhpc I think you and I should catch up as isle-web and isle-db are no longer used. Additionally the issue with the copy of settings.php in the web Dockerfile has since been removed. Much of this has changed radically. I'll be pushing new documentation to this effect tomorrow and would love if you could test (again) ;)

from isle.

@hamhpc Please let us know what the default site settings look like? My sense is that the settings.php file wrongly defines the db settings array.

The file is located /var/www/html/sites/default/settings.php if I'm reading your logs correctly (and I know the container)

on Slack always if I can expand further.

from isle.

Thanks @br2490 ... I'm running the install again to see if I can catch an error with the install. I'm not quite sure where in the process that the settings.php file get's populated with DB info. As far as I can tell that's what is failing as there is no site info in the settings.php file which I suspect is why I'm taken to the install drupal page when browsing it. I'm using https://github.com/hamhpc/ISLE-ks to install this VM in virtual box on my Mac. This way someone else should be able to reproduce it. I'm trying to iron out a consistent scripted install with it. I think it's 90% ... just need to figure out what I'm missing. All the other services seem to be up and running properly. I'll report back once I'm able to do some more debugging.

from isle.

from isle.

Perfect @br2490 ! That's what I'm wondering and will look at once I have it back up and running to check. I'll report back.

from isle.

Ok I think I see where the issue is. Thanks to @br2490 for the help to diagnose this. So when the apache container is built it ends up containing /var/www/html/sites/default/settings.php with the DB connect info and settings. However, when we run make_site.sh it creates a drupal_install in /tmp and then ends up copying the data over to /var/www/html. I suspect that the copy is over-writing the settings.php file with a blank version from the generic /tmp/drupal-install setup. I ended up saving the settings.php file from when the container was built. Then I copied it back into sites/default before running the install_site.sh and now it appears to be enabling the modules and installing the site. So far so good. I'll report on how it works when it's up and I can log in.

from isle.

from isle.

Thanks @g7morris ... I actually have updated and am using apache and mysql when you switched it =). Every build pulls a new git from ISLE. I'm running through it on our VMware side since I can make it work in virtual box. I'll be able to see if the same situation persists and report. I plan to do many more installs of this so no worries I'm happy to keep testing =).

from isle.

Yea I am still seeing this issue but will run through this again in the morning anyhow. I can reproduce. Basically everything builds fine. But it's when running make_site.sh and install_site.sh. When the apache container is built it has a file /var/www/html/sites/default/settings.php which has all the correct db connect info.
However, when one runs make_site.sh it creates a blank drupal install in /tmp... /tmp/drupal_install. When this gets populated it creates a blank sites/default/settings.php WITHOUT the correct db settings. So when in make_site.sh does the copy....

echo "Copy /tmp/drupal_install contents to /var/www/html"
cp -rv /tmp/drupal_install/. /var/www/html/

We might have the make_sites.sh script do:

rm -f /tmp/drupal_install/sites/default/settings.php
THEN do the above copy to /var/www/html.

By doing this the copy command won't clobber over the proper settings.php file that is already loaded into the container. The other option would be to copy the settings.php file back in after you copy in the blank drupal directory tree containing the blank settings.php. Does this make sense and are you seeing the same? Once I do another build in the am I'll probably try to get with Gavin to sort it out if I still have the same results. Thanks.

from isle.

@hamhpc & @br2490

I think @hamhpc hits the nail on the head here.

We might have the make_sites.sh script do:
rm -f /tmp/drupal_install/sites/default/settings.php
THEN do the above copy to /var/www/html.

I apparently also found this issue in my build notes and it appears, I sadly didn't push the rm -f command as @hamhpc suggests. D'ouh! Apologies.

How I missed it several times since testing is not good, but hey this is why we test.

So big thanks @hamhpc & @br2490 for your eagle eyes, testing and hanging on to this thread..

I'll incorporate this change in the script in the next day, push to master and that should stop this heartache.

from isle.

This issue is fixed by this commit

make_sites.sh script now has these lines:

echo "Remove blank settings.php from /tmp/drupal_install"
rm -f /tmp/drupal_install/sites/default/settings.php

Closing ticket.

from isle.