SUMMARY rpc.ttdbserverd

From: Alan Douglas (alan.douglas_at_mentec.ie)
Date: 03/29/04

  • Next message: John Galt: "Enhanced security files migration from one system to another" 
    Date: Mon, 29 Mar 2004 11:20:34 +0100
To: tru64-unix-managers@ornl.gov

    All,

    Unfortunately after going through Johns suggestions below, I was still left
    with the errors. I got on to HP support, and after a discussion decided that
    it was quicker and safer to re-install the O/S. I know that doesn't fix the
    problem, but I had that option open to me. Johns detailed and informative
    response is below my original mail.

    Regards,
    Alan

    Alan Douglas wrote:

    > Hi all,
    >
    > I renamed a DS10 v5.1a for administrative purposes. I also patched it
    from
    > PK4 to PK6. After all was completed I am getting an error. I have done
    > similar before without a problem.
    > I don't have the exact error to hand, but it relates to rpc.ttdbserverd.
    It
    > gives the old server name and gives an error relating to clnt_create.
    >
    > I can get more information, but that is mostly what it gives. I tried
    > deleting the TT.DB from root, but it recreated it and gave the same error
    on
    > reboot.
    >
    > Any ideas? I would also like to know what impact an error like this might
    > have.
    > I have done some research but nothing conclusive. It seems to relate to
    CDE
    > toolkit, but I don't have anything relating to my exact error.
    >
    > Thanks,
    > Alan

    Hello,

    May want to check that you have covered these bases:

    As root:

            1. # rcmgr set HOSTNAME newname

            2. Edit the /etc/hosts file and make the following change

                    From:

                    #

                    127.0.0.1 localhost

                    16.72.0.156 oldname

                    To:

                    #

                    127.0.0.1 localhost

                    16.72.0.156 newname

            3. If using AdvFS, edit /var/opt/advfsd/socket/hosts.allow

                    From:

                    oldhostname.domain.com

                    To:

                    newhostname.domain.com

            4. Reboot the system at a convenient time.

                    # shutdown -r now

            5. Edit the system configuration file so you can rebuild

                the kernel the next time it is needed. The next kernel

                rebuild, you will want to do "doconfig -c NEWNAME," after

                doing the following commands:

                    # cd /sys/conf

                    # cp OLDNAME NEWNAME

                    # vi NEWNAME

                From:
                    ident "OLDNAME"

                To:
                    ident "NEWNAME"

            6. Move the options' HOSTNAME.list file to NEWNAME.list:

                    # cd /sys/conf
                    # cp OLDNAME.list NEWNAME.list

            7. Re-create the link to the kernel rebuild subdirectory:

                    # cd /sys
                    # rm -rf OLDNAME
                    # ln -s ../usr/sys/NEWNAME NEWNAME

                If the directory '/usr/sys/NEWNAME NEWNAME' already
                exists, it is renaming the system to a name it had
                previously. Remove it and it will be re-created
                when doconfig is run.

                    # cd /usr/sys/
                    # rm NEWNAME

                If the system was part of a network, the appropriate hosts
                files on the other systems will also have to be edited to
                reflect the change.

    --John Lanier

    CONFIDENTIALITY NOTICE
    This email is private and confidential and may contain legally privileged
    information.If you are not named above as an addressee it may be unlawful
    for you to read, copy, distribute, disclose or otherwise use the information
    in this email. If you are not the intended recipient of this email please
    contact our systems manager.
    Thank you.
    Any views or opinions presented are solely those of the author and do not
    necessarily represent those of the company or its associated companies
    unless otherwise specifically stated.

  • Next message: John Galt: "Enhanced security files migration from one system to another"