Project

General

Profile

Bug #4574

Possible non-critical likely problem in subprocessSupport.py

Added by John Weigand over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
John Weigand
Category:
Factory
Target version:
Start date:
08/23/2013
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Back on 7/18/13, while assisting Dennis with an upgrade, he would get
this stacktrace when trying to start the factory.

> ./manage-glideins --start factory --ini new.ini
Commands: cd /home/gfactory/v2_7_1/factory;. ./factory.sh;cd /home/gfactory/v2_7_1/factory/glidein_v2_7_1; ./factory_startup start
PROGRAM ERROR: uncaught execption. Contact support
Traceback (most recent call last):
  File "/home/gfactory/v2_7_1/glideinwms/install/manage-glideins", line 459, in main
    process_request(service,gAction,inifile)
  File "/home/gfactory/v2_7_1/glideinwms/install/manage-glideins", line 202, in process_request
    factory(service,action,inifile)
  File "/home/gfactory/v2_7_1/glideinwms/install/manage-glideins", line 172, in factory
    run_command(service,obj.username(),obj.hostname(),cmd)
  File "/home/gfactory/v2_7_1/glideinwms/install/manage-glideins", line 55, in run_command
    common.logit(stdout)
UnboundLocalError: local variable 'stdout' referenced before assignment
None

This initially looked like a problem in the manage-glideins script where stdout was not
defined. On further investigation, it appears to be an issue in the subprocessSupport.py
module... maybe. It appears to be hitting a condition where no failure is detected
and stdout is getting None back... which makes no sense to me.

The condition we were getting this in was when the factory failed to start because we did not
have the log symlink defined in the working directory. It was a "LogDir" attribute error
(whatever that means). This was your typical hacked upgrade from one version to another on
the same node. We had to hack the code to even determine the error condition.

I could not pursue this further at the time as the priority was to get his services upgraded
and running again. Then I forgot.

John Weigand


Related issues

Related to GlideinWMS - Bug #5351: manage-glidein crashing when command invocation failsClosed02/05/2014

History

#1 Updated by Burt Holzman over 6 years ago

Hi John,

subprocessSupport is raising an exception and it's getting caught by manage-glideins.
The logic in retrieving the stdout is defective though. The subroutine doesn't return
and so that doesn't get defined. If you print out the exception, it has the stderr
inside and that may be enough to debug.

#2 Updated by John Weigand over 5 years ago

  • Status changed from New to Rejected

This is old and no longer an issue.
john Weigand

#3 Updated by John Weigand over 5 years ago

  • Status changed from Rejected to Closed


Also available in: Atom PDF