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

Renewal of ADFS signing certificate affects third party services like Oracle cloud and Service-Now

Recently we experienced an outage with third party services like Oracle cloud and Service-Now which were integrated with ADFS.

ADFS creates a new signing certificate and makes it primary 20 days and 15 days respectively before the expiry of the current certificate. After this, the 3rd party services are unable to communicate with ADFS for SSO purposes.

The new federated xml will have information of both the primary and secondary certificates during this period. We will need to edit this XML before uploading to the 3rd party services using respective global administrator accounts.

Look for the following piece of code as show below:

<KeyDescriptor use="signing">
            <KeyInfo xmlns="">

You will find two instances of this code under the tags:

<RoleDescriptor xsi:type="fed:SecurityTokenServiceType">          

<SPSSODescriptor WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:*.0:protocol">

<IDPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:*.0:protocol"> 


Remove the first instance of this code in the three places.

Upload the edited federated xml file to the 3rd party services and all should be working normally.

Note: This has to be done 15 days before the expiry of the certificate.


Popular posts from this blog

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

On-board Linux computers to Azure Log Analytics

Fluentd error: Unable to push logs to [elasticsearch]