Problems after installing 8.0.29

[tarik sims]

Hello,

I did the upgrade to mysql 8.0.29 on ubuntu 20.04 about 2 weeks ago while before I was running the former version.
I noticed a huge increase in disk space utilisation while my data and accounts didn't really explode.
Then when I checked, I found > 140 binlog files in /var/lib/mysql while many had a size= 101MB!!!
Which explained round 13Gb consumed over the last few days.
I cleaned most with:
---------
mysql -uroot -ppassword
PURGE BINARY LOGS BEFORE '2022-05-24 23:00:00';
----------
but still have many produced in the last few days.

My Questions:

Q1) DO I really need these binlog files bearing in mind I don't have a replicated database??

I tried to add the following On my.cnf file
--------
# disable bin logs. they are only useful in replication mode
skip-log-bin
--------


Then, restarting mysql

mysql server just went down and couldn't start:
------------
# systemctl restart mysqld
Failed to restart mysqld.service: Unit mysqld.service not found.
# systemctl restart mysql
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.
# systemctl daemon-reload
# systemctl restart mysql
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.


# systemctl status mysql.service
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-05-26 02:26:43 CEST; 55s ago
Process: 33828 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)

May 26 02:26:43 website.com systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
May 26 02:26:43 website.com systemd[1]: Stopped MySQL Community Server.
May 26 02:26:43 website.com systemd[1]: mysql.service: Start request repeated too quickly.
May 26 02:26:43 website.com systemd[1]: mysql.service: Failed with result 'exit-code'.
May 26 02:26:43 website.com systemd[1]: Failed to start MySQL Community Server.
---------------------

=>/ Here I put back my.cnf file as it was before (removed skip-log-bin parameter)
/then restarted mysql successfully


---------------------------------------------
Q2: If yes I need them, how can I recycle these binlog files and put a limit on size and number of files produced by my database??

Q3: How to make mysql stop using these binlog files that are consuming my space on production and backup server + slowing my server??

Thank you!