Internal Error Pcfg_openfile Called With Null Filename Pam
Date: Thu, 1 Mar 2007 14:12:01 UTC Severity: important Merged with 394097 Found in version libapache2-mod-auth-pam/1.1.1-6.1 Fixed in version 1.1.1-9+rm Done: Debian FTP Masters
basic authentication and specify a different auth method, Apache (at least some versions of it) still looks around for an auth file and throws a "pcfg_openfile() called with NULL" error when it can't find one. To fix, set the user auth file to /dev/null:
AuthBasicAurhorative off
AuthUserFile /dev/null
Or you can just ignore the errror I suppose. It looks more serious than it is. This entry was posted on Friday, February 26th, 2010 at 10:42 am and is filed under Apache, Technology. You can follow any responses to this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=412981 entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. (No Ratings Yet) Loading... Leave a Reply Name (required) Mail (will not be published) (required) Website Notify me of follow-up comments by email. Notify me of new posts by email. Random Quote"Just as the addition of however many zeros will never make a unit, so http://blog.arithm.com/2010/02/26/internal-error-pcfg_openfile-called-with-null-filename/ the value of a community depends upon the spiritual and moral stature of the individuals composing it."-Carl Jung Recently Posted Format a CSV string in Twig Validating multiple files in Symfony 2.5 End User Help Documentation: Tricks of the Trade Postmaster Abuse It's not if, but *when* Pages About Archives February 2015 November 2014 October 2014 May 2014 April 2014 March 2014 February 2014 January 2014 September 2013 May 2013 February 2013 January 2013 September 2012 August 2012 July 2012 June 2012 May 2012 April 2012 March 2012 February 2012 December 2011 November 2011 October 2011 September 2011 August 2011 July 2011 June 2011 April 2011 February 2011 January 2011 December 2010 November 2010 October 2010 September 2010 August 2010 July 2010 June 2010 May 2010 April 2010 March 2010 February 2010 January 2010 December 2009 November 2009 October 2009 September 2009 August 2009 July 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 May 2008 April 2008 March 2008 February 2008 January 2008 December 2007 November 2007 October 2007 S
by joestump I've been putting together a new file server for personal use that I plan on hosting on my DSL at home (7mbit/896kbit). I have Gig-E http://stu.mp/2006/06/webdavsslpam-on-debianapache2.html inside my condo and just shy of 1mbit from outside my condo https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg312458.html over a static IP address. More than enough bandwidth to serve my personal email, my website along with a few friends' sites and email. The next question, of course, is what to do with the hundreds of gigabytes laying vacant on the server. Being that I run OS X internal error 10.4 and so do my other friends the obvious solution was WebDAV over SSL. I wanted to be able to mount my $HOME/public_html over SSL using PAM for authentication. Surprisingly, this actually works with a few hacks. Warning The rest of this article includes a few hacks that mess with permissions in a way that some people will scoff at. internal error pcfg_openfile I understand this fully and am using this little space to warn you ahead of time that doing this will give Apache access to your /etc/shadow file. List of Ingredients An installation of Debian GNU/Linux running Apache2 (specifically apache2, apache2-common, apache2-utils, and libapache2-mod-auth-pam) Everyone's favorite scheduler, cron A text editor Enabling/Disabling the appropriate Apache2 modules Using the script a2enmod you'll want to enable auth_pam, dav_fs, dav and ssl. These are the basic modules required to get this setup going. You might also be interested in installing the php5 module, etc. I won't be covering that in this section. You will actually want to disable the userdir module. I did this mainly to disable WebDAV from working under the non-SSL Apache2 instances. I now include these files directly from my SSL
thread I could get auth_pam to work, but for each action that I take it prints the following in my apache error.log: [Fri Mar 09 08:43:07 2007] [error] Internal error: pcfg_openfile() called with NULL filename [Fri Mar 09 08:43:07 2007] [error] [client 200.189.112.13] (9)Bad file descriptor: Could not open password file: (null) [Fri Mar 09 08:43:07 2007] [error] Internal error: pcfg_openfile() called with NULL filename [Fri Mar 09 08:43:07 2007] [error] [client 200.189.112.13] (9)Bad file descriptor: Could not open password file: (null) [Fri Mar 09 08:43:07 2007] [error] Internal error: pcfg_openfile() called with NULL filename [Fri Mar 09 08:43:07 2007] [error] [client 200.189.112.13] (9)Bad file descriptor: Could not open password file: (null) [Fri Mar 09 08:43:08 2007] [error] Internal error: pcfg_openfile() called with NULL filename [Fri Mar 09 08:43:08 2007] [error] [client 200.189.112.13] (9)Bad file descriptor: Could not open password file: (null) And so on. It works, but still creating those logs. My configuration: