Mail Archives: cygwin/2008/03/14/15:45:54
I noticed that if I try to run setup to add more packages, the problem
reoccurs. Again, the setup process hangs during post-install, but when I kill
it and run the scripts by hand from the (now fully functional) bash console,
they all complete without any problems.
Krzys
-----Original Message-----
From: Krzysztof Ostrowski
Sent: Friday, March 14, 2008 2:40 PM
To: cygwin AT sourceware DOT org; 'jbalonso AT gmail DOT com'; 'Popper, Samuel (US SSA)'
Subject: RE: Cygwin doesn't install on Windows Server 2008 (x64).
Hi,
Path wasn't an issue because I did specify full paths, but when I manually
copied bash.exe onto sh.exe, and terminated the instance of bash.exe that was
trying to run 00ash.sh, the setup did eventually complete. It simply timed
out on the remaining scripts (it didn't previously want to time out on
00ash.sh). After the setup completed I was finally able to launch a working
shell that wouldn't spawn nested chains of child processes, it did work
(except I had no environment setup, of course). In that shell, I could run
each of the failed post-install scripts one by one and now it seems to be
fully functional. I'm not sure why the shell wouldn't be functional at the
time when it runs the setup. Perhaps there's a race condition that makes
something run out of order before the shell is actually fully up and running?
Somehow, letting the setup just timeout on everything apparently "fixes
it"...
Krzys
-----Original Message-----
From: Popper, Samuel (US SSA) [mailto:samuel DOT popper AT baesystems DOT com]
Sent: Friday, March 14, 2008 1:26 PM
To: cygwin AT sourceware DOT org
Cc: Krzysztof Ostrowski
Subject: RE: Cygwin doesn't install on Windows Server 2008 (x64).
Your PATH does not yet have any part of cygwin in it, so I just added
it:
export PATH=$PATH:/bin:/usr/bin
Try adding it to your path and see if you get better results.
But the behavior I saw was different- when the shell couldn't find a
command, it gave an error message but did not spawn a new process.
-Sam
-----Original Message-----
From: Krzysztof Ostrowski [mailto:krzys AT cs DOT cornell DOT edu]
Sent: Friday, March 14, 2008 1:10 PM
To: Popper, Samuel (US SSA); cygwin AT sourceware DOT org
Subject: RE: Cygwin doesn't install on Windows Server 2008 (x64).
Hi,
How did you manage to run something in another shell? When I start a
second
shell, I end up with an instance of bash.exe or ash.exe that doesn't
appear
to respond to any commands except "pwd". Even "ls" doesn't work, it
returns
no output. Instead, the commands I type into "bash.exe" and "ash.exe"
cause
child processes to be spawned. I end up with a list of nested child
processes
that don't consume any CPU and remain blocked forever. The main shell I
launch is responsive, it just completes each command without output and
spawns new child processes instead.
Does that sound familiar? Is there a way to get at a working bash shell
before the post-install scripts complete?
Krzys
-----Original Message-----
From: Popper, Samuel (US SSA) [mailto:samuel DOT popper AT baesystems DOT com]
Sent: Friday, March 14, 2008 12:35 PM
To: cygwin AT sourceware DOT org
Cc: Krzysztof Ostrowski
Subject: RE: Cygwin doesn't install on Windows Server 2008 (x64).
Hey, this sounds like my issue, except that I'm installing on Window
Server 2003. I've completed setup by running the "hanging" shell
scripts from another bash shell and then killing that process (which
allows setup.exe to continue). Does 00ash.sh work if you run it from
another shell?
I'm also at a loss of what to investigate next. I've looked into
running bash shells from an alternate batch file that monitors with
strace and the -x flag to bash, and I see that when the shell hangs, it
occurs at random points while sourcing the profile. When it happens,
there is always some other process (e.g. subshell, id, grep, tr, sed,
date) that exists but doesn't exit. When that happens, I can see it via
ps(1) but not kill it via kill(1) - only through windows tools. Upon
terminating the process that way, the original script continues.
I can generate an strace or process monitor log for when that happens if
it interests anyone. Since they get large, let me know how to send it.
-Sam
-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Krzysztof Ostrowski
Sent: Thursday, March 13, 2008 4:57 PM
To: corinna-cygwin AT cygwin DOT com; cygwin AT sourceware DOT org
Subject: RE: Cygwin doesn't install on Windows Server 2008 (x64).
Hi,
I'm positive about that, I just retried that on a clean machine. I'd be
happy
to send you logs or other debug info if you just tell me what you would
need.
I've looked at the log in C:\cygwin\var, but the file size is 0, the
setup is
probably not flushing the stuff it writes to the file.
The version is -11, I've double-checked it again during the setup.
The issue may not be the same as the one fixed in 1.5.25-11 because I
don't
actually get 100% CPU usage. While running "00ash.sh", bash.exe simply
pauses
forever, without apparently using any CPU.
I've monitored system calls in Process Monitor. While going over
"00bash.sh",
which does eventually complete (after a long time), I can see bash.exe
making
system calls. While going over "00ash.sh", I don't see anything, it
hangs.
I'm running an RTM version of Windows Server 2008, downloaded from MSDN,
on a
fairly new ThinkPad T61p. The systems is otherwise very stable, I didn't
have
problems with 32-bit apps running over WoW so far.
Krzys
> I can't reproduce this problem with 1.5.25-11. It would have been an
> expected problem with 1.5.25-7 (though not on the x64 version), but
when
> you install -11, this is supposed to work fine on 2008 Server. And it
> does for me, I just tried a fresh base install on a vanilla 2008
> Standard Server Edition.
>
> There must be something else broken on your machine. Are you sure
that
> you installed 1.5.25-11 and not another version accidentally? Or,
maybe
> the -7 version was installed already and a Cygwin process was still
> running or something like that?
>
> Corinna
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -