X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.2 required=5.0 tests=BAYES_00,TBC,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message Subject: RE: (nwl) Re: Installation problems - post install scripts all give "abnormal exit: exit code=128" Date: Thu, 29 Apr 2010 23:52:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <3F87AA6367687C43A854B8E7073CDF8C04ED73@es-108a.paxriver.progeny.net> References: <3F87AA6367687C43A854B8E7073CDF8C04ED71 AT es-108a DOT paxriver DOT progeny DOT net> <4BDA5060 DOT 6040707 AT cygwin DOT com> From: "Crow, Frank" To: , X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I looked at the BLODA list. There are a couple of software packages in th= ere that I do have, however I'm not allowed to remove per company policy. = Such as Symantec Anti-virus and even the Embassy Trust Suite. Heck, I'm = not even sure if I can remove Windows Defender for that matter. Actually,= the only piece of software in that list that I do have installed *and* can= remove would be Google desktop. =20 So I'm going to try addressing every other issue that you've suggested firs= t. Like completely removing Cygwin, search & destroy any cygwin1.dll and = then re-install. I'll also take a look at the rebase package, etc. Hopef= ully it won't come down to BLODA being the issue. =20 But let's say that BLODA is the problem... and I'm not allowed to remove th= e offending software. Can I do something like install Cygwin on a differe= nt machine and then copy over the entire C:\Cygwin? I'm betting not, but = I'm asking just in case. =20 Thanks for information. That is very helpful. I've got stuff to try to = now. =20 -Frank =20 ________________________________ From: cygwin-owner AT cygwin DOT com on behalf of Larry Hall (Cygwin) Sent: Thu 4/29/2010 11:37 PM To: cygwin AT cygwin DOT com Subject: (nwl) Re: Installation problems - post install scripts all give "a= bnormal exit: exit code=3D128" On 4/29/2010 11:22 PM, Crow, Frank wrote: > Hi, > > I recently installed the latest version of the full Cygwin. I noticed t= hat many things were not working, so I looked at the /var/log/setup.log fil= e. In that log file, I discovered that all of the package post install sc= ripts failed during installation. All, except two, give the "abnormal ex= it: exit code=3D128" error, such as: > > > 2010/04/25 22:58:53 running: C:\cygwin\bin\bash.exe --norc --noprofile /e= tc/postinstall/000-cygwin-post-install.sh > 2010/04/25 22:59:26 abnormal exit: exit code=3D128 > 2010/04/25 22:59:26 running: C:\cygwin\bin\bash.exe --norc --noprofile /e= tc/postinstall/passwd-grp.sh > 2010/04/25 22:59:53 abnormal exit: exit code=3D128 > 2010/04/25 22:59:53 running: C:\cygwin\bin\bash.exe --norc --noprofile /e= tc/postinstall/coreutils.sh > 2010/04/25 23:00:19 abnormal exit: exit code=3D128 > 2010/04/25 23:00:19 running: C:\cygwin\bin\bash.exe --norc --noprofile /e= tc/postinstall/terminfo.sh > 2010/04/25 23:00:47 abnormal exit: exit code=3D128 > 2010/04/25 23:00:47 running: C:\cygwin\bin\bash.exe --norc --noprofile /e= tc/postinstall/bash.sh > 2010/04/25 23:01:14 abnormal exit: exit code=3D128 > > I did some internet searches and have found a couple other people reporti= ng this problem. Unfortunately, in every case, there has never been a re= solution or fix posted in reply. > > I tried a bit of hacking: I went into the /etc/postinstall directory and = ran > all of the post install scripts manually. While this did have some amou= nt > of success, it still did not result in a fully functional Cygwin > installation. As the scripts ran, many errors were reported. Too many= to > list here. But at least now I have the Cygwin and Cygwin-X start menus, > which I did not have before. > > > So my questions are: > > 1. Does anyone know what "exit code=3D128" or "exit code=3D129" mean? O= r where > to find out what those errors mean? > 2. Does anyone know why all of the post install scripts fail in this mann= er > for some installations such as mine? Or how to better troubleshoot or f= ix > the problem(s)? > > Any information is highly appreciated. Generally, this kind of failure stems from a few common problems: 1. The existence of another (often old) cygwin1.dll. Find it. Remove i= t. 2. http://cygwin.com/acronyms/#BLODA. Remove BLODA. 3. Possibly fork failures. Install the rebase package and run rebaseall after reading the README in /usr/share/doc/Cygwin. Also, make sure you're using the latest 'setup.exe' as found at cygwin.com. Beware of proxies along your path that could be caching an old version. You want version 2.697. > Problem reports: http://cygwin.com/problems.html If it's none of the above, please provide cygcheck output as requested by the link above. -- Larry Hall http://www.rfk.com =20 RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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 -- 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