[BlueOnyx:25797] Re: 5209R/5210R/5211R: ISO images updated

[ernie]

Hi Michael,
that update got rid of the gencerts error, but the admserv still doesn't 
want to start.

[root at bx4 log]# systemctl status admserv-php-fpm.service
× admserv-php-fpm.service - AdmServ PHP FastCGI Process Manager
      Loaded: loaded (/usr/lib/systemd/system/admserv-php-fpm.service; 
enabled; vendor preset: disabled)
      Active: failed (Result: exit-code) since Thu 2022-12-08 07:20:37 
AEST; 1min 42s ago
    Main PID: 1730 (code=exited, status=70)
         CPU: 27ms

Dec 08 07:20:36 bx4 systemd[1]: admserv-php-fpm.service: Main process 
exited, code=exited, status=70/SOFTWARE
Dec 08 07:20:36 bx4 systemd[1]: admserv-php-fpm.service: Failed with 
result 'exit-code'.
Dec 08 07:20:36 bx4 systemd[1]: Failed to start AdmServ PHP FastCGI 
Process Manager.
Dec 08 07:20:37 bx4 systemd[1]: admserv-php-fpm.service: Scheduled 
restart job, restart counter is at 5.
Dec 08 07:20:37 bx4 systemd[1]: Stopped AdmServ PHP FastCGI Process 
Manager.
Dec 08 07:20:37 bx4 systemd[1]: admserv-php-fpm.service: Start request 
repeated too quickly.
Dec 08 07:20:37 bx4 systemd[1]: admserv-php-fpm.service: Failed with 
result 'exit-code'.
Dec 08 07:20:37 bx4 systemd[1]: Failed to start AdmServ PHP FastCGI 
Process Manager.



I have run out of ideas, unless it has something to do with having to 
run QEMU in host mode instead of kvm64.

I have never had this problem with any prior version of BX or BQ.


- Ernie.




On 2022-12-08 03:37, Michael Stauber wrote:
> Hi Ernie,
> 
>> I also just tried the default with LVM makes no difference.
> 
> Different partitioning layouts have no effect on the installed
> software. So that doesn't matter,
> 
>> The admserv works during the first boot after the install, but doesn't
>> launch after any subsequent reboots.
> 
> *That* is something I can't replicate. I just did another install from
> the BlueOnyx-5211R-AlmaLinux-9.1-20221206.iso and rebooted it a few
> times. AdmServ always started w/o a hitch. Just admserv-init.service
> complained, but that's irrelevant.
> 
>> That browser tries to insert the word admin into the IPv6 address
>> field which I then delete and leave empty.
> 
> That's a browser issue that I can't do anything about. It happens in
> certain browsers if you choose to save the user credentials in the
> browser. It then stupidly tries to insert it somewhere into one of the
> form fields where it doesn't belong.
> 
>> Also, every install I get the Active Monitor warning about no Internet
>> connection after an install.
> 
> Go to "Active Monitor", "Settings" and disable "Network Status". THAT
> monitoring component checks if your Gateway is pingable. If it can't
> ping the Gateway it assumes that you have network issues. Most likely
> your Gateway is configured to not be pingable.
> 
>> I have confirmed that there is no such file as
>> /usr/libexec/admserv-ssl-gencerts
>> however there is a /usr/libexec/httpd-ssl-gencerts
> 
> I just published a new base-admserv to YUM and released a new ISO
> image that fixes these issues.
> 
> It now boots as clean as a whistle w/o error messages related to
> "admserv-init.service". There is still the odd Dovecot error that
> briefly pops up, but that's because the CCEd-constructors aren't yet
> finished fixing the configs.
> 
> This is about as clean as it gets.