<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[ServerForum.org - The Professional IT Community - SQL-Databases]]></title>
		<link>https://serverforum.org/</link>
		<description><![CDATA[ServerForum.org - The Professional IT Community - https://serverforum.org]]></description>
		<pubDate>Tue, 07 Apr 2026 10:19:32 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[MYSQL 5.6.38 database after reboot is not starting anymore]]></title>
			<link>https://serverforum.org/showthread.php?tid=22</link>
			<pubDate>Tue, 09 Jan 2018 09:23:06 +0100</pubDate>
			<guid isPermaLink="false">https://serverforum.org/showthread.php?tid=22</guid>
			<description><![CDATA[Hello, <br />
<br />
regarding a maintenance on the host system where my VPS is running the hoster have restart the server. Since the restart my MYSQL database server is not starting anymore. After trying to start the MYSQL server manually I can see the following message in the command line: <br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-family: Consolas,;" class="mycode_font">mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.</span></span></span></span></blockquote>
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Currnent system setup:</span></span><br />
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">‪Ubuntu 14.04.5 LTS‬</span></span><br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Intel Xeon X5650</span></span><br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Plesk Onyx Version 17.5</span></span><br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">MYSQL Server-Version: 5.6.38 - MySQL Community Server</span></span><br />
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">MYSQL error log file: </span></span><br />
<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>170619 11:40:52 mysqld_safe Logging to '/var/log/mysql/error.log'.<br />
170619 11:40:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql<br />
2018-01-09 11:40:52 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.<br />
2018-01-09 11:40:52 0 [Warning] option 'thread_concurrency': unsigned value 0 adjusted to 1<br />
2018-01-09 11:40:52 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.<br />
2018-01-09 11:40:52 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).<br />
2018-01-09 11:40:52 0 [Note] /usr/sbin/mysqld (mysqld 5.6.36) starting as process 29712 ...<br />
2018-01-09 11:40:52 29712 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)<br />
<br />
2018-01-09 11:40:52 29712 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 512)<br />
<br />
2018-01-09 11:40:52 29712 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.<br />
2018-01-09 11:40:52 29712 [Note] Plugin 'FEDERATED' is disabled.<br />
2018-01-09 11:40:52 7f2293e00780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Using atomics to ref count buffer pool pages<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: The InnoDB memory heap is disabled<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Memory barrier is not used<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Compressed tables use zlib 1.2.3<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Using Linux native AIO<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Using CPU crc32 instructions<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Initializing buffer pool, size = 1.0G<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Completed initialization of buffer pool<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Highest supported file format is Barracuda.<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Log scan progressed past the checkpoint lsn 20113308285<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Database was not shutdown normally!<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Starting crash recovery.<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Reading tablespace information from the .ibd files...<br />
2018-01-09 11:40:52 29712 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 0.<br />
2018-01-09 11:40:52 7f2293e00780  InnoDB: Operating system error number 2 in a file operation.<br />
InnoDB: The error means the system cannot find the path specified.<br />
InnoDB: If you are installing InnoDB, remember that you must create<br />
InnoDB: directories yourself, InnoDB does not create them.<br />
2018-01-09 11:40:52 29712 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation<br />
170619 11:40:52 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended</blockquote>
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font"><span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Can anyone please help on this issue the last backup is from 03.12.2017 a lot of mails and important data are saved on the MYSQL server. </span></span><br />
</span></span><br />
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font"><span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Thank you in advanced</span></span></span></span>]]></description>
			<content:encoded><![CDATA[Hello, <br />
<br />
regarding a maintenance on the host system where my VPS is running the hoster have restart the server. Since the restart my MYSQL database server is not starting anymore. After trying to start the MYSQL server manually I can see the following message in the command line: <br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite><span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font"><span style="font-size: small;" class="mycode_size"><span style="font-family: Consolas,;" class="mycode_font">mysqld_safe Can't log to error log and syslog at the same time.  Remove all --log-error configuration options for --syslog to take effect.</span></span></span></span></blockquote>
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Currnent system setup:</span></span><br />
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">‪Ubuntu 14.04.5 LTS‬</span></span><br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Intel Xeon X5650</span></span><br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Plesk Onyx Version 17.5</span></span><br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">MYSQL Server-Version: 5.6.38 - MySQL Community Server</span></span><br />
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">MYSQL error log file: </span></span><br />
<br />
<br />
<blockquote class="mycode_quote"><cite>Quote:</cite>170619 11:40:52 mysqld_safe Logging to '/var/log/mysql/error.log'.<br />
170619 11:40:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql<br />
2018-01-09 11:40:52 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.<br />
2018-01-09 11:40:52 0 [Warning] option 'thread_concurrency': unsigned value 0 adjusted to 1<br />
2018-01-09 11:40:52 0 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.<br />
2018-01-09 11:40:52 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).<br />
2018-01-09 11:40:52 0 [Note] /usr/sbin/mysqld (mysqld 5.6.36) starting as process 29712 ...<br />
2018-01-09 11:40:52 29712 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)<br />
<br />
2018-01-09 11:40:52 29712 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 512)<br />
<br />
2018-01-09 11:40:52 29712 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.<br />
2018-01-09 11:40:52 29712 [Note] Plugin 'FEDERATED' is disabled.<br />
2018-01-09 11:40:52 7f2293e00780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Using atomics to ref count buffer pool pages<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: The InnoDB memory heap is disabled<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Memory barrier is not used<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Compressed tables use zlib 1.2.3<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Using Linux native AIO<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Using CPU crc32 instructions<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Initializing buffer pool, size = 1.0G<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Completed initialization of buffer pool<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Highest supported file format is Barracuda.<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Log scan progressed past the checkpoint lsn 20113308285<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Database was not shutdown normally!<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Starting crash recovery.<br />
2018-01-09 11:40:52 29712 [Note] InnoDB: Reading tablespace information from the .ibd files...<br />
2018-01-09 11:40:52 29712 [ERROR] InnoDB: Tried to read 16384 bytes at offset 0. Was only able to read 0.<br />
2018-01-09 11:40:52 7f2293e00780  InnoDB: Operating system error number 2 in a file operation.<br />
InnoDB: The error means the system cannot find the path specified.<br />
InnoDB: If you are installing InnoDB, remember that you must create<br />
InnoDB: directories yourself, InnoDB does not create them.<br />
2018-01-09 11:40:52 29712 [ERROR] InnoDB: File (unknown): 'read' returned OS error 71. Cannot continue operation<br />
170619 11:40:52 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended</blockquote>
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font"><span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Can anyone please help on this issue the last backup is from 03.12.2017 a lot of mails and important data are saved on the MYSQL server. </span></span><br />
</span></span><br />
<br />
<span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font"><span style="color: #4e4e4e;" class="mycode_color"><span style="font-family: Lato, sans-serif;" class="mycode_font">Thank you in advanced</span></span></span></span>]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Difference between Microsoft SQL allways on and failover cluster? SQL Server 2016...]]></title>
			<link>https://serverforum.org/showthread.php?tid=13</link>
			<pubDate>Wed, 16 Aug 2017 16:47:03 +0200</pubDate>
			<guid isPermaLink="false">https://serverforum.org/showthread.php?tid=13</guid>
			<description><![CDATA[Hello, <br />
<br />
can anyone help? What is the difference between the Microsoft solution always on and failover cluster? And what is the better solution for high awailability?]]></description>
			<content:encoded><![CDATA[Hello, <br />
<br />
can anyone help? What is the difference between the Microsoft solution always on and failover cluster? And what is the better solution for high awailability?]]></content:encoded>
		</item>
	</channel>
</rss>