Systemctl status bitnami.service" and "journalctl -xe" for details. I did not reboot

Keywords: WordPress + NGINX + SSL - AWS - Technical issue - Secure Connections (SSL/HTTPS)
Description:
help, I have stopped bitnami services to generate an ssl certificate according to the article https://docs.bitnami.com/aws/how-to/generate-install-lets-encrypt-ssl/#alternative-approach, now when I try start the services again, the following error appears

bitnami @ ip-172-31-23-49: / $ sudo /opt/bitnami/ctlscript.sh start
Starting services ..
Job for bitnami.service failed because the control process exited with error code.
See "systemctl status bitnami.service" and "journalctl -xe" for details.

and when executing the command

bitnami @ ip-172-31-23-49: / $ sudo /opt/bitnami/ctlscript.sh status
mariadb not running
nginx not running
php-fpm not running

and I don’t know how I can get the service up.

Thank you

Hi @edwin.ruiz

Thanks for using Bitnami WordPress + NGINX + SSL!

Let’s try to obtain some more information to help us identify the issue :slightly_smiling_face: Could you please execute the following commands?

$ systemctl status bitnami.service
$ journalctl -xe
$ sudo apachectl -t

Additionally, we have a Support Tool that will gather relevant information for us to analyze your configuration and logs. Could you please execute it on the machine where the stack is running by following the steps described in the guide below?

Please note that you need to paste the code ID that is shown at the end.

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart:

Hello
Outcome

bitnami@ip-172-31-23-49:/$ 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 Tue 2021-06-01 02:40:16 UTC; 8h ago
  Process: 31718 ExecStart=/etc/init.d/bitnami start (code=exited, status=1/FAILURE)
    Tasks: 20 (limit: 1164)
   Memory: 184.9M
   CGroup: /system.slice/bitnami.service
           ├─ 1785 /opt/bitnami/gonit/bin/gonit
           ├─30767 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
           ├─30771 php-fpm: pool www
           ├─30772 php-fpm: pool www
           ├─30773 php-fpm: pool www
           ├─30774 php-fpm: pool www
           ├─30775 php-fpm: pool www
           ├─30776 php-fpm: pool www
           ├─30777 php-fpm: pool www
           ├─30778 php-fpm: pool www
           ├─30779 php-fpm: pool www
           └─30780 php-fpm: pool www

Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: mariadb 02:40:16.87 ERROR ==> mariadb did not start
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: 2021-06-01T02:40:16.883Z - error: Unable to perform start operation Export start for mariadb failed with exit cod
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata...
Jun 01 02:40:16 ip-172-31-23-49 systemd[1]: bitnami.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 02:40:16 ip-172-31-23-49 systemd[1]: bitnami.service: Failed with result 'exit-code'.
Jun 01 02:40:16 ip-172-31-23-49 systemd[1]: Failed to start LSB: bitnami init script.
 ESCOD
   CGroup: /system.slice/bitnami.service
           ├─ 1785 /opt/bitnami/gonit/bin/gonit
           ├─30767 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
           ├─30771 php-fpm: pool www
           ├─30772 php-fpm: pool www
           ├─30773 php-fpm: pool www
           ├─30774 php-fpm: pool www
           ├─30775 php-fpm: pool www
           ├─30776 php-fpm: pool www
           ├─30777 php-fpm: pool www
           ├─30778 php-fpm: pool www
           ├─30779 php-fpm: pool www
           └─30780 php-fpm: pool www

Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: mariadb 02:40:16.87 ERROR ==> mariadb did not start
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: 2021-06-01T02:40:16.883Z - error: Unable to perform start operation Export start for mariadb failed with exit cod
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/010_bitnami_agent_extra...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/020_bitnami_agent...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/030_update_welcome_file...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/040_bitnami_credentials_file...
Jun 01 02:40:16 ip-172-31-23-49 bitnami[31718]: ## 2021-06-01 02:40:16+00:00 ## INFO ## Running /opt/bitnami/var/init/post-start/050_clean_metadata...
Jun 01 02:40:16 ip-172-31-23-49 systemd[1]: bitnami.service: Control process exited, code=exited, status=1/FAILURE
Jun 01 02:40:16 ip-172-31-23-49 systemd[1]: bitnami.service: Failed with result 'exit-code'.
Jun 01 02:40:16 ip-172-31-23-49 systemd[1]: Failed to start LSB: bitnami init script.
bitnami@ip-172-31-23-49:/$ journalctl -xejournalctl -xe
journalctl: invalid option -- 'j'
bitnami@ip-172-31-23-49:/$ sudo apachectl -t
sudo: apachectl: command not found

