[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

1072.0. "3.0 Agent Problem" by DECWET::WHITE (Surfin' with the Alien) Thu Apr 18 1996 20:42

I get the follwing error trying to start up the scheduler
3.0 agent:

The Distributed Computing Environment (DCE) system was NOT found
to be running on the current node. The DCE RPC daemon -rpcd- is
required to be running before starting POLYCENTER Scheduler V3.0.

**this is not true, I did install it!!!***

Checking configuration

You currently have no DCE services configured.

(rpcd) Verify that no other rpcd/llbd is running: (0x16c9a003) cannot bind socke
t (dce / rpc)
(rpcd) Verify that no other rpcd/llbd is running: (0x16c9a003) cannot bind socke
t (dce / rpc)
(rpcd) Verify that no other rpcd/llbd is running: (0x16c9a003) cannot bind socke
t (dce / rpc)

Sorry, UNABLE to START RPC daemon.
Startup script exiting with failure.
PLEASE REPORT THIS CONDITION TO SYSTEM MANAGER



-Stephen
T.RTitleUserPersonal
Name
DateLines
1072.1Conflict between llbd and rpcdMUZICK::MORIARTYFri Apr 19 1996 14:0629
    
    Stephen,
    
    	       In the POLYCENTER Scheduler Release Notes (README file)
            there is an item about the conflict in running the UNIX
            Local Location Broker Daemon (LLBD) and Distributed
            Computing Environment (DCE) Remote Procedure Call Daemon
            (RPCD). 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. However DCE RPCD will do 
    	    all the communication the LLBD currently does.
    
            For system which did not have DCE services configured and had
            POLYCENTER Scheduler the DCE run time services where started up
            by Scheduler would fail. The Scheduler is S90schedule and thus
            is after the S66llbd start. It is not a problem to have the
    	    startup of Scheduler to stop the LLBD and even the GLB daemons.
    	    The other thing to do is in /sbin/rc3.d remove the softlink
    	    S66llbd and let Scheduler startup DCE automatically. 
    
    	    Note: The DCE rpc daemon will do all of the communication 
    		  the Local Location Broker Daemon (LLBD) currently 
                  does for the Fullsail product.
     
    	    Needless to say you can manually kill the rpcd/llbd and 
    	    the startup the /usr/bin/rpcd image. 
    
    	    Hope this helps.....	
1072.2thanks Shawn!!DECWET::WHITESurfin' with the AlienFri Apr 19 1996 15:590