Sponsored Content
Operating Systems Linux Red Hat How can I monitor network in CentOS .5.5 , my application refuse to read sockets Post 302500095 by umen on Sunday 27th of February 2011 01:27:54 AM
Old 02-27-2011
How can I monitor network in CentOS .5.5 , my application refuse to read sockets

Hi
I have wired problem with one of my applications (servers ) , its suddenly starts to read socket and before it written back , the connection is closed
this is what I see in my logs . is there any took in Linux centos that lets me see what is happening in this time frame ?
 

9 More Discussions You Might Find Interesting

1. Programming

Help in developing a Network Appliation to monitor pc in a network

I am developing a Network Appliation to monitor computers in a network. Specs are App monitors the current web page viewed in each system App also can shutdown the computer in the network App can show all process run by each computer in the network I am now confused how to start my... (2 Replies)
Discussion started by: valaparambil88
2 Replies

2. Linux

Network 10Mb/s half duplex only. r8168 on Centos 5.

Hi, For some reason my network card started going 10Mb/s half duplex instead of 1000Mb/s full duplex. System is connected to 8x1Gb HP switch. Other devices connect fine through the switch and get full 1Gb network. I have Centos 5 with all updates. Driver comes from elrepo and as well is... (1 Reply)
Discussion started by: columb
1 Replies

3. Programming

help: problem with sockets write/read

I am trying to make a server and client, the client will choose between some options and the server will react accordingly. After a some reads and writes that work the server needs to read from client an INT i use this: read(newSd,&k,sizeof(int));But even if all the other times there was no... (1 Reply)
Discussion started by: theSling
1 Replies

4. AIX

powerha application monitor restart counter?

I have configured a custom application monitor with restart count = 3. say the application has restarted 2 times, if the application fail 2 more times within restart interval, it will failover. Is there any counter to tell me the recent restart count? Thanks!! (1 Reply)
Discussion started by: skeyeung
1 Replies

5. Red Hat

Network Teaming not working in RHEL/CentOS 7

I was testing Networking Teaming (activebackup) with a VM hosted on VmWare Workstation and VirtualBox, and the result is, if the active interface is down, the system is not using the backup interface. Tested on both CentOS / RHEL 7 Please find below the command I have used to configure teaming.... (0 Replies)
Discussion started by: atanubanerji
0 Replies

6. Web Development

ASP.NET 5 Application on Centos OS7 Web Hosting Server

Hi All, Frankly I'm new to Linux Environment. While we are trying to Host an ASP.NET 5 Web Application on Centos OS7 Web hosting Server. There were couple of steps which we are supposed to go through, please see this link - We are stuck at Create a Container & then Running the Container,... (1 Reply)
Discussion started by: John Fredric
1 Replies

7. Emergency UNIX and Linux Support

Centos 7 Network Manager overwriting resolv.conf

Hi all, I need to add domain and search parameters to resolv.conf, however network manager overwrites. Setting the PEERDNS=No in the interface file seems to have no effect on this behaviour. Sadly I cannot just disable NM as these are not my hosts, I'm just attempting to install a platform... (3 Replies)
Discussion started by: Skrynesaver
3 Replies

8. IP Networking

I would like to monitor network traffic for a computer on my network

My son does homework on a school laptop. I was thinking about setting up a gateway on my home network, so that I can monitor web traffic and know if he is doing his homework without standing over his shoulder. Ideally I would like to use the Raspberry Pi Model b that I already have. However, I... (15 Replies)
Discussion started by: gandolf989
15 Replies

9. Infrastructure Monitoring

Using Node-RED and MQTT to Monitor Server and Application Stats

After setting up MQTT and testing some ESP8266 and ESP32 modules, where I noted that testing in Programming ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages, I was so impressed with MQTT that I installed MQTT on three different computers, instantly and... (2 Replies)
Discussion started by: Neo
2 Replies
SOCKET(1)                                                     General Commands Manual                                                    SOCKET(1)

NAME
socket - create a TCP or a UNIX domain socket and connect to stdin/out SYNOPSIS
socket [ -bcfqrvw ] [ -p command ] [ -B local address ] host port socket [ -bcfqrvw ] [ -p command ] /path socket [ -bcfqrvw ] [ -p command ] [ -B local address ] -s [ -l ] port socket [ -bcfqrvw ] [ -p command ] -s [ -l ] /path DESCRIPTION
Socket creates an Internet domain TCP or a UNIX domain stream socket and connects it to stdin and stdout. The host argument can be an Internet number in dot-notation (like ``130.149.28.10'') or a domain name. In this case it must be possible to resolve the name to a valid Internet address with gethostbyname(3). The port argument can be a port number or a service name which can be mapped to a port number by getservbyname(3). If an UNIX domain socket is wanted to be created instead of an Internet socket, specify the path instead of an internet (canonical domain named or dot-notated) host. The hostname is treated as a pathname if contains at least a single slash. I.e. if one wants to create or connect to a socket in the current directory, use ./filename to specify the connection point. OPTIONS
-b (background) The program forks itself into the background, detaches from its controlling tty, closes the file descriptors associated with the tty, and changes its current directory to the root directory. -B (local address) This option specifies which local address to binded to when making a connection. -c (crlf) Linefeed characters (LF) are converted to a Carriage Return Linefeed sequence (CRLF) when written to the socket. CRLF sequences read from the socket are converted to a single LF. -f (fork) When a server connection has been accepted, a separate process is forked to handle the connection in background. -l (loop) (only valid with -s) After a connection has been closed, another connection is accepted. -p (program) The specified command is executed for each connection. Its standard input, standard output, and standard error channels are con- nected to the socket. Command can be any shell command since it is passed to /bin/sh. -q (quit) The connection is closed when an end-of-file condition occurs on standard input. -r (read only) No data is read from standard input and written to the socket. -s (server) A server socket is created. A hostname argument is not required of Internet sockets, only the port number but a pathname is required for UNIX domain sockets. -v (verbose) Messages about connections etc. are issued to stderr. -w (write only) No data is read from the socket and written to the standard output. -version Socket prints its version ID and terminates. This must be the first argument to have an effect. EXAMPLES
The command socket -v coma.cs.tu-berlin.de nntp connects to the nntp port (port 119) of coma.cs.tu-berlin.de (130.149.28.10). The command socket -sl 3425 creates a server socket on port 3425 on the local host and waits for a connection. After a connection has been closed, a new connection is accepted. The command socket -wslqvp "echo Socket! " 1938 creates a server socket on port 1938 on the local host and waits for a connection. When a connection is accepted, the string "Socket!" is written to the socket. No data is read from the socket and written to the finger program. The connection is closed when an end-of-file condition at the standard output of the program occurs. Then a new connection is accepted. DIAGNOSTICS
Lots of diagnostics for failed system calls. unknown host host host's address could not be resolved. Signal signal caught, exiting Socket exits on any signal other than SIGTSTP, SIGCONT, SIGCLD, SIGQUIT. A non-zero exit code is returned if socket terminates due to an error condition or a signal. SEE ALSO
ip(7), tcp(7), unix(7), accept(2), bind(2), listen(2), connect(2), socket(2), gethostbyname(3), getservbyname(3) BUGS
socket -p terminates due to a SIGPIPE signal when there is more data from the socket available than the executed program wants to read. Please report any other bugs to the author. VERSION
This manual page describes Socket-1.1. AUTHOR
Juergen Nickelsen <nickel@cs.tu-berlin.de> Aug 6, 1992 SOCKET(1)
All times are GMT -4. The time now is 07:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy