[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | SCHEDULER |
| Notice: | Welcome to the Scheduler Conference on node HUMANE ril |
| 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 |
1071.0. "Again proxy problems." by BACHUS::WILLEMS (Johan Willems @BRO DTN 856-8739) Thu Apr 18 1996 17:12
Hallo,
A customer called today with a proxy problem.
The job with the problem is as follows.
$ sched sh job 198/full
Job Name Entry User_name State Next Run Time
-------- ----- --------- ----- -------------
CHECK_BCCS 198 SYS$SCHEDULE Scheduled 18-APR-1996 14:10 [NXT]
VMS_Command : @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
Group : EXP Type : SYSTEMRUNNING
Comment : BCCS package envir. verification
Requested State : Run
Last Start Time : 18-APR-1996 10:30
Last Finish Time : 18-APR-1996 14:05 Last Exit Status : 0C968A92
Schedule Interval : +0 00:05 Mode : Remote
Mail to : SYS$MAIL_LIST (Always)
Days : ALL
Output File : sys$sysdevice:[000000]TITI.LOG
Cluster_CPU : <Ignored> User not notified on completion
Remote User/Node : BCCS_OPER@BKS004
Max_Time Warning : None Job Always retained
Stall Notify : None No Retry on Error
Success Count : 1 Failure Count : 45
Owner UIC : [200,201] Restart on Crash
No Pre or Post Function for this job
No local jobs depend upon this job.
This job has no Dependencies on other jobs
$ sched
And the proxies defined on BKS004 (The file is copied to
sys$common:[sysexe]netproxy.dat (OpenVMS V5.5-2)
UAF> sh/proxy bks010::* (BKS010 is the server node)
Default proxies are flagged with (D)
BKS010::BCCS_OPER
BCCS_OPER (D)
BKS010::BEAUMET
BEAUMET (D)
BKS010::BREDAEL
BREDAEL (D)
BKS010::EXPSYSTEM
EXPSYSTEM (D)
BKS010::FIELD
FIELD (D)
BKS010::HINDERICKX
HINDERICKX (D)
BKS010::MEDIA
MEDIA (D)
BKS010::SLS
SLS (D)
BKS010::SYS$SCHEDULE
BCCS_OPER (D)
BKS010::SYSTEM
SYSTEM (D)
UAF>
The job does not run and get an invalid proxy error.
Following is the agent log file (with debugging level 5 on)
*** NSCHED$AGENT.LOG ***
543199474: close all other fds
543199474: chdir to SYS$MANAGER:
543199474: set default protection mask to s:rwed,o:rwed,g:rwe,w:
543199474: gp: prot mask: old: fffffa00 new: fffff800
543199474: gp: grandparent pid: 206090f2
543199474: gp: initing socket to listen
543199474: getting name of local host
543199474: getting local host address structure
543199474: No translation found for SCHED_MAX_RETRIES; using default value
543199474: No translation found for SCHED_MAX_PACKET_WAIT; using default value
543199474: No translation found for SCHED_MIN_PACKET_WAIT; using default value
543199474: No translation found for SCHED_PACKET_WAIT; using default value
543199474: opened requested socket 3
543199474: binding socket 3 to port 5481
in open job file
initializing fab/rab
543199474: in init job management
in read next job rec
start=1, active=1
looking for next record
No record l_found: 98938
543199474: i_rcv_socket: 3
543199474: UEU RCV: waiting for IO on socket 3
543199474: ueu_wait_for: starting
543199474: ueu_wait_for - timeout: 30/0
543199474: ueu_wait_for: calling select
543199474: ueu_wait_for: select done
543199474: ueu_wait_for: io received; returning
543199474: received connection on new socket 4 from node 1.58.81.5 port 4313
543199474: ueu_receive_one_message: starting
543199474: ueu_receive_one_message: block SIGCLD
543199474: ueu_receive_one_message: recv on socket 4
543199474: ueu_receive_one_message: reset signals
543199474: 256 bytes read from socket 4 port: 4313 address: 1.58.81.5 at Thu A
pr 18 12:05:34 1996 (829829134)
543199474: ueu_receive_one_message: about to shutdown socket
543199474: ueu_receive_one_message: about to close socket 4
543199474: ueu_receive_one_message: returning
543199474: Dump Packet:
543199474: Type: Comment
543199474: Type: Executor Username BCCS_OPER
543199474: Type: Scheduler Username SYS$SCHEDULE
543199474: Type: Command @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: Type: Protocol 1.1
543199474: Type: OSS Version 2.1
543199474: Type: Output File sys$sysdevice:[000000]TITI.LOG
543199474: Type: Job Number 198
543199474: Type: Message Type 1
543199474: Type: Reply Port 0
543199474: Type: HW Type 1
543199474: Type: SW Type 6
543199474: Type: Packet ID 829081472
543199474: Type: Send PID 985
543199474: gp: status from ueu_listen_for_message: 0
543199474: gp: received packet on W K PORT
543199474: gp: in ues_main
543199474: packet read from address: 1.58.81.5
543199474: gp: getting packet protocol version
543199474: Dump Packet:
543199474: Type: Comment
543199474: Type: Executor Username BCCS_OPER
543199474: Type: Scheduler Username SYS$SCHEDULE
543199474: Type: Command @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: Type: Protocol 1.1
543199474: Type: OSS Version 2.1
543199474: Type: Output File sys$sysdevice:[000000]TITI.LOG
543199474: Type: Job Number 198
543199474: Type: Message Type 1
543199474: Type: Reply Port 0
543199474: Type: HW Type 1
543199474: Type: SW Type 6
543199474: Type: Packet ID 829081472
543199474: Type: Send PID 985
543199474: gp: protocol version V1.1
543199474: gp: getting oss version and message type
543199474: Dump Packet:
543199474: Type: Comment
543199474: Type: Executor Username BCCS_OPER
543199474: Type: Scheduler Username SYS$SCHEDULE
543199474: Type: Command @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: Type: Protocol 1.1
543199474: Type: OSS Version 2.1
543199474: Type: Output File sys$sysdevice:[000000]TITI.LOG
543199474: Type: Job Number 198
543199474: Type: Message Type 1
543199474: Type: Reply Port 0
543199474: Type: HW Type 1
543199474: Type: SW Type 6
543199474: Type: Packet ID 829081472
543199474: Type: Send PID 985
543199474: gp: oss client version V2.1
543199474: gp: received STARTJOB packet
543199474: Dump Packet:
543199474: Type: Comment
543199474: Type: Executor Username BCCS_OPER
543199474: Type: Scheduler Username SYS$SCHEDULE
543199474: Type: Command @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: Type: Protocol 1.1
543199474: Type: OSS Version 2.1
543199474: Type: Output File sys$sysdevice:[000000]TITI.LOG
543199474: Type: Job Number 198
543199474: Type: Message Type 1
543199474: Type: Reply Port 0
543199474: Type: HW Type 1
543199474: Type: SW Type 6
543199474: Type: Packet ID 829081472
543199474: Type: Send PID 985
543199474: packet contents:
543199474: jobnumber: 198
543199474: command: @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: execuser: BCCS_OPER
543199474: scheduser: SYS$SCHEDULE
543199474: outputfile: sys$sysdevice:[000000]TITI.LOG
543199474: comment:
543199474: replyport: 0
543199474: after unload packet: client address: 1.58.81.5
543199474: gp: calling validate client
543199474: in validate_client
543199474: about to call gethostbyaddr for node 1.58.81.5 ( 5513a01)
543199474: gethostbyaddr returned 548848
543199474: lookup succeeded
543199474: schednode set to BKS010
543199474: gp: status of validate client = 0
543199474: after validate client: client address: 1.58.81.5
543199474: gp: received job start packet
543199474: gp: packet is for job number: 198 from node BKS010
543199474: gp: in check job exists
in read job rec
looking for job/node 198::BKS010 active
No MATCH l_found: 98994
in read job rec
looking for job/node 198::BKS010 active or inactive
No MATCH l_found: 98994
543199474: packet: sched username: SYS$SCHEDULE
543199474: exec username: BCCS_OPER
543199474: command: @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: output file: sys$sysdevice:[000000]TITI.LOG
543199474: job number: 198
543199474: reply port: 0
543199474: receieved job 198 from scheduler node BKS010
543199474: local username: BCCS_OPER
543199474: remote username: SYS$SCHEDULE
543199474: command: @EXPDISK5:[BCCS.BANKSYS]CHECK_BCCS
543199474: output file: sys$sysdevice:[000000]TITI.LOG
543199474: in ues_start_job_validate
543199474: call validate inet
543199474: in validate_inet
543199474: client address:
543199474: family: 2
543199474: port: 4313
543199474: address: 1.58.81.5
543199474: status of validate inet = 0
543199474: calling validate port
543199474: in validate_port
543199474: status of validate port = 0
543199474: calling validate username
543199474: in validate_username
543199474: status of validate username = 0
543199474: calling change dir
543199474: calling validate proxy
543199474: in validate_proxy
543199474: clientname: BKS010
543199474: in RUSEROK (check proxy)
543199474: checking NETPROXY.DAT for remote user SYS$SCHEDULE from node BKS010
matching local user BCCS_OPER
543199474: proxy check - nodes or users are the different
543199474: proxy check - checking NETPROXY.DAT for user: 'SYS$SCHEDULE' from n
ode: 'BKS010'
543199474: proxy check - searchkey is 'BKS010 SYS$SCHED
ULE '
543199474: proxy check - checking local user: BCCS_OPER
543199474: compared BCCS_OPER in NETPROXY record to BCCS_OPER; NO Match
543199474: proxy check - NO match in NETPROXY.DAT for local user BCCS_OPER
543199474: status of ruserok: -1
remote proxy access denied543199474: status of validate proxy = -1
*** validation error: -8
Job failed to execute
543199474: gp: NACK - invalid proxy
543199474: in ueu_send_to_address
543199474: connect: 0, shutdown: 1, close: 1
543199474: in ueu_add_id_to_packet
543199474: adding packet id: 829829128 to the packet
543199474: adding pid: 543199474 to the packet
543199474: in ueu_send_one_message
543199474: connect: 0, shutdown: 1, close: 1
543199474: send socket is not 0 ; using socket 4
543199474: connect flag FALSE; not connecting socket 4
543199474: sending to port 4313, address 1.58.81.5, on socket 4
543199474: called send, at Thu Apr 18 12:05:35 1996 (829829135)
543199474: status from sendto: 132
543199474: shutdown socket 4 status 0
543199474: closed socket 4 status 0
543199474: validation error; job BKS010::198 is NOT accepted
543199474: gp: status from ues_process_packet: 0
543199474: gp: in dispatch_pending
543199474: gp: pending que is empty
543199474: gp: status from ues_dispatch_pending: 0
543199474: i_rcv_socket: 3
543199474: UEU RCV: waiting for IO on socket 3
543199474: ueu_wait_for: starting
543199474: ueu_wait_for - timeout: 29/0
543199474: ueu_wait_for: calling select
--------------------------------------------
Can somebody explain from this what goes wrong????
I did some test on our local machine and there all went ok.
Kind regards.
Johan
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1071.1 | forgot versions | BACHUS::WILLEMS | Johan Willems @BRO DTN 856-8739 | Thu Apr 18 1996 17:14 | 7 |
| Sorry,
Forgot to mention that the agent is running on OpenVMS V5.5-2 and the
agent version is V2.1B-04
Johan
|
| 1071.2 | Location of netproxy database??? | CSC32::G_BURTT | | Thu Apr 18 1996 18:46 | 5 |
| Where is the NETPROXY database located? Does the customer have netproxy defined
to someplace other than SYS$SYSTEM? This is a known problem if he has moved it.
Gary Burtt
Colorado CSC
|
| 1071.3 | Problem found but not solved ! | BACHUS::BANKEN | | Fri Apr 19 1996 12:52 | 20 |
| Hello,
I just take this problem over during Johan's absence.
There is apparently a known bug in Scheduler concerning proxies ( see note 1007)
In short, the local username and the remote one must have the same lenght !
I tried it and indeed that works ( bks010::scheduler bccs_oper -> each 9 characters).
Can someone tell me if there is a fixe available for that problem and if not when ?
Thanks in advance.
Alain.
|
| 1071.4 | VMS Agent V2.1B-5 kit solves the problem | MUZICK::MORIARTY | | Fri Apr 19 1996 14:22 | 9 |
|
There is a fixed version for the proxy mechanism which you mentioned
and is available via proxy access, please contact the following
people to grant you access for the VMS Agent V2.1B-5 kit.
A proxy will be granted to you to copy the kits over the net.
Please contact Bob Puishys (project leader) or Raminder Bhatia
(product manager) if you need additional information.
|