Hi, I have a multiserver setup with 3 servers (web, mail, database) Installed ispconfig version is 3.0.5.4p1 On the database server I have this error in /var/log/ispconfig/cron.log: And the /var/log/ispconfig/ispconfig.log tells me: ... which isn't true. I can connect to the local mysql, and I can connect to the web-server (main ispconfig installation) server using port 3306. The other servers logs are empty. Any ideas?
I've fixed the syntax error in the dev version now. Please post the output of: netstat -tap | grep mysql from database server.
From within the database server console: netstat tells that it's listening on *.* But telnet localhost 3306 doesn't connect. > netstat -tap | grep mysql tcp 0 0 *:mysql *:* LISTEN 15221/mysqld tcp 0 0 dbdomain.tld:mysql webdomain.tld:55293 VERBUNDEN 15221/mysqld tcp 0 0 dbdomain.tld:37181 webdomain.tld:mysql TIME_WAIT - tcp 0 0 dbdomain.tld:37167 webdomain.tld:mysql VERBUNDEN 8547/php tcp 0 0 dbdomain.tld:mysql webdomain.tld:54584 VERBUNDEN 15221/mysqld dbdomain = domain of my database server webdomain = domain of my webserver (ispconfig main installation) hosts file is standard, localhost entries are: 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback But nevertheless, netstat shows that the webserver is connected to the database server. So the ispconfig check of the database seems to check localhost (ipv6)
ISPConfig is checking mysql on localhost ipv4, not ipv6. If you are not able to connect to your mysql on localhost with telnet, then ispconfig will not be able to connect too.
Ok no idea why but telnet tries and so does ispconfig. After unblocking ipv6 in iptables, it works now Nevertheless, till can you tell me if there's any other cron besides crontab -e as the error was repeated every 22 minutes: Or maybe the database check is made only every n-th run of the cronjob?
This are all cronjobs. This error is not related to the creation of databases. It is a completely different part of ispconfig and it is not run every minute like the databse creation job. yes. This job has a internal timer.