From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: New cygwin install hanging on postinstall
Date: Fri, 22 Jan 2016 07:30:00 -0000 [thread overview]
Message-ID: <56A152F3.9040308@tiscali.co.uk> (raw)
In-Reply-To: <B8D164BED956C5439875951895CB4B2250BB08B3@CAFRFD1MSGUSRJH.ITServices.sbc.com>
On 21/01/16 21:17, KARR, DAVID wrote:
>> -----Original Message-----
>> From: cygwin-owner <at> cygwin.com [mailto:cygwin-owner <at> cygwin.com] On
>> Behalf Of Achim Gratz
>> Sent: Thursday, January 21, 2016 12:10 PM
>> To: cygwin <at> cygwin.com
>> Subject: Re: New cygwin install hanging on postinstall
>>
>> KARR, DAVID writes:
>>> While it's sitting here, I dumped out "/var/log/setup.log.full".
>> Here is the end of the file:
>>> ----------------
>>> The following DLLs couldn't be rebased because they were in use:
>>> /usr/bin/cygssp-0.dll
>>> /usr/bin/cygperl5_22.dll
>>> /usr/bin/cyggcc_s-1.dll
>>> /usr/bin/cygcrypt-0.dll
>>> /usr/lib/perl5/vendor_perl/5.22/i686-cygwin-threads-
>> 64int/auto/List/Util/Util.
>>> dll
>>> /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/IO/IO.dll
>>> /usr/lib/perl5/5.22/i686-cygwin-threads-
>> 64int/auto/File/Glob/Glob.dll
>>> /usr/lib/perl5/5.22/i686-cygwin-threads-
>> 64int/auto/Fcntl/Fcntl.dll
>>> /usr/lib/perl5/5.22/i686-cygwin-threads-
>> 64int/auto/Encode/Encode.dll
>>> /usr/lib/perl5/5.22/i686-cygwin-threads-
>> 64int/auto/Digest/MD5/MD5.dll
>>> /usr/lib/perl5/5.22/i686-cygwin-threads-64int/auto/Cwd/Cwd.dll
>>> 2016/01/21 09:15:40 running: C:\cygwin\bin\dash.exe
>> "/etc/postinstall/0p_texlive
>>> _prep.dash"
>>> 2016/01/21 09:19:20 note: Nothing needed to be installed
>>> 2016/01/21 09:19:20 Ending cygwin install
>>> -----------
>> So this isn't a fresh install and in fact there is not only some
>> Cygwin
>> process running but a full blown Perl that has loaded a number of
>> modules. How'd you manage to do that before Cygwin was ready
>> installing? Are you perhaps reporting from a follow-on invocation
>> of
>> setup.exe after the first install already failed?
> Beats the heck out of me. I didn't have Cygwin installed. I ran the installer. It hung at this point. I eventually cancelled it, because it obviously wasn't going to complete. This output is from one of the later retries. I never attempted to run anything installed in cygwin, I'm just trying to complete the installation.
If setup has been killed and attempted a second time, it could be that
one of the post-install scripts was left running.
>
>> For your current case, you need to get rid of _all_ running Cygwin
>> processes. Best idea is to open a shell and issue
>>
>> /usr/bin/rebase-trigger fullrebase
>> /usr/bin/pkill .
>>
>> (you need to have procps installed for this command to be
>> available).
>> Then run setup again to have it re-do the rebase and run all
>> postinstall
>> scripts that failed before. But I'm still interested how that
>> initial
>> failure could have occured, so if you could maybe look in
>> /var/log/setup.log if something indicates what happened there that
>> would
>> be good.
> More weirdness. I ran a mintty window, and I ran those command lines, but it gives me lots of lines like this:
> -------------
> 2 [main] bash 28452 child_info_fork::abort: C:\cygwin\bin\cygiconv-2.dll: Loaded to different address: parent(0x4D0000) != child(0x2E0000)
> bash: fork: retry: No child processes
> -------------
>
> I don't believe either of these command lines did anything, but just to be sure, after I ran them I killed the window an reran setup, and got the same symptoms.
How many Cygwin packages are you attempting to install? You mentioned
that you were installing on 32-bit Win 7, so you must be installing
32-bit Cygwin. The amount of address space is rather limited on 32-bit,
so installing a very large number of packages could give the symptoms
you're seeing.
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-01-21 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:34 KARR, DAVID
2016-01-21 5:42 ` Stephen John Smoogen
2016-01-21 19:09 ` KARR, DAVID
2016-01-21 21:29 ` Ken Brown
2016-01-21 21:51 ` Achim Gratz
2016-01-22 3:12 ` KARR, DAVID
2016-01-22 7:30 ` David Stacey [this message]
2016-01-22 17:32 ` Andrey Repin
2016-01-22 18:50 ` KARR, DAVID
2016-01-22 20:07 ` Mark Geisert
2016-01-22 20:14 ` Andrey Repin
2016-01-21 8:02 ` Ken Brown
2016-01-21 13:18 ` Achim Gratz
2016-01-21 21:17 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A152F3.9040308@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).