This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: apache2 and cygwin- problems running


I suppose I should have directed my question better, I was a tad confused for sure.

I wasn't aware I -had- to use cygserver in order to get this to startup, you helped lead
me down the path that I had to install the package. I outright forgot that I did in
fact read the docs for it, when I tried to run the command to do the config it
wasn't found.


Who knows what else I was tasking to, I've been in a state of Bliss since I went back to
try Cygwin. Previously, I was on a slow connection so to download all the packages was
really tiresome. KDE has been wonderful to me so far, and I've been able to get rid of
all my xwindows managers for win32 so I can run a few ulities on my gateway.


So thanks a lot, it runs fine with the exception that I am told the service fails to start,
when it's quite the opposite. That however can be fixed now that the httpd.exe is running.




On Tue, 2 Mar 2004, robert atkinson wrote:



I am running CYGWIN 1.5.7 on WindowsXP, been having problems getting
apache2 (2.0.47 & 2.0.48)
to startup and continue running. It just simply shows up on my taskmgr,
then exits with little fanfair.

I have no issues compiling Apache2, I get the normal .exe errors so I
simply copy the .exe's left behind over
to the default /usr/local/apache2/bin. I have tried:

'./httpd.exe -k start'
'./httpd.exe -t'
'./httpd.exe -e debug'
'./apachectl start'

I get no errors on the httpd.exe, on the apachectl I get the 'ulimit'
not available, but nothing else save a 'pid overwritten' message in the
errors_log.
I have tried the various switches for no shared objects, or all shared
objects. I have compiled with default prefork as the model, then tried to
change all the paths, thinking it was possible I had wrong server roots.

I've seen that others were fruitfull on getting it to at least run, but
it just dies on me no matter what ports I set, ip's.
I changed the user/group as well thinking that could be the problem,
tried SYSTEM, my username and always left group to the default.
I made sure the permissions on the cygwin directory allowed writes, etc.

Lastly, I fell back to running strace.
**********************************************
Program name: i:\mozilla\cygwin\usr\local\apache2\bin\httpd.exe (2668)
App version:  1005.7, api: 0.109
DLL version:  1005.7, api: 0.109
DLL build:    2004-01-30 19:32
OS version:   Windows NT-5.1
Heap size:    402653184
Date/Time:    2004-03-02 15:20:09
**********************************************

Then after a pretty big trace, this is at the end of the process life.

26  290212 [main] httpd 2972 fhandler_base::close: closing '/usr/local/apache2/logs/httpd.pid' handle 0x6C4
  93  290305 [main] httpd 2972 close: 0 = close (8)
  72  290377 [main] httpd 2972 semget: semget (key = 0, nsems = 1, semflg = 0x380)
  44  290421 [main] httpd 2972 cygserver_init: cygserver use disabled in client
  29  290450 [main] httpd 2972 client_request::make_request: cygserver un-available
  26  290476 [main] httpd 2972 semget: -1 [88] = semctl ()
  25  290501 [main] httpd 2972 kill: kill (2972, 12)
  27  290528 [main] httpd 2972 sig_send: sendsig 0x700, pid 2972, signal 12, its_me 1
  37  290565 [main] httpd 2972 sig_send: wakeup 0x6C4
  42  290607 [main] httpd 2972 sig_send: Waiting for pack.wakeup 0x6C4
  39  290646 [sig] httpd 2972 sig_handle: signal 12 processing
  29  290675 [sig] httpd 2972 sig_handle: signal 12, about to call do_exit
  71  290746 [sig] httpd 2972 signal_exit: about to call do_exit (10C00)
  24  290770 [sig] httpd 2972 do_exit: do_exit (68608), exit_state 0
  25  290795 [sig] httpd 2972 void: 0x0 = signal (20, 0x1)
  24  290819 [sig] httpd 2972 void: 0x0 = signal (1, 0x1)
  22  290841 [sig] httpd 2972 void: 0x0 = signal (2, 0x1)
  23  290864 [sig] httpd 2972 void: 0x0 = signal (3, 0x1)
  23  290887 [sig] httpd 2972 fhandler_base::close: closing '/dev/null' handle 0x7D8
  31  290918 [sig] httpd 2972 fhandler_base::close: closing '/dev/null' handle 0x734
  31  290949 [sig] httpd 2972 fhandler_base::close: closing '/usr/local/apache2/logs/error_log' handle 0x6E4
 224  291173 [sig] httpd 2972 fhandler_socket::close: 0 = fhandler_socket::close()
 188  291361 [sig] httpd 2972 fhandler_base::close: closing '/usr/local/apache2/logs/access_log' handle 0x6A8
  97  291458 [sig] httpd 2972 fhandler_base::close: closing '/usr/local/apache2/logs/error_log' handle 0x6EC
 110  291568 [sig] httpd 2972 sigproc_terminate: entering
  36  291604 [sig] httpd 2972 proc_terminate: nchildren 0, nzombies 0
  25  291629 [sig] httpd 2972 proc_terminate: leaving
  84  291713 [sig] httpd 2972 __to_clock_t: dwHighDateTime 0, dwLowDateTime 400576
  27  291740 [sig] httpd 2972 __to_clock_t: total 00000000 00000028
  24  291764 [sig] httpd 2972 __to_clock_t: dwHighDateTime 0, dwLowDateTime 200288
  40  291804 [sig] httpd 2972 __to_clock_t: total 00000000 00000014
1224  293028 [sig] httpd 2972 _pinfo::exit: Calling ExitProcess 68608

Help :) I didn't see much about cygserver, or the cygserver use disabled
in client.
I did however think all I had to do was run the start commands. I of course
have no problem on my BSD machines, so this is the first time apache has
ever let me down.

Thanks in advance.



Robert,


You *did* read the cygserver README at
/usr/share/doc/Cygwin/cygserver.README, right?
Igor




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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]