Warning: session_start(): open(/tmp/sess_d27afbc13d217ae874050eb1a20a5395, O_RDWR) failed: No space left on device (28) in /var/www/html/inc/init.php on line 265

Warning: session_start(): Failed to read session data: files (path: ) in /var/www/html/inc/init.php on line 265

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/inc/init.php:265) in /var/www/html/inc/auth.php on line 432

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/inc/init.php:265) in /var/www/html/inc/actions.php on line 38
powerdns_crashing_-_binary_logging_not_possible [Ben's notes]

Ben's notes

Linux, Unix, network, radio...

User Tools

Site Tools


powerdns_crashing_-_binary_logging_not_possible

PowerDNS crashing - binary logging not possible

If PowerDNS is crashing with the following message

Exiting because communicator thread died with error: 
GSQLBackend unable to refresh domain_id 3: 
Failed to execute mysql_query, perhaps connection died? 
Err=1: Binary logging not possible. 
Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

You can fix this with:

 mysql> SET GLOBAL binlog_format = 'ROW';
 

The error arises only if the binary logging option, which is required for the replication, is turned on for the MySQL server.

powerdns_crashing_-_binary_logging_not_possible.txt · Last modified: 2021/10/09 15:14 by 127.0.0.1