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
pki-upgrade(8)							 PKI Upgrade Tool						    pki-upgrade(8)

NAME
pki-upgrade - Tool for upgrading system-wide configuration for Certificate System. SYNOPSIS
pki-upgrade [OPTIONS] DESCRIPTION
There are two parts to upgrading Certificate System: upgrading the system configuration files used by both the client and the server pro- cesses and upgrading the server configuration files. When upgrading Certificate System, the existing system configuration files (e.g. /etc/pki/pki.conf) may need to be upgraded because the content may have changed from one version to another. The configuration upgrade is executed automatically during RPM upgrade. However, in case there is a problem, the process can also be run manually using pki-upgrade. The system upgrade process is done incrementally using upgrade scriptlets. The upgrade process and scriptlet execution is monitored in upgrade trackers. A counter shows the latest index number for the most recently executed scriptlet; when all scriptlets have run, the com- ponent tracker shows the updated version number. The scriptlets are stored in the upgrade directory: /usr/share/pki/upgrade/<version>/<index>-<name> The version is the system version to be upgraded. The index is the script execution order. The name is the scriptlet name. During upgrade, the scriptlets will back up all changes to the filesystem into the following folder: /var/log/pki/upgrade/<version>/<index> The version and index values indicate the scriptlet being executed. A copy of the files and folders that are being modified or removed will be stored in oldfiles. The names of the newly-added files and folders will be stored in newfiles. The system upgrade process is tracked using this file: /etc/pki/pki.version The file stores the current configuration version and the last successful scriptlet index. OPTIONS
General options --silent Upgrade in silent mode. --status Show upgrade status only without performing the upgrade. --revert Revert the last version. -X Show advanced options. -v, --verbose Run in verbose mode. -h, --help Show this help message. Advanced options The advanced options circumvent the normal component tracking process by changing the scriptlet order or changing the tracker information. WARNING: These options may render the system unusable. --scriptlet-version <version> Run scriptlets for a specific version only. --scriptlet-index <index> Run a specific scriptlet only. --remove-tracker Remove the tracker. --reset-tracker Reset the tracker to match the package version. --set-tracker <version> Set the tracker to a specific version. OPERATIONS
Interactive mode By default, pki-upgrade will run interactively. It will ask for a confirmation before executing each scriptlet. % pki-upgrade If there is an error, it will stop and show the error. Silent mode The upgrade process can also be done silently without user interaction: % pki-upgrade --silent If there is an error, it will stop and show the error. Checking upgrade status It is possible to check the status of a running upgrade process. % pki-upgrade --status Troubleshooting If there is an error, rerun the upgrade in verbose mode: % pki-upgrade --verbose Check the scriptlet to see which operations are being executed. Once the error is identified and corrected, the upgrade can be resumed by re-running pki-upgrade. It is possible to rerun a failed script by itself, specifying the instance and subsystem, version, and scriptlet index: % pki-upgrade --scriptlet-version 10.0.1 --scriptlet-index 1 Reverting an upgrade If necessary, the upgrade can be reverted: % pki-upgrade --revert Files and folders that were created by the scriptlet will be removed. Files and folders that were modified or removed by the scriptlet will be restored. FILES
/usr/sbin/pki-upgrade AUTHORS
Ade Lee <alee@redhat.com>, Ella Deon Lackey <dlackey@redhat.com>, and Endi Dewata <edewata@redhat.com>. pki-upgrade was written by the Dogtag project. COPYRIGHT
Copyright (c) 2013 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is avail- able at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt. version 1.0 Jul 22, 2013 pki-upgrade(8)
All times are GMT -4. The time now is 12:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy