After I tried to run test on Lightsail higher plans now it wont work at all neither on new or old snapshoot. So I tried everything I could and it appears that Bitnami service wont restart.
When used this command "sudo /opt/bitnami/ctlscript.sh status" in SSH this is what I got:
-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)
When tried this command "sudo /opt/bitnami/bndiagnostic-tool" this is what I got:
[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/
===== Begin of bndiagnostic tool output =====Action '-t -f /opt/bitnami/apache2/conf/httpd.conf' failed.The Apache error log may have more information. ✓ Resources: No issues found ? Connectivity: Found possible issues ✓ Mariadb: No issues found ✓ Processes: No issues found ? Wordpress: Found possible issues ? Apache: Found possible issues ✓ Php: No issues found
This command respond with that message:
sudo /opt/bitnami/ctlscript.sh restart apache
-Failed to restart apache: Failed to restart apache
sudo service bitnami restart
-Job for bitnami.service failed because the control process exited with error code.See "systemctl status bitnami.service" and "journalctl -xe" for details.
This command gave me that under "systemctl status bitnami.services"
-bitnami.service - LSB: bitnami init script Loaded: loaded (/etc/init.d/bitnami; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2023-01-17 21:23:39 UTC; 43s ago Process: 3198 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE) Tasks: 50 (limit: 4692) Memory: 379.4M CPU: 1.956s CGroup: /system.slice/bitnami.service ├─778 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf) ├─790 php-fpm: pool www ├─791 php-fpm: pool www ├─792 php-fpm: pool www ├─793 php-fpm: pool www ├─794 php-fpm: pool www ├─795 php-fpm: pool www ├─796 php-fpm: pool www ├─797 php-fpm: pool www ├─798 php-fpm: pool www ├─799 php-fpm: pool www ├─800 php-fpm: pool www ├─801 php-fpm: pool www ├─802 php-fpm: pool www ├─803 php-fpm: pool www ├─804 php-fpm: pool www ├─805 php-fpm: pool www ├─806 php-fpm: pool www ├─807 php-fpm: pool www ├─808 php-fpm: pool www ├─809 php-fpm: pool www ├─810 php-fpm: pool www ├─811 php-fpm: pool www ├─812 php-fpm: pool www ├─813 php-fpm: pool www
This command "journalctl -xe" gave this message:
bitnami@ip-ip-172-??-?-??:~/stack/wordpress/wp-content/plugins$ journalctl -xeJan 17 21:23:39 ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 821 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 822 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 823 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 824 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 825 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 826 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 827 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 828 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 829 (php-fpm) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Unit process 844 (mysqld) remains running after unit stopped.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: Failed to start LSB: bitnami init script.░░ Subject: A start job for unit bitnami.service has failed░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ A start job for unit bitnami.service has finished with a failure.
The job identifier is 770 and the job result is failed.Jan 17 21:23:39 ip-ip-172-??-?-?? systemd[1]: bitnami.service: Consumed 1.943s CPU time.░░ Subject: Resources consumed by unit runtime░░ Defined-By: systemd░░ Support: https://www.debian.org/support░░ ░░ The unit bitnami.service completed and consumed the indicated resources.Jan 17 21:23:44 ip-ip-172-??-?-?? dhclient[443]: PRC: Renewing lease on eth0.Jan 17 21:23:44 ip-ip-172-??-?-?? dhclient[443]: XMT: Renew on eth0, interval 10060ms.Jan 17 21:23:44 ip-ip-172-??-?-?? dhclient[443]: RCV: Reply message on eth0 from fe23::f6:53fc:fi61:2b1l.Jan 17 21:24:54 ip-ip-172-??-?-?? dhclient[443]: PRC: Renewing lease on eth0.Jan 17 21:24:54 ip-ip-172-??-?-?? dhclient[443]: XMT: Renew on eth0, interval 9680ms.Jan 17 21:24:54 ip-ip-172-??-?-?? dhclient[443]: RCV: Reply message on eth0 from fe23::f6:53fc:fi61:2b1l.Jan 17 21:26:04 ip-ip-172-??-?-?? dhclient[443]: PRC: Renewing lease on eth0.Jan 17 21:26:04 ip-ip-172-??-?-?? dhclient[443]: XMT: Renew on eth0, interval 10830ms.Jan 17 21:26:04 ip-ip-172-??-?-?? dhclient[443]: RCV: Reply message on eth0 from fe23::f6:53fc:fi61:2b1l.
I disabled the plugin causing the problems, the connectivity problem was OK Firewall is configured properly yet the problem is still there.
So I tried stoping, restarting, starting Apache nothing worked.
I stoped instance, restarted it. Created a new one via Snapshoot still the same.
Why the heck is this Lightsail so buggy? I really do not understand this.
NOTE IP AND MAC ARE NOT THE REAL ONE! For security reasons they are not shown and are fake one!
If you have some solution for this issue please return to me with some simplified instruction since I am still new to Amazon hosting.
Thx in advance.
AWS OFFICIALUpdated 3 months ago
