This would appear at first glance to be a database connectivity issue but the database is installed (as verified by logging into the database server and checking that the tables were created).
Advise on how to resolve?
There appears to be nothing in the docker logs.
Hi,
could you tell me the context of the error,
and also i would like to know your setup (if it’s docker, database etc…).
Regards
Using docker/compose per https://hub.docker.com/r/pydio/cells however, with the following modifications:
services.cells.enviroment
services.db.image: mariadb:10.2
where X merely indicates the part of the IP not disclosed above.
docker info:
Server Version: 18.06.1-ce
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 1018
Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local local-persist
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
apparmor
Kernel Version: 3.13.0-149-generic
Operating System: Ubuntu 14.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.791GiB
Name: Koinonia
ID: GBSZ:F4QY:L4ZP:O764:RSTI:AWQL:UXTN:DRON:TZRR:6FKC:TMTS:T4U2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: true
Hi,
and if you do a docker logs -f <your cells container>, what does it say?
i used this docker-compose and i did not encounter the error,
version: '3'
services:
# Cells image with two named volumes for the static and for the data
cells:
image: pydio/cells:latest
volumes: ["data:/root/.config/pydio/cells/data"]
ports: ["8080:8080"]
environment:
- CELLS_BIND=0.0.0.0:8080
- CELLS_EXTERNAL=192.168.0.109:8080
- CELLS_NO_SSL=1
mysql:
image: mariadb:10.2
environment:
MYSQL_ROOT_PASSWORD: root
MYSQL_DATABASE: cells
ports: ["3306:3306"]
volumes:
data: {}
If you want to show me your compose file, so that i try it.
I’m getting a different failure now. Where is the database host setting in cells?
See /root/.config/pydio/cells/pydio.json
After install, the database is only showing the following 54 tables which is leading to the timeout issue. Is there a setting in the install script that may help installing all the tables? I assume there are tables that start with the letters following ‘l’.
Current database: cells
±---------------------------------+
| Tables_in_cells |
±---------------------------------+
| data_changes |
| data_changes_archive |
| data_index_cellsdata_idx_commits |
| data_index_cellsdata_idx_nodes |
| data_index_cellsdata_idx_tree |
| data_index_personal_idx_commits |
| data_index_personal_idx_nodes |
| data_index_personal_idx_tree |
| data_index_pydiods1_idx_commits |
| data_index_pydiods1_idx_nodes |
| data_index_pydiods1_idx_tree |
| data_meta |
| dex_auth_code |
| dex_auth_request |
| dex_client |
| dex_connector |
| dex_keys |
| dex_migrations |
| dex_offline_session |
| dex_password |
| dex_refresh_token |
| enc_node_keys |
| enc_nodes |
| gorp_migrations |
| idm_acl_nodes |
| idm_acl_roles |
| idm_acl_workspaces |
| idm_acls |
| idm_policy_group |
| idm_policy_rel |
| idm_role_policies |
| idm_roles |
| idm_user_attributes |
| idm_user_idx_commits |
| idm_user_idx_nodes |
| idm_user_idx_tree |
| idm_user_keys |
| idm_user_policies |
| idm_user_roles |
| idm_usr_meta |
| idm_usr_meta_ns |
| idm_usr_meta_policies |
| idm_workspace_policies |
| idm_workspaces |
| ladon_action |
| ladon_policy |
| ladon_policy_action_rel |
| ladon_policy_permission |
| ladon_policy_resource |
| ladon_policy_resource_rel |
| ladon_policy_subject |
| ladon_policy_subject_rel |
| ladon_resource |
| ladon_subject |
±---------------------------------+
54 rows in set (0.18 sec)
Please advise. What appears to be an install with only half of the tables does not work.
Hi,
could you give me your database version please?
I have attempted MariaDb 10.2 and MySql 5.7.
Mariadb 10.2 should be ok mysql 5.7 too, you have all the tables,
here’s mine (on mariadb 10.3):
Database changed
MariaDB [cells]> show tables;
+----------------------------------+
| Tables_in_cells |
+----------------------------------+
| data_changes |
| data_changes_archive |
| data_index_cellsdata_idx_commits |
| data_index_cellsdata_idx_nodes |
| data_index_cellsdata_idx_tree |
| data_index_personal_idx_commits |
| data_index_personal_idx_nodes |
| data_index_personal_idx_tree |
| data_index_pydiods1_idx_commits |
| data_index_pydiods1_idx_nodes |
| data_index_pydiods1_idx_tree |
| data_meta |
| dex_auth_code |
| dex_auth_request |
| dex_client |
| dex_connector |
| dex_keys |
| dex_migrations |
| dex_offline_session |
| dex_password |
| dex_refresh_token |
| enc_node_keys |
| enc_nodes |
| gorp_migrations |
| idm_acl_nodes |
| idm_acl_roles |
| idm_acl_workspaces |
| idm_acls |
| idm_policy_group |
| idm_policy_rel |
| idm_role_policies |
| idm_roles |
| idm_user_attributes |
| idm_user_idx_commits |
| idm_user_idx_nodes |
| idm_user_idx_tree |
| idm_user_keys |
| idm_user_policies |
| idm_user_roles |
| idm_usr_meta |
| idm_usr_meta_ns |
| idm_usr_meta_policies |
| idm_workspace_policies |
| idm_workspaces |
| ladon_action |
| ladon_policy |
| ladon_policy_action_rel |
| ladon_policy_permission |
| ladon_policy_resource |
| ladon_policy_resource_rel |
| ladon_policy_subject |
| ladon_policy_subject_rel |
| ladon_resource |
| ladon_subject |
+----------------------------------+
54 rows in set (0.001 sec)
I would say if you could try once with mariadb 10.3 to be sure, otherwise we will break this step by step until we figure it out.
Sames result with mariadb 10.3. Has the install been tested using containers? Is there code in the install that creates tables after the ‘ladon_subject’ table which may be blocking the remainder of the tables from being created?
Hi,
yes, i tested it using the docker compose shown previously,
do you mind showing me the docker-compose file or the commands that you are using and also could you tell me if you are using a proxy, ssl etc…? (just describe me all your setup)
Note: The yml formatting does not display correctly in these comments.
version: '3'
networks:
back:
driver: bridge
services:
cells:
container_name: pydio
image: pydio/cells
restart: on-failure:5
security_opt:
- no-new-privileges
cap_drop:
- NET_RAW
- MKNOD
volumes:
- ./data:/root/.config/pydio/cells/data
networks:
- back
ports: ["8080:8080"]
environment:
- CELLS_BIND=0.0.0.0:8080
- CELLS_EXTERNAL=${EXTERNAL_IP}:8080
- CELLS_NO_SSL=1
db:
container_name: pydio_db
image: mariadb:10.3
restart: on-failure:5
security_opt:
- no-new-privileges
cap_drop:
- NET_RAW
- MKNOD
environment:
- MYSQL_ROOT_PASSWORD=${MYSQL_ROOT_PASSWORD}
- MYSQL_DATABASE=cells
- MYSQL_USER=pydio
- MYSQL_PASSWORD=${MYSQL_PASSWORD}
command: [mysqld, --character-set-server=utf8mb4, --collation-server=utf8mb4_unicode_ci]
volumes:
- ./db-vol:/var/lib/mysql
networks:
- back
Hi,
you can use to display it, (the forum accepts markdown).
I’ll try your docker-compose and see what i get.
Just a quick question to better understand your problem:
Are you behind a reverse proxy or do you directly try to connect to 192.168.X.X:8080 ?
There is no proxy. Connection is direct to {EXTERNAL_IP}:8080 specified in the compose file above.
Any update on this issue?
@zayn
It has been 3 weeks since I posted my compose file after you requested it. You have not replied back. Please advise.
Hi,
sorry if i did not reply on the subject but i did not get the issue that you had while using your docker-compose(and adapting it to my network).
Now onto your issue could you start a simple cells container (without docker-compose),
docker run -d -p 8080:8080 -e CELLS_BIND=<ip>:<port> -e CELLX_EXTERNAL=<ip>:<port> pydio/cells in this case port = 8080, you can add a volume if you wish but i would like you to try a simple naked container to see the behaviour.