12-19-2017
Possibly the system has run out of network buffer resources. Has the load/number of users been steadily increasing?
Network configurations determine the number of buffers available for network packets (of various different sizes) arriving and departing, and also the maximum number of connections.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi I am using unix for last few days. Here is my problem
during boot the machine stop giving video signal and I don't know what's happening.
When I ping (during boot) it from another machine it comes alive then goes out.
The power on the CPU is on all the time.
please help. (9 Replies)
Discussion started by: santosh1981
9 Replies
2. UNIX for Dummies Questions & Answers
Is it common in the Unix/Linux environment to install compute intensive applications on a Server system and have the client machines download the executables into memory at runtime to run locally? This model seems taxing to the network, and as I understand, has been largely abandoned in the... (1 Reply)
Discussion started by: jonwillog
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
When most of the server applications get installed, they create their own user. I believe this is to not use the "root" account. For example, Apache when installed creates a user called "apache". And the directories which it uses are all owned by this user. This seems to be the... (2 Replies)
Discussion started by: srikanths
2 Replies
4. Shell Programming and Scripting
Hi all
I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server... (9 Replies)
Discussion started by: sakthifire
9 Replies
5. Programming
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
6. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
7. Solaris
Hi there,
We have a Solaris 10 machine which has been up and running for more than 400 days. A strange behaviour happened. The system date defaulted to epoch timestamp. Oracle stopped and application failed causing management to parade. We managed to reset the date. All other servers and... (8 Replies)
Discussion started by: sundar63
8 Replies
8. Red Hat
I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0
Following is the back trace of the multi-threaded program I am working on:... (0 Replies)
Discussion started by: anuachin
0 Replies
LEARN ABOUT CENTOS
rstream
RSTREAM(1) librdmacm RSTREAM(1)
NAME
rstream - streaming over RDMA ping-pong test.
SYNOPSIS
rstream [-s server_address] [-b bind_address] [-B buffer_size]
[-I iterations] [-C transfer_count]
[-S transfer_size] [-p server_port] [-T test_option]
DESCRIPTION
Uses the streaming over RDMA protocol (rsocket) to connect and exchange data between a client and server application.
OPTIONS
-s server_address
The network name or IP address of the server system listening for connections. The used name or address must route over an RDMA
device. This option must be specified by the client.
-b bind_address
The local network address to bind to.
-B buffer_size
Indicates the size of the send and receive network buffers.
-I iterations
The number of times that the specified number of messages will be exchanged between the client and server. (default 1000)
-C transfer_count
The number of messages to transfer from the client to the server and back again on each iteration. (default 1)
-S transfer_size
The size of each send transfer, in bytes. (default 1000) If 'all' is specified, rstream will run a series of tests of various
sizes.
-p server_port
The server's port number.
-T test_option
Specifies test parameters. Available options are:
s | socket - uses standard socket calls to transfer data
a | async - uses asynchronous operation (e.g. select / poll)
b | blocking - uses blocking calls
f | fork - fork server processing (forces -T s option)
n | nonblocking - uses non-blocking calls
v | verify - verifies data transfers
NOTES
Basic usage is to start rstream on a server system, then run rstream -s server_name on a client system. By default, rstream will run a
series of latency and bandwidth performance tests. Specifying a different iterations, transfer_count, or transfer_size will run a user
customized test using default values where none have been specified.
Because this test maps RDMA resources to userspace, users must ensure that they have available system resources and permissions. See the
libibverbs README file for additional details.
SEE ALSO
rdma_cm(7)
librdmacm 2011-11-16 RSTREAM(1)