couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Rigaux <philippe.rig...@internetmemory.net>
Subject Re: Strange error: 'Error: badmatch {error,enoent}'
Date Mon, 30 Sep 2013 16:17:15 GMT
Dave, thanks a lot for you quick answer. We re-installed CouchDB and it
works fine, so, fausse alerte. I noticed that I have to provide as much
information as I can with my next request. Hope I am forgiven for this time.

Congratulations for your great work.

Philippe


2013/9/27 Dave Cottlehuber <dch@jsonified.com>

> >
> >Hello,
> >
> >We get a strange error after re-installing CouchDB behind a proxy. Each we
> >execute a view we get:
> >
> >Error: badmatch {error,enoent}
> >
> >We tried to apply the SSL configuration explained in the doc, but no
> >success so far. Any help would be quite appreciated.
> >
> >Regards
> >
> >Philippe Rigaux
> >
>
> Salut Philippe,
>
> Usually the help available is commensurate with the amount of information
> provided ;-)
>
> Try sending us the output of:
>
> curl -vX GET …your_view…
>
> the information in couch.log at the same time.
>
> Also, the relevant logs in your proxy. You might want to share some of
> the config for that too.
>
> There's a fair bit of info on the couchdb wiki on proxies etc.
>
> Pay special attention to things getting re-written wrt URL encoding.
>
> A+
> Dave
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message