Indexer failing

Couchbase Server
1

Hello.

I have an old Couchbase (5.0.1) that can’t communicate with the indexer for some reason.
It’s installed on a Windows Server 2019 Datacenter 64bit but since you’ve removed documentation for that version I can’t even see if it’s supported.

IndexerWarning
IndexerWarning1374×725 75.7 KB

Log show this:

[goport(g:/Program Files/Couchbase/Server/bin/indexer)] 2023/07/11 09:55:10 child process exited with status 2
2023-07-11T09:55:15.636+02:00 [Info] Indexer started with command line: [g:/Program Files/Couchbase/Server/bin/indexer -vbuckets=1024 -cluster=127.0.0.1:8091 -adminPort=9100 -scanPort=9101 -httpPort=9102 -streamInitPort=9103 -streamCatchupPort=9104 -streamMaintPort=9105 -storageDir=g:/Program Files/Couchbase/Server/var/lib/couchbase/data/@2i -diagDir=g:/Program Files/Couchbase/Server/var/lib/couchbase/crash -nodeUUID=8d4215bd901d0f071917a91ed38e5387 -isEnterprise=false -storageMode=forestdb]
2023-07-11T09:55:15.637+02:00 [Info] Indexer::Cluster Storage Mode Set forestdb
2023-07-11T09:55:15.657+02:00 [Info] Indexer::NewIndexer Status Warmup
2023-07-11T09:55:15.659+02:00 [Info] Setting buffer block size to 16384 bytes
2023-07-11T09:55:15.659+02:00 [Info] Setting maxcpus = 8
2023-07-11T09:55:15.659+02:00 [Info] Setting log level to Info
2023-07-11T09:55:15.659+02:00 [Info] Indexer::NewIndexer Starting with Vbuckets 1024
2023-07-11T09:55:15.659+02:00 [Info] Indexer::NewIndexer Build Mode Set Community
2023-07-11T09:55:15.662+02:00 [Info] New settings received: 
{"indexer.settings.compaction.days_of_week":"Sunday,Monday,Tuesday,Wednesday,Thursday,Friday,Saturday","indexer.settings.compaction.interval":"00:00,00:00","indexer.settings.compaction.compaction_mode":"circular","indexer.settings.persisted_snapshot.interval":5000,"indexer.settings.log_level":"info","indexer.settings.compaction.min_frag":30,"indexer.settings.inmemory_snapshot.interval":200,"indexer.settings.max_cpu_percent":0,"indexer.settings.storage_mode":"forestdb","indexer.settings.recovery.max_rollbacks":5,"indexer.settings.memory_quota":24739053568,"indexer.settings.compaction.abort_exceed_interval":false}
2023-07-11T09:55:15.663+02:00 [Info] Setting maxcpus = 8
2023-07-11T09:55:15.663+02:00 [Info] Setting log level to Info
2023-07-11T09:55:15.681+02:00 [Info] [Queryport ":9101"] started ...
2023-07-11T09:55:15.683+02:00 [Info] Unable to fetch storage mode from metakv during bootrap.  Use storage mode setting for bootstrap
2023-07-11T09:55:15.696+02:00 [Info] bootstrap storage mode forestdb
2023-07-11T09:55:15.760+02:00 [Error] EmbeddedServer.boostrap: error : FDB_RESULT_TOO_BIG_BUFFER_CACHE
panic: close of nil channel

Can’t really figure out why.
I’m attaching full logs.
logs.zip (1.9 MB)

2

Hi @alon.schachter - FYI, we do still support Windows Server 2019: Supported Platforms | Couchbase Docs

Is there a possibility for you to upgrade to a more recent version? 5.0.1 is many, many years old.

FWIW, I can see that error code listed in our code base but it’s not clear to me what would trigger it.

@amit.kulkarni any suggestion?

3

@perry The link you’ve sent is for Couchbase 7.2 not 5.0.1

According to ChatGPT, Couchbase 5.0.1 does not support Windows server 2019 but I am looking for an official answer.
Upgrading might be possible within CB 5 as long as there are no breaking changes but it doesn’t look like we’ll be able to upgrade that particular environment beyond that anytime soon

4

Requesting @sduvuru to respond on forestdb question.

Just by looking at code comments

    /**
     * Buffer cache is too big to be configured because it is greater than
     * the physical memory available.
     */
    FDB_RESULT_TOO_BIG_BUFFER_CACHE = -37,

it looks like memory quota being configured might be too high. Not sure if it is a misconfiguration problem.

1 Like
5

Sorry @alon.schachter , I thought you were asking whether Windows Server 2019 is still supported. I took a look through our docs archive (https://docs-archive.couchbase.com) and it seems that we didn’t start supporting Windows 2019 until version 7.0. Keep in mind that we take a very strict view when it comes to “support”, it’s not just about whether it works or not, but requires us to do extensive QA, etc before we consider something “supported”. It’s quite likely that there’s nothing about Windows Server 2019 that means it won’t work with 5.0.1, just that we didn’t go through the necessary process to officially call it “supported”. Hope that helps.

Either way, keep in mind that 5.0.1 is definitely no longer supported and we strongly encourage you to Upgrade | Couchbase Docs. It will be a bit of a process going from such an old version and you’ll also want to confirm compatibility with the SDK version you’re using.

FWIW, might be a good idea to get some assistance from us and/or look to making a move to Capella if you can which will help avoid getting so far behind in the future.

6

@perry
Thanks for the answer.
We had these discussions with your sales team already.
There is no suitable plan for our needs unfortunately.

We did upgrade to CB 7.2 with newer product versions of ours, but this is a legacy environment that will need to stay legacy for a while.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.