Showing posts from 2016

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

SCVMM error 23351

After importing an exported Generation 2 template in VMM, the following error occurs when trying to deploy :   The input string “” for the FirstBootDevice parameter cannot be parsed and may be invalid. Make sure the string uses one of the following formats: “SCSI,BusId(integer),LunId(integer)” or “NIC,SlotId(integer)” ID: 23351 We can use Powershell to fix this: Import-Module virtualmachinemanager Get-SCVMTemplate -Name 'TEMPLATEXXX'   | Set-SCVMTemplate -FirstBootDevice 'SCSI,0,0'    

DFS Slowdown on Windows Server 2012 R2

The other day, the file server started showing up by not serving any shares. Initially it happened once in a week which was solved by a reboot and then it started started to occur almost every hour. The DFS replication service was showing 99% CPU usage during all of this. After a bit of research, a hotfix for DFS (KB 3172614) released July 2016 was available. After the installation of hotfix, the DFS replication service CPU usage came down to tolerable levels.

Windows 7/2008 VM not booting up on Hyper-V host after windows update using CAU

After updating three hosts out of five in a windows hyper-v cluster based on Nutanix using CAU tool, I noticed the Windows 7/2008 VMs stopped running on the updated hosts. Using the failover cluster manager, I managed to failover the VM to the non-updated host and it started working. During troubleshooting, I came across the below two blogs which set me thinking: In the Hyper-V manager, I noticed the Windows 2012 VMs were running without any issue but the Windows 7/2008 VMs were shown with the message  "Cannot connect to Virtual Machine storage". I was able to access the storage from the hosts without any problem and confirmed this with Nutanix support.  The Hyper-V hosts create symbolic links to th

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 polic

WWN from Hyper-V Nodes

1. Open up Powershell with administrator privileges. 2. Run the command :     Get-InitiatorPort -ConnectionType FibreChannel 3. The column with the header Node Address should give you WWN.

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