[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference humane::scheduler

Title:SCHEDULER
Notice:Welcome to the Scheduler Conference on node HUMANEril
Moderator:RUMOR::FALEK
Created:Sat Mar 20 1993
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1240
Total number of notes:5017

1095.0. "What exactly is required of DCE?" by NQOS01::nqsrv504.nqo.dec.com::WORKBENCH () Mon May 13 1996 17:14

I need some clarification on what is required from DCE for POLYCENTER 
scheduler.  I am trying to install scheduler at a customer site. The 
customer does not normally use DCE.  The only reason we would require DCE 
at all is as a scheduler prerequisite.  My questions are...

1)	What components of DCE do I need to configure as a minimum for 	
	scheduler?

2)	What DCE licenses do we need?  I currently have all of them
	on loan to get scheduler running, but I need to know which ones
	I need permanently.

3)	I currently run llbd for POLYCENTER Performance Monitor.  	
	Apparently llbd and rpcd cannot run together.  How can I
	get around this?

4)	The system that scheduler was purchased for runs C2 security.  
	If I need the security component for DCE, it appears to conflict
	with C2.  If I don't configure the security component, DCE fails 
	to start.  Any ideas?


Versions:

	Digital UNIX V3.2A
	Scheduler V3.0

Sorry for my DCE ignorance, but I haven't had any reason to educate myself 
on it until now.


Thanx
John
T.RTitleUserPersonal
Name		DateLines
1095.1Just install runtime onlyMRBASS::PUISHYSProject Leader Scheduler V3.0 for Digital UNIXMon May 13 1996 18:239
Just install it.

When things start you get an warning that dce is not configed, but that is ok.

All we use is the runtime services specificaly  RPCD

bob
1095.2help!OPCO::TSG_BHLWhen too much horsepower is barely enuff!!Tue May 14 1996 07:4169
    
    mmmm...having just done this myself, I get the following problem when
    starting scheduler.
    
    ie
    aremis_# /sbin/rc3.d/S90schedule start
    
    
        Checking configuration
    
    You currently have no DCE services configured.
    
    
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    ***************************************************
    ***
    ***         Sorry, UNABLE to START DCE RPC daemon
    ***   Startup of POLYCENTER Scheduler exiting with failure.
    ***     PLEASE REPORT THIS CONDITION TO SYSTEM MANAGER
    ***
    ***************************************************
    
    
    aremis_# lmf list
    Product                   Status                     Users: Total     
    Active
    
    DECSCHEDULER-EXEC         active                            unlimited
    DCE-RT-SVC                active                            unlimited
    DECSCHEDULER              active                            unlimited
    
    
    aremis_# setld -i | grep SCH
    SCHAGNT300                      POLYCENTER Scheduler V3.0 Agent for
    Digital UNIX
    SCHCLNT300      installed       POLYCENTER Scheduler V3.0 Client for
    Digital UNIX
    SCHSRVR300      installed       POLYCENTER Scheduler V3.0 Server for
    Digital UNIX
    
    aremis_# setld -i | grep -i dce
    DCEADK130                       DCE Application Dev Kit V1.3
    DCEADKMAN130                    DCE Application Developers Manual Pages
    V1.3
    DCECDS130                       DCE CDS Server V1.3
    DCEDFS130                       DCE DFS Base V1.3
    DCEDFSBIN130                    DCE DFS Kernel Binaries V1.3
    DCEDFSMAN130                    DCE DFS Manual Pages V1.3
    DCEDFSUTL130                    DCE DFS Utilities/Debug V1.3
    DCEMAN130                       DCE Administration Manual Pages V1.3
    DCERTS130       installed       DCE Runtime Services V1.3
    DCESEC130                       DCE Security Server V1.3
    
    
    
    
    Am I missing something or does dce need to be configured???
    
    
    thanks
    
    Byron
1095.3MRBASS::PUISHYSProject Leader Scheduler V3.0 for Digital UNIXTue May 14 1996 14:007
Have you install dce?
If so do you have the performance monitor running?  If so it uses 
llbd which dce prcd is a superset of.  They can not both run at the same time.

See readme for information on how to fix.

bob
1095.4what readme?NQOS01::nqsrv128.nqo.dec.com::WORKBENCHTue May 14 1996 18:255
What readme are you referring to?

John
1095.5hmmmmmOPCO::TSG_BHLWhen too much horsepower is barely enuff!!Wed May 15 1996 03:0236
    
    mmm...the README's answer is very useful.
    
    o  POLYCENTER Scheduler uses the Distributed Computing
    Environment (DCE) Remote Procedure Call Daemon for all
    communication between Scheduler components. Since RPCD
    is part of the DCE run-time services, you must install
    the run-time services (DCERTS130) on the each system on
    which you install a Scheduler component (server,agent,
    or user interface). RPCD must be running when Scheduler
    is started up.
    
    The RPCD startup will fail if a Local Location Broker
    Daemon (LLBD) is already running on the system, because
    the LLBD uses the same port number as the RPCD. Use
    the RPCD instead of the LLBD (RPCD supports the same
    interface as the LLBD).
    
    If an LLBD is running on the system, the following
    message is displayed:
    
    (rpcd) Verify that no other rpcd/llbd is running:
            (0ex12801a) cannot bind socket (dce / rpc)
    
    In this case, you must remove or disable the LLBD. Refer
    to the DCE documentation set for information on removing
    the LLBD.
    
    
    I will  of course look in the DCE documentation. I wonder what this
    does to Polycentre Performance Advisor?
    
    thanks
    
    Byron
1095.6getting closerOPCO::TSG_BHLWhen too much horsepower is barely enuff!!Wed May 15 1996 03:1038
    
    Ok killed llbd and PSDC seems ok.
    
    now rpcd still fails to start even when run by hand ie
    
    aremis_# ps ax | grep llbd
    13415 ttyp3    S  +     0:00.00 grep llbd
    aremis_# ./S90schedule start
    
    
        Checking configuration
    
    You currently have no DCE services configured.
    
    
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    (rpcd) Unable to rpc_server_use_all_protseqs for ept: (0x16c9a029)
    cannot inquire socket (dce / rpc)
    ***************************************************
    ***
    ***         Sorry, UNABLE to START DCE RPC daemon
    ***   Startup of POLYCENTER Scheduler exiting with failure.
    ***     PLEASE REPORT THIS CONDITION TO SYSTEM MANAGER
    ***
    ***************************************************
    
    what now??
    
    
    thanks
    
    Byron
1095.7How do I get these 2 POLYCENTER products working simultaneouslyNQOS01::nqsrv328.nqo.dec.com::WORKBENCHWed May 15 1996 14:5126
The readme doesn't address how to get POLYCENTER Performance Monitor 
(which uses llbd) and POLYCENTER Scheduler (which uses rpcd) to run on the 
same box.  The reason I am currently running llbd is that it is required 
by POLYCENTER Performance Monitor (this is the real-time monitor that used 
to be part of Full Sail, and I think is now being bundled in some fashion 
into dunix V4.0).

Please don't tell me that Digital is selling two products called 
POLYCENTER that can't run on the same system.  This would be an 
embarassing message to have to deliver to my customer.

Thanx
John

BTW: Are there any plans to make the scheduler installation consistent 
with other Digital UNIX software, e.g. release notes in 
/cdrom/<product>/documentation, software installed into /usr/opt, and 
of course most importantly on the standard software distribution.


One other thing...

The job exception window in the GUI is too small and clips its contents.  
It makes the window useless, since there is no way to say "OK" or "Apply".
I'm assuming these buttons are down at the bottom of the window, but I 
can't see them.
1095.8DCE does the work instead of LLBDMUZICK::MORIARTYThu May 16 1996 19:45102
    
    1) DCE run time services (RTS) will not bind to the socket.
    
       The problem with starting the remote procedural 
       call daemon (RPCD) of RTS DCE is that it is attempting 
       to bind to DECNET which if I were to guess is not configured 
       or configured wrong. The solution is to either fix DECNET 
       on the machine or better yet if you do not need DECNET 
       communication with RPCD follow the instructions in the 
       README file Section 2.1:
    
       Follow these steps to disable the DECnet communication
       protocol during DCE startup:
    
       1. Shut down the DCE RPC daemon. You cannot perform the
          steps that follow if the daemon is running.
    
       2. Delete the file /var/dce/local/var/rpc/rpcdep.dat if
          it exists. (Since DCE creates this file at startup
          time, the file will not exist if the DCE RPC daemon
          has never been started.) You need to perform this
          step only once. After you complete these steps, when
          the DCE RPC daemon creates this file at startup time,
          only TCP and UDP will be registered.
    
       3. Find and uncomment the following lines in the file
          sched_init.sh, in the Scheduler home directory /var/sched:
    
          #RPC_SUPPORTED_PROTSEQS=ncacn_ip_tcp:ncadg_ip_udp
          #export RPC_SUPPORTED_PROTSEQS
    
       4. Start up POLYCENTER Scheduler Version 3.0. The
          startup procedure checks to see if the DCE RPC daemon
          is running. If it isn't, Scheduler gives you the
          option of starting it. When the Scheduler startup
          procedure starts up the DCE RPC daemon, DCE reads
    	  the environment variable RPC_SUPPORTED_PROTSEQS.
    
          ________________________ Note ________________________
    
          If you have previously performed the first three
          steps, this step will be performed automatically
          during console startup when the system is rebooted.
    
          ______________________________________________________
       
    2)  Use of Local Location Broker Daemon (LLBD) and Distributed
    	Computing Environment (DCE) Remote Procedure Call Daemon.
    
    	The Fullsail product known in POLYCENTER as the
        Performance Monitor and Solution Tools for UNIX uses the
        LLBD while Scheduler uses RPCD. Both of these daemons can
        not be running at the same time.
    
        DCE is that they they each have a daemon process that allows
        registration of local RPC servers.  They are architected to have
        the endpoint mapper listen and hard coded to the same port 135.
    
        Try running "netstat -A | grep 135" to see if the port is in use.
        This may have actually been done intentional because the DCE RPC
        daemon is intended to be a superset of the Apollo RPC daemon,
        as it can be used instead. The functionality provided by LLBD
        is in RPCD of DCE.
    
    	To be clear: RPCD will do all the communication that the product
                     Full Sail needs in place of LLBD.
    
    	CONSOLE STARTUP: In order to guarantee the startup of LLBD 
                         is disabled remove the softlink in /sbin/rc3.d
    			 called S66llbd.
    
    
    >> BTW: Are there any plans to make the scheduler installation consistent
    >> with other Digital UNIX software, e.g. release notes in
    >> /cdrom/<product>/documentation, software installed into /usr/opt, and
    >> of course most importantly on the standard software distribution.
    
    The installation is consistent with product which are not operating
    system specific and therefore do not belong in /usr/opt. Actually
    it is a requirement on the gold release we place Scheduler on the 
    "/var" parition. The reason the CD directory (documentation) is 
    different is because standard software distribution does the 
    consolidation of UNIX products while Scheduler is done as an IPO.
    This will be resolved in time I am sure.
    
    >> The job exception window in the GUI is too small and clips its contents.
    >> It makes the window useless, since there is no way to say "OK" or "Apply".
    >> I'm assuming these buttons are down at the bottom of the window, but I
    >> can't see them.
    
    I am unsure of the terminal type you are using. It is a problem for
    certain terminal types and is being addressed for next release.
1095.9coolOPCO::TSG_BHLWhen too much horsepower is barely enuff!!Fri May 17 1996 01:036
    
    Cool,
    
    point 1) seems to do the trick, thanks for the time.
    
    Byron
1095.10MRBASS::PUISHYSProject Leader Scheduler V3.0 for Digital UNIXFri May 17 1996 17:348
Also Byron,

	The scheduler and performace advisor do work fine together as long
as you start rpcd before the performance advisor.

rpcd is a will do everything llbd does and more.

bob