MunkiServer HTTP 200 problem

[John Lockwood]

I have (I believe) managed to install MunkiServer and all its dependencies and get it working via Apache in Server.app on a Mountain Lion server. The website runs and the MunkiServer admin interface loads and lets me login. It also lets me manually add a computer and upload a .dmg for a test package. This package then shows up correctly in /usr/local/munkiserver/packages

A test client connects and (after it has initially been manually added to MunkiServer) updates its info in MunkiServer.

My problem is that the test package (an optional install) whilst being listed in the webadmin and Managed Software Update, fails to download to the client which gets the message

Download of XXX failed: HTTP result 200: OK

Further testing shows that even trying to download the same package in the MunkiServer webadmin page on the server itself also fails producing a zero byte file.

This is a single Mac server config with no replicas. Being that I am running Server.app the main httpd.conf file is located at

/Library/Server/Web/Config/apache2/httpd_server_app.conf and not at /etc/apache/httpd.conf I have added the three lines to that file to load mod_passenger.so and ruby and for what its worth mod_xsendfile.so was already listed.

Any suggestions anyone?

Thanks, John

[Ricky Chilcott]

Can you share your apache configs?

My guess is a mis-configuration of xsend_file related configs.

Ricky Chilcott

ri...@rickychilcott.com

--
You received this message because you are subscribed to the Google Groups "munkiserver-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to munkiserver-d...@googlegroups.com.
To post to this group, send email to munkise...@googlegroups.com.
Visit this group at http://groups.google.com/group/munkiserver-dev.
For more options, visit https://groups.google.com/groups/opt_out.

[John Lockwood]

For the benefit of everyone I have now found and fixed the problem. The problem is that whilst standard OS X does not include mod_xsendfile.so at all, if you have Server.app (i.e. the server version) installed it does include a copy of mod_xsendfile.so. I was therefore trying to use this version as would make sense.

It turns out however the version included with Server.app must be an old version of this plugin as it does not support the XSendFilePath command but does support the older XSendFileAllowAbove command. This means it must be version 0.1.0 or earlier. As there is no easy way to tell what version is installed this was not obvious.

To test this I first commented out the XSendFilePath command and tried the older XSendFileAllowAbove command. This worked in that Apache started without complaint and strongly suggested the included version was 0.1.0 or earlier. I then like people without Server.app downloaded the latest version of mod_xsendfile.c and compiled it and installed it and tried the XSendFilePath command again and this time Apache started with no problems. I was then able to test downloading a package via the web admin interface and the Manage Software Update client and both could now successfully download packages without an error 200.