New cygwin install hanging on postinstall

New cygwin install hanging on postinstall

[KARR, DAVID]

I was installing cygwin for the first time on a Win7-32bit box.  It is hanging in postinstall, with "0/Perpetual" and "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now, and it hangs effectively forever on this step (waited 15-20 minutes each time).  What other information could I provide?  I looked at the end of the setup.log file, but that just indicates that installation was complete.

--
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

Re: New cygwin install hanging on postinstall

[Stephen John Smoogen]

On 20 January 2016 at 17:06, KARR, DAVID <dk068x@att.com> wrote:
> I was installing cygwin for the first time on a Win7-32bit box.  It is hanging in postinstall, with "0/Perpetual" and "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now, and it hangs effectively forever on this step (waited 15-20 minutes each time).  What other information could I provide?  I looked at the end of the setup.log file, but that just indicates that installation was complete.
>

How much memory does this system have? I know that TexLive is a real
memory hog these days in certain parts.. Does removing TexLive from
your install list go past this?

> --
> 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
>



-- 
Stephen J Smoogen.

--
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

Re: New cygwin install hanging on postinstall

[Ken Brown]

On 1/20/2016 7:06 PM, KARR, DAVID wrote:
> I was installing cygwin for the first time on a Win7-32bit box.  It is hanging in postinstall, with "0/Perpetual" and "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now, and it hangs effectively forever on this step (waited 15-20 minutes each time).  What other information could I provide?  I looked at the end of the setup.log file, but that just indicates that installation was complete.

Check setup.log.full.  If that doesn't help, try running the script 
manually to see what happens (most likely a fork failure requiring a 
full rebase).

Ken

--
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

Re: New cygwin install hanging on postinstall

[Achim Gratz]

Ken Brown <kbrown <at> cornell.edu> writes:
> Check setup.log.full.  If that doesn't help, try running the script 
> manually to see what happens (most likely a fork failure requiring a 
> full rebase).

Well, if it's really a fresh install, the full rebase just has happened, so
if there's still a fork problem it has to be BLODA.

To the OP: if you're using any third-party anti-virus solution, please try
if exempting the Cygwin install directory from the real-time and/or
heuristic scans helps.  In some cases you can re-enable those functions
after a manual full scan, but you would likely run into the same problem
again when the Cygwin packages get updated.


Regards,
Achim.


--
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

RE: New cygwin install hanging on postinstall

[KARR, DAVID]

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of Stephen John Smoogen
> Sent: Wednesday, January 20, 2016 4:19 PM
> To: cygwin@cygwin.com
> Subject: Re: New cygwin install hanging on postinstall
> 
> On 20 January 2016 at 17:06, KARR, DAVID <dk068x@att.com> wrote:
> > I was installing cygwin for the first time on a Win7-32bit box.
> It is hanging in postinstall, with "0/Perpetual" and
> "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now,
> and it hangs effectively forever on this step (waited 15-20 minutes
> each time).  What other information could I provide?  I looked at
> the end of the setup.log file, but that just indicates that
> installation was complete.
> >
> 
> How much memory does this system have? I know that TexLive is a
> real
> memory hog these days in certain parts.. Does removing TexLive from
> your install list go past this?

It has 4g RAM.  Checking "Resource Monitor" while the install is running, there is 750MB "available".

I tried searching for "texlive" and setting all of those to "uninstall".  The "postintall" step spends quite a while on "0p_000_autorebase.dash", but I noticed that before.  However, after that finishes, it then sits on "0p_texlive_prep.dash".

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
-----------

Note that the current time is currently 9:37AM.  The log file hasn't updated in almost 20 minutes.

I would run the script manually, but I don't know what to run.

I tried to exclude c:\cygwin from the virus scanner, but it seems doubtful that the installer would go through all the other steps if this was really an issue.

Re: New cygwin install hanging on postinstall

[Ken Brown]

On 1/21/2016 3:02 AM, Achim Gratz wrote:
> Ken Brown <kbrown <at> cornell.edu> writes:
>> Check setup.log.full.  If that doesn't help, try running the script
>> manually to see what happens (most likely a fork failure requiring a
>> full rebase).
>
> Well, if it's really a fresh install, the full rebase just has happened

His followup message shows that it wasn't a fresh install and that a 
full rebase didn't happen.

Ken


--
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

Re: New cygwin install hanging on postinstall

[Ken Brown]

On 1/21/2016 12:40 PM, KARR, DAVID wrote:
>> -----Original Message-----
>> On 20 January 2016 at 17:06, KARR, DAVID <dk068x@att.com> wrote:
>>> I was installing cygwin for the first time on a Win7-32bit box.
>> It is hanging in postinstall, with "0/Perpetual" and
>> "/etc/postinstall/0p_texlive_prep.dash.  I've tried this twice now,
>> and it hangs effectively forever on this step (waited 15-20 minutes
>> each time).  What other information could I provide?  I looked at
>> the end of the setup.log file, but that just indicates that
>> installation was complete.

> 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

There's your problem.  There were Cygwin processes running when you did 
the most recent install, so the _autorebase script couldn't do its job.

You need to do a full rebase before trying again.  See the instructions in

   https://www.cygwin.com/ml/cygwin/2016-01/msg00216.html

Ken


--
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

Re: New cygwin install hanging on postinstall

[Achim Gratz]

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?

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.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

--
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

RE: New cygwin install hanging on postinstall

[KARR, DAVID]

> -----Original Message-----
> From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
> Behalf Of Achim Gratz
> Sent: Thursday, January 21, 2016 12:10 PM
> To: cygwin@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.

> 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.


--
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

Re: New cygwin install hanging on postinstall

[David Stacey]

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

Re: New cygwin install hanging on postinstall

[Andrey Repin]

Greetings, KARR, DAVID!

>> > I was installing cygwin for the first time on a Win7-32bit box.

> It has 4g RAM.  Checking "Resource Monitor" while the install is running, there is 750MB "available".

How much memory is "available" is not an indication for a 32-bit OS. You
simply can not allocate more than 2GB of RAM to a single process without much
hackery. Which means, certain applications could hit a roadblock just because
of that. Same applies to your 4GB statement: You just can not use it all with
32-bit OS without much hackery on OS level, and that means slowing down entire
system.

You are really, really want 64-bit OS with more than 2GB RAM to see any light
at the end of the tunnel.

On top of that, if you are still struggling with installation, and hints
offered in other messages did not helped to date, the most simple way would be
to eliminate the failed Cygwin install and start anew, this time only install
a base (setup default) set of tools first time, may be accompanying them by
choice things of convenience, like wget and/or procps. But nothing overgrown
like TexLive.


-- 
With best regards,
Andrey Repin
Friday, January 22, 2016 10:27:27

Sorry for my terrible english...


--
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

RE: New cygwin install hanging on postinstall

[KARR, DAVID]

> -----Original Message-----
> From: Andrey Repin [mailto:anrdaemon@yandex.ru]
> Sent: Thursday, January 21, 2016 11:35 PM
> To: KARR, DAVID; cygwin@cygwin.com
> Subject: Re: New cygwin install hanging on postinstall
> 
> Greetings, KARR, DAVID!
> 
> >> > I was installing cygwin for the first time on a Win7-32bit
> box.
> 
> > It has 4g RAM.  Checking "Resource Monitor" while the install is
> running, there is 750MB "available".
> 
> How much memory is "available" is not an indication for a 32-bit
> OS. You
> simply can not allocate more than 2GB of RAM to a single process
> without much
> hackery. Which means, certain applications could hit a roadblock
> just because
> of that. Same applies to your 4GB statement: You just can not use
> it all with
> 32-bit OS without much hackery on OS level, and that means slowing
> down entire
> system.
> 
> You are really, really want 64-bit OS with more than 2GB RAM to see
> any light
> at the end of the tunnel.
> 
> On top of that, if you are still struggling with installation, and
> hints
> offered in other messages did not helped to date, the most simple
> way would be
> to eliminate the failed Cygwin install and start anew, this time
> only install
> a base (setup default) set of tools first time, may be accompanying
> them by
> choice things of convenience, like wget and/or procps. But nothing
> overgrown
> like TexLive.

Ok.  I understand the basic procedure for uninstalling Cygwin, but what's the best way to reset the installer to the "base" install?


--
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

Re: New cygwin install hanging on postinstall

[Mark Geisert]

KARR, DAVID writes:
> Ok.  I understand the basic procedure for uninstalling Cygwin, but 
what's the best way to reset the
> installer to the "base" install?

Doing a base install just means running setup (the appropriate setup*.exe 
for your platform) and clicking Next all the way through, taking all of 
setup's defaults.  Only change a setting if you *know* it needs to be 
changed, which for most folks is just needing to choose a mirror :).

..mark


--
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

Re: New cygwin install hanging on postinstall

[Andrey Repin]

Greetings, KARR, DAVID!

> Ok.  I understand the basic procedure for uninstalling Cygwin, but what's
> the best way to reset the installer to the "base" install?

No need to "uninstall". Just nuke it from the orbit.
Since this is a new installation, you are (presumable) have nothing to lose.

P.S.
Please adjust your mailer template to not include raw email addresses in
message quotes.
Thank you in advance.


-- 
With best regards,
Andrey Repin
Friday, January 22, 2016 21:37:41

Sorry for my terrible english...


--
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