Re: how to find internet dead spots

2013-03-28 Thread Paul Robert Marino 
hello
there are two tools that come to mind first is ntop you will find it in EPEL
its a great tool that will tell you what the network traffic is doing
and has a nice web GUI.

another great tool is smoke ping http://oss.oetiker.ch/smokeping/
there is no RPM for it that I know of but it is an easy way to test
your connectivity and graph your latency and it even does email
alerting.

On Wed, Mar 27, 2013 at 3:36 PM, Todd And Margo Chester
 wrote:
> Hi All,
>
> I have a Cent OS 5.x server sitting on a DSL line
> acting as a firewall.  I have noticed that there are
> dead spots, up to a minute, every so often in their
> Internet service.
>
> It could be a storm on someone's part, but the worst
> they run is IMAP.  No music; no video.
>
> Is there a utility I can run to map this?
>
> Many thanks,
> -T

Re: memory per process/core

2013-03-28 Thread Paul Robert Marino 
kernel.shmmax does nothing if you don't bump up kernel.shmall
accordingly but I can tell you the cap is something wrong with your
application not the OS.
at one time I supported an application that in normal operation used
64BG Resident memory per instance.
And currently my PostgreSQL servers often spike to as much as 2GB of
ram per connection and would use more if i didn't cap it there in the
configurations.

I don't think the kernel settings are your problem what language is
the application written in?
Is it executed by an other process like Apache or Tomcat for example?


On Wed, Mar 27, 2013 at 11:09 PM, Duke Nguyen  wrote:
> On 3/27/13 11:52 PM, Attilio De Falco wrote:
>>
>> Just a stab in the dark, but did you check the Shared Memory kernel
>> parameter (shmmax), type "cat /proc/sys/kernel/shmmax".  We have it set very
>> high so that any process/thread can use as much memory as it needs.  You set
>> the limit to 1 GB without rebooting by typing "echo 1073741824 >
>> /proc/sys/kernel/shmmax"  or modify /etc/sysctl.conf and add the line
>> "kernel.shmmax = 1073741824" so remains after a reboot.  I'm not sure about
>> abinit but some fortran programs need shmmax limit to be set high…
>
>
> Hi Attilio, we already had it at very high value (not sure why, I never
> changed/edited this value before)
>
> [root@biobos:~]# sysctl -p
> net.ipv4.ip_forward = 1
> net.ipv4.conf.default.rp_filter = 1
> net.ipv4.conf.default.accept_source_route = 0
> kernel.sysrq = 0
> kernel.core_uses_pid = 1
> net.ipv4.tcp_syncookies = 1
> error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key
> error: "net.bridge.bridge-nf-call-iptables" is an unknown key
> error: "net.bridge.bridge-nf-call-arptables" is an unknown key
> kernel.msgmnb = 65536
> kernel.msgmax = 65536
> kernel.shmmax = 68719476736
> kernel.shmall = 4294967296
> [root@biobos:~]# cat /proc/sys/kernel/shmmax
> 68719476736
>
> Any other suggestions?
>
>
>>
>> On Mar 26, 2013, at 9:59 PM, Duke Nguyen  wrote:
>>
>>> Hi folks,
>>>
>>> We have SL6.3 64bit installed on a box with two quad core and 8GB RAM. We
>>> installed openmpi, Intel Studio XE and abinit to run parallel (8
>>> cores/processes) some of our applications. To our surprise, the system
>>> usually takes only about half of available memory (about 500MB each core)
>>> and then the job/task was killed with the low-resource error.
>>>
>>> We dont really understand why there is a cap of "512MB" (I guess it would
>>> be 512MB instead of 500MB) for each of our cores whereas in theory, each of
>>> the core should be able to run up to 1GB. Any
>>> suggestions/comments/experience about this issue?
>>>
>>> Thanks in advance,
>>>
>>> D.
>>>
>

Re: memory per process/core

2013-03-28 Thread Duke Nguyen 

On 3/28/13 9:00 PM, Paul Robert Marino wrote:

kernel.shmmax does nothing if you don't bump up kernel.shmall
accordingly but I can tell you the cap is something wrong with your
application not the OS.
at one time I supported an application that in normal operation used
64BG Resident memory per instance.
And currently my PostgreSQL servers often spike to as much as 2GB of
ram per connection and would use more if i didn't cap it there in the
configurations.


Interesting, I never knew of any server process that takes that much of 
memory. Anyway, it is good to know :).




I don't think the kernel settings are your problem what language is
the application written in?
Is it executed by an other process like Apache or Tomcat for example?


The app (a material simulation app) is just an input file which will 
calling abinit (http://www.abinit.org/) using openmpi to run. So it is 
executed by abinit. At the time the app runs, we make sure that no other 
process (apache, tomcat etc...) is running, so basically the app should 
take all available memory.


Thanks,

D.




On Wed, Mar 27, 2013 at 11:09 PM, Duke Nguyen  wrote:

On 3/27/13 11:52 PM, Attilio De Falco wrote:

Just a stab in the dark, but did you check the Shared Memory kernel
parameter (shmmax), type "cat /proc/sys/kernel/shmmax".  We have it set very
high so that any process/thread can use as much memory as it needs.  You set
the limit to 1 GB without rebooting by typing "echo 1073741824 >
/proc/sys/kernel/shmmax"  or modify /etc/sysctl.conf and add the line
"kernel.shmmax = 1073741824" so remains after a reboot.  I'm not sure about
abinit but some fortran programs need shmmax limit to be set high…


Hi Attilio, we already had it at very high value (not sure why, I never
changed/edited this value before)

[root@biobos:~]# sysctl -p
net.ipv4.ip_forward = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key
error: "net.bridge.bridge-nf-call-iptables" is an unknown key
error: "net.bridge.bridge-nf-call-arptables" is an unknown key
kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
[root@biobos:~]# cat /proc/sys/kernel/shmmax
68719476736

Any other suggestions?



On Mar 26, 2013, at 9:59 PM, Duke Nguyen  wrote:


Hi folks,

We have SL6.3 64bit installed on a box with two quad core and 8GB RAM. We
installed openmpi, Intel Studio XE and abinit to run parallel (8
cores/processes) some of our applications. To our surprise, the system
usually takes only about half of available memory (about 500MB each core)
and then the job/task was killed with the low-resource error.

We dont really understand why there is a cap of "512MB" (I guess it would
be 512MB instead of 500MB) for each of our cores whereas in theory, each of
the core should be able to run up to 1GB. Any
suggestions/comments/experience about this issue?

Thanks in advance,

D.

NFS problem on "ls" command

2013-03-28 Thread Evan Sather 
Hi Everyone,

We're experiencing NFS-related problems after viewing home directories
on SL6 desktops.  SL5 clients do not experience this problem.  The NFS
server is a SL5 machine.

One of our desktops outputs this:

[user@host1 ~]$ ls -ltr |tail
ls: reading directory .: Invalid argument


Another of our desktops outputs this:

[user@host2 ~]$ ls -l
ls: reading directory .: Too many levels of symbolic links

Has anyone else seen this or a similar issue?  Does anyone have any
suggestions?

-- 
*Evan Sather*
Linux System Administrator
High Energy Physics
Argonne National Laboratory



signature.asc
Description: OpenPGP digital signature

Re: NFS problem on "ls" command

2013-03-28 Thread Tam Nguyen 
We ran into this issue couple of weeks ago.  There is a ticket about this
bug with the NFS v3+4.  Our work around was to mount it with a different
version of NFS.

https://bugzilla.redhat.com/show_bug.cgi?id=736394#c13 is also
referenced by http://bugs.centos.org/view.php?id=6241.

-T

On Thu, Mar 28, 2013 at 12:58 PM, Evan Sather  wrote:

>  Hi Everyone,
>
> We're experiencing NFS-related problems after viewing home directories on
> SL6 desktops.  SL5 clients do not experience this problem.  The NFS server
> is a SL5 machine.
>
> One of our desktops outputs this:
>
> [user@host1 ~]$ ls -ltr |tail
> ls: reading directory .: Invalid argument
>
>
> Another of our desktops outputs this:
>
> [user@host2 ~]$ ls -l
> ls: reading directory .: Too many levels of symbolic links
>
>  Has anyone else seen this or a similar issue?  Does anyone have any
> suggestions?
>
> --
> *Evan Sather*
> Linux System Administrator
> High Energy Physics
> Argonne National Laboratory
>
>

Re: NFS problem on "ls" command

2013-03-28 Thread Evan Sather 
Thank you, Tam!  I will keep an eye on the bug report.

*Evan Sather*
Linux System Administrator
High Energy Physics
Argonne National Laboratory

On 03/28/2013 12:16 PM, Tam Nguyen wrote:
> We ran into this issue couple of weeks ago.  There is a ticket about
> this bug with the NFS v3+4.  Our work around was to mount it with a
> different version of NFS. 
>
> https://bugzilla.redhat.com/show_bug.cgi?id=736394#c13 is also
> referenced by http://bugs.centos.org/view.php?id=6241.
>
> -T
>
> On Thu, Mar 28, 2013 at 12:58 PM, Evan Sather  > wrote:
>
> Hi Everyone,
>
> We're experiencing NFS-related problems after viewing home
> directories on SL6 desktops.  SL5 clients do not experience this
> problem.  The NFS server is a SL5 machine.
>
> One of our desktops outputs this:
>
> [user@host1 ~]$ ls -ltr |tail
> ls: reading directory .: Invalid argument
>
>
> Another of our desktops outputs this:
>
> [user@host2 ~]$ ls -l
> ls: reading directory .: Too many levels of symbolic links
>
> Has anyone else seen this or a similar issue?  Does anyone have
> any suggestions?
>
> -- 
> *Evan Sather*
> Linux System Administrator
> High Energy Physics
> Argonne National Laboratory
>
>



signature.asc
Description: OpenPGP digital signature

Re: NFS problem on "ls" command

2013-03-28 Thread Connie Sieh 

On Thu, 28 Mar 2013, Evan Sather wrote:


--enig2VHUROTADOEVHDNAEQDLT
Content-Type: multipart/alternative;
boundary="020008050902010202030501"

This is a multi-part message in MIME format.
--020008050902010202030501
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thank you, Tam!  I will keep an eye on the bug report.

*Evan Sather*
Linux System Administrator
High Energy Physics
Argonne National Laboratory

On 03/28/2013 12:16 PM, Tam Nguyen wrote:

We ran into this issue couple of weeks ago.  There is a ticket about
this bug with the NFS v3+4.  Our work around was to mount it with a
different version of NFS.=20

https://bugzilla.redhat.com/show_bug.cgi?id=3D736394#c13 is also
referenced by http://bugs.centos.org/view.php?id=3D6241.

-T

On Thu, Mar 28, 2013 at 12:58 PM, Evan Sather mailto:esat...@anl.gov>> wrote:

Hi Everyone,

We're experiencing NFS-related problems after viewing home
directories on SL6 desktops.  SL5 clients do not experience this
problem.  The NFS server is a SL5 machine.

One of our desktops outputs this:

[user@host1 ~]$ ls -ltr |tail
ls: reading directory .: Invalid argument


Another of our desktops outputs this:

[user@host2 ~]$ ls -l
ls: reading directory .: Too many levels of symbolic links

Has anyone else seen this or a similar issue?  Does anyone have
any suggestions?

--=20
*Evan Sather*
Linux System Administrator
High Energy Physics
Argonne National Laboratory







And even more info at

   http://thread.gmane.org/gmane.comp.file-systems.ext4/37022

-Connie Sieh

Re: NFS problem on "ls" command

2013-03-28 Thread Connie Sieh 

On Thu, 28 Mar 2013, Evan Sather wrote:


--enig2GQLSDWJADQIIIAUXHNWJ
Content-Type: multipart/alternative;
boundary="090004020404060409070304"

This is a multi-part message in MIME format.
--090004020404060409070304
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Everyone,

We're experiencing NFS-related problems after viewing home directories
on SL6 desktops.  SL5 clients do not experience this problem.  The NFS
server is a SL5 machine.

One of our desktops outputs this:

   [user@host1 ~]$ ls -ltr |tail
   ls: reading directory .: Invalid argument


Another of our desktops outputs this:

   [user@host2 ~]$ ls -l
   ls: reading directory .: Too many levels of symbolic links

Has anyone else seen this or a similar issue?  Does anyone have any
suggestions?

--=20
*Evan Sather*
Linux System Administrator
High Energy Physics
Argonne National Laboratory




Evan,

We are trying to pin down which versions of the client software have this 
issue.  We know that the server side changed via a bug fix in SL 5.9 via 
the 2.6.18-348 kernels.  We are trying to figure out a way to predict the 
issue on the client side.  So


   What kernel version do you have on the server?
   What arch is the server?

   What kernel version is on the client?
   What are the versions of nfs-utils* ?
   What arch is the client?

Thanks

-Connie Sieh

Scientific Linux 6.4 is officially released for i686/x86_64

2013-03-28 Thread Pat Riehecky 

Scientific Linux 6.4 i386/x86_64Mar 28, 2013

As a reminder, the SL6x repo always points to the most recent release.  The
SL6x repo has been updated to SL6.4 at this time.

Users of the Scientific Linux 6x repo should runyum clean expire-cache
This should allow yum to notice the updated metadata within the 6x repo.

Mirror sites are encouraged to synchronize their mirrors at this time.

You can read the full release notes at:

http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/os/sl-release-notes-6.4.html
---

Download

http://ftp.scientificlinux.org/linux/scientific/6.4/
http://ftp1.scientificlinux.org/linux/scientific/6.4/
ftp://ftp.scientificlinux.org/linux/scientific/6.4/

ISO Download area
i686:

http://ftp.scientificlinux.org/linux/scientific/6.4/i386/iso/
http://ftp.scientificlinux.org/linux/scientific/6.4/i386/iso/readme

x86_64:

http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/iso/
http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/iso/readme

Mirror List

http://www.scientificlinux.org/download/mirrors

---

Major Differences from SL6.3

As always we encourage you to read the official release notes:
http://ftp.scientificlinux.org/linux/scientific/6.4/x86_64/os/sl-release-notes-6.4.html

OpenAFS
OpenAFS kernel module package has changed. With SL6.0 we started
packaging the OpenAFS client's kernel module according to the guidelines
from TUV's Driver Update Program.

Due to unanticipated changes with the 6.3 kernel, we've had to revisit
the process. With the 6.4 release, we modified the packaging to provide a
dedicated build of the module for each minor SL release, instead of one
kernel module (kmod) for all SL6 kernels. Since the EL kernel ABI is
supposed to be kept stable within a minor release, this should avoid the
problems some SL users experienced.

For those updating their system using yum, this change should be
completely transparent.

yum-conf-sl6x
This is now installed by default. You may remove it to return to the
historical behavior.

yum-conf-sl-other
This now features an entry for 'sl-addons' repo. For more information on
sl-addons please view the README file within the addons repo itself.

xorg-x11-server
Features a new ABI, this was a security errata so it should be available
to earlier releases.

matahari
Upstream has discontinued the matahari packages

--- 



Mailing Lists

scientific-linux-us...@fnal.gov - Users of Scientific Linux supporting
  each other
scientific-linux-de...@fnal.gov - Development of Scientific Linux
scientific-linux-annou...@fnal.gov - Announcements concerning Scientific
 Linux
scientific-linux-err...@fnal.gov -  Announcements about Security Errata
scientific-linux-mirr...@fnal.gov - Announcements about Scientific Linux
related to mirroring


--
Pat Riehecky

Scientific Linux developer
http://www.scientificlinux.org/

Re: NFS problem on "ls" command

2013-03-28 Thread Evan Sather 
Hi Connie,

 1. 2.6.18-348.3.1.el5PAE
 2. i686
 3. Both are SL 6.3 running 2.6.32-358.2.1.el6.x86_64
 4. Both are 1:1.2.3-26.el6 (x86_64)
 5. Both are x86_64

Also, thank you for the additional link with more information on the bug.

*Evan Sather*
Linux System Administrator
High Energy Physics
Argonne National Laboratory

On 03/28/2013 01:42 PM, Connie Sieh wrote:
> On Thu, 28 Mar 2013, Evan Sather wrote:
>
>> --enig2GQLSDWJADQIIIAUXHNWJ
>> Content-Type: multipart/alternative;
>> boundary="090004020404060409070304"
>>
>> This is a multi-part message in MIME format.
>> --090004020404060409070304
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: quoted-printable
>>
>> Hi Everyone,
>>
>> We're experiencing NFS-related problems after viewing home directories
>> on SL6 desktops.  SL5 clients do not experience this problem.  The NFS
>> server is a SL5 machine.
>>
>> One of our desktops outputs this:
>>
>>[user@host1 ~]$ ls -ltr |tail
>>ls: reading directory .: Invalid argument
>>
>>
>> Another of our desktops outputs this:
>>
>>[user@host2 ~]$ ls -l
>>ls: reading directory .: Too many levels of symbolic links
>>
>> Has anyone else seen this or a similar issue?  Does anyone have any
>> suggestions?
>>
>> --=20
>> *Evan Sather*
>> Linux System Administrator
>> High Energy Physics
>> Argonne National Laboratory
>>
>>
>
> Evan,
>
> We are trying to pin down which versions of the client software have
> this issue.  We know that the server side changed via a bug fix in SL
> 5.9 via the 2.6.18-348 kernels.  We are trying to figure out a way to
> predict the issue on the client side.  So
>
>What kernel version do you have on the server?
>What arch is the server?
>
>What kernel version is on the client?
>What are the versions of nfs-utils* ?
>What arch is the client?
>
> Thanks
>
> -Connie Sieh



signature.asc
Description: OpenPGP digital signature

perl yum problem

2013-03-28 Thread Todd And Margo Chester 

Hi All,

Any idea how to fix this?

Many thanks,
-T

Error: Package: perl-IO-Compress-Bzip2-2.020-127.el6.x86_64 (@sl/6x)
   Requires: perl = 4:5.10.1-127.el6
   Removing: 4:perl-5.10.1-127.el6.x86_64 (@sl/6x)
   perl = 4:5.10.1-127.el6
   Updated By: 4:perl-5.10.1-130.el6_4.x86_64 (sl-security)
   perl = 4:5.10.1-130.el6_4



Fixed it.  Don't know if it is the official "approved" method,
but here goes:

1) # rpm -e --nodeps perl-IO-Compress-Bzip2-2.020-127.el6.x86_64

2) # yum upgrade

3) # yum install perl-IO-Compress-Bzip2
   ...
   Installed:
   perl-IO-Compress-Bzip2.noarch 0:2.015-1.el6.rf


Happy camping has returned.

-T

Re: spice-guest-tools for widows 8?

2013-03-28 Thread Todd And Margo Chester 

-Original Message-
From: owner-scientific-linux-us...@listserv.fnal.gov 
[mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Todd And 
Margo Chester
Sent: Wednesday, March 27, 2013 1:38 AM
To: Scientific Linux Users
Subject: spice-guest-tools for widows 8?

Hi All,

spice-guest-tools-0.52.exe does not support Windows 8.  Anyone know of a 
version that does?  No QXL driver is annoying.

Many thanks,
-T






On 03/27/2013 07:18 AM, Brown, Chris (GE Healthcare) wrote:
> This would be a question better suited to 
spice-de...@lists.freedesktop.org

>
> However as I have noted over time the spice guys do not seem to be 
very motivated to create and publish up to date windows drivers. They 
still have as of yet to publish properly signed QXL drivers for Windows 7.

>
> *HINT*
> These drivers do exist as part of the virtio-win package however if 
you have an active RHEL subscription :-)

> - Chris
>

Found something over at:
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-52.iso

Have yet to test it

-T

Re: spice-guest-tools for widows 8?

2013-03-28 Thread Todd And Margo Chester 

-Original Message-
From: owner-scientific-linux-us...@listserv.fnal.gov 
[mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Todd And 
Margo Chester
Sent: Wednesday, March 27, 2013 1:38 AM
To: Scientific Linux Users
Subject: spice-guest-tools for widows 8?

Hi All,

spice-guest-tools-0.52.exe does not support Windows 8.  Anyone know of a 
version that does?  No QXL driver is annoying.

Many thanks,
-T






On 03/27/2013 07:18 AM, Brown, Chris (GE Healthcare) wrote:

This would be a question better suited to

spice-de...@lists.freedesktop.org


However as I have noted over time the spice guys do not seem to be

very motivated to create and publish up to date windows drivers. They still 
have as of yet to publish properly signed QXL drivers for Windows 7.


*HINT*
These drivers do exist as part of the virtio-win package however if

you have an active RHEL subscription :-)

- Chris



Found something over at:
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-52.iso

Have yet to test it

-T


Hm.  Not sure that iso contains the QXL drivers.  W8
sure doesn't think there are any video drivers in it.