You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just set up a new container, but can't get it to install.
It looks like it is not connecting to the database, but I can connect to it from within the container just fine.
What I tried so far:
Tried it on another server (hardware) and other database host (Virtual Machine).
Started over using the 14, 15, and develop branch.
Connecting to the local ip (In my case 10.0.1.44) instead of the mariadb hostname.
Using a simple password with just letters and numbers.
Tested using root user and password of MariaDB.
Using mysqlcheck --repair --all-databases and mysqlcheck reported no errors.
Still giving the SQLSTATE[HY000] [2002] error.
What could be wrong, how to troubleshoot/debug?
My setup is:
When I shell into the container I can connect to the mariadb container just fine.
[tiredofit/debian 18:58:48] # mysql -h lab-mariadb.flissinger.com -P 3307 -u freepbx -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 30
Server version: 10.11.3-MariaDB-1:10.11.3+maria~ubu2204 mariadb.org binary distribution
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]>
The text was updated successfully, but these errors were encountered:
Heya
I've been struggling to install, and got the same fwconsole error
That's how I ended up here
So far here's what I found out
it seems tat many processes are running with uid.gid of 2600.
when I create bind volumes, it seems I always have a permission error somewhere in the volume mounted. Probably because 2600 is not a UID that exists in the docker host system (a synology NAS)
it seems to work when I create a mount volume, using --volume freepbx-data:/data
a docker run with just this parameter changed to --volume /synologydisk1/docker/freepbx/data:/data results in the failures you describe with a "[freepbx] Can't seem to locate /usr/sbin/fwconsole.. exiting"
[INFO] ** [freepbx] New install detected - please wait while we fetch FreePBX - will take up to 30 minutes!
[NOTICE] ** [freepbx] Starting Asterisk 17.9.3 for the first time
[NOTICE] ** [freepbx] Installing FreePBX 15.0.16.56 source code
[ERROR] ** [freepbx] Can't seem to locate /usr/sbin/fwconsole.. exiting
[cont-init.d] 10-freepbx: exited 1.
[cont-init.d] 15-socat: executing...
[cont-init.d] 15-socat: exited 0.
[cont-init.d] 99-container: executing...
**********************************************************************************************************************
**********************************************************************************************************************
**** ****
**** ERROR - Some initialization scripts haven't completed - All services are now halted ****
**** - The following scripts in '/etc/cont-init.d' did not pass their completion check ****
**** ****
**********************************************************************************************************************
**********************************************************************************************************************
10-freepbx
I am now fiddling around to find a way to make it read properly the SSL certificates which are generated by acme.sh on the host, and are sitting in a specific directory mounted. Currently trying with this in the docker run:
Just set up a new container, but can't get it to install.
It looks like it is not connecting to the database, but I can connect to it from within the container just fine.
What I tried so far:
Tried it on another server (hardware) and other database host (Virtual Machine).
Started over using the 14, 15, and develop branch.
Connecting to the local ip (In my case 10.0.1.44) instead of the mariadb hostname.
Using a simple password with just letters and numbers.
Tested using root user and password of MariaDB.
Using mysqlcheck --repair --all-databases and mysqlcheck reported no errors.
Still giving the SQLSTATE[HY000] [2002] error.
What could be wrong, how to troubleshoot/debug?
My setup is:
docker-compose:
logs:
When I shell into the container I can connect to the mariadb container just fine.
The text was updated successfully, but these errors were encountered: