LSB failed to start

Keywords: WordPress - AWS - Technical issue - Other

bnsupport ID: 46306379-42f9-f144-09a9-9cfcf09649e9

bndiagnostic output:

? Apache: Found possible issues
? Resources: Found possible issues

bndiagnostic failure reason: I do not know how to perform the changes explained in the documentation

Description:
When following the how-to for installing SSL I wasn’t able to restart with this command sudo /opt/bitnami/ctlscript.sh start

I have tried troubleshooting but have been unsuccessful and cannot log into my admin counsel.

Bitnami installation directory

Please type a directory that contains a Bitnami installation. The default 
installation directory for Linux installers is a directory inside /opt.

Bitnami installation directory [/opt/bitnami]: ^C
bitnami@ip-172-26-9-8:~$ 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.
bitnami@ip-172-26-9-8:~$ systemctl status bitnami.service
● bitnami.service - LSB: bitnami init script
   Loaded: loaded (/etc/init.d/bitnami; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2021-10-27 04:44:58 UTC; 33s ago
  Process: 6601 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE)
    Tasks: 41 (limit: 1164)
   Memory: 495.8M
   CGroup: /system.slice/bitnami.service
           ├─729 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
           ├─733 php-fpm: pool www
           ├─734 php-fpm: pool www
           ├─735 php-fpm: pool www
           ├─736 php-fpm: pool www
           ├─737 php-fpm: pool www
           ├─738 php-fpm: pool www
           ├─739 php-fpm: pool www
           ├─740 php-fpm: pool www
           ├─741 php-fpm: pool www
           ├─742 php-fpm: pool www
           └─758 /opt/bitnami/mariadb/sbin/mysqld --defaults-file=/opt/bitnami/mariadb/con

Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: SSLCertificateFile: file '/opt/bitnami/apache
Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: 2021-10-27T04:44:58.010Z - error: Unable to p
Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: ## 2021-10-27 04:44:58+00:00 ## INFO ## Runni
Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: ## 2021-10-27 04:44:58+00:00 ## INFO ## Runni
Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: ## 2021-10-27 04:44:58+00:00 ## INFO ## Runni
Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: ## 2021-10-27 04:44:58+00:00 ## INFO ## Runni
Oct 27 04:44:58 ip-172-26-9-8 bitnami[6601]: ## 2021-10-27 04:44:58+00:00 ## INFO ## Runni
Oct 27 04:44:58 ip-172-26-9-8 systemd[1]: bitnami.service: Control process exited, code=ex
Oct 27 04:44:58 ip-172-26-9-8 systemd[1]: bitnami.service: Failed with result 'exit-code'.
Oct 27 04:44:58 ip-172-26-9-8 systemd[1]: Failed to start LSB: bitnami init script.

Hi @bookings,

The Bitnami Diagnostic Tool is warning you about the different Apache-related errors it found, did you check them?

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

[Apache]

The Apache configuration has errors:

apache2: Syntax error on line 66 of /opt/bitnami/apache2/conf/httpd.conf: Cannot load modules/mod_mpm_event.so into server: /opt/bitnami/apache/modules/mod_mpm_event.so: undefined symbol: ap_run_child_stopping

Please check the configuration.

System Apache is running:

root 7095 0.0 0.5 12968 5332 ? Ss 05:02 0:00 /usr/sbin/apache2 -k start www-data 7096 0.0 0.5 758916 5812 ? Sl 05:02 0:00 /usr/sbin/apache2 -k start

If Bitnami Apache isn’t starting this is the most likely cause. Please run the following command to stop it:

sudo service apache2 stop

I had tried checking them and wasn’t about to resolve them.

I am early on enough in the site development that it is easier to create a new instance.

Hi @bookings,

If you can start from scratch, that’ll solve all the issues that the tool reported. Please apply your changes one by one and ensure they all work before applying the next one. That way you will know what change introduced the issue in the configuration.

Thanks

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.