I have configured a MariaDB Galera cluster with three nodes. The master node and one slave-master node is up and running, but the third node just won't run. The system specs and cluster config are the same on all three nodes (except changing the wsrep_node_address and the wsrep_node_name on each node). Here is the config for the nodes (wsrep_node_address and the wsrep_node_name are unique on each node): [galera] binlog_format=ROW default-storage-engine=innodb innodb_autoinc_lock_mode=2 innodb_locks_unsafe_for_binlog=1 query_cache_size=0 query_cache_type=0 bind-address=0.0.0.0 datadir=/var/lib/mysql innodb_log_file_size=100M innodb_file_per_table innodb_flush_log_at_trx_commit=2 wsrep_provider=/usr/lib64/galera/libgalera_smm.so wsrep_cluster_address="gcomm://192.168.1.111,192.168.1.112,192.168.1.113" wsrep_cluster_name='galera_cluster' wsrep_node_address='192.168.9.113' wsrep_node_name='george-db4' wsrep_sst_method=xtrabackup wsrep_sst_auth=username:password It seems like MariaDb does not like the config wsrep_cluster_address="gcomm://192.168.1.111,192.168.1.112,192.168.1.113" When I comment it out MariaDB restarts just fine. When I uncomment it, it just displays this message: Starting MySQL................................... ERROR! ERROR! Failed to restart server. When I change the wsrep_cluster_address to just wsrep_cluster_address="gcomm:// MariaDb runs with no problem. So I am not sure why it is having problems with assigning the IP address (even if it works fine on the other two nodes). I have tried emptying the galera.cache file, I have tried re-installing the cluster, I have tried rebooting the machine etc. and nothing works so far. I even truncated the log file /var/lib/mysql/db1.err with the command truncate logfile --size 0 (now I cannot figure out how to get my log file back with space as I realized I would need the log file).

I am collecting errors data using the error_reported event and saving the data on XEL files. The problem is that there are hundreds of thousands of errors over there and querying them can take a lot of time. One option is to prevent errors from being logged twice if they happened on the same object in the same timestamp. I really don't think the second option is possible. Second option is to index the file in a way that it will be quick to filter errors by the error text and the object that caused them. So far I thought of creating a separate process that will run in the background and writes filtered values from the files to an indexed table, but its a bad solution. That process would need maintenance and could be expensive on IO resources. So far I didn't find a way to solve it on the extended event level. Does anyone have a better idea?

This threads follows a previous one, given at this URL: https://dba.stackexchange.com/questions/285442/mysql-8-0-20-master-replica-scheme-increasing-delay-between-source-and-replic Replica Server has been configured this way, which ensures a fast replication: innodb_flush_method = O_DIRECT SET GLOBAL sync_binlog = 0; SET GLOBAL innodb_flush_log_at_trx_commit = 2; The Source binlogs are in ROW format for instance. As I understand, we cannot change to STATEMENT as it is already a Replication process running, and without restarting Source database, which is touchy. **An I right?** However, the replication process sometimes falls in error, because of inexisting records: `Last_SQL_Error: Could not execute Update_rows event on table levelup.videos; Can't find record in 'videos', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log binlog.001822, end_log_pos 328518491` We checked in source Binlog file, without finding anything to show us the incorrect record nor the source of the error. **Any help to decrypt the logs would be very appreciated. Thanks in advance** Command executed on Master :

--base64-output=decode-rows --start-position=328517915 --stop-position=328518679 binlog.001822 --verbose

Result :

