Looks like this got solved on slack.
Cheers
Jan
—
> On 1. Feb 2019, at 08:03, Jan Lehnardt <j...@apache.org> wrote:
>
> Hi Mark,
>
> There is a "nodedown" issue in the logs, that means the instance you're
> talking to can't connect to the instance that has the data you are requesting.
>
> Since the name is logged as couchdb@127.0.0.1, it looks like a cluster
> configuration error.
>
> How did you do the upgrade to 2.3?
>
> Cheers
> Jan
> —
>
>> On 31. Jan 2019, at 22:36, Mark Richter <mrich...@solarflare.com> wrote:
>>
>> All DB accesses get this response:
>>
>> {
>> "error": "internal_server_error",
>> "reason": "No DB shards could be opened.",
>> "ref": 1699161575
>> }
>>
>> $ tail /opt/couchdb/couchdb.log
>> [error] 2019-01-31T21:02:17.885747Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/_users.1519191048">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:02:20.934646Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/deployment_db.1545165540">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:02:23.999984Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/alerts_db.1542131962">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:02:27.049062Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/info_db.1542149885">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:02:30.114469Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/flow_db.1542131961">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:02:33.163443Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/event_tags_db.1542149885">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:02:36.195516Z couchdb@127.0.0.1 <0.260.0> --------
>> Could not get design docs for
>> <<"shards/20000000-3fffffff/stat_db.1542131961">>
>> error:{error,{nodedown,<<"progress not possible">>}}
>> [error] 2019-01-31T21:03:00.112876Z couchdb@127.0.0.1 emulator --------
>> Error in process <0.10793.0> on node 'couchdb@127.0.0.1' with exit value:
>> {{nocatch,{error,timeout}},[{fabric_view_changes,send_changes,6,[{file,"src/fabric_view_changes.erl"},{line,192}]},{fabric_view_changes,keep_sending_changes,8,[{file,"src/fabric_view_changes.erl"},{line,82}]},{fabric_view_changes,go,5,[{file,"src/fabric_view_changes.erl"},{line,43}]}]}
>>
>> What did I miss?
>>
>> Mark Richter | Senior Staff Engineer
>> SolarFlare Communications, Inc. | www.Solarflare.com
>> 9444 Waples Street, #170, San Diego, CA 92121
>> Mobile: +1 949-632-8403
>>
>>
>> The information contained in this message is confidential and is intended
>> for the addressee(s) only. If you have received this message in error,
>> please notify the sender immediately and delete the message. Unless you are
>> an addressee (or authorized to receive for an addressee), you may not use,
>> copy or disclose to anyone this message or any information contained in this
>> message. The unauthorized use, disclosure, copying or alteration of this
>> message is strictly prohibited.
