bitnami / vms

Bitnami VMs
https://bitnami.com
Other
203 stars 43 forks source link

Bitnami Wordpress bitnami.service failed because the control process exited with error code #1354

Closed jteck closed 6 months ago

jteck commented 8 months ago

Platform

AWS

bndiagnostic ID know more about bndiagnostic ID

d658f762-6f57-6b9b-f962-eb9eb0ac0215

bndiagnostic output

===== Begin of bndiagnostic tool output =====

✓ Resources: No issues found
? Connectivity: Found possible issues
✓ Mariadb: No issues found
✓ Processes: No issues found
✓ Wordpress: No issues found
? Apache: Found possible issues
✓ Php: No issues found

[Connectivity]

Server ports 22, 80 and/or 443 are not publicly accessible. Please check the following guide to open server ports for remote access:

https://docs.bitnami.com/general/faq/administration/use-firewall/

[Apache]

Press [Enter] to continue: Found recent error or warning messages in the Apache error log.

[Fri Jan 12 15:09:33.153747 2024] [core:error] [pid 2314511:tid 140617665328896] 
[client **ip_address**:54697] AH00124: Request exceeded the limit of 10 internal 
redirects due to probable configuration error. Use 'LimitInternalRecursion' to 
increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
 [Fri Jan 12 15:09:33.594959 2024] [core:error] [pid 2291459:tid 
140617094854400] [client **ip_address**:54700] AH00124: Request exceeded the 
limit of 10 internal redirects due to probable configuration error. Use 
'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel 
debug' to get a backtrace.
 [Fri Jan 12 17:34:36.681285 2024] [core:error] [pid 2291459:tid 
140617380206336] [client **ip_address**:41442] AH00124: Request exceeded the 
limit of 10 internal redirects due to probable configuration error. Use 
'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel 
debug' to get a backtrace., referer: http://simplesite.com

Please check the following guide to troubleshoot server issues:

https://docs.bitnami.com/general/apps/wordpress/troubleshooting/debug-erro rs-apache/

Press [Enter] to continue: The Apache configuration has errors:

AH00526: Syntax error on line 18 of 
/opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf: SSLCertificateFile: file 
'/opt/bitnami/apache/conf/server.crt' does not exist or is empty

Please check the configuration.

===== End of bndiagnostic tool output =====

Press [Enter] to continue: The diagnostic bundle was uploaded successfully to the Bitnami servers. Please copy the following code:

d658f762-6f57-6b9b-f962-eb9eb0ac0215

bndiagnostic was not useful. Could you please tell us why?

unsure what to do next

Describe your issue as much as you can

the issue started when I changed the .key and .crt to servers.key and .crt in /opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf

I tried to add it manually after fail to /opt/bitnami/apache2/conf/vhosts/wordpress-https-vhost.conf

I had my ssl for https with let's encrypt expire even though i had it setup for the auto renew. i used the bitnami HTTPS configuration tool to revoke and get new cert. it failed because it had expired so i wasn't able to do it wouthout removing the old certs first.

An error occurred revoking certificates with Let's Encrypt: 2024/01/12 21:58:41 Trying to revoke certificate for domain

Error while revoking the certificate for domain

acme: error: 403 :: POST :: 

https://acme-v02.api.letsencrypt.org/acme/revoke-cert :: urn:ietf:params:acme:error:unauthorized :: Certificate is expired

Please check our documentation and support forums, we'll be happy to help!

Press [Enter] to continue:

Error

An error occurred when applying configurations.

The web server configuration was left unchanged. There was an error in the new configuration, so it was reverted.

Failed steps:

Find more details in the log file:

/tmp/bncert-202401122156.log

If you find any issues, please check Bitnami Support forums at:

https://github.com/bitnami/vms

Press [Enter] to continue:

jteck commented 8 months ago

$ sudo /opt/bitnami/ctlscript.sh restart Restarting services.. Job for bitnami.service failed because the control process exited with error code. See "systemctl status bitnami.service" and "journalctl -xe" for details.

sudo /opt/bitnami/ctlscript.sh status Cannot find any running daemon to contact. If it is running, make sure you are pointing to the right pid file (/var/run/gonit.pid)

mdhont commented 7 months ago

the issue started when I changed the .key and .crt to servers.key and .crt in /opt/bitnami/apache/conf/bitnami/bitnami-ssl.conf

It seems the SSLCertificateFile in this file is pointing to a non existing file. Does a file still exist in the /opt/bitnami/apache/conf/server.crt path?

jteck commented 7 months ago

I put a file in Apache2. Are those connected?

mdhont commented 7 months ago

The apache folder is a symlink to the apache2 directory, so they are the same.

jteck commented 7 months ago

Will you check it out again please I had moved that elastic IP to a different EC2 to try and compare when you had looked at it

jteck commented 7 months ago

Here is what i have in the conf folder 2024-01-16_13-51-57

jteck commented 7 months ago

@mdhont any advise here?

jteck commented 7 months ago

i got it back working and now i can't renew the certificate because it is expired. What do I do next? I am trying to use bitnami https configuration tool

mdhont commented 7 months ago

Instead of renewing I recommend creating a new one manually following these steps:

https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/#alternative-approach

jteck commented 7 months ago

ok. Thank you! I will update if I have any issues or when its solved.

jteck commented 7 months ago

@mdhont where do i find the archive number referenced in step 1 ?

Run the following commands to install the Lego client. Note that you will need to replace the X.Y.Z placeholder with the actual version number of the downloaded archive:

mdhont commented 7 months ago

With the "curl" command you downloaded the lego binary file, which consists of the name (lego) and the version of the binary. You can check the full name with these command:

cd /tmp
ls lego*.tar.gz
github-actions[bot] commented 7 months ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

jteck commented 6 months ago

With the "curl" command you downloaded the lego binary file, which consists of the name (lego) and the version of the binary. You can check the full name with these command:

cd /tmp
ls lego*.tar.gz

Is the full name the version of the binary? Share more details please

github-actions[bot] commented 6 months ago

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

github-actions[bot] commented 6 months ago

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.