Svc:/network/nfs/client problem in Solaris 10

Hi,
I`ve been trying to figure out what is the problem with the below scenario for so long and till now i`m not able to.
i have a X4100 SunFire system with solaris 10 installed.
most of the services are not coming up (ssh,ftp,etc....) each time i reboot the server, and after approximately 3 hours everything comes fine by it self.
i noticed that the service :/network/nfs/client is taking too long while starting. This might be related to the problem.
See below the svcs command : hope this will be usefull :)
bash-3.00# svcs -xv ssh
svc:/network/ssh:default (SSH server)
State: offline since Wed May 20 16:37:45 2009
Reason: Service svc:/network/nfs/client:default is starting.
See: http://sun.com/msg/SMF-8000-GE
Path: svc:/network/ssh:default
svc:/system/filesystem/autofs:default
svc:/network/nfs/client:default
See: man -M /usr/share/man -s 1M sshd
Impact: 3 dependent services are not running:
svc:/milestone/multi-user-server:default
svc:/system/basicreg:default
svc:/system/zones:default
any advise on this ?
Appreciate your help,

hi all
issue resolved actually port was conflicting in /etc/services i have readded the entry in /etc/service
Thanks

Similar Messages

"/network/physical:default" problem in Solaris 10 x86

I have a problem with network interface on Solaris 10 x86 on HP Proliant ML 370 G4 server.
The problem is that at the boot time it report some problem with network interface and writes "see svcs -x"
# svcs -x
svc:/network/physical:default (physical network interfaces)
State: maintenance since Mon 21 Mar 2005 09:55:39
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
See: http://sun.com/msg/SMF-8000-KS
See: ifconfig(1M)
See: /etc/svc/volatile/network-physical:default.log
Impact: 5 dependent services are not running. (Use -v for list.)
svc:/application/print/server:default (LP print server)
State: disabled since Mon 21 Mar 2005 09:55:38
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 2 dependent services are not running. (Use -v for list.)
svcs -v shows that /network/physical:default need maintance
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
# svcs -xv /network/physical:default
svc:/network/physical:default (physical network interfaces)
State: maintenance since Mon 21 Mar 2005 09:55:39
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M ifconfig
See: /etc/svc/volatile/network-physical:default.log
Impact: 5 dependent services are not running:
svc:/milestone/network:default
svc:/network/nfs/nlockmgr:default
svc:/network/nfs/client:default
svc:/network/nfs/status:default
svc:/network/ssh:default
# more /etc/svc/volatile/network-physical:default.log
[ Mar 21 09:55:37 Enabled. ]
[ Mar 21 09:55:38 Executing start method ("/lib/svc/method/net-physical") ]
[ Mar 21 09:55:38 Timeout override by svc.startd. Using infinite timeout ]
ifconfig: plumb: eri0: No such file or directory
moving addresses from failed IPv4 interfaces: eri0 (couldn't move, no alternative interface).
[ Mar 21 09:55:39 Method "start" exited with status 96 ]
I have not any eri device in /dev directory
How can I add a network interface?

Try elxl0 :-) This is: E L X L - zero :-) instead of: qfe0.
PS The 0 can increase to 1,2,.. if you have more 3com cards in the system.

NFS client problem "The document X could not be saved"

Hi,
Briefly: Debian Linux server (Lenny), OS X 10.5.7 client. NFS server config is simple enough:
/global 192.168.72.0/255.255.255.0(rw,rootsquash,sync,insecure,no_subtreecheck)
This works well without our Linux clients, and generally it is Ok with my OS X iMac. OS X NFS client is configured through Directory Utility, with no "Advanced" options. Client can authenticate with NIS nicely, and NFS, on the whole, works. I can manipulate files with Finder, and create files on the commandline with the usual tools.
The problem is TextEdit, iWork and other Cocoa apps (not all). They can save a file once, but subsequently saving a file produces a "The document X.txt cannot be saved" error dialog. If I remove the file on the commandline and re-save, then the save succeeds. It is as if re-saving the document with the same name as an existing file causes issues. There seems to be no problem with file permissions. When I save in a non NFS exported directory everything is fine.
Has anyone spotted this problem before?
Lawrence

I doubt that "OS X NFS is fundamentally broken" seeing as how many people use it successfully.
tcpdump (or more preferably: wireshark) might be useful in tracking down what's happening between the NFS client and NFS server. Sometimes utilities like fs_usage can be useful in tracking down the application/filesystem interaction.
It's usually a good idea to check the logs (e.g. /var/log/system.log) for possible clues in case an error/warning is getting logged around the same time as the failure. And if you can't reproduce the problem from the command line, then that can be a good indication that the issue is with the higher layers of the system.
Oh, and if you think there's a bug in the OS, it never hurts to officially tell Apple that via a bug report:
http://developer.apple.com/bugreporter/
Even if it isn't a bug, they should still be able to work with you to help you figure out what's going on. They'll likely want know details about what exactly isn't working and will probably ask for things like a tcpdump capture file and/or an fs_usage trace.
HTH
--macko

NFS client problem

Hi,
I have setuped NFS environment on solaris 9.
All the services are running in Server and Client side.
While the client rebooted im getting the mount point is not found.
like : /pani/notape is not found or does not exist.
When i umount /pani im getting mounted with some delay....
Any body tell me if any solution is there.
Thanks in advance.
Pani.

How does the client mount the share -- you use automount maps or just an entry in vfstab? Did you try snooping the traffic to see if the client is at least attempting to mount the share?

Daisy Chained Airport Network Wireless Client Problem

It's a long distance from my cable modem to the last area in my house I want to establish a wireless network in, so I set up a three-Airport network, with a Time Capsule at the cable modem, connected to an Airport Extreme (wirelessly), which is connected to another Extreme (wirelessly). Airport Utility shows the three in a chained arrangement:
The problem I'm having is that the last Airport won't allow any wireless clients. It does allow several devices to connect to it with a wired connection, just fine. Any suggestions how I can allow the last Airport to extend my network wirelessly as well as wired?

When I add a few clients to the list with their Mac addresses and change the Unlimited settings to No Access, the Airport Express stops working.
The last AirPort is configured to "join" the wireless network....even if you think that it might be set to "extend" a wireless network. In this type of configuration, the last AirPort provides no wireless signal extension.....but.... the Ethernet ports are enabled.
If you want the last AirPort to extend the wireless signal coverage, it will need to be connected using a wired Ethernet connection to your main router.....or.....it will need to be moved much closer to the Time Capsule if you want to try to extend wirelessly.
Maybe they're all really connected in a hub-spoke arrangement after all, and Airport Utiity is just showing them wrong?
No, they are not configured in a hub-spoke setup. If they were, then both of the AirPort Extremes would be displayed as connecting directly to the Time Capsule.

Solaris 10 NFS caching problems with custom NFS server

I'm facing a very strange problem with a pure java standalone application providing NFS server v2 service. This same application, targeted for JVM 1.4.2 is running on different environment (see below) without any problem.
On Solaris 10 we try any kind of mount parameters, system services up/down configuration, but cannot solve the problem.
We're in big trouble 'cause the app is a mandatory component for a product to be in production stage in a while.
Details follows
System description
Sunsparc U4 with SunOS 5.10, patch level: Generic_118833-33, 64bit
List of active NFS services
disabled   svc:/network/nfs/cbd:default
disabled   svc:/network/nfs/mapid:default
disabled   svc:/network/nfs/client:default
disabled   svc:/network/nfs/server:default
disabled   svc:/network/nfs/rquota:default
online       svc:/network/nfs/status:default
online       svc:/network/nfs/nlockmgr:default
NFS mount params (from /etc/vfstab)
localhost:/VDD_Server - /users/vdd/mnt nfs - vers=2,proto=tcp,timeo=600,wsize=8192,rsize=8192,port=1579,noxattr,soft,intr,noac
Anomaly description
The server side of NFS is provided by a java standalone application enabled only for NFS v2 and tested on different environments like: MS Windows 2000, 2003, XP, Linux RedHat 10 32bit, Linux Debian 2.6.x 64bit, SunOS 5.9. The java application is distributed with a test program (java standalone application) to validate main installation and configuration.
The test program simply reads a file from the NFS file-system exported by our main application (called VDD) and writes the same file with a different name on the VDD exported file-system. At end of test, the written file have different contents from the read one. Indeep investigation shows following behaviuor:
_ The read phase behaves correctly on both server (VDD) and client (test app) sides, trasporting the file with correct contents.
_ The write phase produces a zero filled file for 90% of resulting VDD file-system file but ending correctly with the same sequence of bytes as the original read file.
_ Detailed write phase behaviour:
1_ Test app wites first 512 bytes => VDD receive NFS command with offset 0, count 512 and correct bytes contents;
2_ Test app writes next 512 bytes => VDD receive NFS command with offset 0, count 1024 and WRONG bytes contents: the first 512 bytes are zero filled (previous write) and last 512 bytes with correct bytes contents (current write).
3_ Test app writes next 512 bytes => VDD receive NFS command with offset 0, count 1536 and WRONG bytes contents: the first 1024 bytes are zero filled (previous writes) and last 512 bytes with correct bytes contents (current write).
4_ and so on...
Further tests
We tested our VDD application on the same Solaris 10 system but with our test application on another (Linux) machine, contacting VDD via Linux NFS client, and we don�t see the wrong behaviour: our test program performed ok and written file has same contents as read one.
Has anyone faced a similar problem?
We are Sun ISV partner: do you think we have enough info to open a bug request to SDN?
Any suggestions?
Many thanks in advance,
Maurizio.

I finally got it working. I think my problem was that I was coping and pasting the /etc/pam.conf from Gary's guide into the pam.conf file.
There was unseen carriage returns mucking things up. So following a combination of the two docs worked. Starting with:
http://web.singnet.com.sg/~garyttt/Configuring%20Solaris%20Native%20LDAP%20Client%20for%20Fedora%20Directory%20Server.htm
Then following the steps at "Authentication Option #1: LDAP PAM configuration " from this doc:
http://docs.lucidinteractive.ca/index.php/Solaris_LDAP_client_with_OpenLDAP_server
for the pam.conf, got things working.
Note: ensure that your user has the shadowAccount value set in the objectClass

Problems enabling nfs client and server

I just re-build a solaris 11.1x86 on a x4640 SunFire
Have problems enabling nfs
First i typed the following command:
# svcs network/nfs/server
disable
Second I typed the following command:
#svcadm enable network/nfs/server
# svcs network/nfs/server
offline
did this 3 or 4 times without success...
any ideas?
I holding production here! Please help!!

Let's rule out the easier stuff first...
Do you have something shared?
I think you need to have something shared before you can enable the nfs server service.
Or, if you share something, the service is started automatically. See below.
Thanks, Cindy
# svcs -a | grep nfs
disabled Feb_26 svc:/network/nfs/client:default
disabled Feb_26 svc:/network/nfs/server:default
disabled Feb_26 svc:/network/nfs/rquota:default
# svcadm enable svc:/network/nfs/server:default
# svcs | grep nfs
disabled 13:51:52 svc:/network/nfs/server:default
# zfs set share.nfs=on rpool/cindy
# share
rpool_cindy /rpool/cindy nfs sec=sys,rw
# svcs | grep nfs
online Feb_26 svc:/network/nfs/fedfs-client:default
online Feb_27 svc:/network/nfs/status:default
online Feb_27 svc:/network/nfs/cbd:default
online Feb_27 svc:/network/nfs/mapid:default
online Feb_27 svc:/network/nfs/nlockmgr:default
online 13:52:35 svc:/network/nfs/rquota:default
online 13:52:35 svc:/network/nfs/server:default

Mountd just keeps on spinning, network/nfs/server never enters online state

Hi Everyone,
I'm administrating a Solaris 10 5/09 Thumper, full patched to up until Sept 8th.
I'm having a problem with nfs, in our environment we create a new zfs for every home directory. This gives us full control over everyone's space, and allows us to reserve space for important users. We currently have about 350 zfs's we export to a cluster. When we rebooted this machine everything came up alright but svcs:/network/nfs/server never entered a running state. See below:
root@x4500-2:~# svcs -l network/nfs/server
fmri svc:/network/nfs/server:default
name NFS server
enabled true
state offline
next_state online
state_time Fri Sep 11 11:21:23 2009
logfile /var/svc/log/network-nfs-server:default.log
restarter svc:/system/svc/restarter:default
contract_id 61
dependency require_any/error svc:/milestone/network (online)
dependency require_all/error svc:/network/nfs/nlockmgr (online)
dependency optional_all/error svc:/network/nfs/mapid (online)
dependency require_all/restart svc:/network/rpc/bind (online)
dependency optional_all/none svc:/network/rpc/keyserv (disabled)
dependency optional_all/none svc:/network/rpc/gss (online)
dependency require_all/error svc:/system/filesystem/local (online)
Has anyone seen this before?
I'm using the DTraceToolkit-0.99 & top, and see lots of cpu cycles using mountd; but there aren't any errors being generated.
Thanks,
Gregory

what shows up in logfile /var/svc/log/network-nfs-server:default.log?

Systemd nfs client mount share ???

Just installed systemd, systemd-arch-units and initscripts-systemd as per the wiki and all went well except mounting a nfs share from my server. (networking is OK!)
This is the old working mount command run from rc.local before installing systemd;
mount -t nfs4 -o rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 192.168.0.250:/ /media/SERVER_NYTT &
Did not mount at all with systemd, not even when run manually from command line. From systemd log netfs and nfs-common failed to start.
So I tried from fstab instead;
192.168.0.250:/ /media/SERVER_NYTT nfs rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 0 0
This did work but 'mount' showed that systemd had mounted with nfs default options instead of mine (wsize, rsize ...). Still errors from systemd starting netfs and nfs.
So I disabled netfs and nfs-common/rpcbind from rc.conf and created this systemd file (/etc/systemd/system/192.168.0.250.mount);
[Unit]
Description=ServerNfs
Wants=network.target rpc-statd.service
After=network.target rpc-statd.service
[Mount]
What=192.168.0.250:/
Where=/media/SERVET_NYTT
Type=nfs
Options=rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp
DirectoryMode=0777
StandardOutput=syslog
StandardError=syslog
From the sparce wiki and 'man systemd.mount'. Now nothing happens. With my limited understanding I thought it would start neccessary services (wants) and replace the entry in fstab.
I will now enable systemd services rpcbind, rpcstatd and see what happens.
Overall the transition to systemd went very well indeed; slim, openbox, network, .xinitrc, e4rat all started OK much to my surprise! There's still some fine-tuning to do like nfs, and possibly automounting and at last weeding out unneccessary services.
But any help with this nfs client problem is much appreciated.

swanson wrote:
Do you use any of this;
Alternatively, you can mark these entries in /etc/fstab with the x-systemd.automount and x-systemd-device-timeout= options (see systemd.mount ..
I did read the man for systemd.mount but couldn't make out what to put in the fstab line.
By the way, I renamed the mountfile to the target mountpoint but no success. I then reactivated the fstab line, with the new mountpoint in /mnt and that worked fine with mount -a. Except the mount options are not as I want, as they are in fstab. They were before systemd, and now they are as default for nfs4.
have a look here regarding the x-systemd-automount option. I seem to be only one who has noticed a problem with this option, comment=systemd.automount works fine for automounting though. I haven't changed the wiki because I'm still not sure if the problem is on my side.

Solaris 10 Network Install TFTP problem

Hi,
I tried to create jumpstart through network install with Solaris 10.
I'm running into trouble of TFTP problem when trying to add_install_client.
Here is the error I got:
./add_install_client xxx sun4u
svcprop: Couldn't find object for FMRI "network/tftp/udp6:default/:properties/restarter/st ate".
enabling network/tftp/udp6 service
svcadm: Pattern 'network/tftp/udp6' doesn't match any FMRIs, ignoring
On the client side, when I do "boot net - install", I get ARP/RARP error, obviously, the TFTP was not set up right on the server.
I could not find tftpd on the server, anyone has any suggestion what I should do to get tftpd running?
Thanks!

Hi,
i don't now, why it is like it is, there is no xlm manifest for the smf, but there is a "simple"solution:
edit the /etc/inet/inetd.conf, unremark the line for tftpd. Than, when restarting the inetd with "kill -HUP <prozessnumber of inetd", you get a message in /var/adm/messages:
......... inetd[185]: [ID 702911 daemon.warning] Configuration file /etc/inet/inetd.conf has been modified since inetconv was last run. "inetconv -i /etc/inet/inetd.conf" must be run to apply any changes to the SMF
Just do what it say's: "inetconf -i /etc/inet/inetd.conf", and you get the smf entry:
# svcs | grep tftp
online 19:05:27 svc:/network/tftp/udp6:default
now it is online, and you can stop and start it with svcadm.
Holger

Solaris ldap client problem (tls:simple + anonymous)

Hi All,
I've installed Directory Server 6.3.1 and it works just fine,
but I have a problem regarding connecting Solaris 10 ldap client to it through SSL using anonymous credential level.
Both SSL with proxy credential level or anonymous without SSL work fine but as you know these configurations are not pretty secure.
More detail.
Profile:
dn: cn=sslnoproxyuser,ou=profile,dc=domain,dc=com
authenticationmethod: tls:simple
bindtimelimit: 10
cn: sslnoproxyuser
credentiallevel: anonymous
defaultsearchbase: dc=domain,dc=com
defaultsearchscope: one
defaultserverlist: servername.domain.com
followreferrals: TRUE
objectclass: top
objectclass: DUAConfigProfile
preferredserverlist: servername.domain.com
profilettl: 43200
searchtimelimit: 30
Ldapclient output:
bash-3.00# ldapclient init -v -a profileName=sslnoproxyuser servername.domain.com
Parsing profileName=sslnoproxyuser
Arguments parsed:
profileName: sslnoproxyuser
defaultServerList: servername.domain.com
Handling init option
About to configure machine by downloading a profile
findBaseDN: begins
findBaseDN: ldap not running
findBaseDN: calling __ns_ldap_default_config()
found 2 namingcontexts
findBaseDN: __ns_ldap_list(NULL, "(&(objectclass=nisDomainObject)(nisdomain=domain.com))"
rootDN[0] dc=domain,dc=com
found baseDN dc=domain,dc=com for domain domain.com
Proxy DN: NULL
Proxy password: NULL
Credential level: 0
Authentication method: 3
No proxyDN/proxyPassword required
About to modify this machines configuration by writing the files
Stopping network services
Stopping sendmail
stop: sleep 100000 microseconds
stop: network/smtp:sendmail... success
Stopping nscd
stop: sleep 100000 microseconds
stop: sleep 200000 microseconds
stop: system/name-service-cache:default... success
Stopping autofs
stop: sleep 100000 microseconds
stop: sleep 200000 microseconds
stop: sleep 400000 microseconds
stop: sleep 800000 microseconds
stop: sleep 1600000 microseconds
stop: sleep 3200000 microseconds
stop: system/filesystem/autofs:default... success
ldap not running
nisd not running
nis(yp) not running
file_backup: stat(/etc/nsswitch.conf)=0
file_backup: (/etc/nsswitch.conf -> /var/ldap/restore/nsswitch.conf)
file_backup: stat(/etc/defaultdomain)=0
file_backup: (/etc/defaultdomain -> /var/ldap/restore/defaultdomain)
file_backup: stat(/var/nis/NIS_COLD_START)=-1
file_backup: No /var/nis/NIS_COLD_START file.
file_backup: nis domain is "domain.com"
file_backup: stat(/var/yp/binding/domain.com)=-1
file_backup: No /var/yp/binding/domain.com directory.
file_backup: stat(/var/ldap/ldap_client_file)=-1
file_backup: No /var/ldap/ldap_client_file file.
Starting network services
start: /usr/bin/domainname domain.com... success
start: sleep 100000 microseconds
start: network/ldap/client:default... maintenance
start: sleep 100000 microseconds
start: system/filesystem/autofs:default... success
start: sleep 100000 microseconds
start: system/name-service-cache:default... success
start: sleep 100000 microseconds
start: network/smtp:sendmail... success
restart: sleep 100000 microseconds
restart: sleep 200000 microseconds
restart: milestone/name-services:default... success
Error resetting system.
Recovering old system settings.
Stopping network services
Stopping sendmail
stop: sleep 100000 microseconds
stop: network/smtp:sendmail... success
Stopping nscd
stop: sleep 100000 microseconds
stop: sleep 200000 microseconds
stop: system/name-service-cache:default... success
Stopping autofs
stop: sleep 100000 microseconds
stop: sleep 200000 microseconds
stop: sleep 400000 microseconds
stop: sleep 800000 microseconds
stop: sleep 1600000 microseconds
stop: sleep 3200000 microseconds
stop: system/filesystem/autofs:default... success
Stopping ldap
stop: network/ldap/client:default... restoring from maintenance state
stop: sleep 100000 microseconds
stop: network/ldap/client:default... success
nisd not running
nis(yp) not running
recover: stat(/var/ldap/restore/defaultdomain)=0
recover: open(/var/ldap/restore/defaultdomain)
recover: read(/var/ldap/restore/defaultdomain)
recover: old domainname "domain.com"
recover: stat(/var/ldap/restore/ldap_client_file)=-1
recover: stat(/var/ldap/restore/ldap_client_cred)=-1
recover: stat(/var/ldap/restore/NIS_COLD_START)=-1
recover: stat(/var/ldap/restore/domain.com)=-1
recover: stat(/var/ldap/restore/nsswitch.conf)=0
recover: file_move(/var/ldap/restore/nsswitch.conf, /etc/nsswitch.conf)=0
recover: stat(/var/ldap/restore/defaultdomain)=0
recover: file_move(/var/ldap/restore/defaultdomain, /etc/defaultdomain)=0
Starting network services
start: /usr/bin/domainname domain.com... success
start: sleep 100000 microseconds
start: system/filesystem/autofs:default... success
start: sleep 100000 microseconds
start: system/name-service-cache:default... success
start: sleep 100000 microseconds
start: network/smtp:sendmail... success
restart: sleep 100000 microseconds
restart: milestone/name-services:default... success
*/var/ldap/cachemgr.log*
Tue Jun 30 10:50:51.4330 Starting ldap_cachemgr, logfile /var/ldap/cachemgr.log
Tue Jun 30 10:50:51.4355 Error: Unable to read '/var/ldap/ldap_client_file': Configuration Error: No entry for 'NS_LDAP_BINDDN' found
Tue Jun 30 10:50:51.4368 detachfromtty(): child failed (rc = 255).
Any ideas?
Edited by: ffffffffff356dfd on 30 ???? 2009 12:07
Edited by: ffffffffff356dfd on 30 ???? 2009 12:07

Hi ,
yes I use it.
Here is my pam.conf:
# Authentication management
# login service (explicit because of pam_dial_auth)
login auth requisite pam_authtok_get.so.1
login auth required pam_dhkeys.so.1
login auth required pam_unix_cred.so.1
login auth required pam_dial_auth.so.1
login auth binding pam_unix_auth.so.1 server_policy
login auth required pam_ldap.so.1
# rlogin service (explicit because of pam_rhost_auth)
# rlogin auth sufficient pam_rhosts_auth.so.1
rlogin auth requisite pam_authtok_get.so.1
rlogin auth required pam_dhkeys.so.1
rlogin auth required pam_unix_cred.so.1
rlogin auth binding pam_unix_auth.so.1 server_policy
rlogin auth required pam_ldap.so.1
# rsh service (explicit because of pam_rhost_auth,
# and pam_unix_auth for meaningful pam_setcred)
# rsh auth sufficient pam_rhosts_auth.so.1
rsh auth required pam_unix_cred.so.1
rsh auth binding pam_unix_auth.so.1 server_policy
rsh auth required pam_ldap.so.1
# PPP service (explicit because of pam_dial_auth)
ppp auth requisite pam_authtok_get.so.1
ppp auth required pam_dhkeys.so.1
ppp auth required pam_dial_auth.so.1
ppp auth binding pam_unix_auth.so.1 server_policy
ppp auth required pam_ldap.so.1
# Default definitions for Authentication management
# Used when service name is not explicitly mentioned for authentication
other auth requisite pam_authtok_get.so.1
other auth required pam_dhkeys.so.1
other auth required pam_unix_cred.so.1
other auth binding pam_unix_auth.so.1 server_policy
other auth required pam_ldap.so.1
# passwd command (explicit because of a different authentication module)
passwd auth binding pam_passwd_auth.so.1 server_policy
passwd auth required pam_ldap.so.1
# cron service (explicit because of non-usage of pam_roles.so.1)
cron account required pam_unix_account.so.1
# Default definition for Account management
# Used when service name is not explicitly mentioned for account management
other account requisite pam_roles.so.1
other account binding pam_unix_account.so.1
other account required pam_ldap.so.1
# Default definition for Session management
# Used when service name is not explicitly mentioned for session management
other session required pam_unix_session.so.1
# Default definition for Password management
# Used when service name is not explicitly mentioned for password management
other password required pam_dhkeys.so.1
other password requisite pam_authtok_get.so.1
other password requisite pam_authtok_check.so.1
other password required pam_authtok_store.so.1 server_policy
# Support for Kerberos V5 authentication and example configurations can
# be found in the pam_krb5(5) man page under the "EXAMPLES" section.
#

How do I disable NFS client in Solaris 10

I am trying to disable NFS client in Solaris 10. In Solaris 9 I would simply rename /etc/rc2.d/S73nfs.client to /etc/rc2.d/s73nfs.client
Since /etc/rc2.d/nfs.client does not seem to exist in 10 I'm wondering how to do this.
Thanks in advance for the help.
Max

Since /etc/rc2.d/nfs.client does not seem to exist in
10 I'm wondering how to do this.Read up on the new Solaris 10 service management faciities. Info at http://docs.sun.com/ There are a couple of tutorial doc's at bigadmin

NFS locking problem, solaris 10, nfsd stops serving

Hi all,
First time poster, short time viewer.
To set the scene...
I have an x86 SAM-QFS installation under management currently. The SAM-QFS infrastructure consists of 2x meta data controllers and 2x file service heads, that currently share out NFS (they are NFS servers).
These systems are not clustered, nor do they have any form of "high availability". They can be failed between, but this is very much a manual process.
The file service heads are running mounted SAM-FS filesystems. These file systems are shared out in the form of /etc/dfs/dfstab style exports to NFS clients (some 250 Mac OS X Tiger/Leopard clients) that use NFS for their home directories et al.
So, here is where things become sad.
For the past month, we've been fighting with our nfsd. Unfortunately for us, at (apparently) completely random moments, our nfsd will simply stop responding to requests, cease to serve out nfs to clients and then silently stop processing any locking/transfer/mapping requests. An svcadm restart nfs/server does nothing, as the process simply 'hangs' in a state of reattempting to stop/start the nfsd. We find that the only way to get nfs to respond is to completely reboot the host. At this point only, will nfs reshare with the "shareall" command based upon our entries in /etc/dfs/dfstab
We have been though a lengthy support case with Sun. We are getting NO closer to understanding the problem, but we are providing Sun with every possible detail we can. We've even gotten to the point of writing crash dumps from the machine out to disk using commands such as 'uadmin 5 1' and then sending our entire vmcore outputs to Sun.
We are stabbing in the dark suggesting it might be file locking related, but we cannot/do not have enough visibility on the inside of the nfds to be able to tell what is happening. We've tried increasing the number of nfs_server allowed daemons in /etc/default/nfs, as well as made the maximum NFS version to serve out as v3, but it hasn't helped us here at all.
If anyone has any experience with what could possibly cause NFS to do this, in what (we thought) was a fairly common, NFS environment, it would be appreciate. Our infrastructure is fairly grounded until we have a resolution to an issue Sun simply can't seem to pinpoint.
Thank you.
z.

I have the same problem on a samfs server. I have never come accross a shittier system then a samfs system. I feel for people who have to support them. SAMFS takes an easy concept and makes it an overwhelming problem.

NFS / automount hangs on Solaris 10 SunOS oats 5.10 Generic_125100-07 sun4u

We are running Solaris 10 125100-07 on a SunFire V440.
We host computer services for another department on this host.
The server acts as both an NFS server and an NFS client. We do a lot of cross-mounting in our environment due to the lack of large centralized storage.
This particular machine automounts shares from our Solaris 8, 9 and 10 servers and possibly a few Suse servers, and a NetApp owned by another department.
Every day and a half or so, something happens to either NFS or the automounter, and the machine 'hangs' in that we have NFS requests that never get filled.
Restarting either autofs or the nfs client, or both does not seem to help. The only fix we have found so far is a reboot.
We have throttled NFS_CLIENT_VERSMAX to 3 and set AUTOMOUNT_VERBOSE and AUTOMOUNTD_VERBOSE both to TRUE.
The general failures we see look like this:
May 17 04:44:15 oats nfs: [ID 333984 kern.notice] NFS server grieg not respondin
g still trying
May 17 04:44:15 oats last message repeated 1 time
May 17 04:46:15 oats automountd[392]: [ID 196269 daemon.error] dupreq_nonidemp:
duplicate request in progress
May 17 04:49:57 oats last message repeated 4 times
May 17 04:52:15 oats automountd[392]: [ID 196269 daemon.error] dupreq_nonidemp:
duplicate request in progress
The dupreq_nonidemp messages repeat until we reboot.
The nfs server that does not respond varies from day to day. No other computer on our network complains about it.
This started after we installed 125100-05, and has continued through 125100-07.
As far as I can tell we are up to date on patches:
root@oats # smpatch analyze
No patches required.
Any thoughts?
I was thinking I might back out 125100-XX.
dal
e

Interesting,
we have the same problem on SunOS Generic_118833-36 on V440, V445, V240, V245, but not on an old E420, and not on a T2000.
We upgraded them with patch cluster to Generic_138888-07, but it has not changed anything:
E420 and T2000 are stable, the Fire-Vxxx have problem, each has its own "problem interval": one system 1.5 days, two systems 10 days, one every 3 months.
The problem is: NFS/TCP is suddenly dead. Then all NFS mounts, e.g. a manual mount, is hung with "NFS server not responding". A reboot helps.
We have added proto=udp to the mount options. No more problems since.
Permanent mounts, without Automounter, would certainly work, too.
But IMHO there is nothing wrong with Automounter itself, but the hanging occurs e.g. after 4000 NFS mounts, and Automounter is the enabler for that.

Sun Ray / DHCP problems on Solaris 10

All,
I have a Sun v240 running Solaris 10 (03/05) with patches current as of late December 2005. I cannot configure DHCP using the "utadm -a bge1" command as I get the following message:
### Warning: DHCP Service is in the maintenance mode
There could be a problem with the DHCP configuration
### It is strongly recommended to fix the problem and then use:
### "/usr/sbin/svcadm clear svc:/network/dhcp-server:default"
### to get DHCP service out of the maintenance mode before running utadm
Do you want to Continue? (Y/[N]):
I type "n" and than from the command line enter:
svcadm clear svc:/network/dhcp-server:default
But when I run the command "svcs -v" I see the following:
maintenance - 13:48:47 - svc:/network/dhcp-server:default
The output from "svcs -x" is the following:
# svcs -x
svc:/application/print/server:default (LP print server)
State: disabled since Sun Jan 22 13:45:48 2006
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 2 dependent services are not running. (Use -v for list.)
svc:/network/dhcp-server:default (DHCP server)
State: maintenance since Sun Jan 22 16:46:52 2006
Reason: Start method failed repeatedly, last exited with status 1.
See: http://sun.com/msg/SMF-8000-KS
See: in.dhcpd(1M)
See: /var/svc/log/network-dhcp-server:default.log
Impact: This service is not running.
In the log mentioned I get the following repeating error:
[ Jan 22 13:46:21 Executing start method ("/usr/lib/inet/in.dhcpd") ]
Datastore status error: Location does not exist
[ Jan 22 13:46:21 Method "start" exited with status 1 ]
[ Jan 22 13:48:47 Leaving maintenance because clear requested. ]
[ Jan 22 13:48:47 Enabled. ]
I cannot get dhcp out of maintenance. I don't know what this "Datastore" status error means. Any ideas?
Bob

DHCP server has two or three different data store types, normally its a plain text files or binary data files. Its store info of clients connected and some other stuff. Maybe files path is incorrect, just try to unconfig the dhcp server. I dont know the exact comand, but im using grafical tool on my opensolaris box, its under /usr/sadm/admin/bin/ directory, dhcpmgr.

Svc:/network/nfs/client problem in Solaris 10

Similar Messages

Maybe you are looking for