Skip to content

Lightsail WordPress Website: Instance created from snapshot WordPress not running, bitnami service cannot be started in SSH console

0

After creating a snapshot of a Lightsail WordPress server and then creating a new instance from that snapshot as a staging environment:

  • Cannot reach WordPress (website or admin console) via the dynamic external IP
  • Cannot reach WordPress (website or admin console) via the static external IP
  • Restarted the bitnami service "sudo /opt/bitnami/ctlscript.sh restart" succeeded
  • Still cannot reach WordPress (website or admin console)
  • Stopped the Lightsail server for 5 minutes, then restarted it
  • Checked bitnami service status "sudo /opt/bitnami/ctlscript.sh status" received the following:

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)

  • Restarted the bitnami service "sudo /opt/bitnami/ctlscript.sh restart" received the following:

Job for bitnami.service failed because the control process exited with error code. See "systemctl status bitnami.service" and "journalctl -xe" for details.

  • Checked status of the bitnami service "systemctl status bitnami.service" received the following:

bitnami.service - LSB: bitnami init script Loaded: loaded (/etc/init.d/bitnami; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2024-08-08 13:43:41 UTC; 1min 30s ago Process: 850 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE) Tasks: 19 (limit: 1116) Memory: 668.2M CPU: 2.457s CGroup: /system.slice/bitnami.service ├─685 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf) ├─689 php-fpm: pool www ├─690 php-fpm: pool www ├─691 php-fpm: pool www ├─692 php-fpm: pool www ├─693 php-fpm: pool www ├─694 php-fpm: pool www ├─695 php-fpm: pool www ├─696 php-fpm: pool www ├─697 php-fpm: pool www ├─698 php-fpm: pool www └─710 /opt/bitnami/mariadb/sbin/mysqld --defaults-file=/opt/bitnami/mariadb/conf/my.cnf --basedir>

Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 692 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 693 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 694 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 695 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 696 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 697 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 698 (php-fpm) remains running after > Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Unit process 710 (mysqld) remains running after u> Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: Failed to start LSB: bitnami init script. Aug 08 13:43:41 ip-172-26-6-240 systemd[1]: bitnami.service: Consumed 2.437s CPU time.

No constructive error messages. I searched the web, no real help there.

asked 2 years ago286 views
1 Answer
0

Hello.

Judging from the error message, I thought that the php-fpm process remained even though it had stopped, causing a problem.
So, why not try stopping all php-fpm processes once?

By the way, have you checked the journal log using the following command?

journalctl -xe

Also, if you have a problem with Bitnami Wordpress, you may be able to get an answer that will help you resolve it if you ask in the GitHub issue below.
https://github.com/bitnami/vms/issues

EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.