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 OSF1
bootpd
bootpd(8) System Manager's Manual bootpd(8)NAME
bootpd - Internet Boot Protocol (BOOTP) server
SYNOPSIS
/usr/opt/obsolete/usr/sbin/bootpd [-c chdir-path] [-ttimeout] [-d debug-level] [configfile [dumpfile]]
OPTIONS
Sets the current directory used by a bootpd process while checking the existence and size of client boot files. This is useful when client
boot files are specified as relative pathnames and the bootpd process needs to use the same current directory as the TFTP server (typically
/tftpboot). Sets the debug-level variable that controls the number of debugging messages generated. For example, -d 4 sets the debugging
level to 4. Valid entries are 1 to 4, where 1 specifies lower level of messages and 4 the highest. Specifies the timeout value (in min-
utes) that a bootpd process waits for a BOOTP packet before exiting. If no packets are received for timeout minutes, the program exits. A
timeout value of zero means that a bootpd process will wait forever. When the bootpd daemon is not started using the inetd daemon, this
option is forced to zero.
DESCRIPTION
The bootpd daemon implements an Internet Boot Protocol server as defined in RFC 951, RFC 1532, and RFC 1533. In order to use the bootpd
daemon, you must install the Obsolete Commands and Utilities subset (OSFOBSOLETExxx). It can be started by the /usr/sbin/inetd daemon by
including the following line in the /etc/inetd.conf file: bootps dgram udp wait root /usr/sbin/bootpd bootpd
This causes bootpd to be started only when a boot request arrives. If bootpd does not receive another boot request within fifteen minutes
of the last one it received, it exits to conserve system resources. The -t option can be used to specify a different timeout value in min-
utes (for example, -t20). A timeout value of zero means forever.
To run the bootpd daemon, you must also run the tftpd daemon.
Upon startup, bootpd first reads its configuration file, /etc/bootptab, and then begins listening for BOOTREQUEST packets. See bootptab(4)
for a description of the configuration file. The bootpd daemon looks in /etc/services to find the port numbers it should use. Two entries
are extracted: The bootp server listening port The destination port used to reply to clients
If the port numbers cannot be determined this way, they are assumed to be 67 for the server and 68 for the client.
The bootpd daemon rereads its configuration file when it receives a hangup signal, SIGHUP, or when it receives a bootp request packet and
detects that the file has been updated. Hosts can be added, deleted, or modified when the configuration file is reread. If bootpd is com-
piled with the -DDEBUG option, receipt of a SIGUSR1 signal causes it to dump its memory-resident database to the /usr/adm/bootpd.dump file
or dumpfile specified in the command line.
RESTRICTIONS
Individual host entries must not exceed 1024 characters.
You cannot run bootpd and joind on the same system at the same time.
FILES
Internet Boot Protocol server. The bootpd daemon dump file. Defines the sockets and protocols used for Internet services.
SEE ALSO
Commands: bootpgw(8), bprelay(8), inetd(8), joind(8), tftpd(8)
Files: bootptab(4)
DARPA Internet Request For Comments:
Bootstrap Protocol (RFC 951)
Clarifications and Extensions for the Bootpstrap Protocol (RFC 1532)
DHCP Options and BOOTP Vendor Extensions (RFC 1533)
bootpd(8)