Displaying 20 results from an estimated 2000 matches similar to: "Solved: on Solaris, "couldn't wait for child '...' completion: No child processes""
2000 May 16
1
on Solaris, "couldn't wait for child '...' completion: No child processes"
Trying to install the portable OpenSSH on Solaris 2.6. Compiling from
openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd
starts fine. First connection from another system works. Child sshd is
forked, but the parent dies and logs:
May 16 11:40:56 qtrade-dev sshd[6510]: error: Couldn't wait for child '/usr/bin/
ls -alni' completion: No child processes
May 16 11:40:56
2000 May 12
1
Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and other systems , too
Hi !
Karsten Thygesen wrote:
>>>>> "carl" == carl <carl at bl.echidna.id.au> writes:
> carl> Marc, I'm seeing the same problem if I use the inbuilt entropy
> carl> generator, but if I use SUNWski's /dev/random, it's fine.
> carl> ssh also coredumps if I use the built in entropy generator if I
> carl> run it in verbose mode.
2001 Jan 09
3
OpenSSH on Reliant UNIX
Hello, it's me again !
I tried to compile / install OpenSSH on our Reliant UNIX
system, OS version 5.45 (and 5.44).
The following problems did appear:
1. OpenSSL-0.9.5a will not compile out of the box.
The problem on RU 5.45 is, that the compiler does
support "long long" but NOT "unsigned long long".
The latter just provokes the error message
"superfluous
2001 Mar 20
3
Rhosts-RSA authentication broken
Hello !
I think a problem was introduced in openssh-2.3.0p1 which is
still there in the latest openssh-2.5.2p1. I just noticed it
before my vacation and could not send this mail earlier than
today.
The problem is:
You can't use the Rhosts-RSA authentication based on the hosts.equiv
file and the host keys.
The only possible way to do rhosts-RSA authentication is to allow
the usage of the
2000 May 19
0
AW: Solved: on Solaris, "couldn't wait for child '...' completion : Nochild processes"
> Andre Lucas [SMTP:andre.lucas at dial.pipex.com] wrote:
>
> No! The error message is because I used 'error()' instead of 'debug()'.
> That's changed in the 2.1.0p1 release, I believe. (I don't have access
> to it right now.) This was discussed last week for 2.1.0 - just change
> error() to debug() for those two messages.
Sorry, you are completely right.
2001 Jan 08
1
X11-Forwarding for Reliant UNIX (formerly SINIX)
Hi !
To all: A Happy New Year !
During the last week I did some investigations why the X11 forwarding
on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box
with OpenSSH-2.3.0p1.
The result fo my investigation is:
1. The OpenSSH sshd opens a TCP/IP-port 6000 + display number
and listens to it. This is fine and works with Solaris 7,
DEC-OSF 4.0D, Linux and FreeBSD-4.2 but not
2001 Jan 08
0
AW: X11-Forwarding for Reliant UNIX (formerly SINIX)
Damien Miller [SMTP:djm at mindrot.org] wrote:
> On Mon, 8 Jan 2001, Bladt Norbert wrote:
[...]
>> The result fo my investigation is:
>> 3. All standard X-applications try to determine whether
>> they are running locally, i.e. if the DISPLAY on
>> computer HOSTX is HOSTX:10.0 the X-applications detect
>> that this is the local computer and try to open the
2001 Jan 09
0
Result: X11-Forwarding for Reliant UNIX (formerly SINIX)
Hi !
I promised to report the result to the list.
Here it is:
Damien Miller [SMTP:djm at mindrot.org] wrote yesterday on his keyboard:
> On Mon, 8 Jan 2001, Bladt Norbert wrote:
[...]
>> During the last week I did some investigations why the X11 forwarding
>> on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box
>> with OpenSSH-2.3.0p1.
>>
>> The
2001 Jan 09
0
AW: fatal: PRNG initialisation failed
Joe Warren-Meeks [SMTP:joe at hole-in-the.net] wrote:
> open("/usr/local/etc/ssh_prng_cmds", O_RDONLY) = 3
open of the command file succeeded.
> brk(0x000E6DB8) = 0
"malloc" in user land, i.e. sshd
> brk(0x000E8DB8) = 0
"malloc" in user land, i.e. sshd
> fstat64(3, 0xFFBEECD8)
2001 Jan 09
0
Difference 2.1.1 and 2.3.0p1 on Reliant UNIX
Hi !
I upgraded one of our Reliant UNIX systems from 2.1.1 to 2.3.0p1.
Now, I suddenly can't login any more.
The error message is:
Attempting authentication for illegal user ...
The reason is:
Password expiration
Although I don't use my password to login, at all.
I login via RSAAuthentication and this did work with version 2.1.1.
Version 2.3.0p1, obviously, checks the password
2000 Jul 04
0
AW: rhostsauthentication fails. (Or why I hate poorly documented software.)
> jeff at ntcor.com [SMTP:jeff at ntcor.com] wrote:
>
> I have a ssh enabled server and client machine (we'll call them "server"
> and "client" respectively...)
OK :-)
> They both have proper RSA and DSA keys,using protocol version 2 works
> fine between them. (so ssh itself and the network is working fine)
OK.
> However, I want to get something that
2000 May 17
4
Openssh-2.1.0p1 test release
This to announce a test release of 2.1.0p1 before making it widely
available.
This release includes many fixes to problems reported over the last
week. In particular:
- spurious error and coredumps caused by the inbuilt entropy gathering
- RSAref detection
- Compilation fixes for Solaris and others
It also contains (completely untested) support for compiling without
RSA support. This may be
2002 Nov 14
3
[Bug 435] internal entropy gatherer
http://bugzilla.mindrot.org/show_bug.cgi?id=435
dtucker at zip.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|internal entropy gatherer |internal entropy gatherer
------- Additional Comments From dtucker at zip.com.au 2002-11-15 00:21 -------
Which platform did you
2001 Feb 19
7
Packet integrity error. (34)
Hi,
I am using Van Dyke SecureCRT 3.2.1 to access an AIX server running
OpenSSH-2.5.0p1. Using ssh1 with X11 forwarding enabled, the server
reports the following error (in the client session):
Packet integrity error. (34)
This problem was not evident in 2.3.0p1. Running sshd in debug gives the
output:
debug1: sshd version OpenSSH_2.5.1p1
debug1: load_private_key_autodetect: type 0 RSA1
2002 Jul 22
1
Antwort: Re: Problem with SSHD-Daemon (OpenSSH)
Hi Ben,
here is the output from sshd -d -d -d:
mvs2:sygm:/usr/local/sbin:#./sshd -d -d -d
debug3: Reading output from 'ls -alni /var/log'
debug3: Time elapsed: 459 msec
debug2: Command 'ls -alni /var/log' timed out
debug3: Got 0.00 bytes of entropy from 'ls -alni /var/log'
debug3: Reading output from 'ls -alni /var/adm'
debug3: Time elapsed: 143 msec
debug2:
2000 May 11
1
OpenSSH 2.1.0 under Solaris 8 ...
Compiled great, got both my RSA and DSA keys' generated for Protocol 1/2,
started up fine ... try to connect and get a bunch of errors:
May 11 14:01:47 iris sshd[8578]: error: Couldn't wait for child '/bin/ls -alni' completion: No child processes
May 11 14:01:47 iris last message repeated 3 times
May 11 14:01:47 iris sshd[8578]: error: Command '/bin/ls -alni': select()
2000 May 10
3
Trying to build OpenSSH-2.1.0 on HP-UX 10.20
Hi,
I just tried building of OpenSSH-2.1.0 on HP-UX 10.20 and found the following
items:
- The configure command I used at the beginning:
CC=cc CFLAGS="-Ae +O2 +DAportable" CPPFLAGS="-I/usr/local/include -I/usr/local/s
sl/include -I/usr/include/X11R6" LDFLAGS="-L/usr/local/lib -L/usr/local/ssl/lib
-L/usr/lib/X11R6" ./configure --prefix=/usr/local/openssh
2000 Jul 20
3
fatal: Not enough entropy in RNG
Hi,
I'm running openssh 2.1.1p4 on Solaris 7 (sparc). Occationally, when I
boot up the server, the startup script I wrote to start sshd fails to start
sshd with the following error:
fatal: Not enough entropy in RNG
What am I doing wrong??
Is there anything I can do to prevent this from happening?
Is just restarting sshd a valid thing to do??
Thanks for any thoughts,
David
2002 May 07
3
openssh 3.1 and rsync dont work
Maybe this is a ssh problem - but are you aware of the general issue ?
http://bugzilla.mindrot.org/show_bug.cgi?id=182
Summary: ssh should still force SIGCHLD to be SIG_DFL when
calling ssh-rand-helper
Product: Portable OpenSSH
Version: 3.1p1
Platform: ix86
OS/Version: All
Status: NEW
Severity: normal
2001 Feb 05
1
I have an odd OpenSSH compatablity issue
I am on Solaris 2.8 with openssh 2.3.0p1 and openssl 0.9.6.
The remote machine is running ssh.com 1.2.20 and Solaris 2.6.
I think the problem has to do with the 1.2.20 KeyRegeneration, because in
the next hour I will beable to get into the machine ok with openssh and
then later in the day I will not beable to ssh in again for another hour.
ssh -v -v sa at myhost.com
SSH Version OpenSSH_2.3.0p1,