Project

General

Profile

Actions

Bug #6051

closed

Warning after policy generation, /bin/pidof does not exists

Added by Vincent MEMBRÉ over 7 years ago. Updated over 6 years ago.

Status:
Released
Priority:
1
Assignee:
Matthieu CERDA
Category:
System integration
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:

Description

After updating my promises, I got this message:

[2014-12-30 02:32:20] WARN  com.normation.rudder.services.policies.RudderCf3PromisesFileWriterServiceImpl - Failed to reload CFEngine server promises with "command /usr/bin/killall -SIGHUP cf-serverd || /bin/kill -SIGHUP `/bin/pidof cf-serverd 2>/dev/null`" - cause is  `/bin/pidof: No such file or directory

On SLES11 and RHEL6, pidof path is /sbin/pidof ...


Subtasks 2 (0 open2 closed)

Bug #6054: Warning after policy generation, /bin/pidof does not exists (rudder part)ReleasedFrançois ARMAND2014-12-30Actions
Bug #6055: Warning after policy generation, /bin/pidof does not exists (integration part)ReleasedBenoît PECCATTE2014-12-30Actions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #5825: rudder-jetty and rudder-inventory-ldap init scripts can fail when killall is not availableReleasedJonathan CLARKE2014-12-04Actions
Actions #1

Updated by Nicolas CHARLES over 7 years ago

  • Assignee changed from Nicolas CHARLES to Matthieu CERDA
Actions #2

Updated by Matthieu CERDA over 7 years ago

So, after testing and discussing with our local Scala experts, I see that executing the command to reload the server during policy generation is done "execve" style in Scala, meaning it takes ONE command and its arguments,

The best approach I can come with for this is to just delegate all the magic to a dedicated script, for several reasons:
  • No more fiddling with process execution magic
  • One script to do it, and do it well instead of an unreadable line in the .properties (we've done this before in cron, never again...)
Therefore, I'm adding subtickets to:
  • Change in rudder the command to be executed in the sample properties(and correct a small but horribly frustrating logging typo)
  • Adapt the packaging to add the right line during migration, and package the script itself
Actions #3

Updated by Nicolas CHARLES over 7 years ago

  • Target version changed from 3.0.0 to 2.11.6

Caution, this appeared in 2.11, so it need to be fixed there

Actions #4

Updated by Matthieu CERDA over 7 years ago

  • Status changed from New to Pending technical review
Actions #5

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from Pending technical review to Pending release
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/576

This was fixed in #6055, I moved back the PR and the commit from there as 6051 is the parent issue.

Since this is a bug, it does not need to have a sub issue to be fixed

Actions #6

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.6 to 2.11.7
Actions #7

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.7, which was released these days.

Actions #8

Updated by Benoît PECCATTE over 6 years ago

  • Pull Request deleted (https://github.com/Normation/rudder-packages/pull/576)
Actions

Also available in: Atom PDF