Re: [MooseFS-Users] Nginx proxy to mfscgiserv

[Neddy, N. N. <na...@nd...>]

It woks but the static files can't be loaded.

I changed the configs related to your ideas:

upstream mfscgi {
    server 10.2.192.130:9425;
}
server {
    listen 81;
    location /mfs.cgi {
        proxy_pass http://mfscgi;
    }
    location /mfs.css {
        proxy_pass http://mfscgi;
    }
    location /acidtab.js {
        proxy_pass http://mfscgi;
    }
    location /logomini.png {
        proxy_pass http://mfscgi;
    }
}

Now it's ok, though you'll have to redirect or put mfs.cgi to your
index direction.

So the original config failed because mfscgiserv put 301 redirect to
mfs.cgi and closed current connection? Below is nginx's error log:

[error] 12224#0: *1 upstream prematurely closed connection while
reading response header from upstream, client: 10.2.x.x, server: ,
request: "GET / HTTP/1.1", upstream: "http://10.2.192.130:9425/"

Thanks,

On Tue, Sep 8, 2015 at 1:52 PM, 黑铁柱 <kan...@gm...> wrote:
> try this
> server {
>     listen 81;
>     location / {
>         proxy_pass http://10.2.192.130:9425/mfs.cgi;
>     }
> }
>
> 2015-09-07 17:01 GMT+08:00 Neddy, NH. Nam <na...@nd...>:
>>
>> Hi,
>>
>> I try to access MooseFS CGI monitor via nginx proxy but no luck.
>>
>> With CGI monitor was started on master server, nginx was configured to
>> pass request to mfscgiserv
>>
>> server {
>>     listen 81;
>>     location / {
>>         proxy_pass http://10.2.192.130:9425;
>>     }
>> }
>>
>> But clients only get "502 Bad Gateway" error when open nginx server
>> address in their browser.
>>
>> I wonder did anybody try to do the same thing?
>> Appreciate your advice.
>>
>>
>> ------------------------------------------------------------------------------
>> _________________________________________
>> moosefs-users mailing list
>> moo...@li...
>> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>
>