nisd can't create writer semaphore

pete_at_coin.org
Date: 06/21/04 

Date: Mon, 21 Jun 2004 13:32:56 GMT

Hi,

I'm running Solaris 2.7 on a Ultra-Enterprise 3000. We've had
nis_cache manager disabled for a while, but we just started seeing these
in the logs recently, however, there have been no noticable problems
with the box:

nisd[214]: can't create writer semaphore: No such file or directory

We have about 15,000 users authenticating off of nis with no issues
either. The nis+ is setup in such a way this it is its own master.
There are no other servers involved.

I've talked to a guy at Sun and he was not really able to give me
much comfort about the error. ie., I don't think he really knew
what's going on either with this one---with is unusual in my experience.

Has anyone seen this before? I'm told it could be related to nis_cache manager
NOT running, but as I said above, it's been off for 9 months and these
just started showing up in the past couple of days.

Thanks,

Pete

                                                                                

Relevant Pages

  • U1 Sol9 box refuses to see new nis maps
    ... running Solaris 9 being the nis clients. ... All clients know both servers and the nis ... domain both defined in their respective /etc/hosts and as nis servers. ...
    (comp.sys.sun.admin)
  • DISCUSSION: NIS vs NIS+ vs LDAP
    ... NIS, NIS+ and LDAP and their merits or lack there of. ... We've been running Solaris systems for a long time and obviously started out ...
    (SunManagers)
  • Changing NIS+ root master server and domain
    ... Sparc E250, running Solaris 8. ... NIS+ domain to reflect a change in company ownership. ... NIS+ root master ... Dump tables on the existing root master server to files with ...
    (SunManagers)
  • Re: Cant change NIS+ password in NIS+ client
    ... >> this in a firewall? ... There is still a NIS+ client, running Solaris ...
    (comp.unix.solaris)
  • /var/adm/messages file nopt being written to
    ... We are running solaris 9. ... Initially the syslogd was not running so started it up. ... It logs one message in the file and nothing more after that ...
    (SunManagers)