Sponsored Content
Operating Systems Linux SuSE Connection is broken because of underlying network issues Post 302928193 by Phuti on Tuesday 9th of December 2014 04:27:22 PM
Old 12-09-2014
Connection is broken because of underlying network issues

Hi Guys,

I have two databases where I copy archivelog files from server A to server B frequently...yesterday we did the VM upgrade now...I am struggling to copy/ship the files from server A to server B...

I manually tested the file transfer but the big files, e.g 46M, stall. I can copy small files but the big ones they stall...

It looks like something to do with the network...

Please Help....

Thanks in advance...
 

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Recover X Forwarding after broken connection

Hello, today I logged in on a remote machine via "ssh -X ..." and started a screen session. In this i started OpenOffice.org writer by writing "oowriter". After some time the connection got lost (The network here is quite unstable). Now I logged in again via "ssh -X ...". The screen session is... (1 Reply)
Discussion started by: schola
1 Replies

2. UNIX for Advanced & Expert Users

Exceed connection issues

I'm trying to use Exceed 7.1 to connect to a Solaris server (T2000, running Solaris 10). What are the settings that should be specified on Solaris to enable this connectivity to happen? I'm getting connection issues. Is there a type of service that needs to be running? If sombody can give a... (1 Reply)
Discussion started by: Sunguy222
1 Replies

3. UNIX for Advanced & Expert Users

connection to localhost:10.0 host broken (explicit kill or server shutdown)

Hi All, We use tomcat web server and it will get terminated with below error: connection to localhost:10.0 host broken (explicit kill or server shutdown) Please let me know how to fix this error. (5 Replies)
Discussion started by: bache_gowda
5 Replies

4. UNIX for Dummies Questions & Answers

IP connection Bash script issues

Hello I need assistance with a bash script that needs to tell me whether in the last "x" days (which is a variable) anyone connected to the xxxx IP (which is another variable). Thank you! (1 Reply)
Discussion started by: Melchiah
1 Replies

5. Infrastructure Monitoring

clstat X connection ... broken ?

Hi. Could you help me with this problem ? When I run clstat then I got this error message: 1:root@test1:/root # clstat X connection to localhost:10.0 broken (explicit kill or server shutdown). I got the same error for both nodes. If I would run xclstat I would understand that there... (5 Replies)
Discussion started by: phobus
5 Replies

6. UNIX for Advanced & Expert Users

lftp connection issues

Hi guys, We are receiving fatal error while trying to use lftp client to connect to an external server using ftps protocol. It seems to connect but when I issue 'ls' command, it fails with below error: $ lftp -u user,pwd ftps://<URL>:990/Submit lftp user@URL:~> ls ls: Fatal error:... (0 Replies)
Discussion started by: nice_chapp
0 Replies

7. AIX

X connection to localhost:10.0 broken (explicit kill or server shutdown)

I want to run applet on AIX 6 machine. I already have setup $DISPLAY variable for putty session by selecting X11 option. I got below error for any X related commands (xclock, X, applet viewer ) X connection to localhost:10.0 broken (explicit kill or server shutdown). Please can anyone... (0 Replies)
Discussion started by: kailas.girase
0 Replies
statd(1M)																 statd(1M)

NAME
statd, rpc.statd - network status monitor SYNOPSIS
DESCRIPTION
is an RPC server. It interacts with to provide the crash and recovery functions for the locking services on NFS (see lockd(1M)). keeps track of the clients with processes which hold locks on a server. When the server reboots after a crash, sends a message to the on each client indicating that the server has rebooted. The client processes then informs the on the client that the server has rebooted. The client then attempts to reclaim the lock(s) from the server. on the client host also informs the on the server(s) holding locks for the client when the client has rebooted. In this case, the on the server informs its that all locks held by the rebooting client should be released, allowing other processes to lock those files. Options recognizes the following options and command-line arguments: This is an obsolete option. All messages and errors are logged to WARNINGS
The crash of a server is only detected upon its recovery. FILES
lists hosts and network addresses to be contacted after a reboot lists hosts and network addresses that could not be contacted after last reboot includes a number which changes during a reboot AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
lockd(1M), fcntl(2), lockf(2), signal(2), sm(4). statd(1M)
All times are GMT -4. The time now is 07:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy