7.4 is not creating postgresql database

[edcolon]

First, excellent job. Congrats!

I've been testing different versions, and the latest (7.4) for some reason is not creating postgresql database when selected. If I go to 7.3 it's working, with some adjustments on permissions and users, as someone else noted in another post. I haven't tried with MariaDB, but I want to preserve PostgreSQL for my testing.

Anyway, I just want to report it, maybe I'm doing something wrong.

Thanks in advance.

@Ed

[douglascrp]

Hello. @edcolon I have just created a 7.4 project in order to test something, and the postgresql database was created without any problem.

Have you executed the create_volumes.sh script before starting the project?

[edcolon]

Yes, I did, then I changed owner for data and logs: chown 501:501 data chown 501:501 logs

I'm using Centos 7 as Host.

Thanks.

El mar, 20 jun 2023 a la(s) 14:13, Douglas C. R. Paes ( @.***) escribió:

Hello. @edcolon https://github.com/edcolon I have just created a 7.4 project in order to test something, and the postgresql database was created without any problem.

Have you executed the create_volumes.sh script before starting the project?

— Reply to this email directly, view it on GitHub https://github.com/aborroy/alfresco-installer/issues/4#issuecomment-1599436568, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEW6SS3OW3GGA72ZVEXJ3N3XMH77ZANCNFSM6AAAAAAZNYALRI . You are receiving this because you were mentioned.Message ID: @.***>

[douglascrp]

If you executed the script, then you should not be changing the permissions again, as the script already sets the right permissions for you.

Please, try again, but first remove both data and log folders, then execute the script and start the project, without touching any permission.

[edcolon]

Let me try, thanks.

[edcolon]

Hi, here are my tests: I tried with Centos 7 and Ubuntu 22.04, and same result. From the scratch I couldn't make 7.4.work. 7.3 it's working, running script: ./create_volumes.sh And then change permissions again: chmod 777 data logs chown 501:501 data logs

One thing is that, if you select https proxy, when I previously added my own cert files (localhost.cer, localhost.key), then I need to shutdown docker, copy certs again on "(alfresco/config/cert)" and then startup and it worked.

About 7.4: Digging into docker logs, some of them through some java errors, which effect is that it throughs and inteface error: User and Password Unknown.

Reading on some other users, they complain about the menus to manage Users and Groups which are not listed on Admin Console, which it seems I have that problem also. I will start sorting out this problem as it's required for my testing.

Thanks again.

[douglascrp]

I don't know what is wrong in your case, but what I know is that I didn't had to change the permissions after creating them by using the script.

So, the commands below are not required for me: chmod 777 data logs chown 501:501 data logs

Actually, if you look closer, you will notice that the chow command is changing the right permissions defined by the script: chown -R 33000 data/alf-repo-data chown -R 33000 logs/alfresco chown 33007 ./data/solr-data chown 999 ./data/postgres-data chown 999 logs/postgres chown -R 33031 data/activemq-data

By running the command you mentioned, you are throwing away all the configurations the script already did for you.

[edcolon]

I only change permissions for the folder itself, not the inner folders, and they remain the same. On the other hand, I successfully got into the "dashboard" console which I didn't remember how to access. For newbies: https://<domain:8080/share/page There, I can configure Alfresco properly.

Which linux distribution you use as host? One of my team tried 7.4 on Centos 7, and it didn't work either.

One of our guess is that at least on Centos 7 the docker user is "polkitd" with uid 999, and we think that could cause something in the installation, but it's only a guess.

Something else it's that when installing, this time I changed (localhost) for my current domain defined at /etc/locahosts. That could help some others to figure out some problems.

Thanks,

@edcolon