Bash startup problems on Windows 2008 server

Bash startup problems on Windows 2008 server

[Steinar Bang]

I tried installing cygwin (the current setup.exe from www.cygwin.com) on
a freshly installed Windows 2008 server.

The installation started normally, and I didn't see anything strange
until I was going to check up on the progress.  Then the cygwin setup
window was gone.

There was no desktop icon, but there was a start menu entry.  When I
selected the "Cygwin Bash Shell" entry, a command line window flashed up
and disappeared.

I tried running the install again, using all defaults from the original
install.  I got no error messages, but again no desktop icon was
created.

Trying to select the start menu item, gave me the same command line
window popping up, and then disappearing.

I started cmd.exe and ran bash, and got the following (which looks
similar to what's displayed in the window that opens and disappears):

C:\Users\myuser>\cygwin\bin\bash
      2 [main] bash 3832 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VI
OLATION
    480 [main] bash 3832 open_stackdumpfile: Dumping stack trace to bash.exe.sta
ckdump
 408620 [main] bash 3832 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VI
OLATION
 425466 [main] bash 3832 _cygtls::handle_exceptions: Error while dumping state (
probably corrupted stack)

Anyone has any idea what might be wrong here?

Thanx!


- Steinar


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash startup problems on Windows 2008 server

[Corinna Vinschen]

On Jun 25 14:11, Steinar Bang wrote:
> I tried installing cygwin (the current setup.exe from www.cygwin.com) on
> a freshly installed Windows 2008 server.
> 
> The installation started normally, and I didn't see anything strange
> until I was going to check up on the progress.  Then the cygwin setup
> window was gone.
> 
> There was no desktop icon, but there was a start menu entry.  When I
> selected the "Cygwin Bash Shell" entry, a command line window flashed up
> and disappeared.
> 
> I tried running the install again, using all defaults from the original
> install.  I got no error messages, but again no desktop icon was
> created.
> 
> Trying to select the start menu item, gave me the same command line
> window popping up, and then disappearing.
> 
> I started cmd.exe and ran bash, and got the following (which looks
> similar to what's displayed in the window that opens and disappears):
> 
> C:\Users\myuser>\cygwin\bin\bash
>       2 [main] bash 3832 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VI
> OLATION
>     480 [main] bash 3832 open_stackdumpfile: Dumping stack trace to bash.exe.sta
> ckdump
>  408620 [main] bash 3832 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VI
> OLATION
>  425466 [main] bash 3832 _cygtls::handle_exceptions: Error while dumping state (
> probably corrupted stack)
> 
> Anyone has any idea what might be wrong here?

No.  This has been reported at least twice already, but personally I
can't reproduce it, neither on my two 2008 i386, nor on my 2008 x86_64
system.  Somebody, who can reproduce this problem will have to debug
this problem.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash startup problems on Windows 2008 server

[Mark J. Reed]

I know this is a lame suggestion, but I figure it can't hurt to throw
it out there anyway:

Does explicitly running setup.exe as Administrator make any difference here?

I wouldn't expect it to matter on Vista, but perhaps Server '08, in
the name of heightened security for servers, doesn't do the automatic
privilege escalation for setup programs?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash startup problems on Windows 2008 server

[Corinna Vinschen]

On Jun 25 10:20, Mark J. Reed wrote:
> I know this is a lame suggestion, but I figure it can't hurt to throw
> it out there anyway:
> 
> Does explicitly running setup.exe as Administrator make any difference here?
> 
> I wouldn't expect it to matter on Vista, but perhaps Server '08, in
> the name of heightened security for servers, doesn't do the automatic
> privilege escalation for setup programs?

Interesting suggestion, but I doubt it.  Setup.exe works really fine
for me, with UAC enabled.  However, trying that doesn't hurt, right?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash startup problems on Windows 2008 server

[Christopher Faylor]

On Wed, Jun 25, 2008 at 03:12:58PM +0200, Corinna Vinschen wrote:
>No.  This has been reported at least twice already, but personally I
>can't reproduce it, neither on my two 2008 i386, nor on my 2008 x86_64
>system.  Somebody, who can reproduce this problem will have to debug
>this problem.

Me too!  I've been using 2008 Server fairly heavily lately and it WJFFM.
I would debug this if I could duplicate it of course.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash startup problems on Windows 2008 server

[caryco]

I can dup it on my system. In fact, bash works nice at the beginning. After I
install Terminal Services and restart the system as requested, it cannot
start anymore. I've disabled UAC and still the same.

Can someone points out how to debug the problem?

Thanks
Cary


Christopher Faylor-8 wrote:
> 
> On Wed, Jun 25, 2008 at 03:12:58PM +0200, Corinna Vinschen wrote:
>>No.  This has been reported at least twice already, but personally I
>>can't reproduce it, neither on my two 2008 i386, nor on my 2008 x86_64
>>system.  Somebody, who can reproduce this problem will have to debug
>>this problem.
> 
> Me too!  I've been using 2008 Server fairly heavily lately and it WJFFM.
> I would debug this if I could duplicate it of course.
> 
> cgf
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Bash-startup-problems-on-Windows-2008-server-tp18110908p18710600.html
Sent from the Cygwin list mailing list archive at Nabble.com.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bash startup problems on Windows 2008 server

[Eric Berge]

On Jun 25 10:20, Mark J. Reed wrote:
> I know this is a lame suggestion, but I figure it can't hurt to throw
> it out there anyway:
> 
> Does explicitly running setup.exe as Administrator make any difference here?
> 
> I wouldn't expect it to matter on Vista, but perhaps Server '08, in
> the name of heightened security for servers, doesn't do the automatic
> privilege escalation for setup programs?

In the cases I ran into this I was always running as Administrator.

As Corinna indicates this works sometimes and not others.  I've had success
on some Win2008 boxes and not others.  In particular I've had two boxes (one
32-bit and one 64-bit that have been problematic).  However, since I saw this
message I tried again and from the current released version this worked just
fine today (and this is after trying probably somewhere around 20 times over
a large span of time).

So the sensitivity on this one is just getting stranger as those systems have
pretty much been unchanged otherwise.  The only thing is that it has been kept
up-to-date with Windows Update.  Which could, of course, explain anything...

-- Eric


      

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/