Re: Problem running under nginx

[Brad]

You will want to review the heyu documentation for this as that is not a domus.Link error. Heyu is trying to write to that directory. Look at heyu.org and http://tech.groups.yahoo.com/group/heyu_users/messages for more information.

Brad

On Friday, March 15, 2013 5:53:22 PM UTC-5, Woody wrote:

I'm trying to get domus.link to work under the nginx web server with php-fpm.  I'm running a pogoplug linux box, which is a little under-powered for apache.  Nginx is a server which uses less resources.

When I try to start heyu, I get the message: "SPOOL directory /var/tmp/heyu does not exist".  The directory does exist and is writable by everybody.  I've tried changing the permissions on that directory every way I can think of, but I always get the error.  Heyu starts without a problem when I run it as root or as any other user.  It only chokes when I run it under domus.

Has anybody else gotten domus to work under nginx?  Any other ideas about why I'm seeing this error?

[Woody]

I don't think it's really a Heyu problem.  Heyu runs fine under every other user I've tried.  It only fails when I try to start it with Domus.  When I run Heyu directly and the permissions on /var/tmp/heyu are insufficient, Heyu gives me an error message that specifically tells me that there's a problem with permissions.  When I try to start Heyu with Domus, the error message says that /var/tmp/heyu does not exist.  This makes me think that Domus is doing something different when it starts Heyu.  I'm wondering if Domus is providing some other base directory for Heyu to store it's tmp files.  If so, I don't know what the base directory is.  

Or it may be an issue with the permissions on webpages running with nginx.  Has anybody used nginx or another web server than Apache?  If so, did you run into any similar problems?

[Brad]

Hmm, is there a security setting for the user/group for the nginx webserver that prevents access to directories outside of the defined pages being served? You might want to look into the settings for that user and it maybe a captured user that is not allowed access outside of the pages served directory for security.

Brad

[Denis Goulet]

The reason you get /var/tmp/heyu does not exist is because Apache uses private temp files. You can change that by going to /usr/lib/systemd/system/httpd.service and changing the line PrivateTemp from true to false or just removing the line completely.

--
You received this message because you are subscribed to the Google Groups "domuslink-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to domuslink-use...@googlegroups.com.
To post to this group, send an email to domusli...@googlegroups.com.
Visit this group at http://groups.google.com/group/domuslink-users?hl=en-GB.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Woody]

den:  I'm not using Apache, I'm using nginx.  It may be the same issue, though.  Nginx doesn't have a setting equivalent to "PrivateTemp" , as far as I can see.  Maybe somebody knows how to set up nginx to avoid this problem.

[Brad]

Well, since I have my pogoplug now I have figured this out.

The assumption is you are running archlinuxarm for this.

The systemd unit file for starting the nginx engine (apache as well)  will need to have the [Service] attribute PrivateTemp set to false. This is due to heyu wanting to create a directory in /var/tmp called heyu and that is not allowed in the private tmp area.

Also, you will need to force permissions on /run/lock to 777 as it is not set to be open. This needs to be done on every boot as it is reset.

I also added :/usr/local/domus.Link/:/etc/heyu/:/var/lock/:/usr/bin/ to the end of the php.ini open_basedir directive so that it will allow access to those files for apache. Not sure if this applies to nginx.

Hope this helps.

Brad