Fwd: Process Restart Problem

chandant_at_indiatimes.com

To: <sunmanagers@sunmanagers.org>
Date: Tue, 26 Oct 2004 14:18:49 +0530


-- 
-Sundaram Ramasamy
------------------------------
Message: 4
Date: Fri, 22 Oct 2004 16:19:07 -0400
From: "Nicole Skyrca" <nskyrca@syr.edu>
Subject: Fwd: Sun 220R and IBM ESS (shark) array
To: <sunmanagers@sunmanagers.org>
Message-ID: <s1793315.057@gwia201.syr.edu>
Content-Type: text/plain; charset=US-ASCII
Hello,
I have a Sun 220R connected to an IBM ESS (shark) model 2150 with
McData Intrepid 6040 Director switch.  The HBA in the 220R is Sun part
x6767a (Sun SorEdge 2G FC PCI Single Channel Network Adapter).  When I
do a "cfgadm -al", more times than not, it shows my disks as failing. 
But occassionally, the command will complete with no errors. 
Some history of the machine:
When I first connected the 220R to the Shark, it was running Solaris 8
HW 2/2002, OBP 3.23.1 7/16/99 & POST 2.0.2 10/19/98, and the firmware
revision of the fiber channel card was 1.13.08 4/10/02.  With this
configuration, I was able to consistantly run "cfgadm -al" without any
errors, and the disks appeared in format. (Please note that I didn't get
to the point to install any multipathing software like mpxio or IBM's
SDD)
I decided to upgrade the OS and firmware to more recent levels. First,
I upgraded the fiber channel firmware to 1.14.09 3/8/04. Next, I upgraed
the OS to Solaris 8 HW 2/04, finally the OBP and POST to 3.31.0
7/25/2001 and 2.30 7/31/2000 respectively.  I was able to successfully
run "cfgadm -al" after each change (although I didn't run it multiple
times).  But a few days after the changes, I'm expiriencing intermittant
problems.
Does anyone have any expirience with SANS and have any clues as to what
could be the cause of the problem?  I know that I changed a lot of
stuff, so any combination of things could have broke it.  I also know
that I have a V440 running solaris 8 HW 2/04 and fiber channel cards
with the same firmware revision, and that seems to be working ok.  I'm
new to SANS so I'm not sure what else to look at. It seems that since
the hardware has not changed, it has to be something on my 220R.
Here are some examples of the cfgadm output that were run within
minutes of each other.
bash-2.03# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant    
Condition
c0                             scsi-bus     connected    configured  
unknown
c0::dsk/c0t0d0                 disk         connected    configured  
unknown
c0::dsk/c0t1d0                 disk         connected    configured  
unknown
c0::dsk/c0t6d0                 CD-ROM       connected    configured  
unknown
c1                             scsi-bus     connected    unconfigured
unknown
c2                             fc-fabric    connected    configured  
unknown
c2::10000000c9333597           unknown      connected    unconfigured
failed
c2::10000000c93335e3           unknown      connected    unconfigured
failed
c2::10000000c9333709           unknown      connected    unconfigured
failed
c2::10000000c9333796           unknown      connected    unconfigured
failed
c2::10000000c93337ee           unknown      connected    unconfigured
failed
c2::10000000c9333e8b           unknown      connected    unconfigured
failed
c2::10000000c9333f72           unknown      connected    unconfigured
failed
c2::10000000c9333f77           unknown      connected    unconfigured
failed
c2::10000000c93f29c8           unknown      connected    unconfigured
failed
c2::210000e08b04ca21           unknown      connected    unconfigured
unknown
c2::210000e08b11beb0           unknown      connected    unconfigured
unknown
c2::5005076300c39cea           disk         connected    configured  
failing
c2::5005076300c49cea           disk         connected    configured  
failing
c2::5005076300c89cea           disk         connected    configured  
failing
c2::5005076300cc9cea           disk         connected    configured  
failing
c2::5005076300cf9cea           disk         connected    configured  
unknown
c2::5005076300d09cea           disk         connected    configured  
unknown
bash-2.03# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant    
Condition
c0                             scsi-bus     connected    configured  
unknown
c0::dsk/c0t0d0                 disk         connected    configured  
unknown
c0::dsk/c0t1d0                 disk         connected    configured  
unknown
c0::dsk/c0t6d0                 CD-ROM       connected    configured  
unknown
c1                             scsi-bus     connected    unconfigured
unknown
c2                             fc-fabric    connected    configured  
unknown
c2::5005076300c39cea           disk         connected    configured  
failing
c2::5005076300c49cea           disk         connected    configured  
failing
c2::5005076300c89cea           disk         connected    configured  
failing
c2::5005076300cc9cea           disk         connected    configured  
failing
c2::5005076300cf9cea           disk         connected    configured  
failing
c2::5005076300d09cea           disk         connected    configured  
failing
bash-2.03# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant    
Condition
c0                             scsi-bus     connected    configured  
unknown
c0::dsk/c0t0d0                 disk         connected    configured  
unknown
c0::dsk/c0t1d0                 disk         connected    configured  
unknown
c0::dsk/c0t6d0                 CD-ROM       connected    configured  
unknown
c1                             scsi-bus     connected    unconfigured
unknown
c2                             fc-fabric    connected    configured  
unknown
c2::5005076300c39cea           disk         connected    configured  
failing
c2::5005076300c49cea           disk         connected    configured  
failing
c2::5005076300c89cea           disk         connected    configured  
failing
c2::5005076300cc9cea           disk         connected    configured  
failing
c2::5005076300cf9cea           disk         connected    configured  
failing
c2::5005076300d09cea           disk         connected    configured  
failing
bash-2.03# uname -a
SunOS libopac.syr.edu 5.8 Generic_117350-11 sun4u sparc SUNW,Ultra-60
bash-2.03# luxadm -e port
Found path to 1 HBA ports
/devices/pci@1f,2000/SUNW,qlc@1/fp@0,0:devctl                     
CONNECTED
bash-2.03# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant    
Condition
c0                             scsi-bus     connected    configured  
unknown
c0::dsk/c0t0d0                 disk         connected    configured  
unknown
c0::dsk/c0t1d0                 disk         connected    configured  
unknown
c0::dsk/c0t6d0                 CD-ROM       connected    configured  
unknown
c1                             scsi-bus     connected    unconfigured
unknown
c2                             fc-fabric    connected    configured  
unknown
c2::10000000c93324e7           unknown      connected    unconfigured
failed
c2::10000000c9333318           unknown      connected    unconfigured
failed
c2::10000000c9333352           unknown      connected    unconfigured
failed
c2::10000000c9333549           unknown      connected    unconfigured
failed
c2::10000000c9333597           unknown      connected    unconfigured
failed
c2::10000000c93335a1           unknown      connected    unconfigured
failed
c2::10000000c93335e3           unknown      connected    unconfigured
failed
c2::10000000c93335f2           unknown      connected    unconfigured
failed
c2::10000000c93335f3           unknown      connected    unconfigured
failed
c2::10000000c9333655           unknown      connected    unconfigured
failed
c2::10000000c9333709           unknown      connected    unconfigured
failed
c2::10000000c9333796           unknown      connected    unconfigured
failed
c2::10000000c93337ee           unknown      connected    unconfigured
failed
c2::10000000c9333827           unknown      connected    unconfigured
failed
c2::10000000c9333874           unknown      connected    unconfigured
failed
c2::10000000c9333e8b           unknown      connected    unconfigured
failed
c2::10000000c9333ee8           unknown      connected    unconfigured
failed
c2::10000000c9333f57           unknown      connected    unconfigured
failed
c2::10000000c9333f72           unknown      connected    unconfigured
failed
c2::10000000c9333f77           unknown      connected    unconfigured
failed
c2::10000000c9333fa7           unknown      connected    unconfigured
failed
c2::10000000c93400b7           unknown      connected    unconfigured
failed
c2::10000000c93486d7           unknown      connected    unconfigured
failed
c2::10000000c93f102f           unknown      connected    unconfigured
failed
c2::10000000c93f1057           unknown      connected    unconfigured
failed
c2::10000000c93f12c5           unknown      connected    unconfigured
failed
c2::10000000c93f29c8           unknown      connected    unconfigured
failed
c2::10000000c93f29ee           unknown      connected    unconfigured
failed
c2::210000e08b04ca21           unknown      connected    unconfigured
unknown
c2::210000e08b05e21b           unknown      connected    unconfigured
unknown
c2::210000e08b091ef6           unknown      connected    unconfigured
unknown
c2::210000e08b113993           unknown      connected    unconfigured
unknown
c2::210000e08b119795           unknown      connected    unconfigured
unknown
c2::210000e08b11beb0           unknown      connected    unconfigured
unknown
c2::210000e08b11c6b1           unknown      connected    unconfigured
unknown
c2::210000e08b1697ea           unknown      connected    unconfigured
unknown
c2::5005076300c39cea           disk         connected    configured  
unknown
c2::5005076300c49cea           disk         connected    configured  
unknown
c2::5005076300c89cea           disk         connected    configured  
unknown
c2::5005076300cc9cea           disk         connected    configured  
unknown
c2::5005076300cf9cea           disk         connected    configured  
unknown
c2::5005076300d09cea           disk         connected    configured  
unknown
Thanks!
Nicole
------------------------------
Message: 5
Date: Fri, 22 Oct 2004 16:55:26 -0400
From: egold@fsa.com
Subject: DISPLAY
To: sunmanagers@sunmanagers.org
Message-ID:
	<OF97E04805.BEF4F1E7-ON85256F35.0072B932-85256F35.0072F176@fsa.com>
Content-Type: text/plain; charset=US-ASCII
Hello,
I run solaris 8
I use a M$ windows pc for my desktop with exceed.
i usually run all my unix display's to ":0"
but now i want to run 2 different exceed's at once on the same pc, the
first using display:0 and the second using display:1
how do i set this up on the windows side? it seems exceed only wants to run
one instance at a time on my pc.
i know how to setup the unix side with "export DISPLAY=mypc:0" and "export
DISPLAY=mypc:1".
thank you,
E
____________________________________
This e-mail message is for the sole use of the intended recipient(s) and
may contain proprietary, confidential and/or privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited.  If you
are not the intended recipient (or an employee or agent responsible to
deliver it to the intended recipient), you may not copy or deliver this
message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply e-mail.
------------------------------
Message: 6
Date: Fri, 22 Oct 2004 22:25:18 -0500
From: "Anthony Gunia" <aggunia@comcast.net>
Subject: fssnap on Solaris 9 for x86
To: <sunmanagers@sunmanagers.org>
Message-ID: <008201c4b8af$ebcffac0$0200a8c0@susie>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Hello,
I am having a problem using fssnap on Solaris 9 x86.  I keep getting a 
prompt to enter an additional key stroke that I don't get on the SPARC 
platform when mounting the snapshot to a mount point so I can tar it up. 
Here is the portion of the script:
# mount -F ufs -o ro /dev/fssnap/`fssnap -i -o snapnumber /' /fssnap ;
>
As you can see, I get the carrot asking for another parameter which I don't 
get on the SPARC platform.  Can anyone shed some light on this for me? 
Thanks!
Anthony
aggunia@comcast.net 
------------------------------
Message: 7
Date: Sat, 23 Oct 2004 10:11:00 -0500 (CDT)
From: Ben Kim <bkim@coe.tamu.edu>
Subject: moving ld.config
To: sunmanagers@sunmanagers.org
Message-ID:
	<Pine.GSO.4.10.10410230957330.21346-100000@edsun.coe.tamu.edu>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Dear list,
