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 policy.
 Get-MailboxServer <Server Name> | Select DatabaseCopyAutoActivationPolicy

4. Set the auto activation policy to “Blocked”
Set-MailboxServer <Server Name> –DatabaseCopyAutoActivationPolicy Blocked  

5.Bring the server into maintenance mode.
Set-ServerComponentState <Server Name>  –Component ServerWideOffline –State InActive –Requester Maintenance 

6. Run
Setup.exe 
for the gui installation or
setup /m:upgrade /IacceptExchangeServerLicenseTerms
for the unattended installation.This should take around 45 minutes per DAG mailbox server.
7. After setup is complete, bring the server out of maintenance mode.
Set-ServerComponentState <Server Name> –Component ServerWideOffline –State Active –Requester Maintenance

8. Resume the DAG server.
Resume-ClusterNode –Name <Server Name>

9. Set the database copy auto activation policy which was existing previously as per step 3.
Set-MailboxServer <Server Name> –DatabaseCopyAutoActivationPolicy Unrestricted

10. Enable database copy activation.
Set-MailboxServer <Server Name>  –DatabaseCopyActivationDisabledAndMoveNow $false

11. Activate the Hub Transport role.
Set-ServerComponentState <Server Name> –Component HubTransport –State Active –Requester Maintenance  


For CAS(Client Access) servers, the following steps are to be followed:
1. Bring the server into maintenance mode.
Set-ServerComponentState <Server Name>  –Component ServerWideOffline –State InActive –Requester Maintenance 

2. Run
Setup.exe 
for the gui installation or
 setup /m:upgrade /IacceptExchangeServerLicenseTerms
for the unattended installation. This should take 15-30 minutes.
3. After setup is complete, bring the server out of maintenance mode.
Set-ServerComponentState –Component ServerWideOffline –State Active –Requester Maintenance


In case of issues, please review the excellent article by Paul Cunningham @ExchServPro

http://exchangeserverpro.com/exchange-server-2013-upgrade-fails-due-to-receive-connector-conflicts/

Comments

Popular posts from this blog

On-board Linux computers to Azure Log Analytics

Nutanix Calm Blueprint for Single Linux VM

Fluentd error: Unable to push logs to [elasticsearch]