David C's questions

This started after installing Google Chrome (for headless browser functionality). I am concluding it has something to do with Chrome. For the first few hours after install, I was building a short-running script calling Chrome in a remote browser.

2 sides to the question. Is it acceptable for systemd to continuously run, and if so, how can the alerts be suppressed?

I have been receiving the below reports for days for the 2 reseller accounts (4 total every hour). Notice the process time is in the "days".

Time:         Sat Oct 19 08:44:54 2024 -0400
Account:      accountname
Resource:     Process Time
Exceeded:     376436 > 1800 (seconds)
Executable:   /usr/lib/systemd/systemd
Command Line: (sd-pam)
PID:          35343 (Parent PID:35342)
Killed:       No

and

Time:         Sat Oct 19 08:44:54 2024 -0400
Account:      accountname
Resource:     Process Time
Exceeded:     376436 > 1800 (seconds)
Executable:   /usr/lib/systemd/systemd
Command Line: /lib/systemd/systemd --user
PID:          35342 (Parent PID:35342)
Killed:       No

After adding the following 4 lines to csf.piginore and restarting LFD, the alerts are still coming.

pcmd: /usr/lib/systemd/systemd
pexe: /usr/lib/systemd/systemd
cmd: (sd-pam)
cmd: /lib/systemd/systemd --user

** Edit ** adding images for grawity's answer.

A VPS on Centos 7 came with a very old version of openssl. I built and installed a newer version of openssl. (details below) This newer openssl was only installed in order to upgrade to a much newer version of curl. It was intended to call this curl specifically by location and not to integrate it into any other programs.

Apparently, the installation caused an issue for exim (and who knows what else). Now, updating exim is failing due to not finding libssl.so.1.1.

Can the openssl binary in /usr/local/openssl/bin/openssl be hidden from the system? (so that exim will update) I'm not quite sure what is happening in the exim build, but of course it worked before.

I suppose two solutions are to move the openssl install to /opt or to rename the openssl to something else. However, I'd like to learn if there is a simpler solution.

All ideas welcome. Thanks for considering this.

Some system info:

[root@vps ~]# which openssl
/usr/bin/openssl

[root@vps ~]# whereis openssl
openssl: /usr/bin/openssl /usr/lib64/openssl /usr/include/openssl /usr/local/openssl /usr/share/man/man1/openssl.1ssl.gz /usr/share/man/man1/openssl.1

[root@vps ~]# /usr/bin/openssl version
OpenSSL 1.0.2k-fips  26 Jan 2017

[root@vps ~]# /usr/lib64/openssl version
-bash: /usr/lib64/openssl: Is a directory

[root@vps ~]# /usr/include/openssl version
-bash: /usr/include/openssl: Is a directory

[root@vps ~]# /usr/local/openssl/bin/openssl version
OpenSSL 1.1.1t  7 Feb 2023

---
*** Could not run ./exim -bV -C /dev/null to find version number ***
*** Exim installation failed ***
./exim: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
make: *** [install] Error 1
Moving exim binary.
---

So, I tried to introduce cURL to HTTP2 - That required nghttp2 - which required a newer version of libxml & Python .... (the road continues)

The server is running Centos 6 and appears to have many "ancient" packages which begin to make me wonder about security. (That is another question!) The hosting company isn't going to do it -- anytime this year! I am a novice system admin, who's primary concern is developing websites.

I am afraid the "manual" updates will cause more harm than good.

Can this server be made to YUM install more recent versions of packages? If so, how?

Please ask for further info. I have been researching both the manual install and fix sides, for several days now.

The goal is to have every page (minus one folder) of a site redirect to https. I've discovered the following does not do that. The one folder contains a subdomain. Let's call it mahogany.com.

Edit: Modify rules

RewriteEngine On
RewriteBase /

RewriteCond %{HTTPS} off
RewriteCond %{HTTP_HOST} ^www.site1\.mobi [NC,OR]
RewriteCond %{HTTP_HOST} ^site1\.mobi [NC,OR]
RewriteCond %{HTTP_HOST} !^mahogany\.com [NC]
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

If someone types site1.mobi or www.site1.mobi into their browser, apache with the above in the document root htaccess will not redirect.

What is wrong with the above? Is a line for mahogany.com needed to exclude it?