/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 156
#210217  9:32:50 server id 1  end_log_pos 125 CRC32 0x74769bdd  Start: binlog v 4, server v 8.0.22-13 created 210217  9:32:50
# at 328517915
#210217  9:41:23 server id 1  end_log_pos 328517994 CRC32 0xa92a39bf    Anonymous_GTID  last_committed=628870   sequence_number=628871  rbr_only=yes    original_committed_timestamp=1613551283843458   immediate_commit_timestamp=1613551283843458     transaction_length=607
/*!50718 SET TRANSACTION ISOLATION LEVEL READ COMMITTED*//*!*/;
# original_commit_timestamp=1613551283843458 (2021-02-17 09:41:23.843458 CET)
# immediate_commit_timestamp=1613551283843458 (2021-02-17 09:41:23.843458 CET)
/*!80001 SET @@session.original_commit_timestamp=1613551283843458*//*!*/;
/*!80014 SET @@session.original_server_version=80022*//*!*/;
/*!80014 SET @@session.immediate_server_version=80022*//*!*/;
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 328517994
#210217  9:41:23 server id 1  end_log_pos 328518081 CRC32 0x56149f5b    Query   thread_id=219241        exec_time=0     error_code=0
SET TIMESTAMP=1613551283/*!*/;
SET @@session.pseudo_thread_id=219241/*!*/;
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1/*!*/;
SET @@session.sql_mode=1174405120/*!*/;
SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;
/*!\C utf8mb4 *//*!*/;
SET @@session.character_set_client=255,@@session.collation_connection=255,@@session.collation_server=255/*!*/;
SET @@session.lc_time_names=0/*!*/;
SET @@session.collation_database=DEFAULT/*!*/;
/*!80011 SET @@session.default_collation_for_utf8mb4=255*//*!*/;
BEGIN
/*!*/;
# at 328518081
#210217  9:41:23 server id 1  end_log_pos 328518171 CRC32 0x40249bce    Table_map: XXX.videos mapped to number 227
# at 328518171
#210217  9:41:23 server id 1  end_log_pos 328518491 CRC32 0x8a73f2c2    Update_rows: table id 227 flags: STMT_END_F
### UPDATE XXX.videos
### WHERE
###   @1=229814401
###   @2=9
###   @3='6801549427720504325'
###   @4='6929519055464353030'
###   @5='2021:02:15'
###   @6='TAG these teammates 😭 #FamilyDay'
###   @7=35
###   @8=NULL
###   @9=NULL
###   @10=1300000
###   @11=8101
###   @12=306600
###   @13=NULL
###   @14=26100
###   @15=NULL
###   @16='0000:00:00'
### SET
###   @1=229814401
###   @2=9
###   @3='6801549427720504325'
###   @4='6929519055464353030'
###   @5='2021:02:15'
###   @6='TAG these teammates 😭 #FamilyDay'
###   @7=35
###   @8=''
###   @9=3
###   @10=1300000
###   @11=8101
###   @12=306600
###   @13=NULL
###   @14=26100
###   @15=NULL
###   @16='0000:00:00'
# at 328518491
#210217  9:41:23 server id 1  end_log_pos 328518522 CRC32 0x7b25222b    Xid = 3758209563
COMMIT/*!*/;
# at 328518522
#210217  9:41:23 server id 1  end_log_pos 328518601 CRC32 0x0342fc32    Anonymous_GTID  last_committed=628871   sequence_number=628872  rbr_only=yes    original_committed_timestamp=1613551283854427   immediate_commit_timestamp=1613551283854427     transaction_length=473
/*!50718 SET TRANSACTION ISOLATION LEVEL READ COMMITTED*//*!*/;
# original_commit_timestamp=1613551283854427 (2021-02-17 09:41:23.854427 CET)
# immediate_commit_timestamp=1613551283854427 (2021-02-17 09:41:23.854427 CET)
/*!80001 SET @@session.original_commit_timestamp=1613551283854427*//*!*/;
/*!80014 SET @@session.original_server_version=80022*//*!*/;
/*!80014 SET @@session.immediate_server_version=80022*//*!*/;
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 328518601
#210217  9:41:23 server id 1  end_log_pos 328518679 CRC32 0xac04ba69    Query   thread_id=49970 exec_time=0     error_code=0
SET TIMESTAMP=1613551283/*!*/;
BEGIN
/*!*/;
ROLLBACK /* added by mysqlbinlog */ /*!*/;
SET @@SESSION.GTID_NEXT= 'AUTOMATIC' /* added by mysqlbinlog */ /*!*/;
DELIMITER ;
# End of log file
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/;

