Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

scylla_cpuscaling_setup doesn't works on AWS/GCE, because these VMs doesn't support cpufreq #2051

Closed
syuu1228 opened this issue Feb 1, 2017 · 4 comments
Closed

scylla_cpuscaling_setup doesn't works on AWS/GCE, because these VMs doesn't support cpufreq #2051

syuu1228 opened this issue Feb 1, 2017 · 4 comments
Assignees
@syuu1228
Labels
type/bug
Milestone
2.0

Comments

@syuu1228
Copy link
Contributor

syuu1228 commented Feb 1, 2017

Since we run scylla_cpuscaling_setup by default, we get error on scylla_setup with default interactive selection.
We probably need to do "exit 0" when the machine doesn't able to load cpufreq device driver, instead of causing such error.

Do you want to setup CPU scalling governor?
Answer yes to set CPU scalling governor to performance at boot time. Answer no t
o do nothing.
[YES/no]
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.atlanticmetro.net
 * epel: mirror.symnds.com
 * extras: mirrors.centos.webair.com
 * updates: mirror.symnds.com
Package kernel-tools-3.10.0-514.6.1.el7.x86_64 already installed and latest vers
ion
Nothing to do
Job for cpupower.service failed because the control process exited with error co
de. See "systemctl status cpupower.service" and "journalctl -xe" for details.
CPU Scalling setup failed. press any key to continue..

And it seems these VMs does not support cpufreq:

Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: Setting cpu: 0
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: Error setting new values. Commo
n errors:
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: - Do you have proper administra
tion rights? (super-user?)
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: - Is the governor you requested
 available and modprobed?
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: - Trying to set an invalid poli
cy?
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: - Trying to set a specific freq
uency, but userspace governor is not available,
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: for example because of hardware
 which cannot be set to a specific frequency
Feb 01 17:39:30 ip-172-30-0-203 cpupower[11408]: or because the userspace govern
or isn't loaded?
Feb 01 17:39:30 ip-172-30-0-203 systemd[1]: cpupower.service: main process exite
d, code=exited, status=237/n/a
Feb 01 17:39:30 ip-172-30-0-203 systemd[1]: Failed to start Configure CPU power 
related settings.
-- Subject: Unit cpupower.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit cpupower.service has failed.
-- 
-- The result is failed.

[centos@ip-172-30-0-203 ~]$ sudo modprobe p4-clockmod
modprobe: ERROR: could not insert 'p4_clockmod': No such device
[centos@ip-172-30-0-203 ~]$ sudo modprobe acpi-cpufreq
modprobe: ERROR: could not insert 'acpi_cpufreq': No such device
[centos@ip-172-30-0-203 ~]$ sudo modprobe pcc-cpufreq
modprobe: ERROR: could not insert 'pcc_cpufreq': No such device
@tzach tzach added the type/bug label Feb 8, 2017
@tzach tzach added this to the 1.8 milestone Feb 8, 2017
@amoskong
Copy link
Contributor

@syuu1228 what's the effect of this bug? can we ignore it?

amoskong added a commit to amoskong/scylla-artifact-tests that referenced this issue Apr 25, 2017
@amoskong
fix raid setup and disable cpuscaling setup
3fbabd9 
We just added a second disks to test vms for raid setup,
this patch adjusted raid option and disable cpuscaling
setup for a known issue [1] will cause full setup fails.

[1] scylladb/scylladb#2051

Signed-off-by: Amos Kong <amos@scylladb.com>
amoskong added a commit to amoskong/scylla-artifact-tests that referenced this issue Apr 25, 2017
@amoskong
fix raid setup and disable cpuscaling setup
1b9ba52 
We just added a second disks to test vms for raid setup,
this patch adjusted raid option and disable cpuscaling
setup for a known issue [1] will cause full setup fails.

[1] scylladb/scylladb#2051

Signed-off-by: Amos Kong <amos@scylladb.com>
amoskong added a commit to amoskong/scylla-artifact-tests that referenced this issue Apr 25, 2017
@amoskong
fix raid setup and disable cpuscaling setup
48013b3 
We just added a second disks to test vms for raid setup,
this patch adjusted raid option and disable cpuscaling
setup for a known issue [1] will cause full setup fails.

[1] scylladb/scylladb#2051

Signed-off-by: Amos Kong <amos@scylladb.com>
@amoskong amoskong mentioned this issue Apr 25, 2017
Merged
@slivne
Copy link
Contributor

slivne commented Jun 29, 2017

@syuu1228 - was this fixed ?

@syuu1228
Copy link
Contributor Author

@amoskong Users who manually installs Scylla on VM/IaaS will get 'CPU Scalling setup failed. press any key to continue..' message when they running interactive scylla_setup.
It's better to skip the step.

@syuu1228
Copy link
Contributor Author

Sent a fix '[PATCH scylla] dist/common/scripts/scylla_cpuscaling_setup: skip configuration when cpufreq driver doesn't loaded'

penberg pushed a commit that referenced this issue Jul 10, 2017
@syuu1228 @penberg
dist/common/scripts/scylla_cpuscaling_setup: skip configuration when …
2d61202 
…cpufreq driver doesn't loaded

Configuring cpufreq service on VMs/IaaS causes an error because it doesn't supported cpufreq.
To prevent causing error, skip whole configuration when the driver not loaded.

Fixes #2051

Signed-off-by: Takuya ASADA <syuu@scylladb.com>
Message-Id: <1498809504-27029-1-git-send-email-syuu@scylladb.com>
(cherry picked from commit 1c35549)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@syuu1228 syuu1228

Labels
type/bug
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
4 participants
@tzach @syuu1228 @amoskong @slivne