Cant't start node on the cluster
when I start my node in the cluster I have this error, what I should do to solve this?
<Oct 30, 2011 11:06:00 PM BRST> <Error> <ALSB Statistics Manager> <BEA-473003> <Aggregation Server Not Available. Failed to get remote aggregator
java.rmi.UnknownHostException: Could not discover URL for server 'Node1'
at weblogic.protocol.URLManager.findURL(URLManager.java:145)
at com.bea.alsb.platform.weblogic.topology.WlsRemoteServerImpl.getInitialContext(WlsRemoteServerImpl.java:94)
at com.bea.alsb.platform.weblogic.topology.WlsRemoteServerImpl.lookupJNDI(WlsRemoteServerImpl.java:54)
at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.getRemoteAggregator(ALSBStatisticsManager.java:291)
at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.access$000(ALSBStatisticsManager.java:38)
at com.bea.wli.monitoring.statistics.ALSBStatisticsManager$RemoteAggregatorProxy.send(ALSBStatisticsManager.java:55)
at com.bea.wli.monitoring.statistics.collection.Collector.sendRawSnaphotToAggregator(Collector.java:284)
at com.bea.wli.monitoring.statistics.collection.Collector.doCheckpoint(Collector.java:245)
at com.bea.wli.monitoring.statistics.collection.Collector$CheckpointThread.doWork(Collector.java:69)
at com.bea.wli.monitoring.utils.Schedulable.timerExpired(Schedulable.java:68)
at com.bea.wli.timer.ClusterTimerImpl$InternalTimerListener.timerExpired(ClusterTimerImpl.java:255)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
I solved this on two steps:
1 - I run ifconfig and check if my network card has MULTICAST flag
2 - I add this route run this command:
route add -host 239.192.0.10 dev eth0
afeter this my nodes has started with sucess
Similar Messages
-
Dear Experts,
Please help me, I am new in RAC and I have a question please;
We have 6 nodes cluster of 11.2.0.2.3 version and my manager wants me to add a new node to the cluster.
Could you please send me the steps 1, 2 , 3 ...
we have not shared oracle homes (oracle user), not shared grid homes (grid user) and they are all patched with patch set update 3 (11.2.0.2.3) all under Enterprise Redhat Linux 5.5.
Please also tell me with which system user (oracle, root or grid) I have to run each command...
Could you help me?
SI have the following errors, could you help me please? (Oracle and grid homes are not shared)
-bash-3.2$ ./addNode.sh "CLUSTER_NEW_NODES={db07}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={db07-vip}"
Performing pre-checks for node addition
Checking node reachability...
Node reachability check passed from node "db01"
Checking user equivalence...
User equivalence check passed for user "grid"
Checking node connectivity...
Checking hosts config file...
Verification of the hosts config file successful
Check: Node connectivity for interface "bond1"
Node connectivity passed for interface "bond1"
Node connectivity check passed
Checking CRS integrity...
CRS integrity check passed
Checking shared resources...
Checking CRS home location...
ERROR:
PRVF-4864 : Path location check failed for: "/opt/11.2.0/grid"
Shared resources check for node addition failed
Check failed on nodes:
db07
Checking node connectivity...
Checking hosts config file...
Verification of the hosts config file successful
Check: Node connectivity for interface "bond0"
Node connectivity passed for interface "bond0"
Check: Node connectivity for interface "bond1"
Node connectivity passed for interface "bond1"
Node connectivity check passed
Total memory check passed
Available memory check passed
Swap space check failed
Check failed on nodes:
db01,db07
Free disk space check failed for "db01:/tmp"
Check failed on nodes:
db01
Free disk space check failed for "db07:/tmp"
Check failed on nodes:
db07
Check for multiple users with UID value 501 passed
User existence check passed for "grid"
Run level check passed
Hard limits check passed for "maximum open file descriptors"
Soft limits check passed for "maximum open file descriptors"
Hard limits check passed for "maximum user processes"
Soft limits check passed for "maximum user processes"
System architecture check passed
Kernel version check passed
Kernel parameter check passed for "semmsl"
Kernel parameter check passed for "semmns"
Kernel parameter check passed for "semopm"
Kernel parameter check passed for "semmni"
Kernel parameter check passed for "shmmax"
Kernel parameter check passed for "shmmni"
Kernel parameter check passed for "shmall"
Kernel parameter check passed for "file-max"
Kernel parameter check passed for "ip_local_port_range"
Kernel parameter check passed for "rmem_default"
Kernel parameter check passed for "rmem_max"
Kernel parameter check passed for "wmem_default"
Kernel parameter check passed for "wmem_max"
Kernel parameter check passed for "aio-max-nr"
Package existence check passed for "make-3.81( x86_64)"
Package existence check passed for "binutils-2.17.50.0.6( x86_64)"
Package existence check passed for "gcc-4.1.2 (x86_64)( x86_64)"
Package existence check passed for "libaio-0.3.106 (x86_64)( x86_64)"
Package existence check passed for "glibc-2.5-24 (x86_64)( x86_64)"
Package existence check passed for "compat-libstdc++-33-3.2.3 (x86_64)( x86_64)"
Package existence check passed for "elfutils-libelf-0.125 (x86_64)( x86_64)"
Package existence check passed for "elfutils-libelf-devel-0.125( x86_64)"
Package existence check passed for "glibc-common-2.5( x86_64)"
Package existence check passed for "glibc-devel-2.5 (x86_64)( x86_64)"
Package existence check passed for "glibc-headers-2.5( x86_64)"
Package existence check passed for "gcc-c++-4.1.2 (x86_64)( x86_64)"
Package existence check passed for "libaio-devel-0.3.106 (x86_64)( x86_64)"
Package existence check passed for "libgcc-4.1.2 (x86_64)( x86_64)"
Package existence check passed for "libstdc++-4.1.2 (x86_64)( x86_64)"
Package existence check passed for "libstdc++-devel-4.1.2 (x86_64)( x86_64)"
Package existence check passed for "sysstat-7.0.2( x86_64)"
Package existence check passed for "ksh-20060214( x86_64)"
Check for multiple users with UID value 0 passed
Current group ID check passed
Checking OCR integrity...
OCR integrity check passed
Checking Oracle Cluster Voting Disk configuration...
Oracle Cluster Voting Disk configuration check passed
Time zone consistency check passed
Starting Clock synchronization checks using Network Time Protocol(NTP)...
NTP Configuration file check started...
NTP Configuration file check passed
Checking daemon liveness...
Liveness check passed for "ntpd"
Check for NTP daemon or service alive passed on all nodes
NTP daemon slewing option check passed
NTP daemon's boot time configuration check for slewing option passed
NTP common Time Server Check started...
Check of common NTP Time Server passed
Clock time offset check from NTP Time Server started...
PRVF-5413 : Node "db01" has a time offset of -165613.0 that is beyond permissible limit of 1000.0 from NTP Time Server "192.168.248.253"
PRVF-5413 : Node "db07" has a time offset of -161593.0 that is beyond permissible limit of 1000.0 from NTP Time Server "192.168.248.253"
PRVF-5424 : Clock time offset check failed
Clock synchronization check using Network Time Protocol(NTP) failed
User "grid" is not part of "root" group. Check passed
Checking consistency of file "/etc/resolv.conf" across nodes
File "/etc/resolv.conf" does not have both domain and search entries defined
domain entry in file "/etc/resolv.conf" is consistent across nodes
search entry in file "/etc/resolv.conf" is consistent across nodes
All nodes have one search entry defined in file "/etc/resolv.conf"
The DNS response time for an unreachable node is within acceptable limit on all nodes
File "/etc/resolv.conf" is consistent across nodes
Checking VIP configuration.
Checking VIP Subnet configuration.
Check for VIP Subnet configuration passed.
Checking VIP reachability
Check for VIP reachability passed.
Pre-check for node addition was unsuccessful on all the nodes.
-bash-3.2$ -
Can I use one transport adapter on the nodes of the cluster?
Hi
I am new to sun cluster, in the cluster documentation they mentioned that each node should have 2 network cards one for public connections and one for private connection. what if I do not want the nodes to have public connections except for one node. In other words, I want to use one network card on each node except for the first node in the cluster, users can access the rest of the nodes through the fist node . Is that possible? If yes, what should be the name of the second transport adapter while installing the cluster software on the nodes.
Thank You for the helpDear
We are using cluster for HA on failover condition, If you have only one network adapter so how you work in failover, and you can't assign one adaptor to two node as same, you have min 2 network adapter for 2 node cluster..
:)GooDLucK
Mohammed Tanvir -
RAC Instalation Problem (shared accross all the nodes in the cluster)
All experts
I am trying for installing Oracle 10.2.0 RAC on Redhat 4.7
reff : http://www.oracle-base.com/articles/10g/OracleDB10gR2RACInstallationOnLinux
All steps successfully completed on all nodes (rac1,rac2) every thing is okey for each node
on single node rac instalation successfull.
when i try to install on two nodes
on specify Oracle Cluster Registry (OCR) location showing error
the location /nfsmounta/crs.configuration is not shared accross all the nodes in the cluster. Specify a shared raw partation or cluster file system file that is visible by the same name on all nodes of the cluster.
I create shared disks on all nodes as:
1 First we need to set up some NFS shares. Create shared disks on NAS or a third server if you have one available. Otherwise create the following directories on the RAC1 node.
mkdir /nfssharea
mkdir /nfsshareb
2. Add the following lines to the /etc/exports file. (edit /etc/exports)
/nfssharea *(rw,sync,no_wdelay,insecure_locks,no_root_squash)
/nfsshareb *(rw,sync,no_wdelay,insecure_locks,no_root_squash)
3. Run the following command to export the NFS shares.
chkconfig nfs on
service nfs restart
4. On both RAC1 and RAC2 create some mount points to mount the NFS shares to.
mkdir /nfsmounta
mkdir /nfsmountb
5. Add the following lines to the "/etc/fstab" file. The mount options are suggestions from Kevin Closson.
nas:/nfssharea /nfsmounta nfs rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768,actimeo=0 0 0
nas:/nfsshareb /nfsmountb nfs rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768,actimeo=0 0 0
6. Mount the NFS shares on both servers.
mount /mount1
mount /mount2
7. Create the shared CRS Configuration and Voting Disk files.
touch /nfsmounta/crs.configuration
touch /nfsmountb/voting.disk
Please guide me what is wrongI think you did not really mount it on the second server. what is the output of 'ls /nfsmounta'.
step 6 should be 'mount /nfsmounta', not 'mount 1'. I also don't know if simply creating a zero-size file is sufficient for ocr (i have always used raw devices, not nfs for this) -
Cant communicate between nodes on the same vlan but on different switches (cat/nexus)
Very odd situation that I cant quite figure out.
I have two nexus switches connecte together with PO5
Each Nexus has PO6 which connects to a Cat3750
The nodes are all on vlan 46.
Nodes that are connected to the nexus switches can ping each other but cant ping other nodes on the cat. switch.
Here is an oddity. Nodes on the CAT switch CAN ping nodes on the nexus switches.
It would appear that the nodes on the nexus (or the switches themselves) do not get the arp requests.
Oddity 2. When I do show vpc I see on one of the nexus vlan 46 is active
id Port Status Consistency Reason Active vlans
6 Po6 up success success 1,31,34,46,200,600-605
When I look at the other switch I dont see vlan 46.
id Port Status Consistency Reason Active vlans
6 Po6 up success success 1,31,34,200,600-605
Comparing the configs I dont see a difference between the two (eyeballing sho run)
Here are the running configs for PO6 on both switches (identical)
MTL-N3548COLO-1# sho run int po6
interface port-channel6
switchport mode trunk
spanning-tree port type normal
speed 1000
vpc 6
Not sure what I am missing. Any help is appreciated.
Thanks
DrewYour setup with vMotion on a separate subnet is absolutely correct. For the vMotion issues I'd suggest you google for vMotion 14% which will list a couple of KB articles with possible issues and resolutions/workarounds.
André -
[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)
Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface. -
Timeout when adding a node to the cluster
I'm creating a cluster between 2 Windows Server 2012 servers in different datacenters.
Servers are on 2 different networks N1 (10.0.17.1 ) and N2 (10.1.17.2).
The servers are virtualized on VMWare ESX Sphere5.5.
When we create the cluster on the node N1, node N2 ends with error timeout.
When we create the cluster on the node N2, node N1 ends with error timeout.
* No Antivirus
* No firewalls
* Ping from N1 to N2 OK.
* Ping from N2 to N1 OK.
* Windows are updated.
Thank you
Logs:
000006dc.000012d4::2014/04/29-12:18:10.431 WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
000006dc.000012d4::2014/04/29-12:18:10.431 ERR [RCM] [GIM] ResType Máquina virtual has no resources, not collecting local utilization info
000006dc.000012d4::2014/04/29-12:18:10.431 INFO [RCM] [GIM] Scheduling Local Node Crawler to run in 300000 millisec.
00000ad0.00000dac::2014/04/29-12:18:12.671 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.00000dac::2014/04/29-12:18:12.671 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.0000054c::2014/04/29-12:18:12.677 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.0000054c::2014/04/29-12:18:12.677 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.0000054c::2014/04/29-12:18:12.677 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:18:12.677 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.0000054c::2014/04/29-12:18:12.677 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:18:12.726 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:18:12.726 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:18:12.726 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:18:12.726 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:18:17.726 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:18:17.726 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:18:17.726 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:18:17.726 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:18:22.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:18:22.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:18:22.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:18:22.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:18:27.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:18:27.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:18:27.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:18:27.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:18:32.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:18:32.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:18:32.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:18:32.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:18:37.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:18:37.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:18:37.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:18:37.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:18:42.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:18:42.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:18:42.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:18:42.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:18:47.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:18:47.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:18:47.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:18:47.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:18:52.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:18:52.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:18:52.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:18:52.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:18:57.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:18:57.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:18:57.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:18:57.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:19:02.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:19:02.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:19:02.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:19:02.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:19:07.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:19:07.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:19:07.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:19:07.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:19:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.0000054c::2014/04/29-12:19:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.0000054c::2014/04/29-12:19:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.0000054c::2014/04/29-12:19:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.0000054c::2014/04/29-12:19:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:19:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.0000054c::2014/04/29-12:19:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:19:12.726 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:19:12.726 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:19:12.726 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:19:12.726 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:19:17.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:19:17.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:19:17.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:19:17.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:19:22.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:19:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:19:22.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:19:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:19:27.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:19:27.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:19:27.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:19:27.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:19:32.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:19:32.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:19:32.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:19:32.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:19:37.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:19:37.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:19:37.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:19:37.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:19:42.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:19:42.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:19:42.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:19:42.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:19:47.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:19:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:19:47.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:19:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:19:52.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:19:52.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:19:52.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:19:52.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:19:57.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:19:57.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:19:57.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:19:57.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:20:02.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:20:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:20:02.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:20:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:20:07.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:07.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:07.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:07.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:20:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.00000dac::2014/04/29-12:20:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.00000dac::2014/04/29-12:20:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.00000dac::2014/04/29-12:20:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.00000dac::2014/04/29-12:20:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.00000dac::2014/04/29-12:20:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:20:12.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:12.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
000006dc.00000044::2014/04/29-12:20:15.779 INFO [CLI] Get last update time from db
000006dc.00000044::2014/04/29-12:20:15.779 INFO [CLI] forming node has not updated last update time yet
000006dc.00000044::2014/04/29-12:20:15.780 INFO [CLI] UpdatePasswordPolicy len 8 secs maxage 2592000 secs
000006dc.00000044::2014/04/29-12:20:15.780 INFO [CLI] UpdatePasswordPolicy curreAge 180 secs
000006dc.00000044::2014/04/29-12:20:15.781 INFO [CLI] UpdatePasswordPolicy - maxAge 30 days passAge 0 days
000006dc.00000044::2014/04/29-12:20:15.781 INFO [CLI] Password MaxAge 30 DisablePasswordChange 0
000006dc.00000044::2014/04/29-12:20:15.781 INFO [CLI] Password MaxAge 30 after checking with clusterdb
000006dc.00000044::2014/04/29-12:20:15.781 INFO [CLI] Update CAM now
000006dc.00000044::2014/04/29-12:20:15.781 INFO [CLI] DeCryptPassword successful
000006dc.00000044::2014/04/29-12:20:15.781 INFO [CLI] Update user passwd
000006dc.00000044::2014/04/29-12:20:15.800 INFO [CLI] User passwd updated
0000021c.00000710::2014/04/29-12:20:15.800 INFO [CAM] CamApCallPackage
0000021c.00000710::2014/04/29-12:20:15.801 INFO [CAM] CallInfo: Proc 1756 Thread 68 Count 0 Att 512
0000021c.00000710::2014/04/29-12:20:15.801 INFO [CAM] ClientInfo: Logon 999 Proc 1756 Thread 68 TCB 1 Impersonating 1 Restrict 0 Flags 0
0000021c.00000710::2014/04/29-12:20:15.801 INFO [CAM] SetCNOCred 1756 14 10 74 0
0000021c.00000710::2014/04/29-12:20:15.801 INFO [CAM] Setting User CLIUSR, Dom SQL2 (Proc 1756)
0000021c.00000710::2014/04/29-12:20:15.801 INFO [CAM] IsCredentialsReplacementNeeded - Passwords match
000006dc.00000044::2014/04/29-12:20:15.801 INFO [CLI] LsaCallAuthenticationPackage: 0, 0 size: 0, buffer: HDL( 0 )
000006dc.00000044::2014/04/29-12:20:15.801 INFO [CLI] Credentials Notified
000006dc.00000044::2014/04/29-12:20:15.801 INFO [CLI] IsLocalIdentityExpired age 0 maxage 30
000006dc.00000044::2014/04/29-12:20:15.801 INFO [CLI] IsLocalIdentityExpired, password not expired
00000ad0.00000dac::2014/04/29-12:20:17.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:20:17.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:20:17.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:20:17.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:20:22.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:22.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:20:27.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:20:27.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:20:27.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:20:27.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:20:32.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:32.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:32.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:32.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:20:37.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:20:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:20:37.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:20:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
000006dc.00000044::2014/04/29-12:20:42.274 INFO [NM] Received request from client address SQL2.
000006dc.00001640::2014/04/29-12:20:42.274 INFO [NM] Received request from client address SQL2.
00000ad0.0000054c::2014/04/29-12:20:42.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:42.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:42.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:42.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
000006dc.00001650::2014/04/29-12:20:45.293 INFO [NM] Received request from client address SQL2.
00000ad0.0000054c::2014/04/29-12:20:47.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:47.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:20:52.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:20:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:20:52.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:20:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:20:57.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:20:57.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:20:57.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:20:57.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:21:02.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:21:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:02.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:21:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:07.734 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:21:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:21:07.734 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:21:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:12.671 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.0000054c::2014/04/29-12:21:12.671 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.0000054c::2014/04/29-12:21:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.0000054c::2014/04/29-12:21:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.0000054c::2014/04/29-12:21:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.0000054c::2014/04/29-12:21:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:21:12.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:21:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:12.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:21:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:17.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:21:17.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:21:17.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:21:17.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:21:22.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:21:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:22.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:21:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:27.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:21:27.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:21:27.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:21:27.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:21:32.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:21:32.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:32.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:21:32.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:37.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:21:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:21:37.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:21:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:21:42.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:21:42.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:42.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:21:42.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:47.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:21:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:21:47.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:21:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:21:52.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:21:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:21:52.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:21:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:21:57.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:21:57.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:21:57.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:21:57.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:02.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:22:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:22:02.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:22:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:22:07.734 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:22:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:07.734 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:22:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.00001720::2014/04/29-12:22:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.00001720::2014/04/29-12:22:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.00001720::2014/04/29-12:22:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.00001720::2014/04/29-12:22:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.00001720::2014/04/29-12:22:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:22:12.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:22:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:12.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:22:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:17.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:22:17.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:22:17.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:22:17.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:22:22.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:22:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:22.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:22:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:27.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:22:27.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:22:27.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:22:27.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
000006dc.00000044::2014/04/29-12:22:30.860 INFO [NM] Received request from client address fe80::7822:e960:da9b:175f.
00000ad0.00000dac::2014/04/29-12:22:32.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:22:32.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:32.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:22:32.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:37.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:22:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:22:37.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:22:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:22:42.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:22:42.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:42.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:22:42.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:47.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:22:47.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:22:47.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:22:47.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:22:52.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:22:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:22:52.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:22:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:22:57.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:22:57.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:22:57.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:22:57.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:23:02.734 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00001720::2014/04/29-12:23:02.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00001720::2014/04/29-12:23:02.734 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00001720::2014/04/29-12:23:02.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00001720::2014/04/29-12:23:07.734 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:23:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:07.734 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:23:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad8.00001580::2014/04/29-12:23:10.436 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
000006dc.00001488::2014/04/29-12:23:10.436 INFO [RCM] result of first load attempt for type MSMQ: 21
000006dc.00001488::2014/04/29-12:23:10.436 WARN [RCM] Failed to load restype 'MSMQ': error 21.
00000ad8.00001580::2014/04/29-12:23:10.438 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
000006dc.00001488::2014/04/29-12:23:10.438 INFO [RCM] result of first load attempt for type MSMQTriggers: 21
000006dc.00001488::2014/04/29-12:23:10.438 WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
000006dc.00001488::2014/04/29-12:23:10.438 ERR [RCM] [GIM] ResType Máquina virtual has no resources, not collecting local utilization info
000006dc.00001488::2014/04/29-12:23:10.439 INFO [RCM] [GIM] Scheduling Local Node Crawler to run in 300000 millisec.
00000ad0.00000dac::2014/04/29-12:23:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.00000dac::2014/04/29-12:23:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.00000dac::2014/04/29-12:23:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.00000dac::2014/04/29-12:23:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.00000dac::2014/04/29-12:23:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.00000dac::2014/04/29-12:23:12.673 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:23:12.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:23:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:12.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:23:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
000006dc.00001488::2014/04/29-12:23:15.802 INFO [CLI] Get last update time from db
000006dc.00001488::2014/04/29-12:23:15.802 INFO [CLI] forming node has not updated last update time yet
000006dc.00001488::2014/04/29-12:23:15.803 INFO [CLI] UpdatePasswordPolicy len 8 secs maxage 2592000 secs
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] UpdatePasswordPolicy curreAge 180 secs
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] UpdatePasswordPolicy - maxAge 30 days passAge 0 days
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] Password MaxAge 30 DisablePasswordChange 0
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] Password MaxAge 30 after checking with clusterdb
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] Update CAM now
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] DeCryptPassword successful
000006dc.00001488::2014/04/29-12:23:15.804 INFO [CLI] Update user passwd
000006dc.00001488::2014/04/29-12:23:15.823 INFO [CLI] User passwd updated
0000021c.00000f88::2014/04/29-12:23:15.823 INFO [CAM] CamApCallPackage
0000021c.00000f88::2014/04/29-12:23:15.823 INFO [CAM] CallInfo: Proc 1756 Thread 5256 Count 0 Att 512
0000021c.00000f88::2014/04/29-12:23:15.823 INFO [CAM] ClientInfo: Logon 999 Proc 1756 Thread 5256 TCB 1 Impersonating 1 Restrict 0 Flags 0
0000021c.00000f88::2014/04/29-12:23:15.823 INFO [CAM] SetCNOCred 1756 14 10 74 0
0000021c.00000f88::2014/04/29-12:23:15.823 INFO [CAM] Setting User CLIUSR, Dom SQL2 (Proc 1756)
0000021c.00000f88::2014/04/29-12:23:15.823 INFO [CAM] IsCredentialsReplacementNeeded - Passwords match
000006dc.00001488::2014/04/29-12:23:15.823 INFO [CLI] LsaCallAuthenticationPackage: 0, 0 size: 0, buffer: HDL( 0 )
000006dc.00001488::2014/04/29-12:23:15.823 INFO [CLI] Credentials Notified
000006dc.00001488::2014/04/29-12:23:15.823 INFO [CLI] IsLocalIdentityExpired age 0 maxage 30
000006dc.00001488::2014/04/29-12:23:15.823 INFO [CLI] IsLocalIdentityExpired, password not expired
00000ad0.00000dac::2014/04/29-12:23:17.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:23:17.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:23:17.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:23:17.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:23:22.728 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:23:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:22.728 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:23:22.728 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:23:27.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:23:27.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:23:27.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:23:27.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:23:32.729 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:23:32.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:32.729 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:23:32.729 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:23:37.730 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:23:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:23:37.730 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:23:37.730 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:23:42.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:23:42.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:42.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:23:42.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:23:47.731 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:23:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:23:47.731 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:23:47.731 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:23:52.732 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:23:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:23:52.732 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:23:52.732 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
000006dc.00000044::2014/04/29-12:23:56.018 INFO [NM] Received request from client address ::1.
00000ad0.00000dac::2014/04/29-12:23:57.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:23:57.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:23:57.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:23:57.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:24:02.733 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:24:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:24:02.733 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:24:02.733 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:24:07.734 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.0000054c::2014/04/29-12:24:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.0000054c::2014/04/29-12:24:07.734 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.0000054c::2014/04/29-12:24:07.734 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.00000dac::2014/04/29-12:24:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
00000ad0.00000dac::2014/04/29-12:24:12.670 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
00000ad0.00000dac::2014/04/29-12:24:12.672 INFO [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
00000ad0.00000dac::2014/04/29-12:24:12.672 INFO [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
00000ad0.00000dac::2014/04/29-12:24:12.672 INFO [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:24:12.672 INFO [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
00000ad0.00000dac::2014/04/29-12:24:12.672 INFO [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000ad0.0000054c::2014/04/29-12:24:12.727 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
00000ad0.00000dac::2014/04/29-12:24:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
00000ad0.00000dac::2014/04/29-12:24:12.727 INFO [RES] Network Name: [NN] got sync reply: 0
00000ad0.00000dac::2014/04/29-12:24:12.727 INFO [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: IdleHi,
Thanks for your post, but unfortunately this is a English forum, The English will more appropriate for all the forum members. Please try to use the English ,Thanks for your
understanding and cooperation.
As far as I know The VMware ESXI® product not certificated by Windows, so you can ‘t get the official support. Personal point is you need first confirm your CSV is work fine,
then disable all cluster node firewall and AV soft then try again.
More information:
Requirements and Recommendations for a Multi-Site Failover Cluster
http://technet.microsoft.com/en-us/library/dd197575(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
RMAN to connect to all nodes within the cluster to parallelize backups
Hi,
I wish to configure my RMAN catalog to backup my Production RAC backups. I wish to parallelize my backups to backup database files of different nodes.
Can anyone help me how can it be done?
Regards,
SriniHi,
May be you are right. I see my RAC cluster databases grow very fast and some nodes are not really performing well resources wise. So, i may need to parallalize the backups across the nodes.
However, i have another idea of finding the best node and take backup on it. checking with my system admins at this point.
Is there any way RMAN can know if the node went down so that it needs to backup the database on a different node instead of the first node it attempted?
May be this is a different question.
Regards,
srini -
Publishing does not clear cache on secondary node on the cluster
Hello,
I am publishing assets from Management to Delivery. Delivery consists of 2 nodes, one of which is the publish destination for the management. So, after a publish, I could see the updated content on Delivery 1 (cs/Satellite) but Delivery 2 (cs/Satellite) still shows stale content.
I checked the following properties on ft.ini and it's holding correcting values
cc.cacheNoSync, ft.sync, ft.usedisksync
Any help/pointers is very much appreciated.
Thanks!Seems like your cache flushing is not working correctly - easiest way to see if your system is configured correctly with regard to the satellite servers - go into support tools / cache / list pages - pick Satellite - - it will log (remotely) onto both satellites and list the inventory - it validates the entries in your system satellite table - that table needs to list all of your delivery satellite servers and credentials -
-
Public Interface not responding after second node is started in the cluster
Hi
Has anyone ever experienced the public interface not responding between nodes in the cluster (ping, ssh, scp) after the second nodeapps is started in the cluster?
This is a new install so all I have installed so far is the base release of CRS 10.2.0. This is on Solaris10. The vipca failed during the installation, however I was able to proceed and manually add the nodeapps using srvctl add nodeaps -n -o -A.
It seems after the second node is started I loose all connectivity to the public interfaces and to my default gateway.
Also I'm getting the following messages sometimes after I try and stop the nodeapps and start them back up.
CRS-1006: No more members to consider
CRS-0215: Could not start resource 'ora.node1.vip'.
Any suggestions on where I should start troubleshooting?
ThanksDo you have default GW?
It can connects with GW, can't it?
Check metalink
CRS-0215: Could not start resource 'ora..vip' [ID 356535.1]
CRS-1006: No more members to consider when starting service [ID 465364.1]
Good Luck -
On start node ina cluster a have Error OSB-Reporting BEA-473500
every time that I start my node in the cluster I have this error:
<Error> <OSB-Reporting> <BEA-473500>
I'm using Oracle Service Bus 11g
what I should do to solve this?Hi Alex,
I would suggest you to check with your network team because BEA-000109 error which points to the NIC card and the network issues.
Ensure that no physical problems exist in your network:
- Verify the network connection for each machine that hosts servers within the cluster.
- Verify that all components of the network, including routers and DNS servers, are connected and functioning correctly.
- Address conflicts within a network can disrupt multicast communications.
- Use the netstat utility to verify that no other network resources are using the cluster multicast address.
- Verify that each machine has a unique IP address.
Workaround: Try using a different multicast address.
Detail Information about the Error Code BEA-000109
Error: An error occurred while sending multicast message:
Description: An IO error occurred while trying to send a message over multicast.
Cause: An error occurred while trying to send a message over multicast.
Action :WebLogic Server will try to recover from this error. If the problem continues to persist, make sure that the network infrastructure and NIC are functioning properly.
a) Suggest you to change the address and port to be certainly unique to have another try.
Is your machine multihomed for managed server?
b) If it is, try specifying Interface Address for each server.
From admin console, you can go to the managed server -> Configuration -> Cluster ->
Interface Address.
Hope this helps.
Thanks,
Cris -
Node removed from the cluster and cannot joined to clustr again
Hi
I have problem with 2 node cluster. we are running windows 2008 R2 enterprise edition. Suddenly one node had some issue with network connnectivity and it was removed from the cluster. on the console its shows node1 offline. connectivity between the
server public and private nic is fine.
Node 'node1' failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available.
Cluster resource 'File Share Witness' in clustered service or application 'Cluster Group' failed.
'File Share Witness is accessible to both the nodes. from the cluster log i can see failed to attempt lock on the FSW.
I have restarted the failure node. still the problem exist.
Thanks in advance to throw some valuable answers to my issue.Are you using Volume Manager Disk Group. Please check the below link if you are using it.
http://www.symantec.com/business/support/index?page=content&id=TECH127796
Thanks,
Umesh.S.K -
How to address message to the specific node of the ESB cluster
Hi!
We are running ESB on two node active-active cluster configuration. We use custom adapter to communicate with customer legacy system over Socket connection. The point is, that we need to transfer large amount of data from our database into customer system using one open socket connection. Because of memory limitation we had to split data into multiple messages in ESB. This socket connection can be open from any of the active cluster node, but ones it's open all messages must be send within the node which had open the connection.So, the messages should not arrive into another node. The question: How is it possible to address (route) ESB messages into specific node of the cluster?
Thanks in advance.
Jaro,Muthu92 wrote:
Thank you for your reply. It is very useful for me. But i can't give conditional operator in that operator. It is showing error.
My Test cases
A[0]+A[1]>150
A[31]-50 <100.
If those are your exact statements, then they don't make sense in a formula node. You have to use them in an if-statement or some other type of control logic. This mimics text-based programming languages such as C... See here for instructions on formula node syntax: http://zone.ni.com/reference/en-XX/help/371361G-01/lvhowto/formula_node_syntax/
For instance, you COULD say something like:
**In this example, let A[0] == x, A[1] == y, A[31] == z**
if(x+y>150)
/* do something if this is true */
else if(z-50 < 100)
/* do something else */
EDIT:
It should also be noted that Variable Names MUST be lowercase!! I just discovered this
EDIT2:
I stand corrected. After trying to create an example and digging through the LabVIEW Help, I stumbled across this:
Differences between the Parser in the Mathematics VIs and the Formula Node
The parser in the Mathematics VIs supports all elements that Formula Nodes support with the following exceptions:
Variables—Only a, a0, ..., a9, ... z, z0, ..., z9, are valid.
Logical, conditional, inequality, equality—?:,, &&, !=, ==, <, >, <=, and >= are not valid.
Functions—atan2, max, min, mod, pow, rem, and sizeOfDim are not valid. You can use these functions in a Formula Node or use their corresponding LabVIEW functions.
So it DOES NOT seem like Eval Formula Node can do conditionals like you want. I would just implement them using a LabVIEW based algorithm after all. Trying to out smart the formula nodes to avoid simple LabVIEW code is just too much of a hassle
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos! -
Regarding number of nodes in endeca cluster
Hi,
I have a question regarding number of nodes in the endeca server cluster.
Our solution contains one data domain running in a endeca cluster with two nodes.
Endeca server documentation recommends to run the cluster with atleast 3 nodes however our solution can't accomdate another server straight away.
Can anyone please suggest what are the implication of running the cluster with two nodes like
1. Can the cluster still serve the request if one node goes down?
2, How the leader promoting works if a node goes down?
Thank you,
regards,
rpHi rp,
You can definitely start with two nodes and then add another Endeca Server node later, if needed. It is recommended to run a cluster of three, for increased availability.
Here are some answers to you questions about the cluster behavior:
Q: Can the cluster still serve the request if one node goes down?
A: Quoting from this portion of the Endeca Server Cluster Guide > How enhanced availability is achieved:
Availability of Endeca Server nodes
In an Endeca Server cluster with more than one Endeca Server instance, an ensemble of the Cluster Coordinator services running on a subset of nodes in the Endeca Server cluster ensures enhanced availability of the Endeca Server nodes in the Endeca Server cluster.
When an Endeca Server node in an Endeca Server cluster goes down, all Dgraph nodes hosted on it, and the Cluster Coordinator service (which may also be running on this node) also go down. As long as the Endeca Server cluster consists of more than one node, this does not disrupt the processing of non-updating user requests for the data domains. (It may negatively affect the Cluster Coordinator services. For information on this, see Availability of Cluster Coordinator services.)
If an Endeca Server node fails, the Endeca Server cluster is notified and stops routing all requests to the data domain nodes hosted on that Endeca Server node, until you restart the Endeca Server node.
Let's consider an example that helps illustrate this case. Consider a three-node single data domain cluster hosted on the Endeca Server cluster consisting of three nodes, where each Endeca Server node hosts one Dgraph node for the data domain. In this case:
If one Endeca Server node fails, incoming requests will be routed to the remaining nodes.
If the Endeca Server node that fails happens to be the node that hosts the leader node for the data domain cluster, the Endeca Server cluster selects a new leader node for the data domain from the remaining Endeca Server nodes and routes subsequent requests accordingly. This ensures availability of the leader node for a data domain.
If the Endeca Server node goes down, the data domain nodes (Dgraphs) it is hosting are not moved to another Endeca Server node. If your data domain has more than two nodes dedicated to processing queries, the data domain continues to function. Otherwise, query processing for this data domain may stop until you restart the Endeca Server node.
When you restart the failed Endeca Server node, its processes are restarted by the Endeca Server cluster. Once the node rejoins the cluster, it will rejoin any data domain clusters for the data domains it hosts. Additionally, if the node hosts a Cluster Coordinator, it will also rejoin the ensemble of Cluster Coordinators.
Q: How the leader promoting works if a node goes down? See part of the answer above. Also, this: (from the same topic, but later in text)
Failure of the leader node. When the leader node goes offline, the Endeca Server cluster elects a new leader node and starts sending updates to it. During this stage, follower nodes continue maintaining a consistent view of the data and answering queries. When the node that was the leader node is restarted and joins the cluster, it becomes one of the follower nodes. Note that is also possible that the leader node is restarted and joins the cluster before the Endeca Server cluster needs to appoint a new leader node. In this case, the node continues to serve as the leader node.If the leader node in the data domain changes, the Endeca Server continues routing those requests that require the leader node to the Endeca Server cluster node hosting the newly appointed leader node.
Note: If the leader node in the data domain cluster fails, and if an outer transaction has been in progress, the outer transaction is not applied and is automatically rolled back. In this case, a new outer transaction must be started. For information on outer transactions, see the section about the Transaction Web Service in the Oracle Endeca Server Developer's Guide.
Failure of a follower node. When one of the follower nodes goes offline, the Endeca Server cluster starts routing requests to other available nodes, and attempts to restart the Dgraph process for this follower node. Once the follower node rejoins the cluster, the Endeca Server adjusts its routing information accordingly.
You may ask, why do you need three nodes then? This is to achieve the high availability of the cluster services themselves.
Quoting:
If you do not configure at least three Endeca Server nodes to run the Cluster Coordinator service, the Cluster Coordinator service will be a single point of failure. Should the Cluster Coordinator service fail, access to the data domain clusters hosted in the Endeca Server cluster becomes read-only. This means that it is not possible to change the data domains in any way. You cannot create, resize, start, stop, or change data domains; you also cannot define data domain profiles. You can send read queries to the data domains and perform read operations with the Cluster and Manage Web Services, such as listing data domains or listing nodes. No updates, writes, or changes of any kind are possible while the Cluster Coordinator service in the Endeca Server cluster is down — this applies to both the Endeca Server cluster and data domain clusters. To recover from this situation, the Endeca Server instance that was running a failed Cluster Coordinator must be restarted or replaced (the action required depends on the nature of the failure).
Julia -
Cloned two vm cluster nodes from development cluster to act as template to create production cluster
Morning,
There was so much done to setup the development cluster, I thought it would be easy to have the two nodes in the cluster cloned. To my surprise, the development cluster was up and happily running on the new vm servers. Stopping resources verifies
it is stopping and starting resources on the original cluster. I am not sure how to safely have the two new servers not manage the development cluster and create a new production cluster on them.
I am hesitant to destroy the cluster as I suspect it will destroy the real development cluster. How do I do this? How do I delete the windows cluster software and re-install without affecting the development cluster?
Note that I tried to create a new cluster in the failover cluster manager and specify the new vm cluster servers, but it says they are part of a cluster already. I do not see them listed as nodes. I am not sure how to see what cluster it thinks
the new servers are part of or how to not make them part of the development cluster. That might be the path to my solution.This actually has worked out okay. I found these steps and did them on both of the nodes that were claiming to be in a cluster already:
powershell
Import-Module FailoverClusters;
clear-clusternode
Maybe you are looking for
-
10.3.9 does not print anymore , but command lp does !!
Hi to everybody, im using a HP Laserjet with my Imac connected via ethernet and appletalk. Since some days im not able to print anymore. If I try to print something with apples standard text-editor a requester is shown immediately saying "error while
-
How can the new MobileMe cloud calendars be published locally?
I tried upgrading to the new cloud-based MobileMe calendars twice before the forced upgrade date. Both times I was disappointed (as I was this time), because floating timezone events had their times shifted as though I worked for Apple (i.e. to Pacif
-
I just installed LR CC and it won't work.
I just get a quick snapshot of the initial window, and that's it. I am a Macbook Pro user, been using creative cloud for a while, and I still have installed Lightroom 5, don't know if that helps.
-
Hi all, We have enabled extend features for adobe reader using adobe acrobat 8.0. But few days after its showing error as below "This document enabled extended features in Adobe Reader. The document has been changed since it was created and use of ex
-
JUnit - How to assert exception is thrown?
If I use JUnit how do I assert an exception is thrown when I pass invalid parameters to a method I am testing? For example if I pass a username to a method that I know will cause the method to throw an InvalidUsernameException how do I assert this?