Control Web Panel

Developers => Suggestions => Topic started by: DragoCom on August 03, 2024, 07:17:27 AM

Title: So here we are at EOL's
Post by: DragoCom on August 03, 2024, 07:17:27 AM
So we are at CentOS 7 and 8 both EOL, the panel doesn't work right on rocky 9 or alma 9. It seems developement for newer versions and porting to new redhat flavors has come to a stand still yet there are many many many of us that pay for pro version.

So, what is to come? When will things work properly with rocky and alma 9? When can we see more ports to other RHEL flavors? Will we ever get a dark mode and no not a css fix that messes the panel up like posted in the forums a few years ago.

Just wondering if it's time to move on or continue waiting!!!
Title: Re: So here we are at EOL's
Post by: overseer on August 03, 2024, 01:55:15 PM
Use AlmaLinux 8 for now (supported until nearly the end of the decade!) then upgrade to AlmaLinux 9 when CWP's EL9 support comes out of beta.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 03, 2024, 04:59:48 PM
Contabo hosting doesn't offer 8, only rocky and alma 9.
Title: Re: So here we are at EOL's
Post by: overseer on August 03, 2024, 07:44:41 PM
And you're married to Contabo? Or they wouldn't provide an exception for Alma 8 which is still actively supported?
Title: Re: So here we are at EOL's
Post by: DragoCom on August 04, 2024, 03:38:57 AM
Where can I download this CWP-Centos Stream 8 with the delayed updates until CWP makes them stable ffirst? Would that be a better choice than Alma 8 for the panel to work 100%?
Title: Re: So here we are at EOL's
Post by: overseer on August 04, 2024, 04:36:20 AM
A big N-O. Stream has always been a beta, rolling-release OS, not really fit for production. AlmaLinux 8 is a full, stable release fit for production use and supported almost to the end of the decade.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 04, 2024, 04:43:20 AM
What are the issues with CWP on AlmaLinux-8-latest-x86_64-minimal.iso      2024-05-25 08:01  2.0G
Title: Re: So here we are at EOL's
Post by: DragoCom on August 04, 2024, 04:44:16 AM
Or this one if it would run better on this one: AlmaLinux-8.10-x86_64-minimal.iso          2024-05-25 08:01  2.0G 
Title: Re: So here we are at EOL's
Post by: Starburst on August 04, 2024, 04:55:11 AM
The EOL is OLD news for CentOS 7 & 8.
Actually RH killed CentOS 8 before 7.

RH has also archived CentOS 8 Stream, as Stream 10 is coming out soon.

CWP works fine on AlmaLinux 8 and 9.

Rocky is missing some key files for some reason.

Yes, I would you run the latest Stable release of AlmaLinux 8, which currently is 8.10.

We have server running both version of AlmaLinux, depending on what is required.
But 4 of our mirror servers are running AlmaLinux 9.4.
We mirror for AlmaLinux, AlmaLinux-ELevate, ELRepo, EPEL, and MariaDB in 5 countries.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 04, 2024, 05:00:29 AM
I have already tried Alma 9 with CWP and it wouldn't function correct on Contabo. I will go with Alma 8.1 as soon as Contabo fixes the error in their custom image order form hehe
Title: Re: So here we are at EOL's
Post by: Starburst on August 04, 2024, 05:04:48 AM
If you have their custom ISO service, upload the AlmaLinux 8.10 DVD ISO directly their from the nearest AlmaLinux mirror.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 04, 2024, 05:23:48 AM
Oh the 13GB one? I thought minimal was always suggested from CWP hehe
Title: Re: So here we are at EOL's
Post by: Starburst on August 04, 2024, 05:40:04 AM
No, use the DVD ISO, it has all the libraries needed for the initial setup.

I personally always ran into trouble using the Minimum or Network versions.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 12:42:10 AM
No, use the DVD ISO, it has all the libraries needed for the initial setup.

I personally always ran into trouble using the Minimum or Network versions.


3rd attempt, 1 time using minimal and 2 times using  dvd install and got the same thing:

2024-08-06 02:36:40 (20.1 MB/s) - ‘cwp-services.zip’ saved [34026386/34026386]

Installing phpMyAdmin
#######################
cwp-el7-latest: line 558: mysql: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8978  100  8978    0     0  47252      0 --:--:-- --:--:-- --:--:-- 47252
curl: (23) Failed writing body (0 != 8978)
cwp-el7-latest: line 559: mysql: command not found
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3987  100  3987    0     0  21668      0 --:--:-- --:--:-- --:--:-- 21668
(23) Failed writing body
cwp-el7-latest: line 561: mysql: command not found
Failed to enable unit: Unit file named.service does not exist.
sed: can't read /etc/named.conf: No such file or directory
sed: can't read /etc/named.conf: No such file or directory
sed: can't read /etc/named.conf: No such file or directory
56 files removed
#########################################################
          CentOS Web Panel MailServer Installer
#########################################################

visit for help: www.centos-webpanel.com

cwp-el7-latest: line 604: mysql: command not found
MySQL root password is invalid!!!
Check password and run this script again.
[root@viking src]#


How can the mysql password be wrong when cwp is installing mysql itself ugggh
Title: Re: So here we are at EOL's
Post by: Starburst on August 06, 2024, 02:19:35 AM
If you want do the base OS install, no Apache, MariaDB, PHP, etc.
And then I can try to login with SSH and see why the script isn't installation anything.

I've never had the script have problems on a virgin server.
Whether AlmaLinux 8 or 9.

That shows even BIND didn't install, not to mention the main problem that MariaDB didn't install.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 03:00:29 AM
If you want do the base OS install, no Apache, MariaDB, PHP, etc.
And then I can try to login with SSH and see why the script isn't installation anything.

I've never had the script have problems on a virgin server.
Whether AlmaLinux 8 or 9.

That shows even BIND didn't install, not to mention the main problem that MariaDB didn't install.

I finally got it and it was working fine then I did the spf and dkim setups per domain and now I get this for every panel page I try to go to:

Unable to connect

An error occurred during a connection to viking.dragocom.xyz:2031.

    The site could be temporarily unavailable or too busy. Try again in a few moments.
    If you are unable to load any pages, check your computer’s network connection.
    If your computer or network is protected by a firewall or proxy, make sure that Waterfox is permitted to access the web.
Title: Re: So here we are at EOL's
Post by: BeZazz on August 06, 2024, 11:09:45 AM
It works for me, maybe something is cached at your end?

EDIT: Maybe just a hard refresh in your web browser?
Title: Re: So here we are at EOL's
Post by: Starburst on August 06, 2024, 11:13:04 AM
Ditto.

Tried viking.dragocom.xyz:2031 and it came up wit the normal login screen.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 05:19:55 PM
Yeah I got it working now. I did a reinstall and finally got it all working great. Now I just can't remember how to stop these lfd emails. I went to bed and woke up to 100+ lfd emails saying excessive resource: username and excessive resource: redis.
Title: Re: So here we are at EOL's
Post by: Starburst on August 06, 2024, 07:37:09 PM
Raise up your mem_Limit under: PHP Settings -> PHP Simple Editor

Also those LFD emails will tell you what program is causing the problem, and you can add it to
Code: [Select]
nano /etc/csf/csf.pignore
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 07:53:32 PM
Raise up your mem_Limit under: PHP Settings -> PHP Simple Editor

Also those LFD emails will tell you what program is causing the problem, and you can add it to
Code: [Select]
nano /etc/csf/csf.pignore

I have mem limit set 3096 already and I have added php-fpm and redis paths in pignore and I am still getting them.
Title: Re: So here we are at EOL's
Post by: Dutch_Mike on August 06, 2024, 08:04:43 PM
I have mem limit set 3096 already and I have added php-fpm and redis paths in pignore and I am still getting them.  <<<

I have been reading about that memory_limit. it is the limit that every connection / user gets. if you you have a server with just 4 gb of memory your system can handle only  40 connections or users before it goes out of memory.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 08:09:32 PM
I have mem limit set 3096 already and I have added php-fpm and redis paths in pignore and I am still getting them.  <<<

I have been reading about that memory_limit. it is the limit that every connection / user gets. if you you have a server with just 4 gb of memory your system can handle only  40 connections or users before it goes out of memory.

I would say that I definitely don't have that issue with 48GB ram and 1.6TB ssd hehe

(https://www.zothnet.com/dragomemlimit.png)
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 08:13:29 PM
Raise up your mem_Limit under: PHP Settings -> PHP Simple Editor

Also those LFD emails will tell you what program is causing the problem, and you can add it to
Code: [Select]
nano /etc/csf/csf.pignore

exe:/usr/sbin/varnishd
exe:/usr/sbin/nginx
exe:/usr/sbin/mariadbd
exe:/usr/sbin/redis
exe:/usr/bin/redis-server
exe:/opt/alt/php-fpm72/usr/sbin/php-fpm
exe:/opt/alt/php-fpm74/usr/sbin/php-fpm
exe:/opt/alt/php-fpm81/usr/sbin/php-fpm
exe:/opt/alt/php-fpm82/usr/sbin/php-fpm
exe:/opt/alt/php-fpm83/usr/sbin/php-fpm
Title: Re: So here we are at EOL's
Post by: Starburst on August 06, 2024, 08:35:09 PM
What is your memory_limit = line set to?

Do you have a screenshot of that.

You should see the format of the csf.pignore, and just add to the bottom.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 06, 2024, 09:34:34 PM
What is your memory_limit = line set to?

Do you have a screenshot of that.

You should see the format of the csf.pignore, and just add to the bottom.

(https://www.zothnet.com/dragophpmem.png)
Title: Re: So here we are at EOL's
Post by: Starburst on August 07, 2024, 12:28:01 AM
Have to say, never seen someone reserve 3GB for PHP before.

The normal recommended is usually only 512M

Also a 2GB limit on uploads, interesting.

Why is the max execution time 100 mins.?
If a script goes rouge, and locks, waiting 1.67 hours for it to timeout seems a little long.

But to each their own.
Title: Re: So here we are at EOL's
Post by: DragoCom on August 07, 2024, 12:41:00 AM
Have to say, never seen someone reserve 3GB for PHP before.

The normal recommended is usually only 512M

Also a 2GB limit on uploads, interesting.

Why is the max execution time 100 mins.?
If a script goes rouge, and locks, waiting 1.67 hours for it to timeout seems a little long.

But to each their own.

3GB because there is 6 sites on the server and it won't hurt to allow each one some wiggle room. As for 512mb ram that's old school memory rates, that's like saying lets run an AMD Ryzen 9 with 512MB ram hehe.

2GB limit because a lot of my sites are download/upload file sharing and some files are as high as 1.7gb or so. Hence the reason for 6000 because uploading through php times out way to quickly.

I run file sharing, I run XF/IPS forums, these type of sites require higher resources than the typical wordpress or html5 site. I don't have strangers on my box, it is me and one other person with 6 sites.
Title: Re: So here we are at EOL's
Post by: Starburst on August 07, 2024, 01:40:24 PM
I am old school, what can I say.
Been doing this way to long.

My test box is even an old HP EliteDesk 705 G4 Mini with an AMD A10 PRO / 32GB / 4TB NVMe Gen 4 SSD.  8)

It's what  I use to test new OS'es with various config, like when CWP first starting supporting AlmaLinux 9.
How I figured out the correct install steps.

Glad you got everything working.