Author Topic: So here we are at EOL's  (Read 849 times)

0 Members and 2 Guests are viewing this topic.

Offline
*
Re: So here we are at EOL's
« Reply #15 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.

Offline
*
Re: So here we are at EOL's
« Reply #16 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?
« Last Edit: August 06, 2024, 11:12:04 AM by BeZazz »

Offline
*****
Re: So here we are at EOL's
« Reply #17 on: August 06, 2024, 11:13:04 AM »
Ditto.

Tried viking.dragocom.xyz:2031 and it came up wit the normal login screen.

Offline
*
Re: So here we are at EOL's
« Reply #18 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.

Offline
*****
Re: So here we are at EOL's
« Reply #19 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

Offline
*
Re: So here we are at EOL's
« Reply #20 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.

Offline
*
Re: So here we are at EOL's
« Reply #21 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.

Offline
*
Re: So here we are at EOL's
« Reply #22 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


Offline
*
Re: So here we are at EOL's
« Reply #23 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

Offline
*****
Re: So here we are at EOL's
« Reply #24 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.

Offline
*
Re: So here we are at EOL's
« Reply #25 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.


Offline
*****
Re: So here we are at EOL's
« Reply #26 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.

Offline
*
Re: So here we are at EOL's
« Reply #27 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.

Offline
*****
Re: So here we are at EOL's
« Reply #28 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.