AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070814165103.67a89ccf@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<dl-cougar>,<sandrine.boulanger@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E0221597F@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 14 Aug 2007 16:51:47 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: dl-cougar
Cc: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>
Subject: Re: Vurrent status for Bobcat-linux testing
Message-ID: <20070814165147.6801212a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0221597F@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E04FA7EB7@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E0221597F@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

This could be the result of an unclean shutdown.  If you are running NFS
root (duh, everyone is) and have a kernel crash or an unclean
shutdown/reboot, then certain files are messed up and the first time
you boot you might have problems mounting things like /proc, and the
root filesystem will likely not be able to re-mount in RW mode, leading
the the "permission denied" type messages.  A clean shutdown reboot
will usually fix the problem.  If the problem is persistent, it's
probably a server configuration problem.

a


On Tue, 14 Aug 2007 16:04:29 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

> Just FYI, when I was mounting filesystems from 10.2.0.4 I also saw
> permission denied errors and the next mount would work - this has
> nothing to do with our filers, but it is an anomaly that appeared this
> morning. It is intermittent and it makes me wonder if the problem is
> somehow related to the 10.2.0.0 network.
> 
> _____________________________________________
> From: Maxim Kozlovsky 
> Sent: Tuesday, August 14, 2007 3:59 PM
> To: Sandrine Boulanger; Larry Scheer
> Cc: Andy Sharp; Tim Gardner
> Subject: RE: Vurrent status for Bobcat-linux testing
> 
> I have it running with my build, which is from the tree I have checked
> out just now, and clean cluster database, so any differences in
> behavior must be because of the root filesystem.  There was really a
> bug in the virtual server names, which I have fixed.
> 
> Sandrine, you should be able to continue the testing. The NFS
> permission problem may be something intermittent, I did not get
> permission denied when trying to mount, but got an error on the first
> access. We will need to look at why some time later. CIFS seems to be
> ok.
> 
> Larry should look at the differences between my root filesystem and
> the one the build scripts produce and we'll get the differences
> checked in.
> 
> _____________________________________________
> From: Sandrine Boulanger 
> Sent: Tuesday, August 14, 2007 12:39 PM
> To: Larry Scheer
> Cc: Maxim Kozlovsky; Andy Sharp; Tim Gardner
> Subject: Vurrent status for Bobcat-linux testing
> 
> I'm blocked right now since I cannot mount the volume. Don't know why
> ping is missing (see #6). I have a trace for #8 but is just shows
> mount reply with access denied.
> 
> 
> #1 eth1 
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> eth1: Wake-up event 0xffffffff
> eth1: Setting full-duplex based on negotiated link capability.
> eth1: Tx/Rx process did not stop in 2000 usec.
> 
> 
> 
> 
> #2 Mgmt vsvr name
> eng63 diag> vsvr show
> Virtual servers on nas gateway eng63
> 
>  ID  State                             Name
> ====================================================
> 1    Enabled                           VS_MGMT_4294967224
> 
> 
> 
> #3 snmpd restarting
> Aug 14 12:09:46 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18153) exited with status 1 
> Aug 14 12:09:46 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18162) exited with status 1 
> Aug 14 12:09:46 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18171) exited with status 1 
> Aug 14 12:09:47 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18180) exited with status 1 
> Aug 14 12:09:47 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18189) exited with status 1 
> Aug 14 12:09:47 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18198) exited with status 1 
> Aug 14 12:09:47 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18207) exited with status 1 
> Aug 14 12:09:48 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18216) exited with status 1 
> Aug 14 12:09:48 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18225) exited with status 1 
> Aug 14 12:09:48 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18234) exited with status 1 
> Aug 14 12:09:48 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18243) exited with status 1 
> Aug 14 12:09:49 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18252) exited with status 1 
> Aug 14 12:09:49 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18261) exited with status 1 
> Aug 14 12:09:49 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18270) exited with status 1 
> Aug 14 12:09:50 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18279) exited with status 1 
> Aug 14 12:09:50 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18288) exited with status 1 
> Aug 14 12:09:50 eng63 : 0:0:pm:ERROR: pm_sig_handler:
> /usr/local/agile/bin/snmpd (pid 18297) exited with status 1 
> 
> 
> #4 cannot create vsvr interface with name that starts with "eth":
> eng63 VS_MGMT_4294967224 diag> interface create eth0 -l fp1.0 -a
> 10.3.163.1/16
> Invalid interface 'eth0' for the virtual server.
>  The name of the interface cannot start with 'sc'.
> % Command failure.
> eng63 VS_MGMT_4294967224 diag> interface create eth2 -l fp1.0 -a
> 10.3.163.1/16
> Invalid interface 'eth2' for the virtual server.
>  The name of the interface cannot start with 'sc'.
> % Command failure.
> eng63 VS_MGMT_4294967224 diag> interface create eth3 -l fp1.0 -a
> 10.3.163.1/16
> Invalid interface 'eth3' for the virtual server.
>  The name of the interface cannot start with 'sc'.
> % Command failure.
> 
> eng63 VS_MGMT_4294967224 diag> interface create fp1.0 -l fp1.0 -a
> 10.3.163.1/16
> eng63 VS_MGMT_4294967224 diag>
> 
> #5 Autosupport does not work since there is no sendmail daemon running
> eng63 VS_MGMT_4294967224 diag> autosupport generate report
> Verify autosupport mode. Report not generated, error 0xffffffff.
> eng63 VS_MGMT_4294967224 diag> autosupport show config
> Auto Support configuration
> --------------------------
> Auto Support State: Enabled
> Auto Support TO address: sandrine.boulanger@onstor.com
> Auto Support NOTETO address: --Not-Set--
> Auto Support FROM address: eng63@onstor.com
> Auto Support MAIL SERVER: 0.0.0.0
> Auto Support Schedule:
>                min  : 0
>                hour : 8
>                date : *
>                month: *
>                day  : *
> 
> eng63 VS_MGMT_4294967224 diag>
> 
> #6 ping does not work to and from vsvr:
> eng63 VS_MGMT_4294967224 diag> system ping 10.3.0.1
> src ip bind is 192.167.1.1
> Can't execute /sbin/ping: No such file or directory
> eng63 VS_MGMT_4294967224 diag>
> [root@c18r15-rh80 root]# ping 10.3.163.2
> PING 10.3.163.2 (10.3.163.2) from 10.3.15.18 : 56(84) bytes of data.
> 
> --- 10.3.163.2 ping statistics ---
> 3 packets transmitted, 0 received, 100% loss, time 2012ms
> 
> 
> 
> 
> #7 Can't join vsvr to windows domain
> eng63 diag> vsvr create eng63-vs1
> eng63 ENG63-VS1 diag> interface create int1 -l fp1.0 -a 10.3.163.2/16
> eng63 ENG63-VS1 diag> route add default -g 10.3.0.1
> eng63 ENG63-VS1 diag> vsvr set domain nis onstorlab
> eng63 ENG63-VS1 diag> vsvr set domain windows matrix enguser
> Enter Password:
> eng63 ENG63-VS1 diag> vsvr enable
> Retrieving windows domain information failed. Verify your domain
> configuration and network connectivity to the domain controller(s).
> 
> Error log:
> 
> Unable to find a suitable server
> 
> % Command failure.
> eng63 ENG63-VS1 diag> domain show all
> Type       Domain name
> Address(es)
> nis        onstorlab
> 10.3.0.4
> 
> Type       Domain name        Login user
> Address(es)
> windows    MATRIX             enguser
> 10.3.0.5
> 
> Type       Domain name        Login user
> Address(es)
> eng63 ENG63-VS1 diag>
> 
> 
> #8 Cannot mount volume from client:
> [root@c18r15-rh80 root]# showmount -e 10.3.163.2
> Export list for 10.3.163.2:
> /vol1 (everyone)
> [root@c18r15-rh80 root]# mount 10.3.163.2:/vol1 /mnt/bob
> mount: 10.3.163.2:/vol1 failed, reason given by server: Permission
> denied
> [root@c18r15-rh80 root]#
	