Sponsored Content
Full Discussion: Ssh stopped working AIX
Top Forums UNIX for Dummies Questions & Answers Ssh stopped working AIX Post 302908713 by fierfek on Thursday 10th of July 2014 03:09:33 PM
Old 07-10-2014
Ssh stopped working AIX

I Was able to ssh into the AIX box. now i cannot When I run the command to start it it comes back that is was started, but still does not work. Here is a shot i what i see

Code:
# server:/> lslpp -l | grep ssh
  openssh.base.client     4.3.0.5201  COMMITTED  Open Secure Shell Commands
  openssh.base.server     4.3.0.5201  COMMITTED  Open Secure Shell Server
  openssh.license         4.3.0.5201  COMMITTED  Open Secure Shell License
  openssh.man.en_US       4.3.0.5201  COMMITTED  Open Secure Shell
  openssh.msg.EN_US       4.3.0.5201  COMMITTED  Open Secure Shell Messages -
  openssh.msg.en_US       4.3.0.5201  COMMITTED  Open Secure Shell Messages -
  openssh.base.client     4.3.0.5201  COMMITTED  Open Secure Shell Commands
  openssh.base.server     4.3.0.5201  COMMITTED  Open Secure Shell Server
# server:/> startsrc -s sshd
0513-059 The sshd Subsystem has been started. Subsystem PID is 6778932.
# server:/> lssrc -s sshd
Subsystem         Group            PID          Status
 sshd             ssh                           inoperative
# server:/> startsrc -g ssh
0513-059 The sshd Subsystem has been started. Subsystem PID is 6778946.
# server:/> lssrc -s ssh
0513-085 The ssh Subsystem is not on file.
# server:/> lssrc -g ssh
Subsystem         Group            PID          Status
 sshd             ssh                           inoperative

---------- Post updated 07-10-14 at 03:09 PM ---------- Previous update was 07-09-14 at 09:59 PM ----------

I tried a stop and start again. the ssh localhost here is what i got.

Code:
# server:/> stopsrc -s sshd
0513-004 The Subsystem or Group, sshd, is currently inoperative.
# server:/> startsrc -s sshd
0513-059 The sshd Subsystem has been started. Subsystem PID is 6266918.
# server:/> ssh localhost
Could not load program ssh:
        Dependent module /usr/lib/libcrypto.a(libcrypto.so.0.9.7) could not be l
oaded.
        Member libcrypto.so.0.9.7 is not found in archive

 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

#!/bin/bash has stopped working

Hi I'm writing a script and I've put #!/bin/bash as the first line so that I can just type my scripts name 'whodate' at PS1 instead of ./whodate. This has suddenly stopped working for me. It used to be the case that I could start a script with #!/bin/bash and it would work, but for this script... (2 Replies)
Discussion started by: zorrokan
2 Replies

2. Linux

Cronjobs stopped working

Hi All, I am user of a Linux machine and I have approximatly 15 cronjobs scheduled in my crontab. Yesterday my administrator made LDAP active on my userid and all the things are doing fine after that. But all cronjobs for my user id stored in my crontab have stopped working after that. Could... (1 Reply)
Discussion started by: bisla.yogender
1 Replies

3. Shell Programming and Scripting

cronjobs stopped working

Hello people, I had these cronjobs scheduled in some Unix boxes which were running fine until yesterday.But then the password was changed for that user id and then the jobs stopped working. As far as i know cron jobs run from super user. I am completely lost over here now. Thanks. (2 Replies)
Discussion started by: King Nothing
2 Replies

4. UNIX for Advanced & Expert Users

suPHP stopped working after dist-upgrade

Hi all, My server was Debian Etch (4) and had a working suPHP module (version 0.6.2-1). After I dist-upgraded it to Lenny (Debian 5), suPHP (version 0.6.2-3) stopped working. I read in the mailing list that I should change the settings of /etc/suphp/suphp.conf to this form: ;Handler... (1 Reply)
Discussion started by: mjdousti
1 Replies

5. IP Networking

Wireless stopped working- Fedora 12

I installed F12 around the time it was released and it picked up my wireless card and worked like a charm.....Suddenly last week everything stopped working and I receive what appears to be a driver error when wlan0 tries to load. Error for wireless request "Set Mode" (8B06) : SET failed on... (1 Reply)
Discussion started by: woodson2
1 Replies

6. Hardware

Middle Mouse Button stopped working

I have no idea what happened, but my middle mouse button stopped working since yesterday. I checked the settings for the mouse, everything seems fine. Reconnected mouse , restarted PC, nothing works. What kind of issue this could be, anyone experienced something like this before? If you have... (4 Replies)
Discussion started by: zdorian
4 Replies

7. Shell Programming and Scripting

Perl script stopped working

Hi, I have the following segment of a script which is supposed to prompt a user for password and then capture the password entered by the user. The function is called in by another script and used to work without issue, the problem is that recently the script is not waiting for the user to... (3 Replies)
Discussion started by: belalr
3 Replies

8. AIX

Printer stopped working

I have a serial printer connected to a 16 port ran. All of a sudden my printer stopped working and not sure how to get it back. Can anyone help pint me in the write direction? lsdev -Cc printer gives me the following. lp0 Defined 0A-08-11-00 Other serial printer lp1 Defined 0A-08-11-03... (3 Replies)
Discussion started by: Gmanx
3 Replies

9. Solaris

Mailx stopped working

after a new patch set on the 14th. I noticed that mailx stopped working, as far a I can tell that is the only thing that changed. solaris 10 OS it seems everything is the same, sendmail seems to be running root@server # ps -ef | grep -i sendmail smmsp 687 1 0 10:42:25 ? ... (0 Replies)
Discussion started by: goya
0 Replies
stopped(7)						 Miscellaneous Information Manual						stopped(7)

NAME
stopped - event signalling that a job has stopped SYNOPSIS
stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]... DESCRIPTION
The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. The JOB environment variable contains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs. If the job was stopped normally, the RESULT environment variable will be ok, otherwise if the job was stopped because it has failed it will be failed. When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start, main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job was stopped because it hit the respawn limit. Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received. The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see init(5) for more information. If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not found). See the system logs for the error. init(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other activity. It is typically combined with the starting(7) event by services when inserting themselves as a dependency. Job configuration files may use the export stanza to export environment variables from their own environment into the stopped event. See init(5) for more details. EXAMPLE
A service that wishes to be running whenever another service would be running, started before and stopped after it, might use: start on starting apache stop on stopped apache A task that must be run after another task or service has been stopped might use: start on stopped postgresql SEE ALSO
starting(7) started(7) stopping(7) init(5) Upstart 2009-07-09 stopped(7)
All times are GMT -4. The time now is 06:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy