02-20-2004
client app not letting go of socket
Ok here's the situation
We have an application that our users log into over the network to one of our unix boxes (Solaris 8). I had this situation occur the other day where an user claimed that he totally shutdown the app because it froze up and wasn't able to log back in.
I performed a netstat on the port and I could see that he wasn't getting back in because the original connection (frozen app) was still established and I could see time_waits for the new attempts to login (the time_waits are because we're not allowing the user to log back in because technically he's still logged in).
after a while I saw the ESTABLISHED switch to FIN_WAIT_2, I never seen this state before (can someone explain what it means in laymens terms and give an example of a situation it might occur).
Anyway the user wanted an explanation and I have never seen this before, usually when a user closes the app the connection will drop but this time it stayed established. Is it possible that the session level processes were still running on the Windows 2000 server pc he was using?? even though everything on the desktop said the app was closed??
Anyway, I would greatly appreciate any info you could spare on this situation and also is there a website or reference somewhere that could explain real life situations where certain netstat states would occur??
thanks in advance
10 More Discussions You Might Find Interesting
1. Programming
Hi
I have apeculiar problem with sockets.
I have a shared object for my client program.
when I send a request to the server, it is suppose to process and sends back the result string to the client.
For the first request, it is working fine i.e. client sends the req. and gets the... (1 Reply)
Discussion started by: axes
1 Replies
2. Programming
Hi,
Am very new to socket programming.
When we use UDP sockets to communicate between two processess,
will both the client/server socket be able to send/recv ?
meaning can sendto()/ recvfrom() be used on both server and client?
It could be useful even if anybody provide some link on socket... (1 Reply)
Discussion started by: rvan
1 Replies
3. UNIX for Dummies Questions & Answers
I'm new to socket programming. Have a basic doubt.
I have a structure(global) at the server side.
I have two different client connecting to the server. Will the changes made by one client on the structure be visible to the other client when it accesses the same client? I'm creating a STREAM... (3 Replies)
Discussion started by: abc.working
3 Replies
4. 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
5. Programming
Am trying to connect to local machine on port 9102
There is no server application listening on port 9102.
if (connect(fd,(struct sockaddr *)&addr, (socklen_t)sizeof(struct sockaddr)) == -1)
return -1;
cout<<"Connected ,ERRNO:"<<errno<<", txt:"<<strerror(errno);
netstat -na |grep... (5 Replies)
Discussion started by: johnbach
5 Replies
6. Programming
char name;
printf ("Welcome to the server \n");
printf ("Enter user name: \n");
scanf ("%c", &name);
how can client send name to server:what should be the code?
int send ( int sid , const char ∗buffer Ptr , int len , int f l a g )
how can client receive ack from... (1 Reply)
Discussion started by: saiful_911
1 Replies
7. Programming
hei,
i want to enter name and read it by client server socket program after checking name validity put the password and check.if ok than server clirnt say correct other wise incorrect.
below my code:
char name;
printf ("Welcome to the server \n");
printf ("Enter user name: \n");
scanf... (1 Reply)
Discussion started by: saiful_911
1 Replies
8. Programming
Hello people.
I'm trying to do something like a search engine.
Server runs in the background by using ./server & which has data from a textfile stored in an array.
Client then runs by using ./client
It will then prompt "Search for:"
For example, if I searched for Products called Instant... (0 Replies)
Discussion started by: andylbh
0 Replies
9. Programming
Ok so this is what I have.
I have separate client and server codes. I initially had the server listening and accepting connections from ONE port, and it was working great.
Now, what I want to do is, enable the server to listen and accept connections on TWO OR MORE ports , thus, effectively... (2 Replies)
Discussion started by: CrazedMonk
2 Replies
10. Programming
I'm trying to make a "dual/server client" (ipv4,ipv6) with sockets in linux but i don't know how to join both codes. I have a dual client ipv4 and ipv6, but i have problems with the server if you notice the only difference between them it's the AF_INET (pf_inet ipv4, and if_inet6 ipv6) and the port... (3 Replies)
Discussion started by: godna
3 Replies
SHUTDOWN(8) System Manager's Manual SHUTDOWN(8)
NAME
shutdown - close down the system at a given time
SYNOPSIS
shutdown [ -k ] [ -r ] [ -h ] [ -f ] [ -n ] time [ warning-message ... ]
DESCRIPTION
Shutdown provides an automated shutdown procedure which a super-user can use to notify users nicely when the system is shutting down, sav-
ing them from system administrators, hackers, and gurus, who would otherwise not bother with niceties.
Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number and hour:min. The first form brings the system down in number minutes and the second brings the
system down at the time of day indicated (as a 24-hour clock).
At intervals which get closer together as apocalypse approaches, warning messages are displayed at the terminals of all users on the sys-
tem. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are disabled by creating /etc/nologin and
writing a message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed
just before shutdown exits.
At shutdown time a message is written in the system log, containing the time of shutdown, who ran shutdown and the reason. Then a termi-
nate signal is sent to init to bring the system down to single-user state. Alternatively, if -r, -h, or -k was used, then shutdown will
exec reboot(8), halt(8), or avoid shutting the system down (respectively). (If it isn't obvious, -k is to make people think the system is
going down!)
With the -f option, shutdown arranges, in the manner of fastboot(8), that when the system is rebooted the file systems will not be checked.
The -n option prevents the normal sync(2) before stopping.
The time of the shutdown and the warning message are placed in /etc/nologin and should be used to inform the users about when the system
will be back up and why it is going down (or anything else).
FILES
/etc/nologin tells login not to let anyone log in
SEE ALSO
login(1), reboot(8), fastboot(8)
BUGS
Only allows you to kill the system between now and 23:59 if you use the absolute time for shutdown.
4th Berkeley Distribution November 16, 1996 SHUTDOWN(8)