[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ssic-linux-users
Subject:    RE: [SSI-users] Node2 stops booting after ipcname_read completed
From:       Karl Vogel <karl.vogel () seagha ! com>
Date:       2003-10-28 15:43:48
[Download RAW message or body]

Just a guess.. at boot the port on the switch might block for 
1-2 minutes because of spanning-tree updates. On a cisco switch 
you have a setting which you can use to disable this behaviour.

ie. on a cisco switch add
	spanning-tree portfast

to the interface config. You should only do this on ports with
PC's attached to it, certainly no other switches else you could
create loops!

Karl


> -----Original Message-----
> From: Walker, Bruce J [mailto:bruce.walker@hp.com]
> Sent: Tuesday, October 28, 2003 16:26
> To: Ehringer, Patrick; Zafman, David
> Cc: ssic-linux-users@lists.sourceforge.net
> Subject: RE: [SSI-users] Node2 stops booting after ipcname_read
> completed
> 
> 
> Pat:
>   I'm glad you resolved the problem.  Does anyone understand 
> how the switch could be problem so we can help others from 
> running across this in the future?
> 
> Bruce
> 
> 
> > -----Original Message-----
> > From: Ehringer, Patrick [mailto:Patrick.Ehringer@dekabank.lu] 
> > Sent: Monday, October 27, 2003 5:14 AM
> > To: Zafman, David
> > Cc: ssic-linux-users@lists.sourceforge.net
> > Subject: Re: [SSI-users] Node2 stops booting after 
> > ipcname_read completed
> > 
> > 
> > 
> > Problem solved: The 2 nodes were interconnected before through
> > a 10/100 switch which caused the problems during the boot!!!!
> > Problem was solved by connecting the 2 netcards (interconnect)
> > directly over cross-over cable.
> > Thanks for your suggestion
> > 
> > Pat
> > DekaBank Luxembourg
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: David B. Zafman [mailto:david.zafman@hp.com]
> > Gesendet: Donnerstag, 23. Oktober 2003 22:27
> > An: Ehringer, Patrick
> > Cc: ssic-linux-users@lists.sourceforge.net
> > Betreff: Re: [SSI-users] Node2 stops booting after ipcname_read
> > completed
> > 
> > 
> > 
> > Boot up to the hang and drop into kdb by pressing ^A.  Then 
> > type "bta" 
> > and send the resulting stack traces (I hope you have a serial 
> > console). 
> >  Here is part of the log of my dependent node when it 
> boots.  This is 
> > occuring during the ramdisk phase in the /linuxrc.
> > 
> > ..
> > Gathering cluster info
> > Configuring cluster
> > Running pre-root cluster initialization
> > Searching for an existing root node...
> > Found node 1 as the root node.
> > ipcnameserver ready completed
> >                                                               
> >                  
> > This is a CI/OpenSSI kernel.
> >     This Cluster Node: 2
> >     Cluster Master Node(s): 1:192.168.0.63
> >                                                               
> >                  
> > Name server registered with clms
> > ipcname_read completed
> > Mounting root in linuxrc
> > Unmounting /proc
> > Attempting pivot_root
> > Running post-root cluster initialization
> > Starting init
> > /etc/rc.d/rc.nodeup 2 running
> > ..
> > 
> > Ehringer, Patrick wrote:
> > 
> > >Hello all,
> > >
> > >Running redhat 9.0 with 0.9.95, after upgrade from RH8.0 
> > with upgrade-kit
> > >Node 1 runs fine, when node2 comes up it will stop after:
> > >"Name server registered with clms"
> > >"ipcname_read completed"
> > >Seems waiting for input because num-lock is still working
> > >
> > >Could anyone give me a hint about this???
> > >
> > >Thanxxxxx Pat
> > 
> > 
> > 
> > "Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte
> > Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind,
> > informieren Sie bitte sofort den Absender und loeschen Sie 
> > diese E-Mail.
> > Das unbefugte Kopieren dieser E-Mail oder die unbefugte 
> Weitergabe der
> > enthaltenen Informationen ist nicht gestattet.
> > 
> > The information contained in this message is confidential 
> or protected
> > by law. If you are not the intended recipient, please contact 
> > the sender
> > and delete this message. Any unauthorised copying of this message or
> > unauthorised distribution of the information contained herein is
> > prohibited." 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: The SF.net Donation Program.
> > Do you like what SourceForge.net is doing for the Open
> > Source Community?  Make a contribution, and help us add new
> > features and functionality. Click here: 
> http://sourceforge.net/donate/
> > _______________________________________________
> > Ssic-linux-users mailing list
> > Ssic-linux-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
> > 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> Ssic-linux-users mailing list
> Ssic-linux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
> 


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Ssic-linux-users mailing list
Ssic-linux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ssic-linux-users

[prev in list] [next in list] [prev in thread] [next in thread]