Windows Vista Tips
Home Register Members Search Windows Vista Tips File Database Links
Member Login:

Windows Vista Tips > Newsgroups > Windows Server > Clustering > Issue with Node since reboot

Reply
Thread Tools Display Modes

Issue with Node since reboot

 
 
Lee
Guest
Posts: n/a

 
      01-04-2009
Hi all,

We rebooted a node as we kept getting file shares going offline with error
code 1450.
After the last reboot the cluster service will not start. Event log says
the following.

Event Type: Error
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1000
Date: 04/01/2009
Time: 07:42:58
User: N/A
Computer: S-MPL-GPMS1
Description:
Cluster service suffered an unexpected fatal error at line 951 of source
module d:\nt\base\cluster\service\dm\dmsync.c. The error code was 6.

Get these in the last few lines of my cluster.log....

00000b64.000018b8::2009/01/04-07:49:16.614 INFO [NMJOIN] Establishing
security contexts with all active nodes.
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] Establishing
outbound security context with the NTLM package.
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
security context to node 2 was initialized, status 00090312.
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
security context was accepted by node 2, status 0x00090312.
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
security context to node 2 was initialized, status 00000000.
00000b64.00001e58::2009/01/04-07:49:16.614 INFO [ClMsg] Establishing inbound
security context with node 2, sequence 62984
00000b64.00001e58::2009/01/04-07:49:16.614 INFO [ClMsg] The inbound security
context from node 2 using the NTLM package was accepted, status 00090312
00000b64.00001e58::2009/01/04-07:49:16.614 INFO [ClMsg] The inbound security
context from node 2 using the NTLM package was accepted, status: 00000000
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
security context was accepted by node 2, status 0x00000000.
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] Importing security
contexts from NTLM package.
00000b64.000018b8::2009/01/04-07:49:16.614 INFO [NMJOIN] Petitioning to join
cluster membership.
00000b64.00001e58::2009/01/04-07:49:16.614 INFO [RGP] Node 1: RGP Debug
event : 0xf, 0x1, 0x0, 0x0.
00000b64.00001e58::2009/01/04-07:49:16.614 INFO [RGP] Node 1: RGP SetRGPInfo
: 0x1, 0x2, 0x4, 0x4000.
00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Debug
event : 0xc, 0x1, 0x0, 0x0.
00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Monitor
node: 0x1, 0x0, 0xc000, 0xc000.
00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Debug
event : 0xa, 0x1, 0x0, 0x0.
00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Start
called: 0x0, 0x1091a45, 0x0, 0x0.
00000b64.000018b8::2009/01/04-07:49:17.223 INFO [GUM] GumpNodeCallback
setting node 2 active.
00000b64.000018b8::2009/01/04-07:49:17.223 INFO [GUM] GumBeginJoinUpdate
succeeded with sequence 62985 for type 1
00000b64.000018b8::2009/01/04-07:49:17.223 INFO [DM] DmJoin: getting new
registry database
00000b64.00001f64::2009/01/04-07:49:17.395 INFO [JOIN] No need to ask
S-MPL-GPMS2 to sponsor us after delay of 1000 milliseconds.
00000b64.00001b3c::2009/01/04-07:49:17.395 INFO [JOIN] No need to ask
10.0.0.14 to sponsor us after delay of 1000 milliseconds.
00000b64.00001e48::2009/01/04-07:49:18.020 INFO [ClMsg] Received interface
up event for node 2 network 2
00000b64.00000eac::2009/01/04-07:49:18.020 INFO [NM] Communication was
(re)established with interface 61062ab1-782d-4045-a531-10a543321476 (node:
S-MPL-GPMS2, network: Cluster VNIC)
00000b64.00001e48::2009/01/04-07:49:18.020 INFO [ClMsg] Received interface
up event for node 2 network 1
00000b64.00000eac::2009/01/04-07:49:18.020 INFO [NM] Scheduled network
connectivity report worker thread.
00000b64.00000eac::2009/01/04-07:49:18.020 INFO [NM] Communication was
(re)established with interface 6bae9d29-b0d6-48fb-89ab-0fd360f71f8b (node:
S-MPL-GPMS2, network: DEFAULT_VLAN VNIC)
00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Connectivity report
worker thread running.
00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Updating local
connectivity info for network 5d5b0937-ca6c-4b04-9a5b-6b78838b0e42.
00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Reporting connectivity
to sponsor for network 5d5b0937-ca6c-4b04-9a5b-6b78838b0e42.
00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Updating local
connectivity info for network c7a85fa6-dab0-4880-8e05-2ae38143e216.
00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Reporting connectivity
to sponsor for network c7a85fa6-dab0-4880-8e05-2ae38143e216.
00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Connectivity report
worker thread finished.
00000b64.00001f14::2009/01/04-07:49:18.395 INFO [JOIN] No need to ask
172.20.104.41 to sponsor us after delay of 2000 milliseconds.
00000b64.000018b8::2009/01/04-07:49:26.565 INFO [Qfs] QfsGetTempFileName
C:\DOCUME~1\cluster\LOCALS~1\Temp\, CLS, 0 => , status 80
00000b64.000018b8::2009/01/04-07:49:30.205 INFO [Qfs] QfsGetTempFileName .,
CLS, 0 => , status 80
00000b64.000018b8::2009/01/04-07:49:30.205 ERR Cluster service suffered an
unexpected fatal error at line 951 of source module
d:\nt\base\cluster\service\dm\dmsync.c. The error code was 6.
 
