Showing posts from April, 2016

Latest Post

Fluentd error: Unable to push logs to [elasticsearch]

After application deployments, Kibana stopped showing logs exactly after 7 days. The error "Fluentd error: Unable to push logs to [elasticsearch]" was shown in the fluentd logs. The initial response was to increase the buffer limits for fluentd as follows: chunk_limit_size 10M queue_limit_length 256 The behavior occurred again after two weeks, which led to the same error. On closer investigation, the error was preceded by the statement "Failed to write to the buffer." This led me to inspect the fluentd configuration again and found the following code in the buffer part which caused the fluentd buffers to be filled as per the official documentation on Fluentd : overflow_action block The fix for this overflow_action is to change from block to drop_oldest_chunk, allowing the fluentd logs to flow seamlessly to the elastic search by dropping the oldest logs in the buffer.   <buffer> @type file path /var/log/fluentd-buffers/kubernet

Cumulative update on Exchange 2013

1. Download the Cumulative update for Exchange 2013. 2. For the update of Exchange server 2013 CU 1-6, AD Schema needs to be extended. For update of Exchange 2013 CU 6 and later, the following steps 3-6 is not required. 3. Open a command prompt, go to the folder with the CU and type PackageName-KB12345-x64.exe /x:C:\abc\Unpacked 4.Prepare the AD Schema. setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms 5. Prepare AD. setup.exe /PrepareAD /IacceptExchangeServerLicenseTerms 6. Prepare the domain. setup.exe /PrepareDomain /IacceptExchangeServerLicenseTerms Mailbox servers in the DAG should be updated first. For Mailbox servers in the DAG, the following steps should be followed: 1. Suspend the DAG member by running the command Suspend-ClusterNode –Name <Server Name> in EMS.  2. Disable database copy activation. Set-MailboxServer <Server Name> –DatabaseCopyActivationDisabledAndMoveNow $true  3. Check the existing database copy auto activation polic