code

88d7750d-5879-60cc-49b1-02e4486850d8

Hi @edwin.ruiz

There is a typo in one of your commands above, journalctl -xejournalctl -xe should be journalctl -xe

However, I was able to take a look at the report the tool generated. It seems you have configured improper permissions for the /opt/bitnami/mariadb folder.

Somehow, some of the logfiles couldn’t be retrieved by the tool. Would you mind executing the following commands to get more information?

$ sudo nginx -t
$ sudo tail -n 40 /opt/bitnami/mariadb/logs/mysqld.log

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart:

Hello
this is the output of the commands

bitnami@ip-172-31-23-49:/$ sudo nginx -t
nginx: the configuration file /opt/bitnami/nginx/conf/nginx.conf syntax is ok
nginx: configuration file /opt/bitnami/nginx/conf/nginx.conf test is successful

bitnami@ip-172-31-23-49:/$ sudo tail -n 40 /opt/bitnami/mariadb/logs/mysqld.log
2021-05-31 17:31:00 45814 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
2021-05-31 17:31:30 45821 [Warning] Access denied for user 'root'@'localhost' (using password: YES)
2021-06-01  1:52:58 51092 [Warning] Aborted connection 51092 to db: 'bitnami_wordpress' user: 'bn_wordpress' host: 'localhost' (Got an error reading communication packets)
2021-06-01  1:52:58 51093 [Warning] Aborted connection 51093 to db: 'bitnami_wordpress' user: 'bn_wordpress' host: 'localhost' (Got an error reading communication packets)
2021-06-01  1:52:58 51090 [Warning] Aborted connection 51090 to db: 'bitnami_wordpress' user: 'bn_wordpress' host: 'localhost' (Got an error reading communication packets)
2021-06-01  1:52:59 0 [Note] /opt/bitnami/mariadb/sbin/mysqld (initiated by: unknown): Normal shutdown
2021-06-01  1:52:59 0 [Note] Event Scheduler: Purging the queue. 0 events
2021-06-01  1:52:59 0 [Note] InnoDB: FTS optimize thread exiting.
2021-06-01  1:53:00 0 [Note] InnoDB: Starting shutdown...
2021-06-01  1:53:00 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mariadb/data/ib_buffer_pool
2021-06-01  1:53:00 0 [Note] InnoDB: Instance 0, restricted to 256 pages due to innodb_buf_pool_dump_pct=25
2021-06-01  1:53:00 0 [Note] InnoDB: Buffer pool(s) dump completed at 210601  1:53:00
2021-06-01  1:53:01 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2021-06-01  1:53:01 0 [Note] InnoDB: Shutdown completed; log sequence number 193887779; transaction id 280491
2021-06-01  1:53:01 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: Shutdown complete

