Author Topic: Issues with brand new fresh install with almalinux 9.4  (Read 1002 times)

0 Members and 2 Guests are viewing this topic.

Offline
*
Issues with brand new fresh install with almalinux 9.4
« on: July 25, 2024, 04:23:59 AM »
I am having issues with Apache starting and Bind starting. I have a fresh install of almalinux 9.4 and cwp pro latest. Here is what the logs say for each:

APACHE:

 An ExecStart= process belonging to unit httpd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 25 06:16:35 viking.dragocom.haha systemd[1]: httpd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ The unit httpd.service has entered the 'failed' state with result 'exit-code'.
Jul 25 06:16:35 viking.dragocom.haha systemd[1]: Failed to start Web server Apache.
░░ Subject: A start job for unit httpd.service has failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit httpd.service has finished with a failure.
░░
░░ The job identifier is 1914 and the job result is failed.
Jul 25 06:16:35 viking.dragocom.haha kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:53:da:45:74:83:ef:4e:ad:b9:08:00 SRC=194.38.20.75 DST=185.xxx.xxx.xxx LEN=52 TOS=0x00 PREC=0x00 TTL=117 ID=43284 DF PROTO=TCP SPT=60992 DPT=3389 WINDOW=64240 RES=0x00 CWR ECE SYN URGP=0
Jul 25 06:16:36 viking.dragocom.haha postfix/pickup[1287]: 6861B700205: uid=0 from=
Jul 25 06:16:36 viking.dragocom.haha postfix/cleanup[17284]: 6861B700205: message-id=<20240725041636.6861B700205@viking.dragocom.haha>
Jul 25 06:16:36 viking.dragocom.haha postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:16:36 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf lookup error for "admin@dragocom.lol"
Jul 25 06:16:36 viking.dragocom.lol postfix/cleanup[17284]: warning: 6861B700205: virtual_alias_maps map lookup problem for admin@dragocom.lol -- message not accepted, try again later
Jul 25 06:16:36 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_vacation.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:16:36 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error for "admin@dragocom.lol"
Jul 25 06:16:36 viking.dragocom.lol postfix/cleanup[17284]: warning: 6861B700205: recipient_bcc_maps map lookup problem -- message not accepted, try again later
Jul 25 06:16:37 viking.dragocom.lol postfix/pickup[1287]: 6905370019B: uid=0 from=
Jul 25 06:16:37 viking.dragocom.lol postfix/cleanup[17284]: 6905370019B: message-id=<20240725041637.6905370019B@viking.dragocom.lol>
Jul 25 06:16:37 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:16:37 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf lookup error for "admin@dragocom.lol"
Jul 25 06:16:37 viking.dragocom.lol postfix/cleanup[17284]: warning: 6905370019B: virtual_alias_maps map lookup problem for admin@dragocom.lol -- message not accepted, try again later
Jul 25 06:16:37 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_vacation.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:16:37 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error for "admin@dragocom.lol"
Jul 25 06:16:37 viking.dragocom.lol postfix/cleanup[17284]: warning: 6905370019B: recipient_bcc_maps map lookup problem -- message not accepted, try again later
Jul 25 06:16:37 viking.dragocom.lol kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:53:da:45:74:83:ef:4e:ad:b9:08:00 SRC=149.22.90.230 DST=185.xxx.xxx.xxx LEN=52 TOS=0x00 PREC=0x00 TTL=122 ID=39873 DF PROTO=TCP SPT=61468 DPT=3389 WINDOW=65340 RES=0x00 SYN URGP=0
Jul 25 06:16:38 viking.dragocom.lol postfix/pickup[1287]: 69D38700205: uid=0 from=
Jul 25 06:16:38 viking.dragocom.lol postfix/cleanup[17284]: 69D38700205: message-id=<20240725041638.69D38700205@viking.dragocom.lol>
Jul 25 06:16:38 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:16:38 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf lookup error for "admin@dragocom.lol"
Jul 25 06:16:38 viking.dragocom.lol postfix/cleanup[17284]: warning: 69D38700205: virtual_alias_maps map lookup problem for admin@dragocom.lol -- message not accepted, try again later
Jul 25 06:16:38 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_vacation.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:16:38 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error for "admin@dragocom.lol"
Jul 25 06:16:38 viking.dragocom.lol postfix/cleanup[17284]: warning: 69D38700205: recipient_bcc_maps map lookup problem -- message not accepted, try again later

BIND:

