Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Checking setup, getting bad numbers

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Checking setup, getting bad numbers


Chronological Thread 
  • From: Pol Llovet <>
  • To: Andrew Lake <>, Szymon Trocha <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] Checking setup, getting bad numbers
  • Date: Wed, 23 Mar 2016 18:03:05 +0000

Andy,

Are there other configuration changes that might have similar issues (are there other files I should check for config updates that might have been missed)?

--

Assc. Director of Research CI
Montana State University
XSEDE Campus Champion
o: 406-994-3416
m: 406-646-6747

On Wed, Mar 23, 2016 at 11:52 AM Andrew Lake <> wrote:
Hi,

Its actually not related to the file path changes…I am not even entirely sure its new in 3.5.1. I did some testing this afternoon and it does in fact run when you install the system from the ISO, but it looks like it’s possible for it to run prior to the /etc/sysctl.conf file being created by the “initscripts” package. The initscripts package is the Linux package that installs the default system /etc/sysctl.conf. Thus when the initscripts package installs, it overrides any changes made by the perfsonar-toolkit-sysctl package. It looks like perfsonar-toolkit-sysctl needs its dependencies updated to ensure it is installed and runs the script after initscripts is in place. It’s an easy enough fix. 

A new RPM will be up today that should help fresh NetInstalls. We’ll have a new FullInstall ISO up in a couple days (incidentally we also have a new web100 kernel to build and test, so we’ll cut a new ISO when that is ready as well).

Thanks,
Andy


On March 23, 2016 at 12:33:07 PM, Pol Llovet () wrote:

Heh, you need to supply a "new" option to that script or it does nothing:
====
[root@ps-10g-dmz ~]# head /usr/lib/perfsonar/scripts/configure_sysctl
#!/bin/bash

COMMAND=$1

if [ "${COMMAND}" != "new" ]; then
    exit 0
fi
====

Do you know why this wouldn't have run during setup?  Is it related to the bug that the bwctld name changed?

--

Assc. Director of Research CI
Montana State University
XSEDE Campus Champion
o: 406-994-3416
m: 406-646-6747

--

Assc. Director of Research CI
Montana State University
XSEDE Campus Champion
o: 406-994-3416
m: 406-646-6747

On Wed, Mar 23, 2016 at 5:40 AM Szymon Trocha <> wrote:
W dniu 22.03.2016 o 23:45, Pol Llovet pisze:
It didn't look like it should be in sysctl.conf... I ended up here


And it lists that you use ifconfig for the txqueuelen param. Is that right?

I did notice that none of the recommended linux tuning params were set in the sysctl.conf of my perfsonar server, is that something that I should change? Should I add the es.net recommended lines to sysctl.conf?

Hi Pol,

There is a configuration script which sets these parameters in sysctl.conf and should have run:
/usr/lib/perfsonar/scripts/configure_sysctl

You may want to run this manually

Regards,

--  
Szymon Trocha

Poznań Supercomputing & Netw. Center ::: NETWORK OPERATION CENTER
Tel. +48 618582022 ::: http://noc.man.poznan.pl



Archive powered by MHonArc 2.6.16.

Top of Page