cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

wrong energy saving mode

andreas_sturm
Newcomer

Hi everybody,

after the Upgrade from Appmon 7.1 to 7.2 we got the following error message.


Appmon is working fine, but im not fine with this message :).

We are hosting Appmon on a Suse Linux and on this system the energy mode is set right to "performance".

how can i get rid of this message?

Thanks in advance

Andi

8 REPLIES 8

If you're certain the power mode is set correctly on the operating system level, it should not show this. Are you running the latest fixpack 7.2.21?

andreas_sturm
Newcomer

Yes, we made the update from 7.1.x to 7.2.21. This was the only change, the OS is untouched.

In my opinion it looks like, there ist a dynatrace parameter with another barrier.

Best would then be to open a support ticket if the status hasn't changed.

stefan_moschins
Dynatrace Guide
Dynatrace Guide

The logic works for Linux in this way: for each core the scaling governor is checked (e.g., for core 0 the value of /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is read). For each core, the mode needs to set to "performance", otherwise the incident will be raised.

@Andreas S. can you please check whether all cores are set to performance?

Hi Stefan,

here ist what the server admins told me:

(every CPU has the same governor)

--- START ---


analyzing CPU 0:

driver: intel_pstate

CPUs which run at the same hardware frequency: Not Available

CPUs which need to have their frequency coordinated by software: Not Available

maximum transition latency: Cannot determine or is not supported.

hardware limits: 1.20 GHz - 3.20 GHz

available cpufreq governors: performance

current policy: frequency should be within 1.20 GHz and 3.20 GHz.

The governor "powersave" may decide which speed to use

within this range.

current CPU frequency: Unable to call hardware

current CPU frequency: 1.46 GHz (asserted by call to kernel)

boost state support:

Supported: yes

Active: yes


analyzing CPU 1:

driver: intel_pstate

CPUs which run at the same hardware frequency: Not Available

CPUs which need to have their frequency coordinated by software: Not Available

maximum transition latency: Cannot determine or is not supported.

hardware limits: 1.20 GHz - 3.20 GHz

available cpufreq governors: performance

current policy: frequency should be within 1.20 GHz and 3.20 GHz.

The governor "powersave" may decide which speed to use

within this range.

current CPU frequency: Unable to call hardware

current CPU frequency: 2.06 GHz (asserted by call to kernel)

boost state support:

Supported: yes

Active: yes


analyzing CPU 2:

driver: intel_pstate

CPUs which run at the same hardware frequency: Not Available

CPUs which need to have their frequency coordinated by software: Not Available

maximum transition latency: Cannot determine or is not supported.

hardware limits: 1.20 GHz - 3.20 GHz

available cpufreq governors: performance

current policy: frequency should be within 1.20 GHz and 3.20 GHz.

The governor "powersave" may decide which speed to use

within this range.

current CPU frequency: Unable to call hardware

current CPU frequency: 1.72 GHz (asserted by call to kernel)

boost state support:

Supported: yes

Active: yes

.

.

.

.

analyzing CPU 15:

driver: intel_pstate

CPUs which run at the same hardware frequency: Not Available

CPUs which need to have their frequency coordinated by software: Not Available

maximum transition latency: Cannot determine or is not supported.

hardware limits: 1.20 GHz - 3.20 GHz

available cpufreq governors: performance

current policy: frequency should be within 1.20 GHz and 3.20 GHz.

The governor "powersave" may decide which speed to use

within this range.

current CPU frequency: Unable to call hardware

current CPU frequency: 1.32 GHz (asserted by call to kernel)

boost state support:

Supported: yes

Active: yes


--- END ---


is this helpful for you?


Greetings

Andi

Hello Andi,

The following output shows that "powersave" mode is activated:

current policy: frequency should be within 1.20 GHz and 3.20 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.

Please ask your admins to switch to "performance" mode. For example, see https://askubuntu.com/a/936488 how to do it.

Best regards,

Stefan

Hi Stefan,

ok i will give this to our admins. But for now i have another question.

Is this power-mode relevant on the dynatrace-server or the eap-server where the application is running on?


best regards,

Andi

The incident concerns 'dynatrace appmon server', thus the power mode we are discussing here is also related to the image on which AppMon server resides.