Reply With Quote
 
 
 
 
John Fullbright
Guest
Posts: n/a

 
      01-04-2009
What's in C:\DOCUME~1\cluster\LOCALS~1\Temp\ ?
How much space is on C:?


"Lee" <> wrote in message
news:E09EAB5D-7D9F-4DD8-9150-...
> Hi all,
>
> We rebooted a node as we kept getting file shares going offline with error
> code 1450.
> After the last reboot the cluster service will not start. Event log says
> the following.
>
> Event Type: Error
> Event Source: ClusSvc
> Event Category: Database Mgr
> Event ID: 1000
> Date: 04/01/2009
> Time: 07:42:58
> User: N/A
> Computer: S-MPL-GPMS1
> Description:
> Cluster service suffered an unexpected fatal error at line 951 of source
> module d:\nt\base\cluster\service\dm\dmsync.c. The error code was 6.
>
> Get these in the last few lines of my cluster.log....
>
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [NMJOIN] Establishing
> security contexts with all active nodes.
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] Establishing
> outbound security context with the NTLM package.
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
> security context to node 2 was initialized, status 00090312.
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
> security context was accepted by node 2, status 0x00090312.
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
> security context to node 2 was initialized, status 00000000.
> 00000b64.00001e58::2009/01/04-07:49:16.614 INFO [ClMsg] Establishing
> inbound
> security context with node 2, sequence 62984
> 00000b64.00001e58::2009/01/04-07:49:16.614 INFO [ClMsg] The inbound
> security
> context from node 2 using the NTLM package was accepted, status 00090312
> 00000b64.00001e58::2009/01/04-07:49:16.614 INFO [ClMsg] The inbound
> security
> context from node 2 using the NTLM package was accepted, status: 00000000
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] The outbound
> security context was accepted by node 2, status 0x00000000.
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [ClMsg] Importing security
> contexts from NTLM package.
> 00000b64.000018b8::2009/01/04-07:49:16.614 INFO [NMJOIN] Petitioning to
> join
> cluster membership.
> 00000b64.00001e58::2009/01/04-07:49:16.614 INFO [RGP] Node 1: RGP Debug
> event : 0xf, 0x1, 0x0, 0x0.
> 00000b64.00001e58::2009/01/04-07:49:16.614 INFO [RGP] Node 1: RGP
> SetRGPInfo
> : 0x1, 0x2, 0x4, 0x4000.
> 00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Debug
> event : 0xc, 0x1, 0x0, 0x0.
> 00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Monitor
> node: 0x1, 0x0, 0xc000, 0xc000.
> 00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Debug
> event : 0xa, 0x1, 0x0, 0x0.
> 00000b64.00001e58::2009/01/04-07:49:17.223 INFO [RGP] Node 1: RGP Start
> called: 0x0, 0x1091a45, 0x0, 0x0.
> 00000b64.000018b8::2009/01/04-07:49:17.223 INFO [GUM] GumpNodeCallback
> setting node 2 active.
> 00000b64.000018b8::2009/01/04-07:49:17.223 INFO [GUM] GumBeginJoinUpdate
> succeeded with sequence 62985 for type 1
> 00000b64.000018b8::2009/01/04-07:49:17.223 INFO [DM] DmJoin: getting new
> registry database
> 00000b64.00001f64::2009/01/04-07:49:17.395 INFO [JOIN] No need to ask
> S-MPL-GPMS2 to sponsor us after delay of 1000 milliseconds.
> 00000b64.00001b3c::2009/01/04-07:49:17.395 INFO [JOIN] No need to ask
> 10.0.0.14 to sponsor us after delay of 1000 milliseconds.
> 00000b64.00001e48::2009/01/04-07:49:18.020 INFO [ClMsg] Received interface
> up event for node 2 network 2
> 00000b64.00000eac::2009/01/04-07:49:18.020 INFO [NM] Communication was
> (re)established with interface 61062ab1-782d-4045-a531-10a543321476 (node:
> S-MPL-GPMS2, network: Cluster VNIC)
> 00000b64.00001e48::2009/01/04-07:49:18.020 INFO [ClMsg] Received interface
> up event for node 2 network 1
> 00000b64.00000eac::2009/01/04-07:49:18.020 INFO [NM] Scheduled network
> connectivity report worker thread.
> 00000b64.00000eac::2009/01/04-07:49:18.020 INFO [NM] Communication was
> (re)established with interface 6bae9d29-b0d6-48fb-89ab-0fd360f71f8b (node:
> S-MPL-GPMS2, network: DEFAULT_VLAN VNIC)
> 00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Connectivity report
> worker thread running.
> 00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Updating local
> connectivity info for network 5d5b0937-ca6c-4b04-9a5b-6b78838b0e42.
> 00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Reporting
> connectivity
> to sponsor for network 5d5b0937-ca6c-4b04-9a5b-6b78838b0e42.
> 00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Updating local
> connectivity info for network c7a85fa6-dab0-4880-8e05-2ae38143e216.
> 00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Reporting
> connectivity
> to sponsor for network c7a85fa6-dab0-4880-8e05-2ae38143e216.
> 00000b64.00001cbc::2009/01/04-07:49:18.020 INFO [NM] Connectivity report
> worker thread finished.
> 00000b64.00001f14::2009/01/04-07:49:18.395 INFO [JOIN] No need to ask
> 172.20.104.41 to sponsor us after delay of 2000 milliseconds.
> 00000b64.000018b8::2009/01/04-07:49:26.565 INFO [Qfs] QfsGetTempFileName
> C:\DOCUME~1\cluster\LOCALS~1\Temp\, CLS, 0 => , status 80
> 00000b64.000018b8::2009/01/04-07:49:30.205 INFO [Qfs] QfsGetTempFileName
> .,
> CLS, 0 => , status 80
> 00000b64.000018b8::2009/01/04-07:49:30.205 ERR Cluster service suffered
> an
> unexpected fatal error at line 951 of source module
> d:\nt\base\cluster\service\dm\dmsync.c. The error code was 6.
>
>
 
Reply With Quote
Reply

« Duplicate mac addresses on HP Proliant BL460c G1 servers? | Generic Script resource to interact with desktop »
Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
reboot a 2 node file cluster Phillip McIntosh Clustering 4 06-13-2007 06:54 PM
Problems that occur when you reboot both nodes of a 2 node cluster cmenard Clustering 1 05-01-2007 04:01 PM
Cluster node failover takes very long only from Node A to Node B arrowman Clustering 4 05-10-2006 06:45 PM
Failing Virt. Server on node 1 to node 2 and VS on node 2 to node JM Clustering 3 05-13-2005 12:05 AM
Cluster node reboot Chris Chan [Founder Globaltech] Clustering 4 04-21-2005 11:40 PM


Forum Software Powered by vBulletin®, Copyright Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc.
Contact Us - Windows Vista Tips - Archive - Privacy Statement - Top

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59