V 0.9.4: unexpected end of file, expecting "; " or "}" in /etc/mime.types:789

Ron Savage ron at savage.net.au
Sun Feb 13 08:09:05 MSK 2011


Hi Marcus

On Sun, 2011-02-13 at 05:53 +0200, Eugaia wrote:
> Hi,
> 
> On 13/02/2011 04:23, Ron Savage wrote:
> > Hi Folks
> >
> > I couldn't see a reference to this in the recent archives, and googling
> > didn't help.
> >
> > I've just installed Debian 6 on a new laptop, and compiled nginx 0.9.4
> > with:
> > ./configure --with-http_ssl_module --with-http_gzip_static_module \
> >   --without-http_autoindex_module --without-http_browser_module
> > --without-http_fastcgi_module \
> >   --without-http_geo_module --without-http_empty_gif_module
> > --without-http_map_module \
> >   --without-http_proxy_module --without-http_memcached_module
> > --without-http_ssi_module \
> >   --without-http_userid_module --prefix=/usr/local/nginx
> > --sbin-path=/usr/local/sbin/nginx \
> >   --conf-path=/etc/nginx.conf --pid-path=/var/run/nginx.pid
> > --http-log-path=/var/log/nginx/access.log \
> >   --error-log-path=/var/log/nginx/error.log --user=nginx --group=nginx
> >
> > Starting nginx with the default /etc/nginx.conf, with Debian's
> > default /etc/mime.types gives:
> >
> > nginx at zigzag:~$ nginx: [emerg] unexpected end of file, expecting ";" or
> > "}" in /etc/mime.types:789
> /etc/mime.types is not an Nginx config file on my Debian 6 setup.  The 
> default config folder for Nginx is /etc/nginx, and the default config 
> file is /etc/nginx/nginx.conf.  The mime.types file is 
> /etc/nginx/mime.types.  You should probably just use /etc/nginx as your 
> base, not /etc.

Thanx for the replies. You gave me an idea.

I understand /etc/mime.types is a Deb file, not an nginx file.

I changed my config.sh to use 
--conf-path=/etc/nginx/nginx.conf rather than as above,
/and/ copied /etc/mime.types to /etc/nginx/
assuming there was a bug in nginx when the config was /etc/nginx.conf,
in that the line # of the error is the (correct) last line
of /etc/mime.types, so I guess the code is not handling properly the
case where nginx.conf and mime.types are in /etc/, somehow.

And yes, after cleaning up my old proxy pass stuff, that fixed it.

Many thanx.

-- 
Ron Savage
http://savage.net.au/
Ph: 0421 920 622




More information about the nginx mailing list