The unit named-setup-rndc.service has successfully entered the 'dead' state.
Jul 25 06:17:24 viking.dragocom.lol systemd[1]: Finished Generate rndc key for BIND (DNS).
░░ Subject: A start job for unit named-setup-rndc.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit named-setup-rndc.service has finished successfully.
░░
░░ The job identifier is 2056.
Jul 25 06:17:24 viking.dragocom.lol systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
░░ Subject: A start job for unit named.service has begun execution
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit named.service has begun execution.
░░
░░ The job identifier is 1985.
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone localhost.localdomain/IN: loaded serial 0
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone localhost/IN: loaded serial 0
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone 0.in-addr.arpa/IN: loaded serial 0
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone dragocom.lol/IN: NS 'ns1.dragocom.lol' has no address records (A or AAAA)
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone dragocom.lol/IN: NS 'ns2.dragocom.lol' has no address records (A or AAAA)
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone dragocom.lol/IN: not loaded due to errors.
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: _default/dragocom.lol/IN: bad zone
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone nullwarehouse.com/IN: loaded serial 2024072479
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone nulled.news/IN: loaded serial 2024072479
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone NS1.DRAGOCOM.lol/IN: loaded serial 2013071600
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone NS2.DRAGOCOM.lol/IN: loaded serial 2013071600
Jul 25 06:17:24 viking.dragocom.lol bash[17437]: zone vipanels.lol/IN: loaded serial 2024072518
Jul 25 06:17:24 viking.dragocom.lol systemd[1]: named.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ An ExecStartPre= process belonging to unit named.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jul 25 06:17:24 viking.dragocom.lol systemd[1]: named.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ The unit named.service has entered the 'failed' state with result 'exit-code'.
Jul 25 06:17:24 viking.dragocom.lol systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
░░ Subject: A start job for unit named.service has failed
░░ Defined-By: systemd
░░ Support: https://wiki.almalinux.org/Help-and-Support
░░
░░ A start job for unit named.service has finished with a failure.
░░
░░ The job identifier is 1985 and the job result is failed.
Jul 25 06:17:25 viking.dragocom.lol postfix/pickup[1287]: 498C3700205: uid=0 from=
Jul 25 06:17:25 viking.dragocom.lol postfix/cleanup[17336]: 498C3700205: message-id=<20240725041725.498C3700205@viking.dragocom.lol>
Jul 25 06:17:25 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:17:25 viking.dragocom.lol postfix/cleanup[17336]: warning: proxy:mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf lookup error for "admin@dragocom.lol"
Jul 25 06:17:25 viking.dragocom.lol postfix/cleanup[17336]: warning: 498C3700205: virtual_alias_maps map lookup problem for admin@dragocom.lol -- message not accepted, try again later
Jul 25 06:17:25 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_vacation.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:17:25 viking.dragocom.lol postfix/cleanup[17336]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error for "admin@dragocom.lol"
Jul 25 06:17:25 viking.dragocom.lol postfix/cleanup[17336]: warning: 498C3700205: recipient_bcc_maps map lookup problem -- message not accepted, try again later
Jul 25 06:17:25 viking.dragocom.lol kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:53:da:45:74:83:ef:4e:ad:b9:08:00 SRC=185.169.4.105 DST=185.xxx.xxx.xxx LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=57461 PROTO=TCP SPT=40866 DPT=1314 WINDOW=1024 RES=0x00 SYN URGP=0
Jul 25 06:17:26 viking.dragocom.lol postfix/pickup[1287]: 4A8B170019B: uid=0 from=
Jul 25 06:17:26 viking.dragocom.lol postfix/cleanup[17284]: 4A8B170019B: message-id=<20240725041726.4A8B170019B@viking.dragocom.lol>
Jul 25 06:17:26 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:17:26 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_alias_default_maps.cf lookup error for "admin@dragocom.lol"
Jul 25 06:17:26 viking.dragocom.lol postfix/cleanup[17284]: warning: 4A8B170019B: virtual_alias_maps map lookup problem for admin@dragocom.lol -- message not accepted, try again later
Jul 25 06:17:26 viking.dragocom.lol postfix/proxymap[16039]: warning: mysql:/etc/postfix/mysql-virtual_vacation.cf is unavailable. unsupported dictionary type: mysql
Jul 25 06:17:26 viking.dragocom.lol postfix/cleanup[17284]: warning: proxy:mysql:/etc/postfix/mysql-virtual_vacation.cf lookup error for "admin@dragocom.lol"
Jul 25 06:17:26 viking.dragocom.lol postfix/cleanup[17284]: warning: 4A8B170019B: recipient_bcc_maps map lookup problem -- message not accepted, try again later

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #1 on: July 25, 2024, 08:41:15 PM »
EL9 support is still beta and there are still bugs. Best to use EL8 releases at present (AlmaLinux 8 being the most fit for production use).

Offline
*
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #2 on: July 25, 2024, 09:43:02 PM »
I only have a few options with my host. I wanted CentOS7.9 but they will not allow EOL OS's. The screenshot is my only options. Will CWP Pro run on any of these options without issues like I am having now?


Offline
*
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #3 on: July 25, 2024, 11:04:10 PM »
I installed Rocky Linux 9 to try and see if it works better. Out of ghe box the services are working the same as it did with almalinux 9 until I set nginx, apache and varnish and changed php to 8.2.21

Offline
*
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #4 on: July 25, 2024, 11:23:14 PM »
Rocky did the same thing. Apache works right out of the box, you change to nginx anything apache fails, if you add your hostname and nameservers then bind fails.

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #5 on: July 26, 2024, 03:53:14 AM »
Can you not do the Manual Linux Installer and provide an AlmaLinux 8 installation media/ISO?

