MySql died on one of the node in a 3 node cluster

Hi Team,

Recently we encountered a situation where MySQL died on one of the node in a 3 node cluster. In the log, it shows that “Can’t generate a unique log-filename” but ample space is available on the disk to create the new files.

Here are the contents of the log:

2019-05-27T08:12:18.524860Z 3 [ERROR] Can’t generate a unique log-filename XXXX-bin.(1-999)

2019-05-27T08:12:18.525250Z 3 [ERROR] /usr/sbin/mysqld: Binary logging not possible. Message: Either disk is full or file system is read only while rotating the binlog. Aborting the server.
08:12:18 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

Can you suggest if something is wrong …

Apparently something went wrong with logrotate.

Are you able to rename the file using mysql user? You should be. If not:
[]Does the user for logrotate exist and is the password set correctly? For example on Debian the user is debian-sys-maint and the password should be set in /etc/mysql/debian.cnf.
]Does the file belong to mysql user and mysql group? Is it writeable by the owner? (if not, it should)