Eramba - System Health, worker error
Zitat von mpachmann am 28. Dezember 2023, 11:20 Uhrhttps://discussions.eramba.org/t/question-virtual-machine-cron-error/3551/3
In Eramba VM,
docker container ls
docker exec -it DOCKERID bashYou can also go into eramba container and try to run it manually and see what error it gives you.
su -s /bin/bash -c "/var/www/eramba/app/upgrade/bin/cake queue run -v" www-data
https://discussions.eramba.org/t/question-community-setup-issues/3196/4
I cleaned everything and restarted from scratch:
Installed OVF File in ESX
Set IP Address and checked startscript has no errorsudo su
cd /etc/netplan/*.ymal
network:
version: 2
renderer: networkd
ethernets:
ensxxx:
addresses:
- 192.168.1.xx/24
routes:
- to: default
via: 192.168.1.254
nameservers:
addresses: [192.168.1.x, 192.168.1.x]
I put the folder “docker” (and subfolders/files) as NOT readonly
chmod -R u+rw /home/docker/*
I edited DB_PASSWORD and MYSQL_ROOT_PASSWORD
cd /home/docker/
nano .envI browsed ALL files in the docker (sub)folder(s) and make sure the EOL were Unix compatible (that was the fix I did in the past when the cron container couldn’t execute docker-cron-entrypoint.sh)
curl https://support-v3.eramba.org/ping.html is successful
Install Docker Enterprise Containers from Eramba git
docker compose -f docker-compose.simple-install.yml -f docker-compose.simple-install.enterprise.yml up -dI stopped all the containers
docker stop $(docker ps -a -q)In sql container, I edited /etc/my,cnf by adding, under [mysqld]
docker container cp containerId:/etc/my.cnf container-my.cnfnano container-my.cnf
innodb_lock_wait_timeout="200"
sql_mode=""
max_allowed_packet="128000000"
(these were the suggestions from eramba health page)
docker container cp container-my.cnf containerId:/etc/my.cnfI started all the containers in DockerDesktop
docker start $(docker ps -a -q)Login to Webinterface and check if cronjob errors are present, check for updates.
https://discussions.eramba.org/t/question-virtual-machine-cron-error/3551/3
In Eramba VM,
docker container ls
docker exec -it DOCKERID bash
You can also go into eramba container and try to run it manually and see what error it gives you.
su -s /bin/bash -c "/var/www/eramba/app/upgrade/bin/cake queue run -v" www-data
https://discussions.eramba.org/t/question-community-setup-issues/3196/4
I cleaned everything and restarted from scratch:
Installed OVF File in ESX
Set IP Address and checked startscript has no error
sudo su
cd /etc/netplan/*.ymal
network:
version: 2
renderer: networkd
ethernets:
ensxxx:
addresses:
- 192.168.1.xx/24
routes:
- to: default
via: 192.168.1.254
nameservers:
addresses: [192.168.1.x, 192.168.1.x]
I put the folder “docker” (and subfolders/files) as NOT readonly
chmod -R u+rw /home/docker/*
I edited DB_PASSWORD and MYSQL_ROOT_PASSWORD
cd /home/docker/
nano .env
I browsed ALL files in the docker (sub)folder(s) and make sure the EOL were Unix compatible (that was the fix I did in the past when the cron container couldn’t execute docker-cron-entrypoint.sh)
curl https://support-v3.eramba.org/ping.html is successful
Install Docker Enterprise Containers from Eramba git
docker compose -f docker-compose.simple-install.yml -f docker-compose.simple-install.enterprise.yml up -d
I stopped all the containers
docker stop $(docker ps -a -q)
In sql container, I edited /etc/my,cnf by adding, under [mysqld]
docker container cp containerId:/etc/my.cnf container-my.cnf
nano container-my.cnf
innodb_lock_wait_timeout="200"
sql_mode=""
max_allowed_packet="128000000"
(these were the suggestions from eramba health page)
docker container cp container-my.cnf containerId:/etc/my.cnf
I started all the containers in DockerDesktop
docker start $(docker ps -a -q)
Login to Webinterface and check if cronjob errors are present, check for updates.