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...
Post a Comment

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

Post a Comment

Popular posts from this blog

On-board Linux computers to Azure Log Analytics

-
For on-boarding linux servers to Azure log analytics, just execute the command on the respective server: wget https://raw.githubusercontent.com/Microsoft/OMS-Agent-for-Linux/master/installer/scripts/onboard_agent.sh && sh onboard_agent.sh -p [protocol://][user:password@]proxyhost[:port] -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY> In few cases like mine, the servers will not have access to internet and we will need to install the downloaded oms agent package with the proxy information.  sh omsagent-1.6.0-42.universal.x64.sh --install -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY> -p [protocol://][user:password@]proxyhost[:port] The proxy can have username and password for authentication and even if no proxy authentication is required, we will need to enter a dummy username and password which in the example below is azure and azure. sh omsagent-1.6.0-42.universal.x64.sh --install -w <YOUR WORKSPACE ...
Read more

Office 365 User unable to book room on-premise in Exchange Hybrid environment

-
In a federated environment, an Office 365 user was unable to book meeting in room which was on-premise. After tracing the messages created for booking the room, it was confirmed that the message indeed reached but the room was rejecting it for some reason. The room was rejecting the meeting request as it was considering the Office 365 user as an external user. So to solve this, we need to run the following command in the On-premise Exchange environment if we want to allow all the rooms: Get-Mailbox | where {$_.RecipientTypeDetails -like "Roommailbox"}| Get-CalendarProcessing | Set-CalendarProcessing -ProcessExternalMeetingMessages $true For single room, run the following command: Get-CalendarProcessing -Identity <Room name> | Set-CalendarProcessing -ProcessExternalMeetingMessages $true  Now the Office 365 user will be able to book the on-premise meeting room. (This is assuming that the free/busy calendar sharing is already enabled in the federated environme...
Read more

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...
Read more