Newbie Local install, Table 'hpw_drupal.semaphore' doesn't exist:

[Daniel Roller]

This is a LOCAL Windows 10 install by a newbie. Execute step 9.

The website encountered an unexpected error. Please try again later.

Error messagePDOException: SQLSTATE[42S02]: 

Base table or view not found: 1146 Table 'hpw_drupal.semaphore' doesn't exist: 

SELECT expire, value FROM {semaphore} WHERE name = :name; Array ( [:name] => variable_init ) 

in lock_may_be_available() (line 167 of /var/www/html/includes/lock.inc).

Looking around, I see no new databases for drupal and fedora in my MySQL.

Okay, I then see data/apache/html/INSTALLmysql.txt, so I created the databases, the users, and did the grants.

Now I get a different message, at the same place.

PDOException: SQLSTATE[HY000] [1045] Access denied for user 'drupal_user'@'172.28.0.7' (using password: YES) in lock_may_be_available() (line 167 of /var/www/html/includes/lock.inc).  

I had created 'user 'drupal_user'@'localhost'.  If I create user 'drupal_user'@'172.28.0.7',

then the next time 'drupal_user'@'172.29.0.7' fails. I I create user 'drupal_user' without 

a host, then ''drupal_user'@'172.30.0.7' 

Clearly, I'm in need of some inspiration .

Step 8, did run all green and end with the right message.

FYI, I have always had a '$' character in MySql admin password. Does that do a number on php?  How stupid of a question is that!

Thanks for you time

Dan

[Yamil Suarez]

Daniel,

I once spent two days repeatedly rebuilding a local ISLE install that was failing in step 8, and it turned out to be because my DRUPAL_ADMIN_USER value contained an "@" in local.env.  For those two days I did not realize that is what was giving me issues, but after changing one thing at a time and rebuilding ISLE, the moment I removed the "@" the ISLE build worked flawlessly. 

My suggestion, though I am not an expert, is to change one config value at a time that you think could be causing the starting up again with fresh containers by running...

docker-compose down -v

Then start again from docker-compose up -d 

If you are interested we can chat via the ISLE channel in the Isolandora Slack Workspace, and we can go over some of the values in your local.env. Of course I don't want to know exactly what passwords you are using, just how many characters and what kind of characters you are using. 

Good luck,

Yamil

--------------------------------

Yamil Suarez, MCS

Associate Director of Library Systems & Web Development

Stan Getz Library

Berklee College of Music

1140 Boylston St

Boston, MA 02215

ysu...@berklee.edu

617-747-2617

Pronouns: he/him/his

--
You received this message because you are subscribed to the Google Groups "Islandora ISLE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora-isl...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora-isle/7f24cc6a-72c9-4fbe-85ab-18712fc9d33fn%40googlegroups.com.

[Yamil Suarez]

Daniel,

I forgot to mention that when we set up software like Drupal or MySQL directly, then we will normally have a lot of flexibility in how complex we make our usernames and passwords. 

The issue I had, and you may be having, is that we are using an automated build process, and our very secure and complex usernames and/or passwords are being set in one place and then shared with other build scripts. Each scrip will have different programming grammars where our fancy special characters will not be interpreted as a plain old string character, but could be in turn parsed as a programming directive in that particular moment inside a secondary build script. That is why all of a sudden a really secure and complex username or password that you have used for years will break the ISLE build process, even though it works fine when we install or configure software "manually." I have seen this happen in many other software packages, where you have to turn to other approaches to secure passwords to not break the build scripts. It may seem initially limiting, but the power of build scripts is worth it in my opinion, even though I may have to tweak some of my passwords or username practices. For example, picking other complex characters or increasing the length of the usernames and passwords.

Later,

Yamil

--------------------------------

Yamil Suarez, MCS

Associate Director of Library Systems & Web Development

Stan Getz Library

Berklee College of Music

1140 Boylston St

Boston, MA 02215

ysu...@berklee.edu

617-747-2617

Pronouns: he/him/his

[William Matheson]

Chiming in, I too have had a boatload of problems boiling down to passwords in the config files before going up, like not being able to log in as the Drupal admin user. My solution is to use ONLY numbers and letters, top to bottom, using something like https://passwordsgenerator.net/ but unchecking "include symbols" and "exclude similar characters" (since I'll probably never actually type it).

[William Matheson]

(I'm also hesitant to include spaces in Site names and often start off with, e.g. "PrinceRupertRegionalNewspaperArchives" and then change it later from Drupal itself.)

[Daniel Roller]

Once I started having this problem, it stemmed like deja vu all over again.

First this ought tp be IN BIG PRINT IN THE DOCUMENTATION for php applications(may have just volunteered).  It affects few, but its so predictable !

Originally I was impressed with the ISLE doc and process but give no expectations of how the connection works,

I will make some assumptions:

I'm not trying to debug  ISLE, just trying to install it so that I can answer to the organization that I am volunteering for, "Is it a viable solution?"

1) Change my mysql admin password to eliminate the $.

2) Guessing that ISLE is supposed to create the database and users ( hey, there is no schema) 

    I will DROP all of the pieces that I have created.

3) I will grep the current installation to see where my password has been distributed., and mug them too.

4) then retry 

I typically get to do this late in the evening.  So don't hold your breath waiting for me!

Thanks for you help,

Dan

[Daniel Roller]

SOVLED.

Quickly tried above strategy and learned nothing.

I have given up on the mysql root password with a $ sign,

If I discover an extra hour or two, I my revisit this.

Since the install document insists that it is a 1-2 hour install,

 I thought that I ought to hone my skills at redoing this install!

So, deleted all including Git repository.

Ran steps 1-8, but step 8 died with MySQL errors.

This was weird: 

  (1) I recorded that it ran to a successful end previously.

  (2) now seems obvious that the documentation is totally missing

      the creation of mysql objects.

I created the mysql objects, reran step 8 and got weirder errors.

So I saved my configuration files setup from steps 1-7, namely

   .env

   docker-compose.local.yml

   local.env

   config\apache\settings_php\settings.local.php

   config\proxy\traefik.local.toml

   scripts\proxy\ssl-certs\local-windows-only.sh

Deleted all including Git repository.

Dropped and recreated my MySQL objects.

Ran steps 1-5 copying my saved configuration files

Ran steps 6-8, step 8 says 

Done. 

'all' cache was cleared.

that last cycle took 1.5 hours

Step 9: Tada!

Tomorrow night I will do steps 10 and 11 and start figuring out Islandora.

Thanks all

Dan

[Daniel Roller]

CONCLUSION 

(1) Local install creates docker container for a private MySQL., my MySQL was ignored.  I learned this in reading about the Staging install.  Would have been nice to understand that fiddling with db parms was probably a waste of time in the Local install document.

(2) I believe that all of my install problems, except one typo, were due to exiting the Run-as-Admin bash (life intercedes) and returning and forgetting to Run-as-Admin.  Would be nice to have scripts requiring Admin, to catch this error of mine.
(3) Would be nice in Local install step 10, to say login with that drupal userid and password from local.env.

Thanks for a relatively smooth install.