topic ssh problem in Operating System - Tru64 Unix

ssh problem

Carlos A. Munoz Lopez — Tue, 06 Jun 2006 12:04:46 GMT

Hi guys. I've been having a problem when I try to connect using ssh on a Tru64 5.1B server. I can't connect to the server, it says the service is not available. When I try to start the service it displays an error message. I also used ssh -v to see the debug information of the service and this is what it shows:

debug: SshAppCommon/sshappcommon.c:185: Allocating global SshRegex context.
ssh: FATAL: pipe: No such file or directory

I don't really know how to solve this problem. It appears that one file is missing but I have no idea which one is. I would appreciate some help on this issue. Thanks in advance!!

Re: ssh problem

Mark Poeschl_2 — Tue, 06 Jun 2006 13:38:36 GMT

What is the error you're getting when you try and start the service? That sould prove more useful than the output of the ssh client trying to connect to a non-existant service.

Please post the output of

# /sbin/init.d/sshd stop
# /sbin/init.d/sshd start

Re: ssh problem

Carlos A. Munoz Lopez — Tue, 06 Jun 2006 16:48:45 GMT

I know the debug information doesn't explain too much about what the problem is, but that is all the information I have. I checked /var/adm/messages but it doesn't display any kind of error. The output of the command you mentioned is:

Secure Shell daemon (sshd2) failed to start properly

Re: ssh problem

Mark Poeschl_2 — Tue, 06 Jun 2006 16:55:43 GMT

You might try starting the daemon by hand with something like:

# sshd2 -d 99 -v > myfile.out 2>&1

Re: ssh problem

Carlos A. Munoz Lopez — Wed, 07 Jun 2006 08:33:38 GMT

Actually I did, but I got the same results. I attach the debug output so you can take a look at it.

Re: ssh problem

Don Ritchey — Wed, 07 Jun 2006 08:53:05 GMT

Twoo suggestions:

1. Check your root and var file systems and make sure that these file systems are not full, since the shell may be trying to create a FIFO in either /tmp or /var/tmp. (Also check the CDSLs for the tmp directories in case these cross mount points.)

2. Move your current /etc/ssh2/sshd2_config file to a temp location and make a fresh copy of /etc/ssh2/sshd2_config.template to /etc/ssh2/sshd2_config. This will eliminate any errors caused by a bad option in the current config file or a garbage character that could gum up the works.

Re: ssh problem

Victor Semaska_3 — Wed, 07 Jun 2006 09:05:53 GMT

I would also suggest checking the permissions on /tmp & /var/tmp. They should be drwxrwxrwt

Vic

Re: ssh problem

Carlos A. Munoz Lopez — Wed, 07 Jun 2006 14:20:06 GMT

Still the same error. I already checked the permissions in tmp directories and they're fine. I have enough free space in both file systems as well. I was thinking in reinstalling ssh, but since it is a required package, will this action cause any implication on the operating system?? If not, what do I have to do to reinstall the package??

Re: ssh problem

Ann Majeske — Wed, 07 Jun 2006 15:46:32 GMT

After looking at the source code for sshd2 it looks like the problem from your sshd2 debug output happens when sshd2 tries to create an interprocess communication channel or "pipe" (see "man pipe(2)") prior to forking a child sshd2 process. (The pipe would then be used to communicate with the child process.) But, the pipe man page doesn't list ENOENT ("No such file or directory") as a possible error.

Ann Majeske, Tru64 UNIX support

Re: ssh problem

Ann Majeske — Wed, 07 Jun 2006 15:58:37 GMT

The only way I can think of to "reinstall" ssh would be to put on the latest patch kit, T64V51BB26AS0005-20050502, see: http://www1.itrc.hp.com/service/patch/mainPage.do and then follow it with T64KIT1000096-V51BB26-E-20051110 (an ERP with scp and sftp fixes) this would get you the latest ssh that has been released. I'm not sure that this would fix your problem, though, since the problem appears to be coming from pipe, not ssh. It's more likely that you've got some sort of a resource issue in creating pipes.

Ann

Re: ssh problem

Carlos A. Munoz Lopez — Wed, 07 Jun 2006 16:04:06 GMT

Ok, thanks. In the meantime I will try that out to see how it goes. I'll let you know if the last patch fixes the problem since I have the first one already installed in the system.

Re: ssh problem

Ann Majeske — Wed, 07 Jun 2006 17:28:02 GMT

In further research I found that System V pipes depend on the pipe device: /dev/streams/pipe. So if you have the System V environment enabled, maybe your problem is with this device.

Ann

Re: ssh problem

Brendan Murphy_5 — Tue, 13 Jun 2006 02:54:31 GMT

Do you have access to create the pipe in the first place??

Re: ssh problem

Carlos A. Munoz Lopez — Tue, 13 Jun 2006 08:30:24 GMT

Recently I solved the problem. The system was initially booted with generic kernel, so, in some way this was causing the problem. I decided to reboot the system with a normal kernel and it worked. Now, the system is accepting all ssh connections. Thanks all of you for your support.