7023264: scaling_governor not visible for all CPUs

This document (7023264) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)
HP ProLiant G6, G7, Gen8 or Gen9 based hardware

Situation

While trying to change the scaling_governor to performance it is observed, that this setting is not available for all CPUs in the system:

# ls -d /sys/devices/system/cpu/cpu4/cpufreq/

/sys/devices/system/cpu/cpu4/cpufreq/

# ls -d /sys/devices/system/cpu/cpu5/cpufreq/

ls: cannot access ‘/sys/devices/system/cpu/cpu5/cpufreq/’: No such file or directory

Resolution

Please change the power settings to HP Power Regulator.

Cause

This behavior may be observed if the BIOS is set to HP Dynamic Savings Mode.

Additional Information

Please see for details the following HP support advisory:

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Re: emc unity 400 configure snapshot schedules every 48 hours

As Rainer says UEMCLI gives alot more config options for snaps than the GUI. Try these as an example of creating a snap every 2 days at 8pm and keeping it for 7 days:

PS C:UsersAdministrator> uemcli -d 1.1.1.1 -u admin -p mypassword /sys/task/rule create -schedName 48hours -type daysinterval -every 2 -at 20:00 -keepFor 7d

Storage system address: 1.1.1.1

Storage system port: 443

HTTPS connection

ID = SchedRule_304

Schedule ID = snapSch_18

Operation completed successfully.

PS C:UsersAdministrator> uemcli -d 1.1.1.1 -u admin -p mypassword /sys/task/rule -id SchedRule_304 show

Storage system address: 1.1.1.1

Storage system port: 443

HTTPS connection

1: ID = SchedRule_304

Type = DaysInterval

Frequency = Every 2d at 20:00

Keep for = 7d

Allow auto-delete = no

Access = Checkpoint

Related:

Symantec detected “io.sys and msdos.sys” as WS.Reputation.1

I need a solution

Hi Team,

We have SEPM version 14. We have found symantec has detecting files  “io.sys and msdos.sys” as WS.Reputation.1 same has been qurantined and deleted by SEPM. but still we are see those file in system but size is 0 kb.

Also we have observed those files(io.sys and msdos.sys) are created by processntvdm.exe“. and this file belong to mircosoft and genuine process

Date size File
03/14/2018 07:34 AM GMT 0 IO.SYS
     
03/14/2018 07:34 AM GMT 0 MSDOS.SYS
     

Symantec Logs:

Filename Risk Original Location Computer Current Location Primary Action Secondary Action Action Description Date and Time
msdos.sys WS.Reputation.1 c: D00070-0061 Quarantine Restart Required – Quarantine Restart Required – Delete Restart Required – The file was quarantined successfully. 12/4/2018 10:19
io.sys WS.Reputation.1 c: D00070-0061 Quarantine Restart Required – Quarantine Restart Required – Delete Restart Required – The file was quarantined successfully. 12/4/2018 10:18
msdos.sys WS.Reputation.1 c: D00070-0061 Quarantine Quarantine Delete Performed Post-Reboot Risk Processing. 12/4/2018 9:54
msdos.sys WS.Reputation.1 c: D00070-0061 Quarantine Quarantine Delete Performed Post-Reboot Risk Processing. 12/4/2018 9:54

Hash value of files io.sys and msdos.sys : E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 

Files path: C:/ io.sys and C:/ msdos.sys

Please confirme what basis symantec has detecting those files io.sys and msdos.sys as WS.Reputation.1. and let us know the reason?

0

Related:

pkgadd on Solaris for ProtectPoint app agent may show message: The following files are already installed on the system and are being used by another package

Article Number: 517190Article Version: 3 Article Type: How To



DD4500 Appliance

When running the pkgadd command on a Solaris server to install the ProtectPoint APP agent, pkgadd will indicate that there are items already installed on the machine (attribute change only) and it will ask for a confirmation to run the installation as seen below:

Install on Solaris incorrectly changes permissions of /opt directory or breaks /opt if it is a symlink

On the Solaris command line:

ls -ltr /opt

————————-

drwxrwxr-x 17 root sys 512 Jan 18 13:52 opt

————————-

Note that /opt is owned by the user “root” and the group name is “sys” and that the permissions are 755, RWX-RX-RX

Install the software:

———————————————–

# pkgadd -d /tmp/ProtectPoint

The following packages are available:

1 emcppfsagent ProtectPoint File System Agent

(sparc) 4.5.0

Select package(s) you wish to process (or ‘all’ to process

all packages). (default: all) [?,??,q]: 1

Processing package instance <emcppfsagent> from </tmp/abdon>

ProtectPoint File System Agent(sparc) 4.5.0

Copyright (c) 1990-2017, EMC Corporation

Using </> as the package base directory.

## Processing package information.

## Processing system information.

2 package pathnames are already properly installed.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

The following files are already installed on the system and are being

used by another package:

/opt <attribute change only>

* – conflict with a file which does not belong to any package.

….

## Executing postinstall script.

Product has been installed into /opt/dpsapps/ppfsagent

Installation of <emcppfsagent> was successful.

—————————————————————-

Now see the permissions and group ownership has changed:

ls -ltr /opt

————————————————————

drwxrwxr-x 17 root other 512 Jan 18 13:52 opt

————————————————————

The new group ownership was changed from “sys” to “other” and the permissions went from 755 to 775 RWX-RWX-RX

To recover from this use the following steps:

chmod 755 /opt

chgrp sys /opt

The group “sys” is used in the example above, if your group ownership is different please enter the correct group name in the chgrp command.

If /opt is a symbolic link then this occurs:

ls -ltr /opt

———————————

lrwxrwxrwx 1 root root 6 Jan 25 14:33 opt -> /test1

———————————

Note the /opt directory is symbolically linked to /test1 which is the parent directory

Check the contents of /opt

—————————————-

cherry# cd opt

cherry# ls -ltr

total 14428

drwxr-xr-x 3 root root 512 Jan 18 08:04 SUNWits

drwxr-xr-x 5 root root 512 Jan 18 08:04 SUNWmlib

drwxr-xr-x 5 root root 512 Jan 18 08:06 SUNWrtvc

drwxr-xr-x 8 root root 512 Jan 18 08:07 staroffice8

drwxr-xr-x 5 root root 512 Jan 18 08:08 emc

drwxr-xr-x 5 root root 512 Jan 18 08:08 EMLXemlxu

drwxr-xr-x 7 root root 1024 Jan 18 08:08 HBAnyware

——————————————–

Install the software:

———————————————-

The following packages are available:

1 emcppfsagent ProtectPoint File System Agent

(sparc) 4.5.0

Select package(s) you wish to process (or ‘all’ to process

all packages). (default: all) [?,??,q]: 1

Processing package instance <emcppfsagent> from </tmp/abdon>

ProtectPoint File System Agent(sparc) 4.5.0

Copyright (c) 1990-2017, EMC Corporation

Using </> as the package base directory.

## Processing package information.

## Processing system information.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

The following files are already installed on the system and are being

used by another package:

/opt

Do you want to install these conflicting files [y,n,?,q]

[ verifying class <none> ]

## Executing postinstall script.

Product has been installed into /opt/dpsapps/ppfsagent

Installation of <emcppfsagent> was successful.

————————————————–

Check /opt and see the symlink was broken:

ls -ltr /opt

drwxrwxr-x 3 root other 512 Jan 25 14:34 opt

and it only contains the FSA software:

ls -ltr /opt/*

——————

total 2

drwxrwxr-x 4 root other 512 Jan 25 14:34 dpsapps

At this point you will need to re-link /opt to it’s original path, in the example above /opt was symbolically linked to /test1

To recover from this:

cd /

mv opt opt.pp -rename the newly created opt directory containing the ProtecPoint installation

ln -s /test1 /opt -to re-establish the symbolic link that was broken

cd opt.pp -change directory into the ‘local” ProtectPoint install directory

cp -R . /opt -copy the ProtectPoint install directory to the linked /opt directory

Related:

Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’)

Try to determine which files are taking up disk space. on Identity disk

For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

The PsExec tool is available for download at this location

http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

Follow these steps to access the Identity disk volume on the VDA:

1. Open elevated command prompt <Run as administrator>

2. execute the command under the context of the Local System account via PsExec:

PSEXEC -i -s cmd.exe

This it to access to the junction linked to the Identity Disk volume

3. Navigate to the root of the junction “PersistedData”, and execute the following command:

DIR /O:S /S > C:{location}Out.txt

4. Open out.txt using Notepad or text editor

5. Check the files taking up the disk space.

6. Move the unwanted files to an alternate location or delete them

Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

Related:

Sys Led Proxy SG amber

I need a solution

Hi all.

i want to ask about Sys led proxy in our customers.

why sys led amber ? i know the status is become warning. but when i check in healt check there’s no information about warning. just info warning only.

what should i do ?

Below i attach picture sys led status on proxy SG.

Best Regards

Indra Pramono

0

Related:

Event ID 1023 Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’). VDAs in Delivery Group losing registration with the Delivery Controllers

Try to determine which files are taking up disk space. on Identity disk

For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

The PsExec tool is available for download at this location

http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

Follow these steps to access the Identity disk volume on the VDA:

1. Open elevated command prompt <Run as administrator>

2. execute the command under the context of the Local System account via PsExec:

PSEXEC -i -s cmd.exe

This it to access to the junction linked to the Identity Disk volume

3. Navigate to the root of the junction “PersistedData”, and execute the following command:

DIR /O:S /S > C:{location}Out.txt

4. Open out.txt using Notepad or text editor

5. Check the files taking up the disk space.

6. Move the unwanted files to an alternate location or delete them

Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

Related:

@sys-date and @sys-time issues

I have found several issues related with @sys-date and @sys-time. Here are some examples

“aternoon” is being resolved to a @sys-time=18:00. Shouldn’t be resolved to an interval, 12:00 to 18:00, much like it happens with “December” that is resolved to @sys-date=1 December and @sys-date=31 December?

The same happens with “morning” and “evening” which also represent time-ranges.

Furhtermore, watson sees no difference between “early morning” and “late morning”. In this case I can define a new entity for late and early to react accordingly, but it would work only if “morning”, “afternoon” and “evening” were recognized as time ranges.

Related:

  • No Related Posts