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

SharePoint 2013 Installation Error: The current server cannot be joined to this farm

I got this error while running the SharePoint Product Configuration Wizard
An exception of type System.InvalidOperationException was thrown. Additional exception information: The current server cannot be joined to the farm because the set of installed products does not match the products installed in the farm.
I looked at the logs and found this error:
The current server cannot be joined to this farm because the set of installed products does not match the products installed in the farm. The license state for the current server doesn’t match the farm’s license state.
After validating the current and new servers products I found that the product key that was provided was for a SharePoint Enterprise and the current one was running Standard Edition. In order to join a server to the farm you need to have the same products installed on the new server.

Here is a quick way to validate the products installed on a server:

1. Run regedit

2. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\InstalledProducts

3. The product GUIDs are as follows:


C5D855EE-F32B-4A1C-97A8-F0A28CE02F9C – “SharePoint Server 2013”
B7D84C2B-0754-49E4-B7BE-7EE321DCE0A9 – “SharePoint Server 2013 Enterprise”
9FF54EBC-8C12-47D7-854F-3865D4BE8118 – “SharePoint Foundation 2013”

4. Replace with the necessary product GUID.

5. Enjoy

Comments

Post a Comment

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]