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

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 environment.)


Comments

  1. Thanks for sharing the best information and suggestions, it is very nice and very useful to us. I appreciate the work that you have shared in this post. Keep sharing these types of articles here.Flushing Shared Office Space

    ReplyDelete
  2. On the other hand, when utilizing CNC machines in-house, you'll need to make certain may have} the proper equipment, software, and materials to create your prototype. In abstract, CNC machines provide greater precision, speed, and flexibility in large-scale production environments than 3D printers. When it comes to effectivity CNC machining and accuracy, CNC machines provide a compelling manufacturing resolution. Developed in the 1940s, the primary CNC machines used punched-paper expertise as an alternative of the digital software we see at present.

    ReplyDelete

Post a Comment

Popular posts from this blog

Oracle Audit Vault on Hyper-V

On-board Linux computers to Azure Log Analytics