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 SUSE
opiepasswd
OPIEPASSWD(1) General Commands Manual OPIEPASSWD(1)NAME
opiepasswd - Change or set a user's password for the OPIE authentication system.
SYNOPSIS
opiepasswd [-v] [-h] [-c|-d] [-f]
[-n initial_sequence_number ] [-s seed ] [ user_name ]
DESCRIPTION
opiepasswd will initialize the system information to allow one to use OPIE to login. opiepasswd is downward compatible with the keyinit(1)
program from the Bellcore S/Key Version 1 distribution.
OPTIONS -v Display the version number and compile-time options, then exit.
-h Display a brief help message and exit.
-c Set console mode where the user is expected to have secure access to the system. In console mode, you will be asked to input your
password directly instead of having to use an OPIE calculator. If you do not have secure access to the system (i.e., you are not on
the system's console), you are volunteering your password to attackers by using this mode.
-d Disable OTP logins to the specified account.
-f Force opiepasswd to continue, even where it normally shouldn't. This is currently used to force opiepasswd to operate in "console"
mode even from terminals it believes to be insecure. It can also allow users to disclose their secret pass phrases to attackers. Use
of the -f flag may be disabled by compile-time option in your particular build of OPIE.
-n Manually specify the initial sequence number. The default is 499.
-s Specify a non-random seed. The default is to generate a "random" seed using the first two characters of the host name and five
pseudo-random digits.
EXAMPLE
Using opiepasswd from the console:
wintermute$ opiepasswd -c
Updating kebe:
Reminder - Only use this method from the console; NEVER from remote. If you
are using telnet, xterm, or a dial-in, type ^C now or exit with no password.
Then run opiepasswd without the -c parameter.
Using MD5 to compute responses.
Enter old secret pass phrase:
Enter new secret pass phrase:
Again new secret pass phrase:
ID kebe OPIE key is 499 be93564
CITE JAN GORY BELA GET ABED
wintermute$
Using opiepasswd from remote:
wintermute$ opiepasswd
Updating kebe:
Reminder: You need the response from your OPIE calculator.
Old secret password:
otp-md5 482 wi93563
Response: FIRM BERN THEE DUCK MANN AWAY
New secret password:
otp-md5 499 wi93564
Response: SKY FAN BUG HUFF GUS BEAT
ID kebe OPIE key is 499 wi93564
SKY FAN BUG HUFF GUS BEAT
wintermute$
FILES
/etc/opiekeys -- database of key information for the OPIE system.
SEE ALSO passwd(1), opie(4), opiekey(1), opieinfo(1), opiesu(1), opielogin(1), opieftpd(8), opiekeys(5), opieaccess(5)AUTHOR
Bellcore's S/Key was written by Phil Karn, Neil M. Haller, and John S. Walden of Bellcore. OPIE was created at NRL by Randall Atkinson, Dan
McDonald, and Craig Metz.
S/Key is a trademark of Bell Communications Research (Bellcore).
CONTACT
OPIE is discussed on the Bellcore "S/Key Users" mailing list. To join, send an email request to:
skey-users-request@thumper.bellcore.com
7th Edition January 10, 1995 OPIEPASSWD(1)