<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MariaDB Archives - Vavai&#039;s Personal Notes</title>
	<atom:link href="https://www.vavai.net/tag/mariadb/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vavai.net/tag/mariadb/</link>
	<description>Life is our precious gift</description>
	<lastBuildDate>Mon, 29 Oct 2018 19:58:39 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Zimbra MariaDB Error : Can&#8217;t init tc log</title>
		<link>https://www.vavai.net/zimbra-mariadb-error-cant-init-tc-log/</link>
					<comments>https://www.vavai.net/zimbra-mariadb-error-cant-init-tc-log/#respond</comments>
		
		<dc:creator><![CDATA[Muhammad Rivai]]></dc:creator>
		<pubDate>Mon, 29 Oct 2018 19:58:39 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[MariaDB]]></category>
		<category><![CDATA[Zimbra]]></category>
		<guid isPermaLink="false">http://v2.vavai.net/?p=2107</guid>

					<description><![CDATA[<p>A few days ago, our clients had problems with their on-premise mail server deployment. Their Zimbra services are down and mailbox service could not restart. After a quick check, it turns out that one of the disk partitions is full because there is an incorrect mounting disk. As it uses incorrect folder/disk, backup process filling up...</p>
<p>The post <a href="https://www.vavai.net/zimbra-mariadb-error-cant-init-tc-log/">Zimbra MariaDB Error : Can&#8217;t init tc log</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>A few days ago, our clients had problems with their on-premise mail server deployment. Their Zimbra services are down and mailbox service could not restart. After a quick check, it turns out that one of the disk partitions is full because there is an incorrect mounting disk. As it uses incorrect folder/disk, backup process filling up primary partition instead of external disk.<br />
<img decoding="async" class="alignnone wp-image-2055 size-medium" src="http://v2.vavai.net/wp-content/uploads/2018/10/Zimbra-logo-color-300x66.png" alt="" width="300" height="66" srcset="https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color-300x66.png 300w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color-1024x225.png 1024w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color-768x168.png 768w, https://d3b35uem336dgh.cloudfront.net/wp-content/uploads/2018/10/Zimbra-logo-color.png 1500w" sizes="(max-width: 300px) 100vw, 300px" /><br />
To deal with this problem, I move some unimportant data from primary partition and release quite enough free space and trying to restart services. LDAP, mta and others services are up but mailbox services won&#8217;t. More detailed checking on log shows that the MariaDB database services cannot run. Inspecting /opt/zimbra/log/mysql_error.log log file, there is an error message: &#8220;Can&#8217;t init tc log&#8221;.</p>
<blockquote><p>181022 22:35:42 mysqld_safe mysqld from pid file /opt/zimbra/log/mysql.pid ended<br />
201-10-10 22:35:42 140144607115136 [Note] InnoDB: 128 rollback segment (s) are active.<br />
201-10-10 22:35:42 140144607115136 [Note] InnoDB: Waiting for purge to start<br />
201-10-10 22:35:43 140144607115136 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.0 started; log sequence number 6803622123<br />
201-10-10 22:35:43 140141100709632 [Note] InnoDB: Dumping buffer pool (s) not yet started<br />
2018-10-22 22:35:43 140144607115136 [Note] The plugin &#8216;FEEDBACK&#8217; is disabled.<br />
2018-10-22 22:35:43 140144607115136 [Note] Recovering after a crash using tc.log<br />
2018-10-22 22:35:43 140144607115136 [ERROR] Can&#8217;t init tc log<br />
2018-10-22 22:35:43 140144607115136 [ERROR] Aborting<br />
181022 22:35:45 mysqld_safe mysqld from pid file /opt/zimbra/log/mysql.pid ended</p></blockquote>
<p>As the problem related to tc.log, some reference on Google search recommends an easy resolution.  Simply delete or move (I would rather choose the moving process for the sake of precaution) the file /opt/zimbra/db/data/tc.log to a different location and then restart the database services. Database services turn out OK and the next process is to restarting Zimbra services.<br />
One more important step is to ensure the preventive checks run even better, in the sense that an early warning of an almost full disk should be escalated earlier.</p>
<p>The post <a href="https://www.vavai.net/zimbra-mariadb-error-cant-init-tc-log/">Zimbra MariaDB Error : Can&#8217;t init tc log</a> appeared first on <a href="https://www.vavai.net">Vavai&#039;s Personal Notes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.vavai.net/zimbra-mariadb-error-cant-init-tc-log/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Object Caching 28/41 objects using Disk
Page Caching using Disk: Enhanced 
Content Delivery Network via Amazon Web Services: CloudFront: d3b35uem336dgh.cloudfront.net
Lazy Loading (feed)
Minified using Disk
Database Caching 15/30 queries in 0.011 seconds using Disk

Served from: www.vavai.net @ 2026-11-16 07:51:31 by W3 Total Cache
-->