cagefs related info

Comments

• jokymic Barred

  August 2019

  @MikePT @Da_Mark can help ?
• MikePT Veteran

  August 2019

  @jokymic said:
  @MikePT @Da_Mark can help ?

  https://www.cloudlinux.com/forum/forum11/how-can-i-safely-exclude-all-mysql-databases-from-cagefs

  Seems to be just mounted, however, to confirm, you may want to open a ticket with CloudLinux, they're really fast getting back to us.
• jokymic Barred

  August 2019

  @MikePT said:

  @jokymic said:
  @MikePT @Da_Mark can help ?

  https://www.cloudlinux.com/forum/forum11/how-can-i-safely-exclude-all-mysql-databases-from-cagefs

  Seems to be just mounted, however, to confirm, you may want to open a ticket with CloudLinux, they're really fast getting back to us.

  already submitted ticket there waiting for their response
• MikePT Veteran

  August 2019

  jokymic said: already submitted ticket there waiting for their response

  That's still mounted, which seems normal, but, best to confirm.
• Daniel15 Veteran

  August 2019 edited August 2019

  It might just be regular MySQL binlogs (binary logs) rather than anything specific to CloudLinux. Binary logs are logs of all writes performed to your MySQL server. They're used for replication and for data recovery. See https://dev.mysql.com/doc/internals/en/binary-log-overview.html

  How many queries is your server running? A lot of writes will result in large binlogs. Check how many days of binlogs you're storing:

  mysql -u root -p
  

  then:

  # MySQL 8.0 and above
  SHOW VARIABLES LIKE 'binlog_expire_logs_seconds';
  
  # MySQL 5.x or MariaDB
  SHOW VARIABLES LIKE 'expire_logs_days';
  

  If you don't need older binlogs you can purge them: https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html
  eg this will delete all binlogs older than 24 hours:

  PURGE BINARY LOGS BEFORE (NOW() - INTERVAL 24 HOUR);
  

  You can also reduce the binlog_expire_logs_seconds or expire_logs_days setting to keep a smaller number of binlogs.

  Do not manually delete binlog files - Use the PURGE BINARY LOGS command.

  Thanked by 4ITLabs laoban raindog308 ViridWeb
• jokymic Barred

  August 2019

  mo> @Daniel15 said:

  It might just be regular MySQL binlogs (binary logs) rather than anything specific to CloudLinux. Binary logs are logs of all writes performed to your MySQL server. They're used for replication and for data recovery. See https://dev.mysql.com/doc/internals/en/binary-log-overview.html

  How many queries is your server running? A lot of writes will result in large binlogs. Check how many days of binlogs you're storing:

  mysql -u root -p
  

  then:

  # MySQL 8.0 and above
  SHOW VARIABLES LIKE 'binlog_expire_logs_seconds';
  
  # MySQL 5.x or MariaDB
  SHOW VARIABLES LIKE 'expire_logs_days';
  

  If you don't need older binlogs you can purge them: https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html
  eg this will delete all binlogs older than 24 hours:

  PURGE BINARY LOGS BEFORE (NOW() - INTERVAL 24 HOUR);
  

  You can also reduce the binlog_expire_logs_seconds or expire_logs_days setting to keep a smaller number of binlogs.

  Do not manually delete binlog files - Use the PURGE BINARY LOGS command.

  THANKS CL Team was solved this issue with the same guide
• Radi Host Rep, Veteran

  August 2019 edited August 2019

  Its not safe to just delete them.
• MikePT Veteran

  August 2019 edited August 2019

  @Radi said:
  Its not safe to just delete them.

  Definitely not. That is what PURGE BINARY LOGS is for. 🤘