RE: upgrades hang forever on 0p_000_autorebase.dash

RE: upgrades hang forever on 0p_000_autorebase.dash

[Maarten Jacobs]

Hello,

This may not be relevant - but I ran into a very similar issue tonight... Setup appeared to "hang" - until I found out that Eclipse was "helpful" and pointing out to me that something had changed in the environment... And it was patiently waiting for my input.

The only problem was that the window was hidden under a stack of other windows.

When you run setup, are you sure there's not some window popped up somewhere - but not to the foreground?

Thanks,

Maarten Jacobs

----------------------------------------
> To: cygwin@cygwin.com
> From: patrick@spacesurfer.com
> Subject: Re: upgrades hang forever on 0p_000_autorebase.dash
> Date: Sun, 31 Jan 2016 22:45:14 +0000
>
> Hello,
>
> It seems that the cygwin setup works fine on one of the machines I tried
> (windows 8.1). However on the other machine I have these issues (even on
> a fresh install). The other machine is a work machine (windows 7). I do
> not have access to the admin user, I run the install from my account.
> However, the machine has some software (possibly avecto) that lets me
> run it with what it calls admin privileges. Whenever I run setup it
> blocks on the 0p_000_autorebase.dash script and I have to kill the dash
> process for setup to finish. Is there any way for me to see the
> stdout/stderr of the script that setup is running?
>
> regards,
> Patrick
>
>> Patrick Mackinlay <patrick <at> spacesurfer.com> writes:
>>> It requires user input because the file
>>> /var/cache/rebase/rebase_dyn
>>> is created read only the first time and then the second time a rm
>>> requires user confirmation.
>>
>> When run from setup then rm should not prompt (and it doesn't for my
>> installations), at least not if the permissions on the directory are>
> correct
>> and you always run it under the same UID. I could add a "-f", but...
>>
>> You seem to have some borked ACL on your Cygwin installation (i.e. a>
> fresh
>> installation shouldn't have these) or something's wrong with the UID
>> settings (maybe mopve /etc/passwd and /etc/group files). Do you run
>> setup.exe as administrator? Is this a system-wide or user installation?
>>
>> Also the latest snapshot changes the handling of the Administrator and
>> SYSTEM accounts to resolve some issues with intended vs. effective group
>> rights and ACL mask computation.
>
>
>> Regard,
>> Achim.
>
> --
> Patrick Mackinlay patrick@spacesurfer.com
> http://patrick.spacesurfer.com/ tel: +44.7050699851
> Yahoo messenger: patrick00_uk fax: +44.7050699852
> SpaceReg Limited http://www.spacereg.com/
>
 		 	   		  
--
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: upgrades hang forever on 0p_000_autorebase.dash

[Patrick Mackinlay]

[-- Attachment #1: Type: text/plain, Size: 3708 bytes --]

Hi,

I think that is very unlikely, I tried running setup many times and at
least once I rebooted and just ran setup, that time I left the laptop
running all night to see if the 0p_000_autorebase.dash would ever finish
(it didn't!). I think I would have noticed if there were any background
windows then, assuming that they would have at least appeared in the
task bar. I think it it is much more likely to be related to
permissions. When setup is running scripts what happens to stdin, is it
closed, is /dev/null redirected to it or is it just left open? Is there
any way for me to see the stdout/stderr of the script that setup is running?

Patrick

On 01/02/2016 05:32, Maarten Jacobs wrote:
> Hello,
> 
> This may not be relevant - but I ran into a very similar issue tonight... Setup appeared to "hang" - until I found out that Eclipse was "helpful" and pointing out to me that something had changed in the environment... And it was patiently waiting for my input.
> 
> The only problem was that the window was hidden under a stack of other windows.
> 
> When you run setup, are you sure there's not some window popped up somewhere - but not to the foreground?
> 
> Thanks,
> 
> Maarten Jacobs
> 
> ----------------------------------------
>> To: cygwin@cygwin.com
>> From: patrick@spacesurfer.com
>> Subject: Re: upgrades hang forever on 0p_000_autorebase.dash
>> Date: Sun, 31 Jan 2016 22:45:14 +0000
>>
>> Hello,
>>
>> It seems that the cygwin setup works fine on one of the machines I tried
>> (windows 8.1). However on the other machine I have these issues (even on
>> a fresh install). The other machine is a work machine (windows 7). I do
>> not have access to the admin user, I run the install from my account.
>> However, the machine has some software (possibly avecto) that lets me
>> run it with what it calls admin privileges. Whenever I run setup it
>> blocks on the 0p_000_autorebase.dash script and I have to kill the dash
>> process for setup to finish. Is there any way for me to see the
>> stdout/stderr of the script that setup is running?
>>
>> regards,
>> Patrick
>>
>>> Patrick Mackinlay <patrick <at> spacesurfer.com> writes:
>>>> It requires user input because the file
>>>> /var/cache/rebase/rebase_dyn
>>>> is created read only the first time and then the second time a rm
>>>> requires user confirmation.
>>>
>>> When run from setup then rm should not prompt (and it doesn't for my
>>> installations), at least not if the permissions on the directory are>
>> correct
>>> and you always run it under the same UID. I could add a "-f", but...
>>>
>>> You seem to have some borked ACL on your Cygwin installation (i.e. a>
>> fresh
>>> installation shouldn't have these) or something's wrong with the UID
>>> settings (maybe mopve /etc/passwd and /etc/group files). Do you run
>>> setup.exe as administrator? Is this a system-wide or user installation?
>>>
>>> Also the latest snapshot changes the handling of the Administrator and
>>> SYSTEM accounts to resolve some issues with intended vs. effective group
>>> rights and ACL mask computation.
>>
>>
>>> Regard,
>>> Achim.
>>
>> --
>> Patrick Mackinlay patrick@spacesurfer.com
>> http://patrick.spacesurfer.com/ tel: +44.7050699851
>> Yahoo messenger: patrick00_uk fax: +44.7050699852
>> SpaceReg Limited http://www.spacereg.com/
>>
>  		 	   		  
> 

-- 
Patrick Mackinlay                              patrick@spacesurfer.com
http://patrick.spacesurfer.com/                    tel: +44.7050699851
Yahoo messenger: patrick00_uk                      fax: +44.7050699852
SpaceReg Limited                              http://www.spacereg.com/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

Re: upgrades hang forever on 0p_000_autorebase.dash

[Achim Gratz]

Patrick Mackinlay writes:
> Is there
> any way for me to see the stdout/stderr of the script that setup is running?

The most recent run of setup logs into /var/log/setup.log.full.

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: upgrades hang forever on 0p_000_autorebase.dash

[Achim Gratz]

Patrick Mackinlay <patrick <at> spacesurfer.com> writes:
> It requires user input because the file
> /var/cache/rebase/rebase_dyn
> is created read only the first time and then the second time a rm
> requires user confirmation.

When run from setup then rm should not prompt (and it doesn't for my
installations), at least not if the permissions on the directory are correct
and you always run it under the same UID.  I could add a "-f", but...

You seem to have some borked ACL on your Cygwin installation (i.e. a fresh
installation shouldn't have these) or something's wrong with the UID
settings (maybe mopve /etc/passwd and /etc/group files).  Do you run
setup.exe as administrator?  Is this a system-wide or user installation?

Also the latest snapshot changes the handling of the Administrator and
SYSTEM accounts to resolve some issues with intended vs. effective group
rights and ACL mask computation.


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

upgrades hang forever on 0p_000_autorebase.dash

[Patrick Mackinlay]

[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]

Hello,

I tried upgrading some old cygwin installs on a couple of computers
today. I downloaded the very latest setup (32 bit) and ran them. On one
machine I ran the upgrade twice, on this machine the process hanged
forever on 0p_000_autorebase.dash

Running 0p_000_autorebase.dash manually from dash I found that the very
first time you run it it works fine, but any subsequent times in
requires user input (and hence would hang forever in a non interactive
terminal).

It requires user input because the file
/var/cache/rebase/rebase_dyn
is created read only the first time and then the second time a rm
requires user confirmation.

Here is the full terminal output:

$ 0p_000_autorebase.dash
Updating package information in /var/cache/rebase/rebase_pkg.
Updating rebase information for installed dynamic objects in
/var/cache/rebase/rebase_lst.
/bin/rebaselst: 211: /bin/rebaselst: cannot create
/var/cache/rebase/rebase_lst: Permission denied
Updating rebase information for installed executables in
/var/cache/rebase/rebase_exe.
/bin/rebaselst: 197: /bin/rebaselst: cannot create
/var/cache/rebase/rebase_exe: Permission denied
removing /var/cache/rebase/rebase_dyn
rm: remove write-protected regular file '/var/cache/rebase/rebase_dyn'?

As you can see a number of files are created read only and cause a
number of failures.

regards,
Patrick

-- 
Patrick Mackinlay                              patrick@spacesurfer.com
http://patrick.spacesurfer.com/                    tel: +44.7050699851
Yahoo messenger: patrick00_uk                      fax: +44.7050699852
SpaceReg Limited                              http://www.spacereg.com/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]