setup stuck on cygwin.ldif

Jon Turney jon.turney@dronecode.org.uk
Tue Oct 10 15:31:00 GMT 2017 

On 10/10/2017 08:21, Shaddy Baddah wrote:
> On 10/10/17 17:59, Shaddy Baddah wrote:
>> On 09/10/17 04:16, Brian Inglis wrote:
>>> On 2017-10-08 07:46, Shaddy Baddah wrote:
>>>> I have a weird problem happening... so I have tried to update a 64-bit
>>>> Cygwin installation on Windows 10 Pro. I closed all Cygwin processes,
>>>> and a ps -ef is showing only the ps process itself.
>>>> In anycase, during the install I was prompted that the file
>>>> /usr/share/cygwin/cygwin.ldif was busy.
>>>> I ran Process Explorer and searched for what might have the file open.
>>>> I couldn't find anything. I clicked retry a number of times, but it
>>>> wouldn't yield. Finally, I clicked continue. And now I'm stuck in this
>>>> endless loop on the file:
>>>> https://imgur.com/Nj35Y3T
>>>> It's a animated gif, so you may have to select play in your browser. 
>>>> Not
>>>> much to see, except the constant attempt to install the cygwin.ldif
>>>> file.
>>>> Any ideas here? I guess I'll have to kill setup... but I fear that it
>>>> will play havoc with my install :-(
>>>
>>> Have you tried Windows cmd OPENFILES /Query ?
>>>
>>
>> So I tried to "Reinstall" all, and now the problem has shifted. Every
>> attempt to reinstall stops with "Unable to extract
>> /etc/defaults/etc/pki/ca-trust/ca-legacy.conf". "The file is in use or
>> some other error occurred.".
>>
>> Retry doesn't help. openfiles doesn't reveal anything:
>>
>> https://imgur.com/a/XV1YQ
>>
>> Having enhanced setup.exe at one point, and accordingly debugged it,
>> I'll try and see if I can turn up the logging, see what is going on
>> exactly. I actually don't know where setup.log/setup.log.full is going
>> to at the moment.
> 
> OK, I understand the logging only gets written when setup exits. So here
> is what I am seeing:

This is to allow for the fact that we don't know where /var/log/ is 
going to be when setup starts.  But yeah, waiting until it exits to 
write the log is a bit of a misfeature.

> Installing file cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf
> 2017/10/10 18:09:58 io_stream_cygfile: 
> fopen(/etc/defaults/etc/pki/ca-trust/ca-legacy.conf) failed 13 
> Permission denied
> 2017/10/10 18:09:58 Failed to open 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf for writing.
> 
> There is nothing in the target folder. icacls of ca-trust shows:
> 
> portapps@AVANT-W10 F:\portapps-sw\cygwin\etc\defaults\etc\pki
>  > icacls ca-trust
> ca-trust AVANT-W10\portapps:(F)
>           AVANT-W10\None:(RX)
>           Everyone:(RX)
>           CREATOR OWNER:(OI)(CI)(IO)(F)
>           CREATOR GROUP:(OI)(CI)(IO)(RX)
>           Everyone:(OI)(CI)(IO)(RX)
> 
> Successfully processed 1 files; Failed processing 0 files
> 
> A retry, just repeats of course:
> 
> 2017/10/10 18:13:08 io_stream_cygfile: 
> fopen(/etc/defaults/etc/pki/ca-trust/ca-legacy.conf) failed 13 
> Permission denied
> 2017/10/10 18:13:08 Failed to open 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf for writing.
> 
> Then if you click continue, you get an endless loop that takes up
> all your CPU:

Fascinating.

I did a bit of staring at [1], and this log looks like we not advancing 
to the next archive member before next_file_name(), because not only 
does extract_file() fail, but also extract_replace_on_reboot() (creating 
the .new file to be renamed on reboot) is failing.

It looks like we've never handled extract_replace_on_reboot() failing 
correctly, since we don't advance to the next archive member in that case.

I'm assuming there's something unusual about permissions which is why 
the .new file can't be created, or perhaps this problem would be more 
common?

You might be able to work around this using the --no-replaceonreboot 
option, but it looks like that will always suffer from the same problem.

[1] 
https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=blob;f=install.cc;h=f8f0b59d2d2163798c1e222b913b2a8ee0c009d9;hb=HEAD#l474

> 2017/10/10 18:13:11 io_stream_cygfile: 
> fopen(/etc/defaults/etc/pki/ca-trust/ca-legacy.conf.new) failed 13 
> Permission denied
> 2017/10/10 18:13:11 Failed to open 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf.new for writing.
> 2017/10/10 18:13:11 Unable to install file 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf.new
> Installing file cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf
> 2017/10/10 18:13:11 io_stream_cygfile: 
> fopen(/etc/defaults/etc/pki/ca-trust/ca-legacy.conf) failed 13 
> Permission denied
> 2017/10/10 18:13:11 Failed to open 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf for writing.
> 2017/10/10 18:13:11 io_stream_cygfile: 
> fopen(/etc/defaults/etc/pki/ca-trust/ca-legacy.conf.new) failed 13 
> Permission denied
> 2017/10/10 18:13:11 Failed to open 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf.new for writing.
> 2017/10/10 18:13:11 Unable to install file 
> cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf.new
> Installing file cygfile:///etc/defaults/etc/pki/ca-trust/ca-legacy.conf

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

More information about the Cygwin mailing list