Anyone having issue with getting OnlyOffice working? I keep having issues with MySQL not starting.
++ (( I++ ))
++ (( I<4 ))
+++ echo 172.17.0.2/16
+++ sed -ne 's:^[^/]*/\([0-9]\+\)$:\1:p'
++ local IP_MASK=16
++ echo 172.17.0.0/16
+ DOCKER_APP_SUBNET=172.17.0.0/16
+ check_partnerdata
+ PARTNER_DATA_FILE=/var/www/onlyoffice/Data/json-data.txt
+ '[' -f /var/www/onlyoffice/Data/json-data.txt ']'
+ re='^[0-9]+$'
+ [[ 1 =~ ^[0-9]+$ ]]
+ '[' '!' -f /proc/net/if_inet6 ']'
+ cp /etc/nginx/includes/onlyoffice-communityserver-nginx.conf.template /etc/nginx/nginx.conf
+ sed 's/^worker_processes.*/worker_processes 12;/' -i /etc/nginx/nginx.conf
+ sed 's/worker_connections.*/worker_connections 40960;/' -i /etc/nginx/nginx.conf
+ cp /etc/nginx/includes/onlyoffice-communityserver-common-init.conf.template /etc/nginx/sites-enabled/onlyoffice
+ '[' -f /var/www/onlyoffice/Data/certs/onlyoffice.crt -a -f /var/www/onlyoffice/Data/certs/onlyoffice.key ']'
+ sed '/{{SSL_CERTIFICATE_PATH}}/d' -i /etc/nginx/sites-enabled/onlyoffice
+ sed '/{{SSL_KEY_PATH}}/d' -i /etc/nginx/sites-enabled/onlyoffice
+ sed '/listen\s*443/d' -i /etc/nginx/sites-enabled/onlyoffice
+ rm -f '/etc/nginx/conf.d/*.conf'
+ service nginx restart
++ grep -oP '\d+'
++ free -m
++ head -n 1
+ TOTAL_MEMORY=15919
+ MEMORY_REQUIREMENTS=12228
+ '[' 15919 -gt 12228 ']'
+ grep -q '[-]Xms1g' /etc/elasticsearch/jvm.options
+ echo -Xms4g
+ grep -q '[-]Xmx1g' /etc/elasticsearch/jvm.options
+ echo -Xmx4g
+ '[' ']'
+ '[' ']'
+ '[' ']'
+ '[' false == true ']'
+ '[' false == true ']'
+ '[' 127.0.0.1 '!=' localhost ']'
+ '[' 127.0.0.1 '!=' 127.0.0.1 ']'
+ '[' ']'
+ '[' ']'
+ MAIL_SERVER_API_PORT=8081
+ MAIL_SERVER_API_HOST=
+ MAIL_SERVER_DB_HOST=
+ MAIL_SERVER_DB_PORT=3306
+ MAIL_SERVER_DB_NAME=onlyoffice_mailserver
+ MAIL_SERVER_DB_USER=mail_admin
+ MAIL_SERVER_DB_PASS=Isadmin123
+ '[' ']'
++ date +%Y-%m-%dT%H:%M:%S
+ MAIL_IMAPSYNC_START_DATE=2023-10-27T20:13:13
+ sed 's_\(\"ImapSyncStartDate":\).*,_\1 "2023-10-27T20:13:13",_' -i /etc/onlyoffice/communityserver/mail.production.json
+ sed '/mail\.imap-sync-start-date/s/value="\S*"/value="2023-10-27T20:13:13"/g' -i /var/www/onlyoffice/WebStudio/web.appsettings.config
+ '[' ']'
+ REDIS_SERVER_HOST=
+ REDIS_SERVER_CACHEPORT=6379
+ REDIS_SERVER_PASSWORD=
+ REDIS_SERVER_SSL=false
+ REDIS_SERVER_DATABASE=0
+ REDIS_SERVER_CONNECT_TIMEOUT=5000
+ REDIS_SERVER_EXTERNAL=false
+ REDIS_SERVER_SYNC_TIMEOUT=60000
+ '[' ']'
+ '[' false == false ']'
+ '[' -e /etc/redis/redis.conf ']'
+ sed -i 's/bind .*/bind 127.0.0.1/g' /etc/redis/redis.conf
+ ELASTICSEARCH_SERVER_HOST=
+ ELASTICSEARCH_SERVER_HTTPPORT=9200
+ grep -q '<section name="elastic" type="ASC.ElasticSearch.Config.ElasticSection, ASC.ElasticSearch" />' /var/www/onlyoffice/WebStudio/Web.config
+ '[' ']'
+ '[' false == false ']'
+ chown -R mysql:mysql /var/lib/mysql/
+ chmod -R 755 /var/lib/mysql/
+ '[' '!' -f /var/lib/mysql/ibdata1 ']'
+ mysql_install_db
/app/run-community-server.sh: line 557: mysql_install_db: command not found
+ true
+ '[' ']'
+ myisamchk -q -r /var/lib/mysql/mysql/proc
myisamchk: error: File '/var/lib/mysql/mysql/proc' doesn't exist
+ true
+ systemctl enable mysql.service
Synchronizing state of mysql.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mysql
+ service mysql start
su: warning: cannot change directory to /nonexistent: Permission denied
* Restarting nginx nginx
...done.
* Starting MySQL database server mysqld
...fail!
+ '[' '!' -f /var/lib/mysql/mysql_upgrade_info ']'
+ mysqladmin --silent ping -u root
+ grep -q 'mysqld is alive'
+ mysql_upgrade --password=
mysql_upgrade: [Warning] Using a password on the command line interface can be insecure.
The mysql_upgrade client is now deprecated. The actions executed by the upgrade client are now done by the server.
To upgrade, please start the new MySQL binary with the older data directory. Repairing user tables is done automatically. Restart is not required after upgrade.
The upgrade process automatically starts on running a new MySQL binary with an older data directory. To avoid accidental upgrades, please use the --upgrade=NONE option with the MySQL binary. The option --upgrade=FORCE is also provided to run the server upgrade sequence on demand.
It may be possible that the server upgrade fails due to a number of reasons. In that case, the upgrade sequence will run again during the next MySQL server start. If the server upgrade fails repeatedly, the server can be started with the --upgrade=MINIMAL option to start the server without executing the upgrade sequence, thus allowing users to manually rectify the problem.
+ service mysql restart
* Stopping MySQL database server mysqld
...done.
* Starting MySQL database server mysqld
su: warning: cannot change directory to /nonexistent: Permission denied