Project

General

Profile

Bug #5148

Factory RPM /etc/init.d/gwms-factory script does not work

Added by Parag Mhashilkar over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
RPM - Frontend/Factory
Target version:
Start date:
01/06/2014
Due date:
% Done:

0%

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

Description

The script we provide with the gwms-factory rpm is bugged and options other than start/stop/upgrade/update may not be working correctly. We need to test and fix all the other options.

[root@cmssrv160 work-dir]# service gwms-factory down CMS_T1_US_FNAL_ce4Setting downtime...COMMAND: manageFactoryDowntimes.py -cmd down -dir /var/lib/gwms-factory/work-dir down down CMS_T1_US_FNAL_ce4
Usage:
  manageFactoryDowntimes.py -dir factory_dir -entry ['all'|'factory'|'entries'|entry_name] -cmd [command] [options]
where command is one of:
  add           - Add a scheduled downtime period
  down          - Put the factory down now(+delay)
  up            - Get the factory back up now(+delay)
  ress          - Set the up/down based on RESS status
  bdii          - Set the up/down based on bdii status
  ress+bdii     - Set the up/down based both on RESS and bdii status
  check         - Report if the factory is in downtime now(+delay)
  vacuum        - Remove all expired downtime info
Other options:
  -start [[[YYYY-]MM-]DD-]HH:MM[:SS] (start time for adding a downtime)
  -end [[[YYYY-]MM-]DD-]HH:MM[:SS]   (end time for adding a downtime)
  -delay [HHh][MMm][SS[s]]           (delay a downtime for down, up, and check cmds)
  -ISinfo 'CEStatus'        (attribute used in ress/bdii for creating downtimes)
  -security SECURITY_CLASS  (restricts a downtime to users of that security class)
                            (If not specified, the downtime is for all users.)
  -frontend SECURITY_NAME   (Limits a downtime to one frontend)
  -comment "Comment here"   (user comment for the downtime. Not used by WMS.)

-cmd -dir and -entry arguments are required.
                                                           [FAILED]
[root@cmssrv160 work-dir]# 

History

#1 Updated by Krista Larson over 5 years ago

Also, why is the factory_startup script in the working dir? It can't be used for anything.

#2 Updated by Parag Mhashilkar over 5 years ago

I think this is also a good opportunity to modify the rpms to use init.d scripts that we ship with glideinwms.

#3 Updated by Marco Mambelli over 5 years ago

  • Assignee changed from Parag Mhashilkar to Marco Mambelli

#4 Updated by Marco Mambelli over 5 years ago

Handling this in 5071

#5 Updated by Marco Mambelli over 5 years ago

The following commands are supposed to work:

gwms-factory {down|up} -entry factory|entries|ENTRY_NAME [-delay DELAY] [-frontend SEC_NAME|All] [-security SEC_CLASS|All] [-comment COMMENT]
gwms-factory infosysdown [-delay DELAY] [-frontend SEC_NAME] [-security SEC_CLASS|All] [-comment COMMENT]
gwms-factory statusdown -entry factory|entries|ENTRY_NAME [-delay DELAY]

I will test them once 5071 is merged

The other options mentioned above are not passed from the init script.
Should support for those options be added?
Thanks,
Marco

#6 Updated by Marco Mambelli over 5 years ago

  • Status changed from New to Closed

See 5071 for details. Merged in branch_v3_2, ready for v3_2_4rc1 release



Also available in: Atom PDF