Red Hat Bugzilla – Bug 1238423
migration error "Process ID out of range error" after evmserverd start
Last modified: 2015-12-08 08:21:07 EST
Description of problem: Migrate from 5.3.4 to 5.4.0.5 using https://access.redhat.com/articles/1435433 Section "Upgrade and Migration Procedure from 5.3.1 and above" The start of the evmserverd service will generate the following error. "Process ID out of range error" A #service evmserverd status shows all workers started without error. Version-Release number of selected component (if applicable): 5.4.0.5 How reproducible: very Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Was not able to reproduce by following the directions in the KB article exactly. For this to happen, you would need to run yum update from the command line without stopping the server first then continue with the commands listed in step 5 of "Upgrade and Migration Procedure from 5.3.1 and above." https://github.com/ManageIQ/manageiq/pull/3417
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/653fd8523288b8dda8c702f6204871fa3ea6fdab commit 653fd8523288b8dda8c702f6204871fa3ea6fdab Author: Nick Carboni <ncarboni@redhat.com> AuthorDate: Fri Jul 10 16:16:45 2015 -0400 Commit: Nick Carboni <ncarboni@redhat.com> CommitDate: Fri Jul 10 16:16:45 2015 -0400 Make PidFile#pid return nil for non-numeric pid file contents If we return a non-numeric pid from PidFile#pid MiqProcess.command_line will cause ps(1) to output a usage message. This usage message was seen during the upgrade process if the server was started through the command line. https://bugzilla.redhat.com/show_bug.cgi?id=1238423 lib/pid_file.rb | 2 +- spec/lib/pid_file_spec.rb | 5 +++++ 2 files changed, 6 insertions(+), 1 deletion(-)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:2551