I recently migrated a SQL Server 2017 TDE database to SQL Server 2019 CU4. I was browsing the Error Log and noticed intermittent messages about An error occurred while processing log encryption. The process was recovered automatically. No user action is required. These messages are always preceded by Error: 1222, Severity: 16, State: 55. And Lock request time out period exceeded. I found [FIX: TDE encrypted Databases go in suspect state during the recovery phase when you restart SQL Server](https://support.microsoft.com/en-us/help/3197631) , where it discusses a fix that has been back-ported to previous versions of SQL Server. From that post > Assume that you have a Transparent Data Encryption (TDE) encrypted > database on an instance of Microsoft SQL Server. When you restart the > instance of SQL Server, you may receive a lock time-out error that > resembles the following: Starting up database . Error: > 1222, Severity: 16, State: 55. Lock request time out period exceeded. > Error: 9016, Severity: 21, State: 7. An error occurred while > processing the log for database . The log block could > not be decrypted. Then, the database will go in a suspect state.You > can get the database back online by using Emergency Mode. You won't > encounter corruption. I'm not in the situation where my instance is being restarted, but it seems this _fix_ is similar to what I am experiencing. While I appreciate the process being automatically recovered, I'm concerned why the error is even showing up in the error log. I also have an almost identical instance in the same migration scenario from SQL Server 2017 to 2019 that is NOT experiencing these errors.

I'm trying to remove some data to get some extra free space, but running the "DELETE FROM table ..." query gives me this error: > Error Code: 3019 Undo Log error: No more space left over in system > tablespace for allocating UNDO log pages. Please add new data file to > the tablespace or check if filesystem is full or enable auto-extension > for the tablespace I found this: https://stackoverflow.com/questions/42628687/undo-log-error-no-more-space-left-over-in-system-tablespace-for-allocating-undo The recommend to run this query: ALTER UNDO TABLESPACE tablespace_name SET INACTIVE; But it gives me an Error Code: 1064 MySQL version: 5.7.31

I'm getting the error below in my MySQL log file. [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. How do I turn it off? Does turning the error off have an impact on my database? I'm on MySQL 5.7.14. My.ini contains this: sql-mode="STRICT_ALL_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER"

How do you change the default location of the log_error file? If you point it to a new path, will it automatically move the existing file? Or will it create a new file, and the original file can be deleted? Software is installed on Windows. Also, how do you change the default location of the innodb log files?

My postgresql.conf contains this: log_destination = 'csvlog' logging_collector = on log_directory = 'C:\\Users\\John Doe\\Documents\\PostgreSQL logs' log_filename = 'PG_%Y-%m-%d_%H;%M;%S' log_rotation_age = 1min log_rotation_size = 0 log_truncate_on_rotation = on log_min_error_statement = 'info' This makes PG log its errors to CSV files in my custom dir. Then, I have a constantly running script which looks for new files in that dir, and if it finds any, COPYies it into a custom database table (as described/recommended in the manual) and deletes the file that was successfully added. It doesn't touch the currently active log file. My table only has one custom column, a boolean called "unimportant", which I set depending on whether I think the error is important or not, so that I can hide the noise in various views and statistics. Since PostgreSQL does not provide any fields such as "file path" or "line number", I'm at a total loss as to what caused the various logged errors. The only thing I have to go by is the application_name, which is uselessly limited due to being 64 characters maximum and no Unicode, even preventing me from abusing this field to, for example, set it to the relevant file path. But even if it were possible, I wouldn't want to do that, since application_name is supposed to be the application name and nothing else. (But again, it doesn't matter since the path would be too long and contain non-ANSI characters anyway.) I've thought long and hard about this, but I just can't figure out a way to make me able to know where exactly the error occurred. Application (PHP) errors will include the relevant location, but these errors are not always logged (I'm unsure why). Here are some examples of errors which don't trigger PHP errors but are logged by PostgreSQL: * there is no transaction in progress for the query COMMIT in application_name whatever123. Okay? Which script did it? And which line? * there is already a transaction in progress for the query BEGIN in application_name whatever123. Okay? Which script did it? And which line? * current transaction is aborted, commands ignored until end of transaction block and deadlock detected ones at least specify what query caused it, but again, I'd have to hunt it down manually by searching for parts of the query. Usually, I don't bother, or am unable to because the query was constructed in code in an unsearchable way. Is there really no way to solve this? Any idea why the above errors aren't considered "real" errors to PHP (or rather, the pg_*/pglib functions)? And can I control that somehow?

DESCRIPTION: SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: 10.XXX.XX.XX} ***The client address is different on different occasion Can i refer this problem to my network admin? is this a network issue or a sql server issue. Is there any other way other then changing the registry ? Can i safely ignore this error ?

I have a process which starts and stops Extended Event sessions in order to transfer data from event files into SQL tables. On a SQL Server 2022 RTM server, I see many lines written to the log files by this process: I would like the starting and stopping of XE sessions to not be written to the log file because my log files are now overwhelmingly filled with these entries. This behavior does not occur on a Microsoft SQL Server 2019 (RTM-CU22-GDR) instance. How can I prevent SQL Server from logging the starting and stopping of XE sessions to the server log files?

I've had a varied career, but I have **never** found relevant information in the SQL Server Error Log. Under what circumstances should I consider inspecting it?

If you have ever played around with the error_reported Extended Event, then it becomes very obvious that the SQL Server Error Log only logs a tiny fraction of the errors that are thrown by code running on your server. Indeed, many things that it logs are explicit about not even being errors. So, broadly speaking, what determines if an error is worthy of inclusion in the Error Log? Is there some list of errors that qualify? Or is it determined based on some criteria?

SharePoint switches OFF and ON options like AUTO_UPDATE_STATISTICS, AUTO_UPDATE_STATISTICS_ASYNC, AUTO_CREATE_STATISTICS, INCREMENTAL on SharePoint databases daily at 12 AM and that generates lots of noise in SQL Server error log. What action should I take(Either in SQL Server or in SharePoint) to keep the error log clean?

A few days ago, in one of my servers, I had the following alert pop out: > A read operation on a large object failed while sending data to the > client. A common cause for this is if the application is running in > READ UNCOMMITTED isolation level. This connection will be terminated. However, it has only happened once, and I could not deal with it there and then. where/how could I search for more information as to what was the primary cause(s) that triggered this alert/message? **Edit** Actually this question could be something down these lines: what should I query at the time the alert was fired, to add more information to the email the DBAs get?

I recently upgraded my Debian 10 server running MySQL 5.7 to Debian 11 and MariaDB 10.3. That upgrade went smoothly. I then decided to upgrade to Debian 12 and MariaDB 10.11. While performing that upgrade, I encountered an issue with mariadb-server:

Setting up mariadb-server (1:10.11.4-1~deb12u1) ...
dpkg: error processing package mariadb-server (--configure):
 installed mariadb-server package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Errors were encountered while processing:
 mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

I re-ran apt install mariadb-server and got the same error. I then ran apt install -f and dpkg --configure -a but they both returned the same error as well. Next, I ran apt purge mariadb-server and then tried to reinstall with apt install mariadb-server and got the same error as above. It appears that the installation itself succeedes as I was able to run systemctl start mariadb so that I could then run mariadb-upgrade but that failed part of the way through with:

Phase 4/7: Running 'mysql_fix_privilege_tables'
ERROR 1408 (HY000) at line 429: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
FATAL ERROR: Upgrade failed

Since mariadb_upgrade is run as part of the installation process, I'm assuming this is what is breaking but I don't know that for sure. Checking /var/log/mysql/error.log, I see the following:

2024-01-15 15:29:32 0 [Note] Starting MariaDB 10.11.4-MariaDB-1~deb12u1 source revision  as process 189707
2024-01-15 15:29:32 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-01-15 15:29:32 0 [Note] InnoDB: Using transactional memory
2024-01-15 15:29:32 0 [Note] InnoDB: Number of transaction pools: 1
2024-01-15 15:29:32 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-01-15 15:29:32 0 [Note] InnoDB: Using liburing
2024-01-15 15:29:32 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000GiB, chunk size = 4.000GiB
2024-01-15 15:29:33 0 [Note] InnoDB: Completed initialization of buffer pool
2024-01-15 15:29:33 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-01-15 15:29:34 0 [Note] InnoDB: 128 rollback segments are active.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Cannot open datafile for read-only: './run_dev/#sql2-7c6-43166.ibd' OS error: 71
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Could not find a valid tablespace file for run_dev/#sql2-7c6-43166. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/  for how to resolve the issue.
2024-01-15 15:29:34 0 [Warning] InnoDB: Ignoring tablespace for run_dev/#sql2-7c6-43166 because it could not be opened.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Cannot open datafile for read-only: './tmp/#sql2fb_6c47_15.ibd' OS error: 71
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Could not find a valid tablespace file for tmp/#sql2fb_6c47_15. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/  for how to resolve the issue.
2024-01-15 15:29:34 0 [Warning] InnoDB: Ignoring tablespace for tmp/#sql2fb_6c47_15 because it could not be opened.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Cannot open datafile for read-only: './tmp/#sql70b1_76eb_0.ibd' OS error: 71
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Could not find a valid tablespace file for tmp/#sql70b1_76eb_0. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/  for how to resolve the issue.
2024-01-15 15:29:34 0 [Warning] InnoDB: Ignoring tablespace for tmp/#sql70b1_76eb_0 because it could not be opened.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Cannot open datafile for read-only: './tmp/#sql70b1_76eb_1.ibd' OS error: 71
2024-01-15 15:29:34 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2024-01-15 15:29:34 0 [ERROR] InnoDB: Error number 2 means 'No such file or directory'
2024-01-15 15:29:34 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 
2024-01-15 15:29:34 0 [ERROR] InnoDB: Could not find a valid tablespace file for tmp/#sql70b1_76eb_1. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/  for how to resolve the issue.
2024-01-15 15:29:34 0 [Warning] InnoDB: Ignoring tablespace for tmp/#sql70b1_76eb_1 because it could not be opened.
2024-01-15 15:29:34 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-01-15 15:29:34 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-01-15 15:29:34 0 [Note] InnoDB: log sequence number 522161950055957; transaction id 14113259426
2024-01-15 15:29:34 0 [Note] InnoDB: Loading buffer pool(s) from /sas/mysql/ib_buffer_pool
2024-01-15 15:29:34 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-buffer-pool-instances' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
2024-01-15 15:29:34 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-01-15 15:29:34 0 [Note] Server socket created on IP: '::'.
2024-01-15 15:29:34 0 [ERROR] Incorrect definition of table mysql.event: expected the type of column 'time_zone' at position 17 to have character set 'latin1' but found character set 'utf8mb3'.
2024-01-15 15:29:34 0 [ERROR] mariadbd: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2024-01-15 15:29:34 0 [Note] /usr/sbin/mariadbd: ready for connections.

1. How do I get mariadb_upgrade / the maraidb-server installation working? 2. What do I do about the ignored tablespaces mentioned in the error log? Thanks!

I will be straightforward and put my question before I add any other information, as I want to keep it objective and to the point. the question is: **How to find out why the replication services are stopping?** I thought that this info would be stored in the distribution database like this : select * from distribution.dbo.msrepl_errors (nolock) where id = 0 But this was not the case. I am coming across some errors on my transactional replication. that I could clearly see: > Source: Microsoft.SqlServer.Management.Sdk.Sfc Target Site: Void > FilterException(System.Exception) Message: Exception of type > 'System.OutOfMemoryException' was thrown. Stack: at > Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException.FilterException(Exception > e) at > Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object > connectionInfo, Request request) at > Microsoft.SqlServer.Management.Smo.ExecutionManager.GetEnumeratorData(Request > req) at > Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetDbCollation(String > dbname) at > Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetDbComparer(Boolean > inServer) at > Microsoft.SqlServer.Management.Smo.SqlSmoObject.InitializeStringComparer() > at > Microsoft.SqlServer.Management.Smo.AbstractCollectionBase.get_StringComparer() > at > Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.InitInnerCollection() > at > Microsoft.SqlServer.Management.Smo.SmoCollectionBase.GetObjectByKey(ObjectKeyBase > key) at > Microsoft.SqlServer.Management.Smo.DatabaseCollection.get_Item(String > name) at > Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.PrefetchObjects(ObjectPrefetchControl[] > objectPrefetchControls) at > Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoPrefetchWithRetry() > at > Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting() > at > Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting() > at > Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot() > at > Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun() > at Microsoft.SqlServer.Replication.AgentCore.Run() while running a snapshot: > memory mapped file write failed and previous to that: > System.OutOfMemoryException and also a few of these: > Error messages: The replication agent has not logged a progress > message in 10 minutes. This might indicate an unresponsive agent or > high system activity. Verify that records are being replicated to the > destination and that connections to the Subscriber, Publisher, and > Distributor are still active. > Error messages: ⦁ Message: memory mapped file write failed Stack: > at > Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* > pNativeConnectionWrapper) at > Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String > strBcpObjectName, String strBcpObjectOwner, String > strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, > String strLoadOrderingHint, String strWhereClause, Boolean > useTableLockHint, Int32 bcpFileFormatVersion) at > Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem > workItem) at > Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc() > at > Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() > (Source: MSSQLServer, Error number: 0) Get help: http://help/0 and the previous error message: > Error messages: ⦁ Source: Microsoft.SqlServer.Management.Sdk.Sfc > Target Site: Void FilterException(System.Exception) Message: Exception > of type 'System.OutOfMemoryException' was thrown. Stack: at > Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException.FilterException(Exception > e) at > Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object > connectionInfo, Request request) at > Microsoft.SqlServer.Management.Smo.ExecutionManager.GetEnumeratorData(Request > req) at > Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetDbCollation(String > dbname) at > Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetDbComparer(Boolean > inServer) at > Microsoft.SqlServer.Management.Smo.SqlSmoObject.InitializeStringComparer() > at > Microsoft.SqlServer.Management.Smo.AbstractCollectionBase.get_StringComparer() > at > Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.InitInnerCollection() > at > Microsoft.SqlServer.Management.Smo.SmoCollectionBase.GetObjectByKey(ObjectKeyBase > key) at > Microsoft.SqlServer.Management.Smo.DatabaseCollection.get_Item(String > name) at > Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.PrefetchObjects(ObjectPrefetchControl[] > objectPrefetchControls) at > Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoPrefetchWithRetry() > at > Microsoft.SqlServer.Replication.Snapshot.SmoScriptingManager.DoScripting() > at > Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.DoScripting() > at > Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot() > at > Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun() > at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: > Microsoft.SqlServer.Management.Sdk.Sfc, Error number: 0) Get help: > http://help/0 and while troubleshooting it it turned out that the computer is really out of memory

I'm running SQL Server 2014 on a VPS with 150Gb SSD. Today, I found that my hard disk was full 100% and there's a very large file from SQL Server Error log that was 45.7Gb. I tried manually delete the file, but Windows says the disk space doesn't change at all. How can I delete this file? I don't need the error log data, it's fine for me to delete it and regain the disk space. I checked the file; it is so large due to failed login attempts. But here I want to delete the file first, these following commands didn't delete it, could u please give me some ideas?

Can you help me understand what was happen on MariaDB server. I wasn't able to connect to this server because there was 'Too many connections'. This is one of our slave in replication so non of main server changes were not applied on this replica. I had to kill (-9) MariaDB server. I saw in error logs:

BUFFER POOL AND MEMORY
----------------------
InnoDB: ###### Diagnostic info printed to the standard error stream
2023-06-28 13:15:46 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789684688640 has waited at trx0rseg.ic line 50 for 272.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887cd1098 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file not yet reserved line 0
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:15:46 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789781440256 has waited at trx0undo.ic line 164 for 271.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887d195a8 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file trx0undo.ic line 180
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:15:46 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789808133888 has waited at srv0srv.cc line 2096 for 250.00 seconds the semaphore:
X-lock on RW-latch at 0x7f28d1cbf440 created in file dict0dict.cc line 1107
a writer (thread id 139789701474048) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0purge.cc line 853
Last time write locked in file dict0stats.cc line 2457
2023-06-28 13:15:46 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789701474048 has waited at trx0trx.cc line 1157 for 251.00 seconds the semaphore:
Mutex at 0x7f28d1cc7fd8, Mutex REDO_RSEG created trx0rseg.cc:168, lock var 2


2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789782349568 has waited at trx0rseg.ic line 50 for 176.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887cd13c8 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file not yet reserved line 0
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789709866752 has waited at dict0dict.cc line 7209 for 12.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789684688640 has waited at trx0rseg.ic line 50 for 272.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887cd1098 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file not yet reserved line 0
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789781440256 has waited at trx0undo.ic line 164 for 271.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887d195a8 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file trx0undo.ic line 180
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789781743360 has waited at dict0dict.cc line 1160 for 169.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789808133888 has waited at srv0srv.cc line 2096 for 250.00 seconds the semaphore:
X-lock on RW-latch at 0x7f28d1cbf440 created in file dict0dict.cc line 1107
a writer (thread id 139789701474048) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0purge.cc line 853
Last time write locked in file dict0stats.cc line 2457
2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789781137152 has waited at dict0load.cc line 2747 for 219.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:15:46 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789701474048 has waited at trx0trx.cc line 1157 for 251.00 seconds the semaphore:
Mutex at 0x7f28d1cc7fd8, Mutex REDO_RSEG created trx0rseg.cc:168, lock var 2

InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
InnoDB: Pending reads 0, writes 0
InnoDB: ###### Diagnostic info printed to the standard error stream
2023-06-28 13:16:17 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789684688640 has waited at trx0rseg.ic line 50 for 303.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887cd1098 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file not yet reserved line 0
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:16:17 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789781440256 has waited at trx0undo.ic line 164 for 302.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887d195a8 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file trx0undo.ic line 180
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:16:17 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789808133888 has waited at srv0srv.cc line 2096 for 281.00 seconds the semaphore:
X-lock on RW-latch at 0x7f28d1cbf440 created in file dict0dict.cc line 1107
a writer (thread id 139789701474048) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0purge.cc line 853
Last time write locked in file dict0stats.cc line 2457
2023-06-28 13:16:17 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789781137152 has waited at dict0load.cc line 2747 for 250.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:16:17 139789791348480 [Warning] InnoDB: A long semaphore wait:
--Thread 139789701474048 has waited at trx0trx.cc line 1157 for 282.00 seconds the semaphore:
Mutex at 0x7f28d1cc7fd8, Mutex REDO_RSEG created trx0rseg.cc:168, lock var 2

2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789782349568 has waited at trx0rseg.ic line 50 for 207.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887cd13c8 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file not yet reserved line 0
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789709866752 has waited at dict0dict.cc line 7209 for 43.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789684688640 has waited at trx0rseg.ic line 50 for 303.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887cd1098 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file not yet reserved line 0
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789781440256 has waited at trx0undo.ic line 164 for 302.00 seconds the semaphore:
X-lock on RW-latch at 0x7f2887d195a8 created in file buf0buf.cc line 1471
a writer (thread id 0) has reserved it in mode  SX
number of readers 0, waiters flag 1, lock_word: 10000000
Last time read locked in file trx0undo.ic line 180
Last time write locked in file buf0flu.cc line 1236
2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789781743360 has waited at dict0dict.cc line 1160 for 200.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789808133888 has waited at srv0srv.cc line 2096 for 281.00 seconds the semaphore:
X-lock on RW-latch at 0x7f28d1cbf440 created in file dict0dict.cc line 1107
a writer (thread id 139789701474048) has reserved it in mode  exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file row0purge.cc line 853
Last time write locked in file dict0stats.cc line 2457
2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789781137152 has waited at dict0load.cc line 2747 for 250.00 seconds the semaphore:
Mutex at 0x7f28d1cbf4c0, Mutex DICT_SYS created dict0dict.cc:1096, lock var 2

2023-06-28 13:16:17 139789791348480 [Note] InnoDB: A semaphore wait:
--Thread 139789701474048 has waited at trx0trx.cc line 1157 for 282.00 seconds the semaphore:
Mutex at 0x7f28d1cc7fd8, Mutex REDO_RSEG created trx0rseg.cc:168, lock var 2

Can you tell me what was happened?

I am looking at my SQL Server error logs and noticed that they cycle frequently. Even though the files are small, some are only around 250 lines, they often cycle a number of times per day. This limits the range of time covered by the retained logs. In the *Configure SQL Server Error Logs* screen, the size of the file is not limited, and I do not have an agent job that is recycling the logs. I am also not in the habit of restarting the server several times per day. Any information you can provide to help me track down the cause would be most appreciated. From what I can see, it doesn't seem to be a restart. Each of the queries below returns a datetime that is within 4 seconds of one another on a date in March when we had our system maintenance:

SELECT sqlserver_start_time FROM sys.dm_os_sys_info
SELECT login_time FROM sys.dm_exec_sessions WHERE session_id = 1
SELECT create_date FROM sys.databases WHERE name = 'tempdb'

I'm trying to figure out which process is trying to connect to my SQL Server instance with a wrong password. The log file only contains the IP address from where the connection is initiated. Example: > Date 4/05/2021 9:43:34 AM >Log SQL Server (Current - 5/05/2021 10:11:00 AM) > >Source Logon > >Message >Login failed for user 'SA'. Reason: Password did not match that for the login provided. [CLIENT: 10.120.1.99] It does not log which PID from the client machine made the attempt. I know that I can use profiler to find out which PID from which machine is responsible for this. But I do not want to keep a profiler running for this. (especially if this happens rarely, in which case I'll need to keep the profiler running for days before I can catch such an attempt). Is there a way to log the PID as well as the IP for such failed logons?