dr_validate.sh fails repeatedly. Cannot update cpufreq/scaling_governor
search cancel

dr_validate.sh fails repeatedly. Cannot update cpufreq/scaling_governor

book

Article ID: 258344

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration

Issue/Introduction

dr_validate  finds these issues:

Not in conformance: /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu5/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu6/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu7/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu8/cpufreq/scaling_governor
Not in conformance: /sys/devices/system/cpu/cpu9/cpufreq/scaling_governor

 

Lines are added to the rc.local local script but not working

Seeing these lines in /var/log/messages

 

Jan 23 06:02:48 systemd: Starting /etc/rc.d/rc.local Compatibility...
Jan 23 06:02:48 rc.local: /etc/rc.d/rc.local: line 37: /sys/devices/system/cpu/cpu24/cpufreq/scaling_governor: No such file or directory
Jan 23 06:02:48 systemd: Failed to start /etc/rc.d/rc.local Compatibility.
Jan 23 06:59:07 systemd: Starting /etc/rc.d/rc.local Compatibility...
Jan 23 06:59:07 rc.local: /etc/rc.d/rc.local: line 37: /sys/devices/system/cpu/cpu24/cpufreq/scaling_governor: No such file or directory
Jan 23 06:59:08 systemd: Failed to start /etc/rc.d/rc.local Compatibility.

Environment

Release : 22.2

Cause

Failed at step EXEC spawning /etc/rc.d/rc.local: Exec format error

Red Hat Enterprise Linux 7.x
Issue

Failed at step EXEC spawning /etc/rc.d/rc.local: Exec format error
Raw

[[email protected]~]# systemctl status rc-local.service

● rc-local.service - /etc/rc.d/rc.local Compatibility

Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static; vendor preset: disabled)

  Active: failed (Result: exit-code) since Tue 2016-10-25 17:59:19 EDT; 1min 32s ago

Process: 1478 ExecStart=/etc/rc.d/rc.local start (code=exited, status=203/EXEC)

 

Oct 25 17:59:19 vc2crtpb148242n systemd[1]: Starting /etc/rc.d/rc.local Compatibility...

Oct 25 17:59:19 vc2crtpb148242n systemd[1478]: Failed at step EXEC spawning /etc/rc.d/rc.local: Exec format error

Oct 25 17:59:19 vc2crtpb148242n systemd[1]: rc-local.service: control process exited, code=exited status=203

Oct 25 17:59:19 vc2crtpb148242n systemd[1]: Failed to start /etc/rc.d/rc.local Compatibility.

Oct 25 17:59:19 vc2crtpb148242n systemd[1]: Unit rc-local.service entered failed state.

Oct 25 17:59:19 vc2crtpb148242n systemd[1]: rc-local.service failed.

You have new mail in /var/spool/mail/root

Resolution

 SOLUTION VERIFIED 

This solution has been verified to work by Red Hat Customers and Support Engineers for the specified product version(s).

Remove any comments for the shebangs (i.e. #!/bin/bash) in the rc.local script, so that it starts correctly with the she-bang sequence:
Raw

#!/bin/bash

 

The issue was the  /etc/rc.d/rc.local. This was missing from the top of the file

cat /etc/rc.d/rc.local

#!/bin/bash

# THIS FILE IS ADDED FOR COMPATIBILITY PURPOSES

#

# It is highly advisable to create own systemd services or udev rules

# to run scripts during boot instead of using this file.

#

# In contrast to previous versions due to parallel execution during boot

# this script will NOT be run after all other services.

#

# Please note that you must run 'chmod +x /etc/rc.d/rc.local' to ensure

# that this script will be executed during boot.

 

touch /var/lock/subsys/local