06-25-2013
But 127.0.0.1 shouldn't be affected by auto-negotiation, right? In our environment the standard is auto on both the switches and servers.
8 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Is the performance now very, very slow (pages take a very long time to load)? Or is it just me?
Neo (6 Replies)
Discussion started by: Neo
6 Replies
2. Shell Programming and Scripting
We have an egrep search in a while loop.
egrep -w "$key" ${PICKUP_DIR}/new_update >> ${PICKUP_DIR}/update_record_new
${PICKUP_DIR}/new_update is 210 MB file
In each iteration, the egrep on an average takes around 50-60 seconds to search. Ther'es nothing significant in the loop other... (7 Replies)
Discussion started by: hidnana
7 Replies
3. Filesystems, Disks and Memory
Hi all
We have got issues with copying a 2.6 GB file from one folder to another folder.
Well, this is not the first issue we are having on the box currently, i will try to explain everything we have done from the past 2 days.
We got a message 2 days back saying that our Production is 98%... (3 Replies)
Discussion started by: b_sri
3 Replies
4. UNIX for Dummies Questions & Answers
hi guys
We are seeing weird issues on my Linux Suse 10, it has lotus 8.5
and 1 filesystem for OS and another for Lotus Database.
the issue is when the Lotus service starts wait on top is very high about 25% percent and in general CPU usage is very high
we found that when this happens if we... (0 Replies)
Discussion started by: kopper
0 Replies
5. Shell Programming and Scripting
Please, I need help tuning my script. It works but it's too slow.
The code reads an acivity log file with 50.000 - 100.000 lines and filters error messages from it. The data in the actlog file look similar to this:
02/08/2011 00:25:01,ANR2034E QUERY MOUNT: No match found using this criteria.... (5 Replies)
Discussion started by: Miila
5 Replies
6. Infrastructure Monitoring
There is a big problem with the server (VPS based on OpenVZ, CentOS 5, 3GB RAM). The problem is the following. The first 15-20 minutes after starting the server is operating normally, the load average is less than or about 1.0, but then begins to increase sharply% wa, then hovers around 95-99%.... (2 Replies)
Discussion started by: draiphod
2 Replies
7. Red Hat
My code
Hi All,
I am having redhat linux 5.3 (Tikanga) with GFS file system and its very very slow for executing ls -ls command also.Please see the below for 2minits 12 second takes.
Please help me to fix the issue.
$ sudo time ls -la BadFiles |wc -l
0.01user 0.26system... (3 Replies)
Discussion started by: susindram
3 Replies
8. Red Hat
Hi,
I have 2 machines in production environment:
1. redhat machine for application
2. DB machine (oracle)
The application doing a lot of small read&writes from and to the DB machine.
The problem is that after some few hours the network from the application to the DB becomes very slow and... (4 Replies)
Discussion started by: moshesa
4 Replies
LEARN ABOUT DEBIAN
kumoctl
KUMOCTL(1) General Commands Manual KUMOCTL(1)
NAME
kumoctl - show kumofs status
SYNOPSIS
kumoctl address[:port=19750] command [options]
DESCRIPTION
Show status of kumo-manager and send control commands to kumo-manager.
COMMANDS
status show status of the cluster
attach attach all new servers and start replace
attach-noreplace
attach all new servers
detach detach all fault servers and start replace
detach-noreplace
detach all fault servers
replace
start replace without attach/detach
full-replace
start full-replace (repair consistency)
backup [suffix=20090304]
create backup with specified suffix
enable-auto-replace
enable auto replace
disable-auto-replace
disable auto replace
STATUS
hash space timestamp
The time that the list of attached kumo-servers is updated. It is updated when new kumo-server is added or existing kumo-server is
down.
attached node
The list of attached kumo-servers. (active) is normal node and (fault) is fault node or recoverd but not re-attached node.
not attached node
The list of recognized but not-attached nodes.
AUTO REPLACING
By default, you have to attach new kumo-servers manually using kumoctl command. If the auto replacing is enabled, new kumo-servers are
attached automatically. This is experimental feature.
EXAMPLE
$ kumoctl mgr1 status
$ kumoctl mgr1 attach
SEE ALSO
kumo-manager(1).
kumoctl July 2009 KUMOCTL(1)