bitnami@ip-172-31-23-49:/$ journalctl -xe
Jun 02 11:17:01 ip-172-31-23-49 CRON[5777]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 02 11:17:01 ip-172-31-23-49 CRON[5778]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 02 11:17:01 ip-172-31-23-49 CRON[5777]: pam_unix(cron:session): session closed for user root
Jun 02 11:18:12 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 115300ms.
Jun 02 11:20:08 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 115190ms.
Jun 02 11:21:29 ip-172-31-23-49 sshd[5780]: Did not receive identification string from 209.141.50.29 port 50278
Jun 02 11:22:03 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 122820ms.
Jun 02 11:24:04 ip-172-31-23-49 dhclient[344]: DHCPREQUEST for 172.31.23.49 on eth0 to 172.31.16.1 port 67
Jun 02 11:24:04 ip-172-31-23-49 dhclient[344]: DHCPACK of 172.31.23.49 from 172.31.16.1
Jun 02 11:24:04 ip-172-31-23-49 dhclient[344]: bound to 172.31.23.49 -- renewal in 1609 seconds.
Jun 02 11:24:06 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 120800ms.
Jun 02 11:26:07 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 112280ms.
Jun 02 11:27:59 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 115850ms.
Jun 02 11:29:55 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 130410ms.
Jun 02 11:32:06 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 112690ms.
Jun 02 11:33:58 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 130320ms.
Jun 02 11:36:09 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 125520ms.
Jun 02 11:38:14 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 121980ms.
Jun 02 11:40:16 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 118700ms.
Jun 02 11:42:15 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 126520ms.
Jun 02 11:43:01 ip-172-31-23-49 CRON[5795]: pam_unix(cron:session): session opened for user bitnami by (uid=0)
Jun 02 11:43:01 ip-172-31-23-49 CRON[5796]: (bitnami) CMD (cd /opt/bitnami/stats && ./agent.bin --run -D)
Jun 02 11:43:01 ip-172-31-23-49 CRON[5795]: pam_unix(cron:session): session closed for user bitnami
Jun 02 11:44:22 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 119690ms.
Jun 02 11:46:22 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 112400ms.
Jun 02 11:48:14 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 131400ms.
Jun 02 11:50:26 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 109430ms.
Jun 02 11:50:53 ip-172-31-23-49 dhclient[344]: DHCPREQUEST for 172.31.23.49 on eth0 to 172.31.16.1 port 67
Jun 02 11:50:53 ip-172-31-23-49 dhclient[344]: DHCPACK of 172.31.23.49 from 172.31.16.1
Jun 02 11:50:53 ip-172-31-23-49 dhclient[344]: bound to 172.31.23.49 -- renewal in 1715 seconds.
Jun 02 11:52:15 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 119270ms.
Jun 02 11:54:14 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 127120ms.
Jun 02 11:56:22 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 126540ms.
Jun 02 11:58:28 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 123770ms.
Jun 02 12:00:32 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 114990ms.
Jun 02 12:02:27 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 121340ms.
Jun 02 12:04:28 ip-172-31-23-49 dhclient[428]: XMT: Solicit on eth0, interval 129920ms.
Jun 02 12:05:10 ip-172-31-23-49 sudo[5880]:  bitnami : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/opt/bitnami/nginx/sbin/nginx -t
Jun 02 12:05:10 ip-172-31-23-49 sudo[5880]: pam_unix(sudo:session): session opened for user root by bitnami(uid=0)
Jun 02 12:05:10 ip-172-31-23-49 sudo[5880]: pam_unix(sudo:session): session closed for user root
Jun 02 12:05:38 ip-172-31-23-49 sudo[5882]:  bitnami : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/tail -n 40 /opt/bitnami/mariadb/logs/mysqld.log
Jun 02 12:05:38 ip-172-31-23-49 sudo[5882]: pam_unix(sudo:session): session opened for user root by bitnami(uid=0)
Jun 02 12:05:38 ip-172-31-23-49 sudo[5882]: pam_unix(sudo:session): session closed for user root

ia code support e support bundle was uploaded successfully to the Bitnami servers. Please copy the following code:

88d7750d-5879-60cc-49b1-02e4486850d8

Hi @edwin.ruiz

Although in the logs I can’t see any reference to permissions, the report generated by the bnsupport-tool indicates that the ownership of all the different folders in /opt/bitnami have been changed to bitnami:daemon. Have you performed any operations regarding permissions/ownership?

Could you please try to execute the following commands:

$ sudo /opt/bitnami/ctlscript.sh stop mariadb
$ sudo cp -R /bitnami/mariadb/data /bitnami/mariadb-back
$ sudo cp -R /opt/bitnami/mariadb /opt/bitnami/mariadb-back
$ sudo chown -R root:root /opt/bitnami/mariadb
$ sudo chown -R mysql:mysql /opt/bitnami/mariadb/logs /opt/bitnami/mariadb/tmp
$ sudo chown -LR mysql:mysql /opt/bitnami/mariadb/data
$ sudo find /bitnami/mariadb/data -type d -exec chmod 700 {} \;
$ sudo find /bitnami/mariadb/data -type f -exec chmod 660 {} \;

After setting the right permissions, let’s try to restart mariadb:

$ sudo /opt/bitnami/ctlscript.sh start mariadb
$ sudo gonit status
$ sudo gonit status

Let’s see if that makes the trick for mariadb :slightly_smiling_face:

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart:

hi

bitnami@ip-172-31-23-49:~$ sudo /opt/bitnami/ctlscript.sh stop mariadb
Stopped mariadb
bitnami@ip-172-31-23-49:~$ sudo cp -R /bitnami/mariadb/data /bitnami/mariadb-back
bitnami@ip-172-31-23-49:~$ sudo cp -R /opt/bitnami/mariadb /opt/bitnami/mariadb-back
bitnami@ip-172-31-23-49:~$ sudo chown -R root:root /opt/bitnami/mariadbsudo chown -R root:root /opt/bitnami/mariadb
chown: cannot access '/opt/bitnami/mariadbsudo': No such file or directory
chown: cannot access 'chown': No such file or directory
chown: cannot access 'root:root': No such file or directory
bitnami@ip-172-31-23-49:~$ sudo chown -R mysql:mysql /opt/bitnami/mariadb/logs /opt/bitnami/mariadb/tmp
bitnami@ip-172-31-23-49:~$ sudo chown -LR mysql:mysql /opt/bitnami/mariadb/data
bitnami@ip-172-31-23-49:~$ sudo find /bitnami/mariadb/data -type d -exec chmod 700 {} \;
bitnami@ip-172-31-23-49:~$ sudo find /bitnami/mariadb/data -type f -exec chmod 660 {} \;
bitnami@ip-172-31-23-49:~$ sudo /opt/bitnami/ctlscript.sh start mariadb
Started mariadb
bitnami@ip-172-31-23-49:~$ sudo gonit 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)

I do not remember, how could I re-leave the permissions and / or property as mentioned

apologies. I made a typing mistake

bitnami@ip-172-31-23-49:~$ sudo /opt/bitnami/ctlscript.sh stop mariadb
Stopped mariadb
bitnami@ip-172-31-23-49:~$ sudo cp -R /bitnami/mariadb/data /bitnami/mariadb-back
bitnami@ip-172-31-23-49:~$ sudo cp -R /opt/bitnami/mariadb /opt/bitnami/mariadb-back
bitnami@ip-172-31-23-49:~$ sudo chown -R root:root /opt/bitnami/mariadb
bitnami@ip-172-31-23-49:~$ sudo chown -R mysql:mysql /opt/bitnami/mariadb/logs /opt/bitnami/mariadb/tmp
bitnami@ip-172-31-23-49:~$ sudo chown -LR mysql:mysql /opt/bitnami/mariadb/data
bitnami@ip-172-31-23-49:~$ sudo find /bitnami/mariadb/data -type d -exec chmod 700 {} \;
bitnami@ip-172-31-23-49:~$ sudo find /bitnami/mariadb/data -type f -exec chmod 660 {} \;
bitnami@ip-172-31-23-49:~$ sudo /opt/bitnami/ctlscript.sh start mariadb
Started mariadb
bitnami@ip-172-31-23-49:~$ sudo gonit 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)

hi i have checked multiple folders and they have owner / group bitnami deaemon, is this correct?

Hi! Well, I don’t really know the scope of the permissions changes that has been done so I can’t state the different commands to revert to the exact default ones. The easiest option if you want to accomplish this would be to launch a new instance and restore a backup of your data. That would ensure that all permissions are set to their default value.

Regarding the execution of the commands, I see that the database was able to start up correctly :confetti_ball: However, there still are some problems with gonit (the program that monitor every other bitnami service). Can you run the following commands to obtain more information?

$ sudo /opt/bitnami/ctlscript.sh status
$ sudo tail -n 30 /opt/bitnami/mariadb/logs/mysqld.log
$ ps aux |  grep 'apache\|mysql\|nginx\|/opt/bitnami\|php-fpm\|maria'
$ ps aux | grep gonit
$ sudo cat /var/run/gonit.pid
$ sudo gonit status
$ sudo head -n10 /var/log/gonit.log

hi i have checked multiple folders and they have owner / group bitnami deaemon, is this correct?

No, the /opt/bitnami folder is expected to be owned by root:root

$ ls -la /opt/
total 12
drwxr-xr-x  3 root root 4096 May 28 05:30 .
drwxr-xr-x 19 root root 4096 Jun  4 13:36 ..
drwxr-xr-x 19 root root 4096 Jun  4 13:37 bitnami

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart:

hello good moring

bitnami@ip-172-31-23-49:~$ 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)
bitnami@ip-172-31-23-49:~$ sudo tail -n 30 /opt/bitnami/mariadb/logs/mysqld.log
2021-06-03 14:03:10 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mariadb/data/ib_buffer_pool
2021-06-03 14:03:10 0 [Note] InnoDB: Buffer pool(s) dump completed at 210603 14:03:10
2021-06-03 14:03:12 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2021-06-03 14:03:12 0 [Note] InnoDB: Shutdown completed; log sequence number 194099419; transaction id 280557
2021-06-03 14:03:12 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: Shutdown complete

