After adding a new vhost through centmin menu i saw the following advice: Code (Text): ------------------------------------------------------------- ok: /usr/local/src/centminmod/addons/acmetool.sh /usr/local/src/centminmod/addons/acmetool.sh issue acceso.imced.edu.mx lived ------------------------------------------------------------------------------ Version Check: ------------------------------------------------------------------------------ !!! there maybe a newer version of /usr/local/src/centminmod/addons/acmetool.sh available https://community.centminmod.com/posts/34492/ update using centmin.sh menu option 23 submenu option 2 or via command: cmupdate Always ensure Current Version is higher or equal to Latest Version ------------------------------------------------------------------------------ Current acmetool.sh Version: 1.0.79 Latest acmetool.sh Version: 1.0.82 ------------------------------------------------------------------------------ But after doing menu option 23 submenu option 2 nothing updated: Code (Text): -------------------------------------------------------- Centmin Mod Updater Sub-Menu -------------------------------------------------------- 1). Setup Centmin Mod Github Environment 2). Update Centmin Mod Current Branch 3). Update Centmin Mod Newer Branch 4). Exit -------------------------------------------------------- Enter option [ 1 - 4 ] 2 -------------------------------------------------------- Updating Current Centmin Mod code branch via git Centmin Mod local code up to date at /usr/local/src/centminmod no available updates at this time... So, im thinking this could be a bug or perhaps we should use some git routine to update acmetool.sh Thanks in advance EVA2000
Not really a bug, 130.00beta01's acmetool.sh is 1.0.82 while 124.00stable's acmetool.sh is 1.0.79 right now. But the check looks for 130.00beta01's version right now - well yeah a bug I'll have to update 124.00stable's version soon though.
Doing a new install of centminmod on a fresh centos 7.9 i discovered that the auditd fails to start with an error: Code (Text): Starting Security Auditing Service... Could not open dir /var/log/audit (No such file or directory) auditd.service: control process exited, code=exited status=6 Failed to start Security Auditing Service. Unit auditd.service entered failed state. auditd.service failed. This is the first time i see this error, but it will be solved easily by doing a: Code: mkdir -p /var/log/audit systemctl start auditd PD. I'll drop the solution here since i cannot open another bug thread since cloudflare blocked me.
Interesting issue, the audit YUM package should of set that up Code (Text): rpm -ql audit | grep '/var/log' /var/log/audit