I'm running Solaris 8/SPARC.
I plan to move /var to another disk since it's too small now, but am not
sure about /var/ld/ld.config. It seemed all processes are using the file
by memory mapping (fuser shows m flags for all). 
Assuming all other files are safely moved already, could someone tell me
if it'd be safe to
1. mv /var/ld /new/disk
2. ln -s /new/disk/ld /var
without going into single user mode, without rebooting, and without
restarting all processes.
What is the minimum disruption it takes to change the ld.config?
I know inodes do not change with mv but I'm not sure if it will create a
problem. (Will the file descriptor remain the same after the file is moved
and linked? If it's changed, will it cause problem with memory mapped
contents?)
I'd also appreciate any tips about whether crle can do anything regarding
this problem.
Thanks.
Ben Kim
Database Developer/Systems Administrator
College of Education 
Texas A&M University
------------------------------
Message: 8
Date: Sat, 23 Oct 2004 23:52:03 +0200
From: Koef <koef@AtosOrigin.nl>
Subject: SUMMARY: Solaris 10 for AMD64?
To: sunmanagers@sunmanagers.org
Message-ID: <20041023215203.GA15837@spooky.webbing.ao-srv.com>
Content-Type: text/plain; charset=us-ascii
Koef wrote:
> Is a Solaris 10 "preview" or "early access" available for the AMD64
> platform? I could not find it on www.sun.com.
"Not yet", "have patience" summarizes the responses. Casper *** (who
else...) had some inside information:
> Not yet; the current "Solaris Express" (as it is called) build is
> build 63, I think.  AMD64 support was added in build 70 which has
> not yet been released even internally.
Thanks to all that responded.
-- 
Koef.
------------------------------
Message: 9
Date: Sun, 24 Oct 2004 00:30:01 -0400
From: John DiMarco <jdd@cs.toronto.edu>
Subject: IMPORTANT: Read this before posting to Sun-Managers
To: sunmanagers@sunmanagers.org
Message-ID: <04Oct24.003008edt.453135-27775@jane.cs.toronto.edu>
Archive-name: sunmanagers-before-posting
Last Updated: $Id: before.posting,v 1.19 2002/11/21 15:07:17 jdd Exp $
NOTE:	This message is posted periodically to sunmanagers on behalf of all
	members of the Sunmanager's mailing list.  Please read it carefully 
	before posting.  This document can be retrieved from:
	ftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/before.posting
Dear prospective sunmanagers poster,
Before posting, please stop for a minute and consider whether or not your
posting is suitable for Sunmanagers.  The list is not intended for just any
possible question related to managing Sun equipment or software.  The only
appropriate questions for Sun Managers are time-critical questions about Sun
system management problems that are not answered in the manuals or system
documentation, or in the Sunmanager's FAQ.
In particular, the following kinds of postings are not appropriate:
	- Subscribe and unsubscribe messages.  Point your web browser to
	  http://www.sunmanagers.org instead.
	- Test messages of any sort.
	- Discussions about anything, including discussions about the list
	  itself, or followups to any posting, with the exception of a single
	  summary to one's own question summarizing the email responses.  Use
	  instead one of the Sun newsgroups, eg.  comp.sys.sun.admin,
	  comp.sys.sun.hardware or comp.unix.solaris.
	- Replies to any SunManagers posting, even if the reply is a
	  separate question.  Please send a separate message instead.
	- Postings not related to Sun equipment or software.  Use the 
	  appropriate newsgroup or mailing list instead.  For example,
	  if your question concerns "sendmail", please consult the
	  comp.mail.sendmail newsgroup or the www.sendmail.org website.
	- General UNIX or network questions.  Use the appropriate newsgroup,
	  eg. comp.unix.questions instead.
	- Postings that are not time-critical.  Use one of the Sun newsgroups,
	  eg. comp.sys.sun.admin, comp.sys.sun.hardware or comp.unix.solaris.
	- Questions answered in the FAQ.  Read the FAQ instead.  If you're
	  not sure if the question is in the FAQ, please check before asking. 
	  You can find the FAQ at:
		ftp://ftp.cs.toronto.edu/pub/jdd/sunmanagers/faq
	- Questions that are answered in the manuals, answerbook, or system
	  documentation.  Read the manuals instead.  If you're not sure if
	  the question is answered in the manuals, please check first!
	- Job postings, requests for jobs, sales pitches, etc.  Use the
	  appropriate newsgroup instead.
	- Please, no postings in HTML, rich-text-format, Microsoft Word,
	  Word Perfect, or any format that some people on the list would not 
	  easily be able to read.  Also, please post in English only; most
	  of our readers are not able to read other languages.
	- Please do not BCC (blind carbon copy) the list.  Many of our
	  list members depend on the list address appearing on incoming
	  mail messages, so that they can automatically distinguish list
	  traffic from other traffic.  
Please note that we are not saying these postings are necessarily "bad" or
"stupid".  They are not.  They are merely inappropriate for this list.  There
are many other lists and newsgroups for which the question may be completely
appropriate, and we encourage you to submit the posting there.
Note also that your question may have been already answered in the past.
Please spend a minute or two checking one of the Sunmanager's archives, 
for example, at http://www.sunmanagers.org, or one of the archive sites
mentioned in the FAQ.
Here's an example of an appropriate question:
	I have a SPARCserver 99 running Solaris 9.8.7 with the fizbozz patch
	and the jumbo kernel patch version 158.  After I installed
	Futzbarworks version 3.2, the machine locks up every couple of
	hours.  When it locks up, the following message appears on the
	console:  
		zz0: out of futzbufs.  Barworks table is full.  
	I need to get this machine working as soon as possible.  Please
	help!  Send email and I will summarize to the list.
To submit a question, email it to sunmanagers@sunmanagers.org.  When you do
this, please indicate all relevant information, including machine type, OS
version and patches.  Collect email replies, and then summarize them to the
list.  If your question was posted with a subject of "foobar", for example,
then please post your summary with a subject of "SUMMARY: foobar".
Why are we asking that only certain types of postings be submitted to the
list?  Very simply, the reason is this:  we want the list to have a very
short turnaround time, and the only reasonable way to do this is to keep it
unmoderated.  But this means that every message sent to the list ends up in
the mailboxes of all the list members.  To keep all the members of the list
from being deluged by inappropriate messages, we need everyone's co-operation
in ensuring that only appropriate messages are sent to the list.
Please remember, Sunmanagers is a public forum: we have thousands of
subscribers, all posts are archived on numerous archive sites, and these are
searchable via various web engines.  A great number of people will read your
message.  Keep in mind that the person reading your message may be your boss,
your future boss, your customer, your seminar instructor, your colleague, or
someone else that you work with today or may find yourself working with
tomorrow.  We do not want you to embarrass yourself by sending an
inappropriate or poorly thought-out posting.
Regards,
John	
--
John DiMarco <jdd@cs.toronto.edu>    Sunmanagers Information Files Maintainer
http://www.cs.toronto.edu/~jdd
------------------------------
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
End of sunmanagers Digest, Vol 19, Issue 27
*******************************************
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers