[Mono-bugs] [Bug 75030][Maj] New - Apache fails to startup on OES server reboot because of mod_mono

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon May 23 17:15:11 EDT 2005


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by ifolder.guy at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75030

--- shadow/75030	2005-05-23 17:15:11.000000000 -0400
+++ shadow/75030.tmp.4956	2005-05-23 17:15:11.000000000 -0400
@@ -0,0 +1,105 @@
+Bug#: 75030
+Product: Mono: Tools
+Version: 1.0
+OS: other
+OS Details: Novell Open Enterprise Server
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: mod_mono
+AssignedTo: gonzalo at ximian.com                            
+ReportedBy: ifolder.guy at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Apache fails to startup on OES server reboot because of mod_mono
+
+Description of Problem:
+After installing iFolder Enterprise server on an OES server, Apache fails
+to come up after a server reboot or after restarting just the Novell Xtier
+service. The following error is thrown 
+
+Starting httpd2 (worker) (98)Address already in use: make_sock: could not
+bind to address [::]:631
+no listening sockets available, shutting down
+Unable to open logs
+startproc:  exit status of parent of /usr/sbin/httpd2-worker: 1
+
+This error/condition is because of a combination of the following things:
+
+mod_mono
+novell-xsrvd startup script
+Higher end hardware
+
+
+Steps to reproduce the problem:
+NOTE: This issue seems to be more reproducible on higher end machines (i.e.
+PIV 2.4 GHz with Hyperthreading).
+1. Install Novell iFolder Enterprise Server on OES
+2. Reboot the server
+3. Notice on the server's way back up that the Xtier script
+(/etc/init.d/novell-xsrvd) is issueing an Apache restart command. Below is
+the snippet from the script
+
+StartXSRVD()
+{
+  # Source the environments file for xsrvd
+  . /etc/opt/novell/xtier/xsrvd/envvars
+
+  # Update the limit parameters
+  ulimit -c unlimited
+  ulimit -f unlimited
+
+  # Start the daemon
+  echo -n "Starting novell-xsrvd..."
+  $START_DAEMON -u $XSRVD_USER $DAEMON -d
+  RVAL=$?
+
+  # Apache needs to start after novell-xsrvd
+  /etc/init.d/apache2 status
+  if [ "x$?" == "x0" ]; then
+    /etc/init.d/apache2 restart
+  fi
+}
+
+4. Because of the issued restart, Apache is now throwing the error and
+failing to restart because of mod_mono. If I remove the following conf files
+/etc/apache2/conf.d/mod_mono.conf
+/etc/apache2/conf.d/ifolder_web.conf  
+/etc/apache2/conf.d/simias.conf 
+, then Apache has no issue with the apache2 restart command from the Xtier
+script. 
+NOTE: I can still reproduce the issue with just the mod_mono.conf file
+intacted. 
+
+
+Actual Results:
+On higher end systems, Apache fails to come back up successfully from a
+restart command. A couple of mono processes are running, but Apache isn't.
+Below are the two process that are returned when issueing a 'ps aux|grep mono'
+
+wwwrun   12895  1.4  0.5 16988 6196 ?        Ss   14:07   0:00
+/usr/bin/mono /usr/lib/mono/1.0/mod-mono-server.exe --filename
+/tmp/mod_mono_server_ifolder --applications
+/ifolder:/opt/novell/ifolder3/webaccess --nonstop
+wwwrun   12905  1.5  0.5 16988 6196 ?        Ss   14:07   0:00
+/usr/bin/mono /usr/lib/mono/1.0/mod-mono-server.exe --filename
+/tmp/mod_mono_server_simias10 --applications
+/simias10:/opt/novell/ifolder3/web --nonstop
+
+In order to make sure everything works again, the user is required to stop
+the mono processes and then start apache again.
+
+Expected Results:
+Apache should be able to successfully stop and start with the restart command.
+
+
+How often does this happen? 
+Depends on the Hardware. Below are the two machine I've tested with and the
+frequency I've seen the issue happen
+
+PIV 2.4Ghz Hyperthreading enable - 100% of the time the issue is reproduced.
+PIII 667Mhz - The novell-xsrvd script (Apache restart) is successful
+everytime. The issue happens 0% of the time.


More information about the mono-bugs mailing list