ssh connection refused post yum interrupted update
an update of RHEL 5.1 via yum was interrupted after installing the following packages.
We rolled back the packages to their original versions but cannot connect any new ssh sessions.
We need access to this box remotely, we have 1 open ssh session to the system and can go to the datacenter to access it locally. Any suggestions or help is GREATLY appreciated. Our linux admin is out for medical reasons and we have limited resources.
Last edited by pludi; 04-05-2010 at 08:05 AM..
Reason: code tags, please...
I installed Openserver 5.0.7 and I cannot telnet to the localhost and I can't telnet from my old SCO 3.2.42 to the new SCO machine but I can ping the new machine and it will telnet to the old machine. (2 Replies)
Hi there,
Anything will help.
I have running server on computer and want to connect from some clients.
Server:
memset(&hints, 0, sizeof(hints));
hints.ai_family = domain;
hints.ai_socktype = SOCK_STREAM;
error = getaddrinfo("localhost", "8300", &hints, &res0);
if (error)
{
... (1 Reply)
Hi,
I would like to know the difference between YUM UPDATE and YUM UPGRADE. The man pages say upgrade is same as update with the obsolete option. And by default it says the obsolete option is turned on, which would make them equivalent. Does not say what obsolete does.
Can someone please... (3 Replies)
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
I dont' what happened with my servers (test servers only) but I just noticed that suddenly I cannot up the domain anymore (Sun Java System Application Server 9.1_01).
a. server.log
org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the... (1 Reply)
Hi all,
I logged on to a Unix server and am trying to connect a remote Windows server (Windows NT) via SSH/SFTP. However I always got the following error,
sftp username@host_server (or ssh username@host_server)
ssh: connect to host host_server port 22: Connection refused
Any advise... (1 Reply)
I have two computers running Debian 6.0 and one running Solaris 2.6 on a private network. The Debian computers can ftp to the Solaris computer but if a Debian computer is the destination the ftp connection is refused. I assume this is some security feature of Debian. What can I do to allow... (2 Replies)
Hi I am trying to execute a shell script which is in unix server gs1. The script is below which basically connects to another unix server q15 and tries to get a file using FTP .
But i get error as "ftp: connect: Connection refused
Not connected.
Not connected."
Please help with if the below... (8 Replies)
Hello everybody,
I'm a begginer using Solaris so I really need your help. I'm trying to copy a file using scp from a Red Hat Linux 6 server to an Oracle Solaris 11 machine and all i get is an error "" ssh: connection to host <HOST_IP> port 22: Connection refused lost connection.
Thanks for... (6 Replies)
I have downloaded RHEV-H 4.2 Red Hat Virtualization - Red Hat Customer Portal (RHVirtualization 4.2 Host and Manager iso). I uploaded the image and installed on an HP G9 server baremetal.
I found I dont have a WAN/net connectivity later on HPG9 server. How can I still install virt-manager on... (1 Reply)
Discussion started by: Paras Pandey
1 Replies
LEARN ABOUT OPENSOLARIS
metadevadm
metadevadm(1M) System Administration Commands metadevadm(1M)NAME
metadevadm - update metadevice information
SYNOPSIS
/usr/sbin/metadevadm [-h] [-n] [ [-l]-r] [-s setname]
[-u disk_specifier] [-v]
DESCRIPTION
The metadevadm command facilitates the administration of device ID entries in Solaris Volume Manager. Use this command when the pathname
stored in the metadevice state database no longer correctly addresses the device or when a disk drive has had its device ID changed.
This command requires root privileges.
OPTIONS
The following options are supported.
-h Provide a help display.
-l Specify that metadevadm log to syslog(3C). metadevadm logs to the DAEMON facility at the ERR level by default. See
syslog.conf(4) for additional information on changing logging levels.
Use this option anytime. It is most useful in startup scripts and less useful interactively.
-n Emulate the effect of a command, without making any changes to the system.
-r Recompute the pathname and disk specifier (including slice) associated with all devices in the metadevice state data-
base if the device supports device IDs. If a device does not support device IDs or the device is not available, then
no action is taken for that device.
Use this option when the disk has been moved or readdressed.
This option is run automatically at boot time to detect device ID changes and update the state database.
-s setname Specify the name of the disk set on which metadevadm works. This option causes the command to perform its administra-
tive function within the specified disk set. Without this option, the command performs its function on devices in the
local disk set.
-u disk_specifier Obtain the device ID associated with the disk_specifier (for example, c1t2d0) of a device and update the metadevice
state database. If the device ID has not changed this option does nothing. Use this option when a disk drive has had
its device ID changed during a firmware upgrade or due to changing the controller of a storage subsystem.
-v Execute in verbose mode. This option has no effect when used with -u. Verbose is the default.
EXAMPLES
Example 1 Updating Device ID of Disk
The following example updates the device c2t3d0:
# metadevadm -u c2t3d0
Updating SLVM device relocation information for c2t3d0.
Old device reloc information: id19280192391293123012012010012012091398
New device reloc information: id19380192391293123012012010012012091398
The following example is a variation of the preceding, using the full pathname.
# metadevadm -u /dev/dsk/c2t3d0
The following example uses the -n option, which means that the command is emulated, but does not take effect. Note that when the -v option
is used with -u, -v has no effect (verbose is the default).
# metadevadm -u -v -n c2t3d0
Updating SLVM device relocation information for c2t3d0.
Old device reloc information: id19280192391293123012012010012012091398
New device reloc information: id19380192391293123012012010012012091398
Example 2 Recomputing Pathnames
In the following example, all device names are valid.
# metadevadm -r
Disk movement detected.
Updating device names in SLVM.
In the following example, once again device names are valid.
# metadevadm -r -v
Disk movement detected.
Updating device names in SLVM.
c0t0d0s0 changed to c0t0d1s0 from device relocation information
id12098123lkmklsdjaasdkfjadfjakds
In the following example, metadevadm detects an invalid device name.
# metadevadm -r
Invalid device relocation information detected in SLVM.
Please check status of following disk(s):
c3t0d0
RETURN VALUES
The following exit values are returned:
0 Command was successful.
1 metadevadm encountered an error condition.
2 An invalid device ID was detected when using the -r option. This is for use in the rc2.d script. See init.d(4).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWmdu |
+-----------------------------+-----------------------------+
|Interface Stability |Stable |
+-----------------------------+-----------------------------+
SEE ALSO mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M),
md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D)SunOS 5.11 26 Mar 2006 metadevadm(1M)