Re: Resolve names from chroot'ed OpenBSD httpd
You found my post nonetheless. I coped over resolve.conf, local time and hosts I believe. Then it started working On Friday, May 22, 2015, Daniel Bolgheroni dbolgher...@gmail.com wrote: On Fri, May 22, 2015 at 06:39:53AM -0400, Dain Bentley wrote: I had this issue a while back. Have you tried restarting the server? Sure, but didn't solve the problem. http://marc.info/?l=openbsd-miscm=135603654831609w=2
Re: Resolve names from chroot'ed OpenBSD httpd
Also check permissions on the files On Thursday, May 21, 2015, Daniel Bolgheroni dbolgher...@gmail.com wrote: Hi, Any advice on resolving names from a chroot'ed httpd? OpenBSD 5.7, Wordpress downloaded from site, mariadb configured, paths set on httpd.conf. Also have /var/www/etc/hosts and /var/www/etc/resolv.conf in place. Works almost as expected, except for some functions like installing plugins/themes, which I get a lot of php_network_getaddresses: getaddrinfo failed: no address associated with name when activating Wordpress debug. Warning: stream_socket_client(): unable to connect to tcp://api.wordpress.org:80 (php_network_getaddresses: getaddrinfo failed: no address associated with name) in /htdocs/wordpress/wp-includes/class-http.php on line 1008 Same problem with nginx from ports. Thank you. -- db
Re: Resolve names from chroot'ed OpenBSD httpd
On 21-05-2015 20:57, Daniel Bolgheroni wrote: Warning: stream_socket_client(): unable to connect to tcp://api.wordpress.org:80 (php_network_getaddresses: getaddrinfo failed: no address associated with name) in /htdocs/wordpress/wp-includes/class-http.php on line 1008 Do you have the relevant files in your chroot's etc directory? I believe that you need at least a resolv.conf there. Also, a localtime is always a good idea. Cheers, Giancarlo Razzolini
Re: Resolve names from chroot'ed OpenBSD httpd
On Fri, May 22, 2015 at 06:39:53AM -0400, Dain Bentley wrote: I had this issue a while back. Have you tried restarting the server? Sure, but didn't solve the problem. http://marc.info/?l=openbsd-miscm=135603654831609w=2
Re: Resolve names from chroot'ed OpenBSD httpd
On Fri, 22 May 2015 11:54:10 -0300, Daniel Bolgheroni wrote: On Fri, May 22, 2015 at 06:39:53AM -0400, Dain Bentley wrote: I had this issue a while back. Have you tried restarting the server? Sure, but didn't solve the problem. http://marc.info/?l=openbsd-miscm=135603654831609w=2 You should ktrace the process and see what files it is unable to open. That should tell you what is missing from the chroot. - todd
Re: Resolve names from chroot'ed OpenBSD httpd
I had this issue a while back. Have you tried restarting the server? On Thursday, May 21, 2015, Daniel Bolgheroni dbolgher...@gmail.com wrote: Hi, Any advice on resolving names from a chroot'ed httpd? OpenBSD 5.7, Wordpress downloaded from site, mariadb configured, paths set on httpd.conf. Also have /var/www/etc/hosts and /var/www/etc/resolv.conf in place. Works almost as expected, except for some functions like installing plugins/themes, which I get a lot of php_network_getaddresses: getaddrinfo failed: no address associated with name when activating Wordpress debug. Warning: stream_socket_client(): unable to connect to tcp://api.wordpress.org:80 (php_network_getaddresses: getaddrinfo failed: no address associated with name) in /htdocs/wordpress/wp-includes/class-http.php on line 1008 Same problem with nginx from ports. Thank you. -- db
Resolve names from chroot'ed OpenBSD httpd
Hi, Any advice on resolving names from a chroot'ed httpd? OpenBSD 5.7, Wordpress downloaded from site, mariadb configured, paths set on httpd.conf. Also have /var/www/etc/hosts and /var/www/etc/resolv.conf in place. Works almost as expected, except for some functions like installing plugins/themes, which I get a lot of php_network_getaddresses: getaddrinfo failed: no address associated with name when activating Wordpress debug. Warning: stream_socket_client(): unable to connect to tcp://api.wordpress.org:80 (php_network_getaddresses: getaddrinfo failed: no address associated with name) in /htdocs/wordpress/wp-includes/class-http.php on line 1008 Same problem with nginx from ports. Thank you. -- db
