Conference azur::mcc

2822.0. "Error creating domain with new ULTRIX T1.2.7 kit" by SLINK::HOOD (Just add water) Wed Apr 22 1992 14:52

When I try to create a new domain on a system with a local nameserver running
the new (16-APR-1992) T1.2.7 ULTRIX BMS kit, I get the following error window:
            +--------------------- CREATE DOMAIN -------------------------+
            | 1992-04-22-10:40:54:816                                     |
            | The requested operation cannot be completed.                |
            | MCC Unhandled Service Reply: The requested operation cannot |
            |                              be completed                   |
            |                              %MCC-E-IO_ERROR, error was     |
            |                              returned by I/O facility       |
            |                     +--------------+                        |
            |                     | Acknowledged |                        |
            |                     +--------------+                        |
            +-------------------------------------------------------------+
And, on the DECterm which created the mcc process:
	Fatal MIR I/O error, repository=mcc_dns_ent, errno=1: Not owner

I did the following:
	(1) used setld to delete all installed MCR kits.
	(2) deleted the /var/mcc and /usr/mcc directory trees and files.
	(3) installed bms, dna5, and dtk
	(4) ran as root.  Worked ok.
	(5) ran as hood.  Watched errors happen.
	(6) set protection to 666 for all files in /var/mcc where the mir's
	    and dns files are.
	(7) ran as hood.  Watched errors happen.
	(8) Thought, "I think I'll re-install BMS."
	(9) setld -d MCRBMSxxx,   setld -l <MCRBMSxxx>
	(10) ran as hood. Watched errors happen.

Help, please.
Tom

The problem is the protection on the /var/mcc directory itself.  It needs
to be world-write.  When we changed the protection to 777 (instead of 775)
it worked ok.  

Perhaps the installation kit should do this?

Thanks,
Tom

	(5) ran as hood.  Watched errors happen.
	(6) set protection to 666 for all files in /var/mcc where the mir's
	    and dns files are.

> Did you restart you MMs at this point (mcc_kill to stop them)?
> Otherwise, the old protection is still in effect.

	(7) ran as hood.  Watched errors happen.

>The problem is the protection on the /var/mcc directory itself.  It needs
>to be world-write.  When we changed the protection to 777 (instead of 775)
>it worked ok.  

>Perhaps the installation kit should do this?

We are not permitted to create world writable directories on the customer
systems.  But if this is not clear in the documentation, then the documentation
should be fixed.

-- Erik

re: -1

>The problem is the protection on the /var/mcc directory itself.  It needs
>to be world-write.  When we changed the protection to 777 (instead of 775)
>it worked ok.  

>Perhaps the installation kit should do this?

Instead of having to go through all of this, perhaps the mcc_domain_fm
needs to have the setuid bit set when it is installed.  Then when it is
owned by root, you don't have to modify the protections on the files,
since root has all the access you could ever want.

Karen

I understand that security can be a pain.  But we can't take security
away from the system managers (they may not WANT everyone to be able
to modify the DECmcc MIR...)

-- Erik