2021-06-03 14:03:12 0 [Note] InnoDB: Using Linux native AIO
2021-06-03 14:03:12 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-06-03 14:03:12 0 [Note] InnoDB: Uses event mutexes
2021-06-03 14:03:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-06-03 14:03:12 0 [Note] InnoDB: Number of pools: 1
2021-06-03 14:03:12 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-06-03 14:03:12 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2021-06-03 14:03:12 0 [Note] InnoDB: Completed initialization of buffer pool
2021-06-03 14:03:12 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-06-03 14:03:12 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-06-03 14:03:12 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-06-03 14:03:12 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-06-03 14:03:12 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-06-03 14:03:12 0 [Note] InnoDB: Waiting for purge to start
2021-06-03 14:03:12 0 [Note] InnoDB: 10.3.29 started; log sequence number 194099419; transaction id 280556
2021-06-03 14:03:12 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
2021-06-03 14:03:12 0 [Note] InnoDB: Buffer pool(s) load completed at 210603 14:03:12
2021-06-03 14:03:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-06-03 14:03:12 0 [Note] Server socket created on IP: '127.0.0.1'.
2021-06-03 14:03:12 0 [Warning] 'proxies_priv' entry '@% root@ip-172-31-23-49' ignored in --skip-name-resolve mode.
2021-06-03 14:03:12 0 [Note] Reading of all Master_info entries succeeded
2021-06-03 14:03:12 0 [Note] Added new Master_info '' to hash table
2021-06-03 14:03:12 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
Version: '10.3.29-MariaDB'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
bitnami@ip-172-31-23-49:~$ ps aux |  grep 'apache\|mysql\|nginx\|/opt/bitnami\|php-fpm\|maria'
mysql     6488  0.1  7.2 1171600 149028 pts/0  Sl   Jun03   1:51 /opt/bitnami/mariadb/sbin/mysqld --defaults-file=/opt/bitnami/mariadb/conf/my.cnf --basedir=/opt/bitnami/mariadb --datadir=/bitnami/mariadb/data --socket=/opt/bitnami/mariadb/tmp/mysql.sock --pid-file=/opt/bitnami/mariadb/tmp/mysqld.pid
root      6543  0.0  0.0  16436  1484 ?        Ss   Jun03   0:00 nginx: master process /opt/bitnami/nginx/sbin/nginx -c /opt/bitnami/nginx/conf/nginx.conf
daemon    6545  0.0  0.3  17188  8116 ?        S    Jun03   0:03 nginx: worker process
root      6567  0.0  1.9 321072 40104 ?        Ss   Jun03   0:02 php-fpm: master process (/opt/bitnami/php/etc/php-fpm.conf)
daemon    6580  0.0  5.7 420144 117704 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6581  0.0  5.8 420840 120536 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6582  0.0  5.6 420992 116128 ?       S    Jun03   1:15 php-fpm: pool www
daemon    6583  0.0  5.7 420032 118068 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6584  0.0  5.6 420912 115872 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6585  0.0  5.8 420440 119916 ?       S    Jun03   1:15 php-fpm: pool www
daemon    6586  0.0  5.8 421604 119168 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6587  0.0  5.5 420048 113832 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6588  0.0  5.4 420032 112056 ?       S    Jun03   1:12 php-fpm: pool www
daemon    6589  0.0  5.8 422308 119696 ?       S    Jun03   1:15 php-fpm: pool www
daemon    6590  0.0  5.6 420240 116456 ?       S    Jun03   1:14 php-fpm: pool www
daemon    6597  0.0  5.9 422400 121456 ?       S    Jun03   1:13 php-fpm: pool www
daemon    8206  0.0  5.9 421124 120776 ?       S    Jun03   1:01 php-fpm: pool www
daemon    9536  0.0  5.6 424268 115096 ?       S    01:15   0:44 php-fpm: pool www
daemon   10018  0.0  5.3 346356 110308 ?       S    02:52   0:38 php-fpm: pool www
daemon   10019  0.0  5.7 420872 116940 ?       S    02:52   0:40 php-fpm: pool www
daemon   10020  0.0  5.3 346080 108960 ?       S    02:52   0:39 php-fpm: pool www
daemon   10025  0.0  5.6 346388 115044 ?       S    02:53   0:39 php-fpm: pool www
daemon   10031  0.0  5.6 348360 115664 ?       S    02:56   0:40 php-fpm: pool www
daemon   10034  0.0  5.2 346040 107112 ?       S    02:57   0:38 php-fpm: pool www
daemon   11287  0.0  5.0 346036 102684 ?       S    11:00   0:12 php-fpm: pool www
daemon   11288  0.0  4.6 345000 95472 ?        S    11:02   0:11 php-fpm: pool www
bitnami  12039  0.0  0.0   6220   824 pts/0    S+   14:30   0:00 grep apache\|mysql\|nginx\|/opt/bitnami\|php-fpm\|maria
bitnami@ip-172-31-23-49:~$ ls -la /opt/
total 12
drwxr-xr-x  3 root    root   4096 May 20 17:02 .
drwxr-xr-x 19 root    root   4096 Jun  2 13:26 ..
drwxrwxr-x 21 bitnami daemon 4096 Jun  3 11:48 bitnami

Hello, from the opt / bitnami folder, how do I leave the owner as it should be?

Hi!

From the first output you provided, it seems that all the services are running (DB + NGINX + PHP-FPM) but still there is some problem with gonit. Unfortunately, you did not executed all the commands I provided and I need their output to know more about gonit's status:

$ ps aux | grep gonit
$ sudo cat /var/run/gonit.pid
$ sudo gonit status
$ sudo head -n10 /var/log/gonit.log

Hello, from the opt / bitnami folder, how do I leave the owner as it should be?

Could that be a possible option for you?

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart:

hi

bitnami@ip-172-31-23-49:~$ ps aux | grep gonit
bitnami  24017  0.0  0.0   6076   824 pts/0    S+   11:38   0:00 grep gonit
bitnami@ip-172-31-23-49:~$ sudo cat /var/run/gonit.pid
cat: /var/run/gonit.pid: No such file or directory
bitnami@ip-172-31-23-49:~$ sudo gonit 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)
bitnami@ip-172-31-23-49:~$ sudo head -n10 /var/log/gonit.log
time="2021-05-21T21:43:13Z" level=info msg="Performing checks"
time="2021-05-21T21:43:13Z" level=info msg="Performing process check php-fpm"
time="2021-05-21T21:43:13Z" level=info msg="Performing process check mariadb"
time="2021-05-21T21:43:13Z" level=info msg="Performing process check nginx"
time="2021-05-21T21:45:13Z" level=info msg="Performing checks"
time="2021-05-21T21:45:13Z" level=info msg="Performing process check php-fpm"
time="2021-05-21T21:45:13Z" level=info msg="Performing process check mariadb"
time="2021-05-21T21:45:13Z" level=info msg="Performing process check nginx"
time="2021-05-21T21:47:13Z" level=info msg="Performing checks"
time="2021-05-21T21:47:13Z" level=info msg="Performing process check php-fpm"

the instance cannot be reinstalled

From the logs you shared I see that gonit is not started in your instance. You can try restarting it following the steps described in this post.

After doing that, execute the following commands to verify everything works as expected:

$ ps aux | grep gonit
$ sudo cat /var/run/gonit.pid
$ sudo /opt/bitnami/ctlscript.sh status
$ sudo gonit status
$ sudo head -n10 /var/log/gonit.log

the instance cannot be reinstalled

Okay, so let’s try to focus on the services first, and then we can see how to tackle the permissions issue.

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart:

hello

bitnami@ip-172-31-23-49:~$ sudo gonit
Starting gonit daemon

bitnami@ip-172-31-23-49:~$ ps aux | grep gonit
root     28779  0.0  0.6 1081232 12640 ?       Ssl  10:52   0:00 gonit
bitnami  28830  0.0  0.0   6076   824 pts/0    S+   10:56   0:00 grep gonit

bitnami@ip-172-31-23-49:~$ sudo cat /var/run/gonit.pid
28779

bitnami@ip-172-31-23-49:~$ sudo /opt/bitnami/ctlscript.sh status
mariadb not running
nginx not running
php-fpm already running

bitnami@ip-172-31-23-49:~$ sudo gonit status

Uptime                         4m27s
Last Check                     2021-06-08 10:56:39.076323925 +0000 UTC m=+240.008527486
Next Check                     2021-06-08 10:58:39.076323925 +0000 UTC m=+360.008527486
Pid                            28779
Pid File                       /var/run/gonit.pid
Control File                   /etc/gonit/gonitrc
Socket File                    /var/run/gonit.sock
Log File                       /var/log/gonit.log
Process 'mariadb'
  monitoring status                        Not monitored

Process 'nginx'
  monitoring status                        Not monitored

Process 'php-fpm'
  status                                        Running
  pid                                              6567
  uptime                                          4m27s
  monitoring status                           monitored

bitnami@ip-172-31-23-49:~$ sudo head -n10 /var/log/gonit.log
time="2021-05-21T21:43:13Z" level=info msg="Performing checks"
time="2021-05-21T21:43:13Z" level=info msg="Performing process check php-fpm"
time="2021-05-21T21:43:13Z" level=info msg="Performing process check mariadb"
time="2021-05-21T21:43:13Z" level=info msg="Performing process check nginx"
time="2021-05-21T21:45:13Z" level=info msg="Performing checks"
time="2021-05-21T21:45:13Z" level=info msg="Performing process check php-fpm"
time="2021-05-21T21:45:13Z" level=info msg="Performing process check mariadb"
time="2021-05-21T21:45:13Z" level=info msg="Performing process check nginx"
time="2021-05-21T21:47:13Z" level=info msg="Performing checks"
time="2021-05-21T21:47:13Z" level=info msg="Performing process check php-fpm"

It seems gonit has started working again

Could you please try to restart the services now?

$ sudo /opt/bitnami/ctlscript.sh restart
$ sudo /opt/bitnami/ctlscript.sh start
$ sudo gonit status
$ ps aux |  grep 'apache\|mysql\|nginx\|/opt/bitnami\|php-fpm\|maria\|gonit'

If those commands succeed, it means the issue is solved :slightly_smiling_face:

Best regards,
Jose Antonio Carmona


Was my answer helpful? Click on :heart: