Yes, the hostname is correct and the FQDN. The results of hostname and the contents of the hosts file is shown below.
============================= [EMAIL PROTECTED] ~]# hostname bbcsrv2.biotech.uconn.edu [EMAIL PROTECTED] ~]# cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 192.168.0.1 oscarhead.biotech.uconn.edu oscarhead oscar_server nfs_oscar pbs_oscar 137.99.46.11 bbcsrv2.biotech.uconn.edu bbcsrv2 # These entries are managed by SIS, please don't modify them. 192.168.0.2 oscarnode1.biotech.uconn.edu oscarnode1 192.168.0.3 oscarnode2.biotech.uconn.edu oscarnode2 [EMAIL PROTECTED] ~]# ============================= Thanks, Jeff. -----Original Message----- From: [EMAIL PROTECTED] on behalf of Michael Edwards Sent: Mon 11/19/2007 3:30 PM To: oscar-users@lists.sourceforge.net Subject: Re: [Oscar-users] Kernel panic after node PXE install on Dell PE 860 The error is fundamentally a problem of mistaken identity. Basically Torque is very picky and for some reason it isn't recognising that root is a valid user for your server. Its generally a problem with /etc/hosts not being set up the way OSCAR or Torque expects it, with the most common problem being the counterintuitive convention with the public/private interface. Is the result of "hostname" the fully qualified domain name of the server? On Nov 19, 2007 2:55 PM, Lary, Jeffrey <[EMAIL PROTECTED]> wrote: > OK. It's link is http://pastebin.ca/784634 > > Thanks, > Jeff. > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of Michael > Edwards > Sent: Mon 11/19/2007 2:19 PM > To: oscar-users@lists.sourceforge.net > Subject: Re: [Oscar-users] Kernel panic after node PXE install on Dell PE > 860 > > The log file seems to have been stripped by your mail server, could you > post > the log at http://pastebin.ca ? > > On Nov 19, 2007 2:09 PM, Lary, Jeffrey <[EMAIL PROTECTED]> wrote: > > > No, it failed in the Torque setup and the MTA, plus some other small > stuff > > between the Torque and MTA (the logfile was attached previously so I > won't > > put it back here again). > > > > Thanks, > > Jeff Lary > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] on behalf of Michael > > Edwards > > Sent: Mon 11/19/2007 1:16 PM > > To: oscar-users@lists.sourceforge.net > > Subject: Re: [Oscar-users] Kernel panic after node PXE install on Dell > PE > > 860 > > > > Was the "Complete Cluster Setup" step successful? > > > > On Nov 19, 2007 11:57 AM, Lary, Jeffrey <[EMAIL PROTECTED]> wrote: > > > > > Michael, > > > hostname gives the correct result, i.e. that of the external > interface. > > > > > > Thanks, > > > Jeff Lary > > > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] on behalf of Michael > > > Edwards > > > Sent: Mon 11/19/2007 11:52 AM > > > To: oscar-users@lists.sourceforge.net > > > Subject: Re: [Oscar-users] Kernel panic after node PXE install on Dell > > PE > > > 860 > > > > > > Make sure that the result of "hostname" is the -external- network > > > interface. This is not usually the interface used by the OSCAR > > installer. > > > > > > Theres some other tips on two network interface setups here. > > > > > > > > > > > > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/TipTwoNetworkInterfaces > > > > > > On Nov 19, 2007 11:20 AM, Lary, Jeffrey <[EMAIL PROTECTED]> > wrote: > > > > > > > Thank you for your reply. I was able, with the help given in the > > link, > > > to > > > > PXE image and successfully boot the two nodes. > > > > Now on to the next problem. I ran Step 7 to complete the cluster > > setup > > > > and it failed on the Torque queue setup and multiple errors down > > through > > > to > > > > the end with a failure in the MTA setup. I've attached a compressed > > > > oscarinstall.log. The pbs_server.log mainly shows the error. > > > > > > > > "11/19/2007 11:16:30;0080;PBS_Server;Req;req_reject;Reject reply > > > > code=15064(Server has no node list), aux=0, type=StatusNode, from > > > > [EMAIL PROTECTED]" > > > > > > > > > > > > Any help would be greatly appreciated. > > > > > > > > Thanks, > > > > Jeff Lary. > > > > > > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] on behalf of Michael > > > > Edwards > > > > Sent: Sat 11/17/2007 12:03 PM > > > > To: oscar-users@lists.sourceforge.net > > > > Subject: Re: [Oscar-users] Kernel panic after node PXE install on > Dell > > > PE > > > > 860 > > > > > > > > Dell likes to use funny drivers which don't always get detected > > properly > > > > by > > > > the scripts which SIS (and therefore OSCAR) use for detecting > > hardware. > > > > Look at the PE1955 bits of this howto and see if they help you. > > > > > > > > http://svn.oscar.openclustergroup.org/trac/oscar/wiki/TipLDAP > > > > > > > > Since you have identical hardware on the head and the compute nodes, > I > > > > would > > > > use the modprobe.conf on the head node to base the node one on > instead > > > of > > > > the one for the PE1955. > > > > > > > > On Nov 17, 2007 11:08 AM, Lary, Jeffrey <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > I have three identical PE 860s. I installed CentOS 4.5 x86_64 on > > one > > > > > (head node) without any problems. I installed Oscar > 5.0successfully > > > > and > > > > > proceeded all the way through Step 6. I PXE booted one of the > other > > > > nodes > > > > > and the installation, via PXE, proceeded through to completion and > > the > > > > node > > > > > rebooted. At that point it went through the grub kernel selection > > > > screen > > > > > and continued on through the boot process. Soon the boot sequence > > > > stopped, > > > > > ending with a kernel panic. The last few lines are shown below - > > > > > > > > > > ... > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Microsoft > > > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > > _______________________________________________ > > > > Oscar-users mailing list > > > > Oscar-users@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > > _______________________________________________ > > > Oscar-users mailing list > > > Oscar-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Oscar-users mailing list > > Oscar-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Oscar-users mailing list > Oscar-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oscar-users > >
<<winmail.dat>>
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
