Hello, I had to reinstall all packages of my Debian 11 (Bullseye) system. After an apt install --reinstall, I wanted to check the webpages. Unfortunately they show either an 503 error or are blank. The ispconfig version is the newest one: 3.2.8p1 When I'm trying to ispconfig_update.sh --force I'm getting the following error: Checking ISPConfig database .. OK PHP Warning: preg_match(): Compilation failed: unrecognised compile-time option bit(s) at offset 0 in /tmp/update_runner.sh.ToTKmnFfMC/install/lib/mysql.lib.php on line 291 PHP Warning: preg_replace(): Compilation failed: unrecognised compile-time option bit(s) at offset 0 in /tmp/update_runner.sh.ToTKmnFfMC/install/lib/mysql.lib.php on line 152 Unable to read server configuration from database.sun It worked before without any problems. Apache2, Mariadb are up and running. The Apache2 error log shows: [Thu Sep 29 06:40:17.092442 2022] [fcgid:warn] [pid 1769395] [client 31.10.154.56:54120] mod_fcgid: stderr: PHP Warning: Trying to access array offset on value of type null in /usr/local/ispconfig/interface/lib/classes/db_mysql.inc.php on line 211 Any hint is very appreciated. Many thanks and kind regards Christian
Run the test script and post the result: https://forum.howtoforge.com/threads/please-read-before-posting.58408/
The domain/error.log shows: [Thu Sep 29 14:10:03.889223 2022] [proxy:error] [pid 3008923] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/lib/php7.4-fpm/web4.sock (*:80) failed [Thu Sep 29 14:10:03.889305 2022] [proxy_fcgi:error] [pid 3008923] [client 31.10.154.56:54063] AH01079: failed to make connection to backend: httpd-UDS I reinstalled php7.4-fpm libapache2-mod-fcgid php7.4-cli Still the same error.
The file htf_report.txt has no more content. It is 93 bytes of size. ##### SERVER ##### IP-address (as per hostname): 85.25.213.11 [WARN] could not determine server's ip address by ifconfig [INFO] OS version is Debian GNU/Linux 11 (bullseye) [INFO] uptime: 14:16:25 up 17:20, 1 user, load average: 0.07, 0.08, 0.09 [INFO] memory: total used free shared buff/cache available Mem: 31Gi 2.1Gi 20Gi 12Mi 9.0Gi 28Gi Swap: 7.6Gi 0B 7.6Gi [INFO] systemd failed services status: UNIT LOAD ACTIVE SUB DESCRIPTION ● openipmi.service loaded failed failed LSB: OpenIPMI Driver init script LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. [INFO] ISPConfig is installed. ##### ISPCONFIG ##### ISPConfig version is 3.2.8p1 ##### VERSION CHECK ##### [INFO] php (cli) version is 7.4.30 ##### PORT CHECK ##### [WARN] Port 8080 (ISPConfig) seems NOT to be listening [WARN] Port 8081 (ISPConfig Apps) seems NOT to be listening [WARN] Port 80 (Webserver) seems NOT to be listening [WARN] Port 443 (Webserver SSL) seems NOT to be listening [WARN] Port 143 (IMAP server) seems NOT to be listening [WARN] Port 993 (IMAP server SSL) seems NOT to be listening [WARN] Port 110 (POP3 server) seems NOT to be listening [WARN] Port 995 (POP3 server SSL) seems NOT to be listening [WARN] Port 25 (SMTP server) seems NOT to be listening : [WARN] Port 465 (SMTP server SSL) seems NOT to be listening [WARN] Port 21 (FTP server) seems NOT to be listening [WARN] Port 22 (SSH server) seems NOT to be listening [WARN] Port 25 (SMTP server) seems NOT to be listening ##### MAIL SERVER CHECK ##### [WARN] I found no "smtp" entry in your postfix master.cf [WARN] I found no "submission" entry in your postfix master.cf [INFO] this is not critical, but if you want to offer port 587 for smtp connections you have to enable this. [WARN] I found no "smtps" entry in your postfix master.cf [INFO] this is not critical, but if you want to offer SSL for smtp (not TLS) connections you have to enable this. ##### RUNNING SERVER PROCESSES ##### [WARN] I could not determine which web server is running. [WARN] I could not determine which mail server is running. [WARN] I could not determine which pop3 server is running. [WARN] I could not determine which imap server is running. [WARN] I could not determine which ftp server is running. ##### LISTENING PORTS ##### (only () Local (Address) 0.0.0.0:22 (461121/sshd 127.0.0.1:953 (449034/named) 0.0.0.0:25 (401065/master) 0.0.0.0:993 (493038/dovecot) 0.0.0.0:995 (493038/dovecot) 127.0.0.1:10023 (447375/postgrey) 127.0.0.1:10024 (484272/amavisd-new) 127.0.0.1:10025 (401065/master) 127.0.0.1:10026 (484272/amavisd-new) 127.0.0.1:10027 (401065/master) 0.0.0.0:587 (401065/master) 127.0.0.1:11211 (395826/memcached) 0.0.0.0:110 (493038/dovecot) 0.0.0.0:143 (493038/dovecot) 0.0.0.0:465 (401065/master) 85.25.213.11:53 (449034/named) 85.25.213.11:53 (449034/named) 85.25.213.11:53 (449034/named) 85.25.213.11:53 (449034/named) : 127.0.0.1:53 (449034/named) 127.0.0.1:53 (449034/named) 127.0.0.1:53 (449034/named) 127.0.0.1:53 (449034/named) 0.0.0.0:21 (408997/pure-ftpd) :::22 (461121/sshd :::25 (401065/master) ::1:953 (449034/named) :::443 (3008918/apache2) :::993 (493038/dovecot) :::995 (493038/dovecot) ::1:10024 (484272/amavisd-new) :::9001 (706/java) ::1:10026 (484272/amavisd-new) :::3306 (433634/mariadbd) :::587 (401065/master) :::110 (493038/dovecot) :::143 (493038/dovecot) :::8080 (3008918/apache2) :::80 (3008918/apache2) :::8081 (3008918/apache2) :::465 (401065/master) :::21 (408997/pure-ftpd) ::1:53 (449034/named) ::1:53 (449034/named) ::1:53 (449034/named) ::1:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) ##### IPTABLES ##### Chain INPUT (policy ACCEPT) target prot opt source destination f2b-dovecot-pop3imap tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 110,995,143,993 f2b-postfix tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 25 f2b-sshd tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 22 Chain FORWARD (policy ACCEPT) ::1:53 (449034/named) ::1:53 (449034/named) ::1:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) fe80::fab1:56ff:feb7:53 (449034/named) ##### IPTABLES ##### Chain INPUT (policy ACCEPT) target prot opt source destination f2b-dovecot-pop3imap tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 110,995,143,993 f2b-postfix tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 25 f2b-sshd tcp -- 0.0.0.0/0 0.0.0.0/0 multiport dports 22 Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain f2b-dovecot-pop3imap (1 references) target prot opt source destination RETURN all -- 0.0.0.0/0 0.0.0.0/0 Chain f2b-postfix (1 references) target prot opt source destination RETURN all -- 0.0.0.0/0 0.0.0.0/0 Chain f2b-sshd (1 references) target prot opt source destination RETURN all -- 0.0.0.0/0 0.0.0.0/0 ##### LET'S ENCRYPT ##### acme.sh is installed in /root/.acme.sh/acme.sh
I installed ispconfig into /usr/local/ispconfig. Not really shure what you mean. rothmedia.net is: web7, client1
My Problem ist, that ISPConfig is not running! That's what I want to get fixed. Meanwile I have another server with same hardware, same OS Debian 11/Bullseye. There I could install ISPConfig without problems. Now I think that the best approach would be to reinstall ISPConfig. I backuped the dbispconfig data base and imported it onto the new server, but after login ISPConfig is still empty. No config, no sites, no email. Where are all the files stored? How do I backup ISPConfig? And will everything be there after a new installation?
You did not say that before just now. I would say after you did Code: apt install --reinstall that is the best approach. However, just reinstalling ISPConfig may not fix the issues, you need to install the OS to an empty disk. If you can not access ISPConfig Panel, you can not use ISPConfig Migration Toolkit to copy all data to new server. If you can fix the server enought that the Panel works, Migration Toolkit would be a good way to get a working server. There is ISPConfig Business support, you pay to get your system fixed. This might work, I suspect your server is very messed up now. https://www.ispconfig.org/support/
Many thanks for your reply. I did a apt install --reinstall and could bring up the server again and access it via ssh. However ISPConfig is not running any more. Then I rented another server with identical hardware, installed the identical OS and ISPConfig. It worked. I have a freshly installed ISPConfig there. My next step would be to migrate all the data i.e. ispconfig data and all the websites to the new server and bend the DNS to the new server to have a functioning system again. I did a mysqldump of dbispconfig data base, imported it to the new server. But there ist nothing there. Which brings me to the asumption that the data is somewhere else. Where is it? Where are all the websites, emails and configurations stored? If I would copy those, the new server should be a copy of the old server, korrect? Kind regards Christian
There should be several threads in the forum about moving an ISPConfig installation to a new server manually without migration tool, you can find them probably with keywords like 'move ispconfig' or similar, probably even in the tips and tricks sub forum.
I did the rsync to move clients and vmail to the new server. When I start the migration: ./migrate --source-temp-dir=/home/temp --target-temp-dir=/home/temp I'm getting the following warning: Warning: preg_match(): Compilation failed: unrecognised compile-time option bit(s) at offset 0 in /usr/local/ispconfig/ispconfig_migration_toolkit/v71/migrate.php on line 21 Warning: preg_match(): Compilation failed: unrecognised compile-time option bit(s) at offset 0 in /usr/local/ispconfig/ispconfig_migration_toolkit/v71/includes/libbashcolor.inc.php on line 140 The script finishes. The importer.conf.php file shows only: <?php $config = array ( ); ?> Other files were not created.
Seems as if the php installation on your old system is already so broken that the Migration Tool can not run. It might that you hit this PHP bug: https://bugs.php.net/bug.php?id=81640
Many thanks Till! I'm always impressed how fast you're responding here! Soo good! I tried to fix the bug regarding the advice in the link you sent. Unfortunately it is not working. I purged php7* and reinstalled it. Still the same error: preg_match(): Compilation failed: unrecognised compile-time option bit(s) at offset 0 In my desperation I did a dist-upgrade to debian testing. Even this did not solve my problem. Still the same error. What other possibilities co I have, apart from setting it all up manual? And If I start ISPConfig up manual, does the new created page within the new ISPConfig on the new server connect to the rsynced mails and websites? Is there not a directory or file, apart of the dbconfig database which I can copy over to the new server and volá everything is up and running again on the new server?
No Please see my post #13. There are several threads that describe manual migration procedures without using the migration tool, These threads contain all the info you need about what is where and what needs to be migrated.
Well, it seems to have worked. Now I see on the new server all the data. Although I did not change /etc/passwd and /etc/group myself, all web and client entries are there. The migration information I found stops here. What I'm wondering is if all the apache entries in /etc/apache2/sites-available/ and /root/.acme.sh/ will be updated via ISPConfig or if I have to rsync these files from the old server as well? At the moment I even don't have an /root/.acme.sh directory on the new server.
I can aswer the question myself. Apache seemd to got all the sites information from ISPConfig. Magically. So great! I love this tool! What's still missing are the files in /root/.acme.sh But maybe these are obsolete and the ones in /var/www/clients/client1..n/web1..n/ssl/ are the ones used.
