Azure VM Agent Status not ready
I have created a red hat openshift private cluster but the VMS are stuck in the state of "agent status not ready." I have followed these troubleshooting steps: Linux Virtual Machine Agent Status "Not Ready" - Microsoft Community Hub However, all of them seem to point to trying to check and see what is on the VM itself. I am unable to do this because I can't SSH into the machine. Has anyone else ran into this issue and been able to resolve it? I am deploying it via CLI as I was not able to do it via GUI for some reason. This is my script: #az login az account set --name "accountnamehidden" #az provider register -n Microsoft.RedHatOpenShift --wait #az provider register -n Microsoft.Compute --wait #az provider register -n Microsoft.Storage --wait #az provider register -n Microsoft.Authorization --wait $LOCATION= "eastus" # the location of your cluster $RESOURCEGROUP= "sample-rg" # the name of the resource group where you want to create your cluster $CLUSTER= "K8sDev1test" # the name of your cluster $arovnet= "sample-vnet" $mastersubnet = "k8sDev1-master-ue-snet" $workersubnet = "k8sDev1-worker-ue-snet" az aro create --resource-group "samplerg" --vnet-resource-group "sample-vnet-rg" --name $CLUSTER --vnet $arovnet --master-subnet "k8sDev1-master-ue-snet" --worker-subnet "k8sDev1-worker-ue-snet" --apiserver-visibility Private --ingress-visibility Private --fips true --outbound-type UserDefinedRouting --client-id hidden --client-secret hidden
[Network Load Balancer] Is there a way to make it aware of Application failures ?
Hello dear Tech Community, I just started to explore NWLB feature of Windows Server so please forgive my very poor knowledge on this IT-oriented topic! My goal is to load balance TCP IP traffic over a cluster of, say, 2 servers for a particular Windows service using port 1234. This service is a custom one developed in my company to expose a particular server application and using it on a single server is not an ideal when the number of consuming clients is exceeding 20 or so. I was able to test LB nominal cases (where both nodes/hosts are up and running), and also to verify that, when one node is down, the LB is still running and serving clients with the other node. But what if the node is up but the application "behind the port" is failing to respond? It seems to me NWLB is totally blind about this case and continue to wait forever. So my question is, is there a way to provide a kind of application-custom health probe to NWLB so that it can discover the node is actually not available for further requests? Many thanks for reading me and looking forward to get your insights !
2k16 Clustering - Error loading custom resource DLL
Hello All, I'm trying to add a custom resource dll into a 2k16 cluster; I'm seeing the same result using both powershell and the failover cluster manager. I have followed the documentation in for creating custom resource types https://docs.microsoft.com/en-us/previous-versions/windows/desktop/mscs/creating-resource-types I took the skeleton from the clipbookserver example and the examples in the cluster api doc cited above. The command 'Add-ClusterResourceType -Name MyTypeBeta -Dll "C:\Windows\cluster\garbagee.dll"' and am receiving the following prints: INFO [RCM] rcm::RcmApi::CreateResType: (MyTypeBeta, MyTypeBeta, C:\Windows\cluster\garbagee.dll)* INFO [RCM] rcm::RcmGum::CreateResType(MyTypeBeta,C:\Windows\cluster\garbagee.dll,MyTypeBeta) ERR [RHS] s_RhsRpcCreateResType: (126)' because of 'Error loading resource DLL c:\windows\cluster\garbagee.dll.' INFO [RCM] result of first load attempt for type MyTypeBeta: 126 WARN [RCM] The DLL for resource type 'MyTypeBeta' is not present. INFO Received notification on resource type that was not findable: mytypebeta The def file is as follows: LIBRARY GARBAGEE EXPORTS Startup PRIVATE Dll is built for x64. I've tried 'extern "C"' for Startup, combining '__declspec(dllexport)'. I've turned off the Props->c/c++->Language 'Conformance mode' and not using precompiled headers. I'm placing the dll and lib directly in the C:\windows\cluster directory on all nodes. I believe this is something fundamental but cannot figure this out? Any help is very much appreciated. Thanks, BLC
