Sponsored Content
Operating Systems Solaris NIS/smtp services issue on Solaris 11 Post 303011180 by solaris_1977 on Sunday 14th of January 2018 06:08:27 PM
Old 01-14-2018
NIS/smtp services issue on Solaris 11

Hi,

Few services not starting on new build Solaris 11 non-global zone. I uninstalled zone and reinstalled and still same issue, while global zone is working fine.

smpt service is going into maintenance mode and /var/svc/log/network-smtp:sendmail.log shows that it tries and then dead
Code:
[ Jan 14 22:13:40 Executing start method ("/lib/svc/method/smtp-sendmail start"). ]
[ Jan 14 22:15:40 Method or service exit timed out.  Killing contract 3322. ]
[ Jan 14 22:15:40 Method "start" failed due to signal KILL. ]

root@servertt1:# cat /var/yp/binding/pre.pointxp.com/ypservers
nis1-dir1-prod
nis2-dir1-prod
root@servertt1:#
root@servertt1:# ypwhich
Domain pre.pointxp.com not bound on servertt1.
root@servertt1:# svcs -a| grep -i nis
online         13:02:27 svc:/network/nis/domain:default
online         13:02:33 svc:/network/nis/client:default
root@servertt1: 
root@servertt1:
root@servertt1:# rpcinfo -p nis1-dir1-prod
   program vers proto   port  service
    100000    4   tcp    111  rpcbind
    100000    3   tcp    111  rpcbind
    100000    2   tcp    111  rpcbind
    100000    4   udp    111  rpcbind
    100000    3   udp    111  rpcbind
    100000    2   udp    111  rpcbind
    100028    1   tcp  41487  ypupdated
    100028    1   udp  43565  ypupdated

In above output, it doesn't go further than this. In good configuration, it is supposed to show yppasswdd, ypbind and ypserv.

I am not bothered about smtp, but something is strange on this server, which is not allowing NIS services to work as expected and I am not able to figure out.

Can somebody help me to fix this ?

Thanks

---------- Post updated at 07:08 PM ---------- Previous update was at 07:02 PM ----------

Disregard this please.
I was able to fix it
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris NIS+ and RedHat NIS+

Hello all, I'm not sure if this is the right forum, but I would like to know if Redhat running NIS ( not NIS +) would have conflict with Solaris running NIS+. Currently I am running NIS+ on Solaris but will be adding RedHat to the network. I seem to be unable to find and information regarding... (2 Replies)
Discussion started by: larry
2 Replies

2. UNIX for Dummies Questions & Answers

SMTP - emailing issue

We are running an application engine program that sends email to a list of users. In our Test Env, users are able to receive the emails but in our Prod environment, they do not. We are running the same program, and using the same stmp config. any idea on how to troubleshoot? (3 Replies)
Discussion started by: tads98
3 Replies

3. UNIX for Dummies Questions & Answers

Solaris 9 NIS user creation issue

Helloo to all... what is the correct way to assign a password to a new NIS user on a NIS master server? When I the following: useradd -s /bin/bash -d /export/home/username -m username The user get created fine but when I try to assign a password I get: #passwd username... (0 Replies)
Discussion started by: GLJ@USC
0 Replies

4. Solaris

make issue when I add some members into a NIS group on solaris 9,please help !!

Hello Sir, I want to add some members into a group on NIS domain, but when I run "/usr/ccs/bin/make group" to update the group map it was failed :-( the error message is : problem storing develop... (4 Replies)
Discussion started by: lk74612
4 Replies

5. Windows & DOS: Issues & Discussions

nfs/nis - microsoft services for UNIX adminstration

hello, I am using "microsoft services for UNIX adminstration" as an nfs/nis client in order to connect to a remote NFS folder with NIS authentication nfs mount seems to fail on the authentication stage. I get the login box from the client, but any (NIS mapped) loging seems to reject me.... (2 Replies)
Discussion started by: ynoatan99
2 Replies

6. Shell Programming and Scripting

Validating that the NIS and NIS+ services are disabled

I'm creating a scrip for auditing our AIX box's to ensure that they are built according to our system standards. I'm not sure on the logic for checking to see if the NIS and NIS+ services are disabled. any idea's? (2 Replies)
Discussion started by: sport
2 Replies

7. Programming

C socket issue with SMTP

Hey guys, im trying to write a program that'll create a report then email the report... my problem is when it comes to the socket trying to send the second command after EHLO smtp,*.* When the first command is sent its working fine... but when the program tries to send the second command it... (6 Replies)
Discussion started by: Jess83
6 Replies

8. Linux

SMTP issue

HI, I am having an issue with the mail. I had certain scripts who used to send mails. now i am not getting the mails as usual. need help to track the issue and resolve. mailx -s "Testing for details" xxx@yyy.zzz above code is used for mailing. can yoou please help? (2 Replies)
Discussion started by: onlyniladri
2 Replies

9. UNIX for Dummies Questions & Answers

How to block FTP ,SMTP,Telnet services?

My distribution details. # lsb_release -a LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: EnterpriseEnterpriseServer Description: Enterprise Linux Enterprise Linux Server release 5.2 (Carthage) Release: 5.2 Codename: ... (13 Replies)
Discussion started by: pinga123
13 Replies

10. Solaris

Boot Error - NIS services fails with Status 96

My system suddenly crash and when it rebooted there was an error: /dev/rdsk/c1t0d0s3 is logging svc.startd: svc:/network/nis/client:default: Method "/method/yp" failed with status 96. The system completes booting however when I log in a user account / directory is not longer... (1 Reply)
Discussion started by: NeedSolarisHelp
1 Replies
rpcinfo(1M)						  System Administration Commands					       rpcinfo(1M)

NAME
rpcinfo - report RPC information SYNOPSIS
rpcinfo [-m | -s] [host] rpcinfo -p [host] rpcinfo -T transport host prognum [versnum] rpcinfo -l [-T transport] host prognum versnum rpcinfo [-n portnum] -u host prognum [versnum] rpcinfo [-n portnum] -t host prognum [versnum] rpcinfo -a serv_address -T transport prognum [versnum] rpcinfo -b [-T transport] prognum versnum rpcinfo -d [-T transport] prognum versnum DESCRIPTION
rpcinfo makes an RPC call to an RPC server and reports what it finds. In the first synopsis, rpcinfo lists all the registered RPC services with rpcbind on host. If host is not specified, the local host is the default. If -s is used, the information is displayed in a concise format. In the second synopsis, rpcinfo lists all the RPC services registered with rpcbind, version 2. Note that the format of the information is different in the first and the second synopsis. This is because the second synopsis is an older protocol used to collect the information displayed (version 2 of the rpcbind protocol). The third synopsis makes an RPC call to procedure 0 of prognum and versnum on the specified host and reports whether a response was received. transport is the transport which has to be used for contacting the given service. The remote address of the service is obtained by making a call to the remote rpcbind. The prognum argument is a number that represents an RPC program number (see rpc(4)). If a versnum is specified, rpcinfo attempts to call that version of the specified prognum. Otherwise, rpcinfo attempts to find all the reg- istered version numbers for the specified prognum by calling version 0, which is presumed not to exist; if it does exist, rpcinfo attempts to obtain this information by calling an extremely high version number instead, and attempts to call each registered version. Note that the version number is required for -b and -d options. The EXAMPLES section describe other ways of using rpcinfo. OPTIONS
-T transport Specify the transport on which the service is required. If this option is not specified, rpcinfo uses the transport specified in the NETPATH environment variable, or if that is unset or NULL, the transport in the netconfig(4) data- base is used. This is a generic option, and can be used in conjunction with other options as shown in the SYNOPSIS. -a serv_address Use serv_address as the (universal) address for the service on transport to ping procedure 0 of the specified prognum and report whether a response was received. The -T option is required with the -a option. If versnum is not specified, rpcinfo tries to ping all available version numbers for that program number. This option avoids calls to remote rpcbind to find the address of the service. The serv_address is specified in universal address format of the given transport. -b Make an RPC broadcast to procedure 0 of the specified prognum and versnum and report all hosts that respond. If transport is specified, it broadcasts its request only on the specified transport. If broadcasting is not supported by any transport, an error message is printed. Use of broadcasting should be limited because of the potential for adverse effect on other systems. -d Delete registration for the RPC service of the specified prognum and versnum. If transport is specified, unregister the service on only that transport, otherwise unregister the service on all the transports on which it was regis- tered. Only the owner of a service can delete a registration, except the superuser, who can delete any service. -l Display a list of entries with a given prognum and versnum on the specified host. Entries are returned for all transports in the same protocol family as that used to contact the remote rpcbind. -m Display a table of statistics of rpcbind operations on the given host. The table shows statistics for each version of rpcbind (versions 2, 3 and 4), giving the number of times each procedure was requested and successfully ser- viced, the number and type of remote call requests that were made, and information about RPC address lookups that were handled. This is useful for monitoring RPC activities on host. -n portnum Use portnum as the port number for the -t and -u options instead of the port number given by rpcbind. Use of this option avoids a call to the remote rpcbind to find out the address of the service. This option is made obsolete by the -a option. -p Probe rpcbind on host using version 2 of the rpcbind protocol, and display a list of all registered RPC programs. If host is not specified, it defaults to the local host. This option is not useful for IPv6; use -s (see below) instead. Note that version 2 of the rpcbind protocol was previously known as the portmapper protocol. -s Display a concise list of all registered RPC programs on host. If host is not specified, it defaults to the local host. -t Make an RPC call to procedure 0 of prognum on the specified host using TCP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. -u Make an RPC call to procedure 0 of prognum on the specified host using UDP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. EXAMPLES
Example 1: RPC services. To show all of the RPC services registered on the local machine use: example% rpcinfo To show all of the RPC services registered with rpcbind on the machine named klaxon use: example% rpcinfo klaxon The information displayed by the above commands can be quite lengthy. Use the -s option to display a more concise list: example% rpcinfo -s klaxon program vrsn netid(s) service owner 100000 2,3,4 tcp,udp,ticlts,ticots,ticotsord rpcbind superuser 100008 1 ticotsord,ticots,ticlts,udp,tcp walld superuser 100002 2,1 ticotsord,ticots,ticlts,udp,tcp rusersd superuser 100001 2,3,4 ticotsord,ticots,tcp,ticlts,udp rstatd superuser 100012 1 ticotsord,ticots,ticlts,udp,tcp sprayd superuser 100007 3 ticotsord,ticots,ticlts,udp,tcp ypbind superuser 100029 1 ticotsord,ticots,ticlts keyserv superuser 100078 4 ticotsord,ticots,ticlts - superuser 100024 1 ticotsord,ticots,ticlts,udp,tcp status superuser 100021 2,1 ticotsord,ticots,ticlts,udp,tcp nlockmgr superuser 100020 1 ticotsord,ticots,ticlts,udp,tcp llockmgr superuser To show whether the RPC service with program number prognum and version versnum is registered on the machine named klaxon for the transport TCP use: example% rpcinfo -T tcp klaxon prognum versnum To show all RPC services registered with version 2 of the rpcbind protocol on the local machine use: example% rpcinfo -p To delete the registration for version 1 of the walld (program number 100008) service for all transports use: example# rpcinfo -d 100008 1 or example# rpcinfo -d walld 1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
rpcbind(1M), rpc(3NSL), netconfig(4), rpc(4), attributes(5) SunOS 5.10 13 Jul 2001 rpcinfo(1M)

Featured Tech Videos

All times are GMT -4. The time now is 10:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy