Project

General

Profile

Bug #15371

Stdout messages from startup script in SL7 are confusing

Added by Marco Mambelli over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
01/30/2017
Due date:
% Done:

0%

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

Description

The new startup scripts on SL7 are printing messages only when invoked when the service is stopped.
Otherwise the messages go only on the log files.

Furthermore there is a confusing "no argument: I have to run kill -1 with the frontend PID" when invoking the reconfig command.

All this is inconsistent and may be confusing for operators. Below some examples of this behavior

[root@fermicloud132 ~]# /usr/sbin/gwms-frontend stop
Shutting down glideinWMS frontend fermicloud132-fnal-gov_OS[  OK  ]ontend:
You have new mail in /var/spool/mail/root
[root@fermicloud132 ~]# /usr/sbin/gwms-frontend reconfig
Using default Frontend config file: /etc/gwms-frontend/frontend.xml
...Saved the current config file into the working dir
...Saved the backup config file into the working dir
...Reconfigured frontend 'fermicloud132-fnal-gov_OSG_gWMSFrontend'
...Active groups are:
     main
...Verifying rrd schema
...Work files are in /var/lib/gwms-frontend/vofrontend
Reconfiguring the frontend                                 [  OK  ]
[root@fermicloud132 ~]# /usr/sbin/gwms-frontend upgrade
Using default frontend config file: /etc/gwms-frontend/frontend.xml
...Updated the frontend_startup script
...Saved the current config file into the working dir
...Saved the backup config file into the working dir
...Reconfigured frontend 'fermicloud132-fnal-gov_OSG_gWMSFrontend'
...Active groups are:
     main
...Verifying rrd schema
...Work files are in /var/lib/gwms-frontend/vofrontend
...Overriding the frontend config file in /etc/gwms-frontend/frontend.xml to the current configuration
Upgrading the frontend                                     [  OK  ]
[root@fermicloud132 ~]# /usr/sbin/gwms-frontend start
Starting glideinWMS frontend fermicloud132-fnal-gov_OSG_gWM[  OK  ]d:
[root@fermicloud132 ~]# /usr/sbin/gwms-frontend reconfig
no argument: I have to run kill -1 with the frontend PID
[root@fermicloud132 ~]# /usr/sbin/gwms-frontend upgrade
[root@fermicloud132 ~]#

Tickets [#4586] and [#14194] changed these scripts last introduciong this in 3.2.17.
This affects only SL7, not SL6

History

#1 Updated by Parag Mhashilkar over 2 years ago

  • Target version changed from v3_2_x to v3_2_18

#2 Updated by Parag Mhashilkar over 2 years ago

  • Assignee set to HyunWoo Kim

#3 Updated by Marco Mambelli over 2 years ago

1. I was not expecting reload to be invalid. What happened?
2. Would be nice to have 'reconfig' as alias of reload (for consistency for the admins)

[root@fermicloud132 ~]# /bin/systemctl restart gwms-frontend
[root@fermicloud132 ~]# /bin/systemctl reload gwms-frontend
Job for gwms-frontend.service invalid.
[root@fermicloud132 ~]# /bin/systemctl reconfig gwms-frontend
Unknown operation 'reconfig’.

#4 Updated by HyunWoo Kim over 2 years ago

I saw "Job for gwms-frontend.service invalid" message from reload command
when the service was not running.
I believe your restart command stopped it but did not start it successfully.

Making reconfig an alias for reload is a good idea.

#5 Updated by Marco Mambelli over 2 years ago

  • Status changed from New to Feedback
  • Assignee changed from HyunWoo Kim to Marco Mambelli

#6 Updated by Marco Mambelli over 2 years ago

  • Assignee changed from Marco Mambelli to HyunWoo Kim

#7 Updated by HyunWoo Kim over 2 years ago

  • Status changed from Feedback to Resolved

Merged into branch_v3_2

#8 Updated by HyunWoo Kim over 2 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF