Having issue restarting MYSQL service even after trying a few solution

Keywords: MySQL - AWS - Technical issue - Other
bnsupport ID: e641f7ea-3d37-5745-7745-73d02c98744a
Description:
Hello, I am having issue starting MYSQL server even after trying a few solution provided in this forum (my technical skills is still at beginner level)

I have followed the instruction on the support tool and generated the following:

e641f7ea-3d37-5745-7745-73d02c98744a

kindly advice and please help.

Hi @dextrolidin,

Can you check the following file:

cat /opt/bitnami/mysql/data/binlog.index

And check if the file paths written there exist on disk?

cd /opt/bitnami/mysql/
sudo cat data/binlog.index

And then:

sudo ls data | grep binlog.[0-9]

Can you share the output of both commands?

Regards,
Michiel

Hi @michiel

Thank you so much for your response, it is greatly appreciated. Thank you!

As per advice kindly find the followings:

bitnami@ip-172-31-5-218:~$ sudo cat /opt/bitnami/mysql/data/binlog.index
./binlog.000013
./binlog.000014


bitnami@ip-172-31-5-218:~$ cd /opt/bitnami/mysql
bitnami@ip-172-31-5-218:/opt/bitnami/mysql$ sudo cat data/binlog.index
./binlog.000013
./binlog.000014


bitnami@ip-172-31-5-218:/opt/bitnami/mysql$ sudo ls data | grep binlog.[0-9]
bitnami@ip-172-31-5-218:/opt/bitnami/mysql$ sudo ls data
auto.cnf                mysqld.log-20191216.gz  mysqld.log-20200419.gz  mysqld.log-20200719     mysqld.log-20201108.gz  mysqld.log-20210314.gz
binlog.index            mysqld.log-20191222.gz  mysqld.log-20200427.gz  mysqld.log-20200720     mysqld.log-20201116.gz  mysqld.log-20210322
bitnami_wordpress       mysqld.log-20191230.gz  mysqld.log-20200503.gz  mysqld.log-20200721.gz  mysqld.log-20201122.gz  mysqld.log-20210322.gz
ca-key.pem              mysqld.log-20200105.gz  mysqld.log-20200511.gz  mysqld.log-20200726.gz  mysqld.log-20201130.gz  mysqld.log-20210323
ca.pem                  mysqld.log-20200113.gz  mysqld.log-20200517.gz  mysqld.log-20200803.gz  mysqld.log-20201206.gz  mysqld.log-20210323.gz
client-cert.pem         mysqld.log-20200119.gz  mysqld.log-20200525.gz  mysqld.log-20200809.gz  mysqld.log-20201213.gz  mysqld.log-20210324.gz
client-key.pem          mysqld.log-20200126.gz  mysqld.log-20200531.gz  mysqld.log-20200817.gz  mysqld.log-20201221.gz  mysql.ibd
ib_buffer_pool          mysqld.log-20200203.gz  mysqld.log-20200608.gz  mysqld.log-20200823.gz  mysqld.log-20201227.gz  performance_schema
ibdata1                 mysqld.log-20200209.gz  mysqld.log-20200614.gz  mysqld.log-20200830.gz  mysqld.log-20210104.gz  private_key.pem
ib_logfile0             mysqld.log-20200216.gz  mysqld.log-20200622.gz  mysqld.log-20200907.gz  mysqld.log-20210110.gz  public_key.pem
ib_logfile1             mysqld.log-20200224.gz  mysqld.log-20200628.gz  mysqld.log-20200913.gz  mysqld.log-20210118.gz  server-cert.pem
#innodb_temp            mysqld.log-20200301.gz  mysqld.log-20200705.gz  mysqld.log-20200921.gz  mysqld.log-20210124.gz  server-key.pem
ip-172-31-5-218.err     mysqld.log-20200309.gz  mysqld.log-20200713     mysqld.log-20200927.gz  mysqld.log-20210201.gz  sys
mysql                   mysqld.log-20200315.gz  mysqld.log-20200714     mysqld.log-20201005.gz  mysqld.log-20210207.gz  undo_001
mysqld.log              mysqld.log-20200323.gz  mysqld.log-20200715     mysqld.log-20201011.gz  mysqld.log-20210214.gz  undo_002
mysqld.log-20191124.gz  mysqld.log-20200329.gz  mysqld.log-20200716     mysqld.log-20201019.gz  mysqld.log-20210222.gz
mysqld.log-20191202.gz  mysqld.log-20200405.gz  mysqld.log-20200717     mysqld.log-20201025.gz  mysqld.log-20210228.gz
mysqld.log-20191208.gz  mysqld.log-20200413.gz  mysqld.log-20200718     mysqld.log-20201102.gz  mysqld.log-20210308.gz
bitnami@ip-172-31-5-218:/opt/bitnami/mysql$ sudo ls data | grep binlog.
binlog.index