Offline
*
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #6 on: July 26, 2024, 04:10:28 AM »
No they won't allow any EOL distro's so I gave up and got Webuzo and I am actually loving it. So much more configuration options but I am getting used to it already hehe. Thanks for your help though :)

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #7 on: July 26, 2024, 04:37:24 AM »
AlmaLinux 8 is NOT EOL -- it is supported almost to the end of the decade. CWP 9 is still in beta, and EL9 releases are still a bit young -- not what you want as a foundation for a server. (CentOS 8 Stream is EOL)

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #8 on: July 27, 2024, 06:19:39 AM »
You can't have any services installed before installing CWP.

So if Apache is working 'out of the box', you are installing AlmaLinux 9.4 LAMP.
That won't work.

Reimage with the bare AlmaLinux 9.4

Setup your networking, hostname, timzone.

Then:

Code: [Select]
dnf install dnf-plugins-core
Code: [Select]
dnf install elrepo-release epel-release -y
Code: [Select]
/usr/bin/crb enable
Code: [Select]
dnf --refresh update
Code: [Select]
dnf install nano wget ipset ebtables iptables uuid uuid-devel libuuid-devel m4 pcre pcre-devel zlib-devel perl-DBD-MySQL perl-IPC-Cmd perl-Pod-Html perl-Sys-Hostname perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch perl-GDGraph libtool s-nail htop sysstat python3-perf ImageMagick ImageMagick-devel -y
Code: [Select]
dnf --refresh update
Code: [Select]
dnf install clamav* clamd
Code: [Select]
dnf clean all
Code: [Select]
cd /usr/local/src
Code: [Select]
wget http://centos-webpanel.com/cwp-el9-latest
Code: [Select]
sh cwp-el9-latest
Code: [Select]
dnf install spamassassin amavis
To updated MariaDB follow:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/

Reboot

Configure & Start CSF

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #9 on: July 27, 2024, 06:21:32 AM »
AlmaLinux 8 is NOT EOL -- it is supported almost to the end of the decade. CWP 9 is still in beta, and EL9 releases are still a bit young -- not what you want as a foundation for a server. (CentOS 8 Stream is EOL)

Contabo removed AlmaLinux 8 from their supported OS's.
There are a couple others that have done the same thing, not knowing AL8 & AL9 are running concurrent.

Offline
*
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #10 on: July 31, 2024, 08:57:43 PM »
We are very excited about the progress we have seen so far and we would like to have support for AlmaLinux 9 very soon or by the end of the year. It would be fantastic to have this version in our community, as we know that many users are eagerly awaiting the improvements and features that AlmaLinux 9 will bring.

I hope the support team can read this.

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #11 on: August 01, 2024, 08:01:05 AM »
CWP works 90% now on AlmaLinux 9.
Some features have to be manually installed, like ClamAV, SpamAssassin and Amavis. But are easy to do with dnf.

CWP -> CWP Migration doesn't fully work.
PHP only supports 7.4.33 or 8.2/8.3. But that isn't a deal breaker, since even 7.4.x is past EOL. And 8.4 is in alpha.

Offline
*
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #12 on: October 14, 2024, 07:17:54 PM »
You can't have any services installed before installing CWP.

So if Apache is working 'out of the box', you are installing AlmaLinux 9.4 LAMP.
That won't work.

Reimage with the bare AlmaLinux 9.4

Setup your networking, hostname, timzone.

Then:

Code: [Select]
dnf install dnf-plugins-core
Code: [Select]
dnf install elrepo-release epel-release -y
Code: [Select]
/usr/bin/crb enable
Code: [Select]
dnf --refresh update
Code: [Select]
dnf install nano wget ipset ebtables iptables uuid uuid-devel libuuid-devel m4 pcre pcre-devel zlib-devel perl-DBD-MySQL perl-IPC-Cmd perl-Pod-Html perl-Sys-Hostname perl-libwww-perl.noarch perl-LWP-Protocol-https.noarch perl-GDGraph libtool s-nail htop sysstat python3-perf ImageMagick ImageMagick-devel -y
Code: [Select]
dnf --refresh update
Code: [Select]
dnf install clamav* clamd
Code: [Select]
dnf clean all
Code: [Select]
cd /usr/local/src
Code: [Select]
wget http://centos-webpanel.com/cwp-el9-latest
Code: [Select]
sh cwp-el9-latest
Code: [Select]
dnf install spamassassin amavis
To updated MariaDB follow:
https://www.alphagnu.com/topic/23-upgrade-mariadb-1011-in-cwp-centos-7-centos-8-stream-almalinux-78-rockylinux-78/

Reboot

Configure & Start CSF

Thank you very much, I solved many problems thanks to you.

Offline
*****
Re: Issues with brand new fresh install with almalinux 9.4
« Reply #13 on: October 15, 2024, 12:16:31 PM »
You're welcome.

We are always tweaking the AL9 install process, that's just a small fraction of the current AL9 internal guide we use that is 12 pages long. :/