I'm trying Aaron Coburn's approach to getting better debug information
from the XML::RPC code in utils.pm.  But along the way I've hit a fresh
snag.

I had been working on (what will be) our production VCL server, but
since I'm tinkering with the code I moved my effort to the development
instance.  Now, when I try to make a block reservation I get a different
error.  From vcld.log:

 2012-10-12 10:19:50|2477|blockrequest|blockrequest.pm:process(167)|help 
address:
 2012-10-12 10:19:50|2477|blockrequest|blockrequest.pm:process(172)|updated 
process flag on blocktime_id= 7
 2012-10-12 10:19:50|2477|blockrequest|blockrequest.pm:process(192)|processing 
blocktime_id= 7 pass 1
 2012-10-12 
10:19:50|2477|blockrequest|utils.pm:xmlrpc_call(9105)|argument_string= 
XMLRPCprocessBlockTime 7 1
 2012-10-12 10:19:50|2477|blockrequest|blockrequest.pm:process(216)|xmlrpc 
error on blockrequest_id=6 blocktime_id=7 : access denied for managing block 
allocations
 2012-10-12 10:19:55|2477|blockrequest|blockrequest.pm:process(192)|processing 
blocktime_id= 7 pass 2
 2012-10-12 
10:19:55|2477|blockrequest|utils.pm:xmlrpc_call(9105)|argument_string= 
XMLRPCprocessBlockTime 7 1
 2012-10-12 10:19:55|2477|blockrequest|blockrequest.pm:process(216)|xmlrpc 
error on blockrequest_id=6 blocktime_id=7 : access denied for managing block 
allocations
 2012-10-12 10:20:00|2477|blockrequest|blockrequest.pm:process(192)|processing 
blocktime_id= 7 pass 3
 2012-10-12 
10:20:00|2477|blockrequest|utils.pm:xmlrpc_call(9105)|argument_string= 
XMLRPCprocessBlockTime 7 1
 2012-10-12 10:20:01|2477|blockrequest|blockrequest.pm:process(216)|xmlrpc 
error on blockrequest_id=6 blocktime_id=7 : access denied for managing block 
allocations


That repeats for three more cycles and then it gives up.

>From the "access denied" error I thought we might have a problem with
our vclsystem account, but there's no way to change or verify the
password, so I deleted it (and its foreign key records) from the
database and recreated it.  No difference.

So what's broken now?


-- 
Michael Jinks :: [email protected]
University of Chicago IT Services

Reply via email to