Hi Ovidiu
I tried TCP earlier to little avail.
*However*
I tried it again anyway (just to say that I did it again) and I got a
YSOD/Exception (which is a start!). After tweaking Web.config and
restarting nginx - my hello world actually printed 'hello world'. It's
almost sad how much joy this brought me! :-)
Now I know TCP does actually work (although I am not sure why it does now),
I can set about solving why the unix socket is behaving so strangely. I
suspect that you (and the others earlier in this thread) are indeed all
correct about the permissions issue.
I have set about resolving it, but I can't see to get past it.
I have chmod '777' (for now) - to no avail.
I ran chmod a+rwx as well - to no avail.
I even tried a different path - sadly, to no avail!
I am sure I am missing something obvious, although I have no idea what it
could be... :-(
Any advice would be hugely appreciated!
Thanks
G
On 7 May 2013 20:57, Ovidiu D <ovidiud...@gmail.com> wrote:
> I'm pretty sure that you have a permission problem here. You should double
> check that both the users of the nginx and mono fastcgi server processes
> have rw access to that socket.
>
> For debugging purposes you can also try to use a TCP socket instead of a
> unix socket and once your setup works you can move back to unix sockets.
>
>
> On Tue, May 7, 2013 at 9:56 PM, Gee <g.pl...@gmail.com> wrote:
>
>> Hi
>>
>> I am having trouble getting Mono to work with nginx. I installed my OS
>> (OpenBSD 5.3) and set up ports. I built mono, mono-xsp and nginx - all
>> without incident. All three appear to be working OK, but not in
>> conjunction.
>>
>> I am trying to run a *very* simple MVC3 app - it is literally a hello
>> world controller (no fancy code whatsoever) - but I keep getting a 502 (Bad
>> gateway). In the log, I see the following:
>>
>> [crit] 31764#0: *1 connect() to unix:/tmp/fastcgi.socket failed (2: No
>> such file or directory) while connecting to upstream,
>>
>> The frustrating thing here is that /tmp/fastcgi.socket does actually
>> exist. I tried 'touch' and making sure 'www' and 'wheel' have the
>> appropriate permissions (which they do). The result of 'ls -la
>> /tmp/fastcgi.socket' revealed nothing awry. I tried using a different path
>> (such as '/home/socket' and '/home/fastcgi.socket'), but all to no avail.
>>
>> Does anyone have any ideas/hints? Could this be a bug in the port?
>>
>> To try and save time, here is my config:
>>
>>
>>
>> worker_processes 1;
>>
>> events {
>> worker_connections 1024;
>> }
>>
>> http {
>> include mime.types;
>> default_type application/octet-stream;
>>
>>
>> server {
>> listen 80;
>> access_log /home/www/nginx.log;
>> error_log /home/www/errors.log;
>>
>> # root /home/www/test;
>> # index index.html index.htm index.aspx default.aspx;
>>
>> location ^~ /Scripts/ { }
>> location ^~ /Content/ { }
>>
>> location / {
>> root /home/www/test;
>> # fastcgi_index /Home/Index;
>>
>> fastcgi_pass unix:/tmp/fastcgi.socket;
>> # include fastcgi_params;
>> include /etc/nginx/fastcgi_params;
>> }
>> }
>> }
>>
>>
>>
>> Thanks!
>> G
>>
>> _______________________________________________
>> Mono-aspnet-list mailing list
>> Mono-aspnet-list@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
>>
>>
>
_______________________________________________
Mono-aspnet-list mailing list
Mono-aspnet-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