My apologies I am still learning ssh and my knowledge is very limited, hopefully what is did above is correct. Kindly advice. Thank you.

Hi @dextrolidin,

The binlog.index contains references to files that do not exist. Can you remove the following lines from the binlog.index:

sudo nano data/binlog.index 

And then remove these lines? (Leaving the file empty)

./binlog.000013
./binlog.000014
```

And then try to restart Apache?

Regards,
Michiel

Hi @michiel

Thank you so much for your advice but unfortunately it’s mysql not booting up please find the following:

bitnami@ip----:~$ sudo /opt/bitnami/ctlscript.sh status
php-fpm already running
apache already running
mysql not running
bitnami@ip----:~$ sudo /opt/bitnami/ctlscript.sh restart apache
Unmonitored apache
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd stopped
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80
Monitored apache
bitnami@ip----:~$ sudo /opt/bitnami/ctlscript.sh status
php-fpm already running
apache already running
mysql not running
bitnami@ip----:~$ sudo /opt/bitnami/ctlscript.sh restart
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd stopped
/opt/bitnami/php/scripts/ctl.sh : php-fpm stopped
/opt/bitnami/mysql/scripts/ctl.sh : mysql not running
/opt/bitnami/mysql/scripts/ctl.sh : mysql  could not be started
/opt/bitnami/php/scripts/ctl.sh : php-fpm started
Syntax OK
/opt/bitnami/apache2/scripts/ctl.sh : httpd started at port 80
bitnami@ip----:~$ sudo /opt/bitnami/ctlscript.sh status
php-fpm already running
apache already running
mysql not running

I have return the previous comment

bitnami@ip----:~$ sudo cat /opt/bitnami/mysql/data/binlog.index
bitnami@ip----:~$ cd /opt/bitnami/mysql
bitnami@ip----:/opt/bitnami/mysql$ sudo cat data/binlog.index
bitnami@ip----:/opt/bitnami/mysql$ sudo ls data
auto.cnf                mysqld.log-20191216.gz  mysqld.log-20200419.gz  mysqld.log-20200719     mysqld.log-20201108.gz  mysqld.log-20210314.gz
binlog.index            mysqld.log-20191222.gz  mysqld.log-20200427.gz  mysqld.log-20200720     mysqld.log-20201116.gz  mysqld.log-20210322
bitnami_wordpress       mysqld.log-20191230.gz  mysqld.log-20200503.gz  mysqld.log-20200721.gz  mysqld.log-20201122.gz  mysqld.log-20210322.gz
ca-key.pem              mysqld.log-20200105.gz  mysqld.log-20200511.gz  mysqld.log-20200726.gz  mysqld.log-20201130.gz  mysqld.log-20210323
ca.pem                  mysqld.log-20200113.gz  mysqld.log-20200517.gz  mysqld.log-20200803.gz  mysqld.log-20201206.gz  mysqld.log-20210323.gz
client-cert.pem         mysqld.log-20200119.gz  mysqld.log-20200525.gz  mysqld.log-20200809.gz  mysqld.log-20201213.gz  mysqld.log-20210324.gz
client-key.pem          mysqld.log-20200126.gz  mysqld.log-20200531.gz  mysqld.log-20200817.gz  mysqld.log-20201221.gz  mysql.ibd
ib_buffer_pool          mysqld.log-20200203.gz  mysqld.log-20200608.gz  mysqld.log-20200823.gz  mysqld.log-20201227.gz  performance_schema
ibdata1                 mysqld.log-20200209.gz  mysqld.log-20200614.gz  mysqld.log-20200830.gz  mysqld.log-20210104.gz  private_key.pem
ib_logfile0             mysqld.log-20200216.gz  mysqld.log-20200622.gz  mysqld.log-20200907.gz  mysqld.log-20210110.gz  public_key.pem
ib_logfile1             mysqld.log-20200224.gz  mysqld.log-20200628.gz  mysqld.log-20200913.gz  mysqld.log-20210118.gz  server-cert.pem
#innodb_temp            mysqld.log-20200301.gz  mysqld.log-20200705.gz  mysqld.log-20200921.gz  mysqld.log-20210124.gz  server-key.pem
ip----.err     mysqld.log-20200309.gz  mysqld.log-20200713     mysqld.log-20200927.gz  mysqld.log-20210201.gz  sys
mysql                   mysqld.log-20200315.gz  mysqld.log-20200714     mysqld.log-20201005.gz  mysqld.log-20210207.gz  undo_001
mysqld.log              mysqld.log-20200323.gz  mysqld.log-20200715     mysqld.log-20201011.gz  mysqld.log-20210214.gz  undo_002
mysqld.log-20191124.gz  mysqld.log-20200329.gz  mysqld.log-20200716     mysqld.log-20201019.gz  mysqld.log-20210222.gz
mysqld.log-20191202.gz  mysqld.log-20200405.gz  mysqld.log-20200717     mysqld.log-20201025.gz  mysqld.log-20210228.gz
mysqld.log-20191208.gz  mysqld.log-20200413.gz  mysqld.log-20200718     mysqld.log-20201102.gz  mysqld.log-20210308.gz

not sure if it helpful, I have already run the support tool again and generated another ticket.

e32f72c9-f6b1-a32c-ef79-dce2fad7488c

kindly advice.

Hi @dextrolidin,

Can you try starting it with the following command and check the output?

sudo /opt/bitnami/mysql/bin/mysqld_safe --pid-file=/opt/bitnami/mysql/data/mysqld.pid --datadir=/opt/bitnami/mysql/data  --lower_case_table_names=1 

Regards,
Michiel

Hi @michiel

Please find the following:

bitnami@ip--:~$ sudo /opt/bitnami/mysql/bin/mysqld_safe --pid-file=/opt/bitnami/mysql/data/mysqld.pid --datadir=/opt/bitnami/mysql/data  --lower_case_table_names=1
2021-03-26T10:46:28.978583Z mysqld_safe Logging to '/opt/bitnami/mysql/data/ip-1                                                                             72-31-5-218.err'.
2021-03-26T10:46:28.996722Z mysqld_safe Starting mysqld daemon with databases fr                                                                             om /opt/bitnami/mysql/data
2021-03-26T10:46:29.509603Z mysqld_safe mysqld from pid file /opt/bitnami/mysql/                                                                             data/mysqld.pid ended 

Kindly advice please.
Thank you.

Hi @dextrolidin,

Can you check the errors in /opt/bitnami/mysql/data/ip-1 72-31-5-218.err?

sudo nano /opt/bitnami/mysql/data/ip-1 72-31-5-218.err

Regards,
Michiel

Hi @michiel

Kindly find the following error

2019-11-18T11:06:27.081993Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use$
2019-11-18T11:06:27.082113Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 3239
2019-11-18T11:06:27.709696Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-11-18T11:06:27.766331Z 0 [System] [MY-010931] [Server] /opt/bitnami/mysql/bin/mysqld.bin: ready for connections. Version: ‘8.0.18’ socket: '/opt/bitna$
2019-11-18T11:06:27.770821Z 9 [System] [MY-013172] [Server] Received SHUTDOWN from user root. Shutting down mysqld (Version: 8.0.18).
2019-11-18T11:06:29.185480Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - G$

I received the above error, try bugging it but still can’t seems to boot mysql back online.

kindly advice. Thank you.

Hi @dextrolidin,

Can you tell me the output of the following command:

sudo cat /opt/bitnami/mysql/data/binlog.index

Can you also run the bnsupport tool again and send me the output ID?

Regards,
Michiel

Hi @michiel

I have run the command as per suggested but the system returned nothing. I have check my binlog.index’s file, it’s left empty as per advice previously.

here is the new support code ae515527-4cde-7cff-f0f6-ff9cd263df85

Kindly advice. Thank you.

Hi @dextrolidin,

From the commands you ran in your previous messages, it seems that you can start the database manually. Did you try to start it using the Bitnami scripts again?

sudo /opt/bitnami/ctlscript.sh start mysql
sudo tail -n 30 /opt/bitnami/mysql/data/mysqld.log

Hi @jota

Thank you so much for your suggestion, I did previous tried it, I even ran a full restart and restart the entire aws instance. But I received the following error:

bitnami@ip:~$ sudo /opt/bitnami/ctlscript.sh start mysql
/opt/bitnami/mysql/scripts/ctl.sh : mysql could not be started
Monitored mysql

Kindly advice please.

Hi @dextrolidin,

Can you run the two commands from Jota’s message and share the output? Apart from that, I checked your bnsupport bundle and your server is running out of free memory, so new processes can’t be started

-----------------------------------
Display amount of free and used memory in the system
-----------------------------------
Running: free -m
In: /opt/bitnami

Output:

              total        used        free      shared  buff/cache   available
Mem:            990         351          70          44         568         377
Swap:           634          22         611

Can you try using a bigger instance?

https://docs.bitnami.com/aws/faq/administration/change-server-type/

Hi @gongomgra

Thank you so much for your advice I have tried upgrading the instance from micro to small and the mysql still can’t be booted, I tried restarting the instance again after but still no luck.

as for the comment kindly find the following result:

bitnami@ip-172-31-5-218:~$ sudo /opt/bitnami/ctlscript.sh start mysql
/opt/bitnami/mysql/scripts/ctl.sh : mysql could not be started
Monitored mysql

sudo tail -n 30 /opt/bitnami/mysql/data/mysqld.log this comment seems to return nothing… I am not too sure if I did it correctly.

I have also generated a new support ticket

8e4f5f68-dbf5-8891-02da-6c1088dba1df

hope this will help provide some clue… Kindly advice. Thank you

Hello @dextrolidin,

Indeed, it seems your mysqld.log file is empty. The last log in a .gz file, /opt/bitnami/mysql/data/mysqld.log-20210328.gz, could you unzip said file and run the tail - 30 command for the extracted log file?

Regards,
Francisco de Paz

Hi @fdepaz

Thank you for your advice, I have done as adviced, kindly find the following:

2021-03-24T06:27:32.707976Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T06:27:32.708123Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 6885
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T06:27:33.614580Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T06:27:33.614721Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T06:27:33.614959Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T06:27:34.917509Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T06:29:52.386713Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T06:29:52.386840Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 7397
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T06:29:52.900165Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T06:29:52.900296Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T06:29:52.900502Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T06:29:53.999715Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T06:31:52.354050Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T06:31:52.354178Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 7937
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T06:31:52.819131Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T06:31:52.819290Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T06:31:52.819496Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T06:31:53.945463Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T06:33:52.348019Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T06:33:52.348145Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 8409
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T06:33:52.809206Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T06:33:52.809337Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T06:33:52.809543Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T06:33:53.936840Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T07:00:10.496894Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T07:00:10.500138Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 1864
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T07:00:11.474547Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T07:00:11.474689Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T07:00:11.474923Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T07:00:12.780487Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T07:02:32.900158Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T07:02:32.900725Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 2633
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T07:02:33.762890Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T07:02:33.763050Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T07:02:33.763258Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T07:02:35.051891Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T07:04:32.573644Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T07:04:32.573769Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 3081
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T07:04:33.063090Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T07:04:33.063228Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T07:04:33.063484Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T07:04:34.157513Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T07:06:32.572675Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T07:06:32.572801Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 3593
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T07:06:33.041222Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T07:06:33.041360Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T07:06:33.041596Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T07:06:34.158410Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T07:08:32.570352Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T07:08:32.570478Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 4036
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T07:08:33.039383Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T07:08:33.039535Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T07:08:33.039742Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T07:08:34.155778Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.
2021-03-24T07:10:32.571795Z 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.
2021-03-24T07:10:32.571926Z 0 [System] [MY-010116] [Server] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 8.0.18) starting as process 4474
mysqld.bin: File ‘./binlog.000014’ not found (OS errno 2 - No such file or directory)
2021-03-24T07:10:33.038977Z 0 [ERROR] [MY-010958] [Server] Could not open log file.
2021-03-24T07:10:33.039109Z 0 [ERROR] [MY-010041] [Server] Can’t init tc log
2021-03-24T07:10:33.039350Z 0 [ERROR] [MY-010119] [Server] Aborting
2021-03-24T07:10:34.158266Z 0 [System] [MY-010910] [Server] /opt/bitnami/mysql/bin/mysqld.bin: Shutdown complete (mysqld 8.0.18) MySQL Community Server - GPL.

I have also generated another support ticket d60d37ec-70a7-b381-f2cb-f22c6e04755d

Kindly advice. Thank you

Hi @dextrolidin,

The MySQL ctlscript.sh seems to be running:

ps aux | grep mysql | grep -v grep

Can you stop that process?

    ps aux | grep mysql | grep -v grep | awk '{print $2}' | xargs kill

And then start it again?

sudo /opt/bitnami/ctlscript.sh start mysql

If it doesn’t start, run the following command that shows the last modified mysql log file:

sudo find /opt/APPNAME/mysql/data/ -type f -name "*mysqld.log*" -printf "%AD %p\n" | sort -k1.8n -k1.1nr -k1

Unzip it and check the latest messages.

Regards,
Michiel

Hi @michiel

Thank you so much for your suggestion I have tried them and returned the following:

bitnami@:~$ ps aux | grep mysql | grep -v grep | awk ‘{print $2}’ | xargs kill

Usage:
kill [options] […]

Options:
[…] send signal to every listed
-, -s, --signal
specify the to be sent
-l, --list=[] list all signal names, or convert one to a name
-L, --table list all signal names in a nice table

-h, --help display this help and exit
-V, --version output version information and exit

For more details see kill(1).
bitnami@:~$ sudo /opt/bitnami/ctlscript.sh start mysql

/opt/bitnami/mysql/scripts/ctl.sh : mysql could not be started
Monitored mysql

as for

sudo find /opt/wordpresspro-5.7-1/mysql/data/ -type f -name “mysqld.log” -printf “%AD %p\n” | sort -k1.8n -k1.1nr -k1

I can’t seem to find the path containing “wordpresspro-5.7-1”…kindly advice on this

Hi @dextrolidin,

Sorry, I gave the wrong example, you need to run:

sudo find /opt/wordpress/mysql/data/ -type f -name "*mysqld.log*" -printf "%AD %p\n" | sort -k1.8n -k1.1nr -k1

The command to stop mysql processes should be:

ps aux | grep mysql | grep -v grep | awk '{print $2}' | xargs sudo kill -9

Regards,

Michiel