SSH Daemon won't start.

[Roger Armitage]

've downloaded and installed my companys depot version of openssh and prngd and openssl.

I'm having a problem making the rest of the configurations changes that seem to start the sshd process.

What I need to know is how do I get the daemon to start. I've added a script in the rc.config.d that should start the process but it's not working.

I'm kinda new to the admin role and installing software and configuring it to run is causing meproblems so if there are any suggested readings on the subject I'd appreciate the help as well.

[Rick Garland]

We have T1471AA installed, the HPUX A.4.00 version of SSH utilities.

The binariy installs into /opt/ssh/sbin/sshd

What happens when you execute the command
/opt/ssh/sbin/sshd

[Roger Armitage]

# cd /opt/openssh/sbin
# ll
total 2096
-rwxr-xr-x 1 bin bin 1073152 Jan 16 2004 sshd
# ./sshd
/usr/lib/dld.sl: Unresolved symbol: getaddrinfo (code) from ./sshd
Abort(coredump)

[Sanjay_6]

Hi Roger,

Looks like the ssh s/w or one of the other s/w's that you have installled is for IPv6. Download the one with support for IPv4.

Take a look at this thread from ITRC.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000081706691

The ITRC doc id is 4000092431.

Hope this helps.

Regds

[Roger Armitage]

I can't install software that isn't on our depot server.

This is what I installed.

OpenSSH 3.7.p1 (OpenSSH) OpenSSH Version 3.7.p1 for HP-UX 11.11

How can you determine if you installed IPv4 or IPv6?

[Roger Armitage]

After doing the install, I couldn't find a entry in init.d directory.

I was able to verify that prngd was running. But not SSHD.


I've since tried swremove and re-installing the file, still no luck.

I've wrote a small script in init.d to execute but can't seem to get it to start after boot up.

[Sameer_Nirmal]

Hi,

If the installation ssh depot is OK, then you should see an entry to start the sshd deamon in /sbin/rc2.d i.e "Sxxxsecsh"

The corresponding config file for this startup would be in /etc/rc.config.d as "sshd". Check SSHD_START = 1 is set.

If the sshd is not running now, you can start it using
# /sbin/3hrc2.d/Sxxxsecsh start
# ps -ef | grep sshd

[Roger Armitage]

I don't see the entry in rc2.config

I created the one in init.d manually, the install I did from depot didn't seem to do much more than install the binaries.

[Steven E. Protter · Accepted solution]

Shalom Roger,

You have inadvertantly answered your question.

You created the rc.d files yourself because the installation did not do that.

That means the installation failed.

swremove secure shell.

Install it again

See if you can get a newer version into your depot, but I've got systems all over our offices that run just fine on that version of secure shell.

I know, I always advocate upgrade, but there are just too many servers. Eeeek. Servers and servers and servers! Oh my.

Seriously, I bet a swverify \* shows an incomplete secureshll installation.

SEP

[Roger Armitage]

Special thanks to everyone who helped me troubleshoot this issue.

It turns out the isntallation I was using was indeed the wrong one. That was verified using swverify. I scoured through my depot resources and found an older version of openssh that seems to work good and matches the version that is on the servers I'm trying to secure shell too.

On a side note, I think depots are a great resource but when you run into problems there is very little resources available on how to build an install from scratch, how to create entries in the rc#.config location, etc...