Something went wrong with the Eventing service

Eventing
1

I’m just getting started with eventing. After updating and deploying a function, It just displays “Something went wrong with the Eventing service.” and wont’ list the functions or let me add a new one. I’ve tried stopping and starting the Couchbase service and it remains the same. I do see the following in the debug.lo which seems to imply the eventing service isn’t running, but it gives no indication as to what is wrong. Where do I go from here?

[ns_server:debug,2019-10-13T10:05:43.978-04:00,ns_1@127.0.0.1:service_stats_collector-eventing<0.446.0>:service_stats_collector:check_status:346]Checking if service service_eventing is started…
[ns_server:debug,2019-10-13T10:05:44.357-04:00,ns_1@127.0.0.1:json_rpc_connection-eventing-cbauth<0.5108.0>:json_rpc_connection:init:73]Observed revrpc connection: label “eventing-cbauth”, handling process <0.5108.0>
[ns_server:debug,2019-10-13T10:05:44.357-04:00,ns_1@127.0.0.1:menelaus_cbauth<0.332.0>:menelaus_cbauth:handle_cast:102]Observed json rpc process {“eventing-cbauth”,<0.5108.0>} started
[ns_server:debug,2019-10-13T10:05:44.361-04:00,ns_1@127.0.0.1:json_rpc_connection-eventing-cbauth<0.5108.0>:json_rpc_connection:handle_info:129]Socket closed
[ns_server:debug,2019-10-13T10:05:44.361-04:00,ns_1@127.0.0.1:menelaus_cbauth<0.332.0>:menelaus_cbauth:handle_info:137]Observed json rpc process {“eventing-cbauth”,<0.5108.0>} died with reason shutdown
[error_logger:error,2019-10-13T10:05:44.361-04:00,ns_1@127.0.0.1:error_logger<0.6.0>:ale_error_logger_handler:do_log:203]Supervisor received unexpected message: {ack,<0.5108.0>,{error,shutdown}}

[ns_server:debug,2019-10-13T10:05:45.993-04:00,ns_1@127.0.0.1:service_stats_collector-eventing<0.446.0>:service_stats_collector:check_status:346]Checking if service service_eventing is started…
[ns_server:error,2019-10-13T10:05:46.369-04:00,ns_1@127.0.0.1:service_status_keeper_worker<0.417.0>:rest_utils:get_json_local:63]Request to (eventing) api/v1/functions failed: {error,
{econnrefused,
[{lhttpc_client,
send_request,1,
[{file,
“c:/Jenkins/workspace/couchbase-server-windows/couchdb/src/lhttpc/lhttpc_client.erl”},
{line,220}]},
{lhttpc_client,execute,9,
[{file,
“c:/Jenkins/workspace/couchbase-server-windows/couchdb/src/lhttpc/lhttpc_client.erl”},
{line,169}]},
{lhttpc_client,request,9,
[{file,
“c:/Jenkins/workspace/couchbase-server-windows/couchdb/src/lhttpc/lhttpc_client.erl”},
{line,92}]}]}}
[ns_server:error,2019-10-13T10:05:46.369-04:00,ns_1@127.0.0.1:service_status_keeper-eventing<0.434.0>:service_status_keeper:handle_cast:119]Service service_eventing returned incorrect status

2

Hi @Tim_Arheit,

A few questions:

What version of the Couchbase Server are you trying? And what is the version of Windows it is running on?

Does an eventing.log file get written, and if yes, can you share the contents of it?

If you don’t see eventing.log, can you please upload a cbcollect from the Couchbase Console (please use tim_arheit as customer name) and let me know.

Thank you,
Siri

3

Version: Enterprise Edition 6.0.2 build 2413
Windows 10 (I believe it’s up to date)

eventing.log does exist though it doesn’t seem to have been updated since the problem occurred. I’ve dropped the evening.log file here: https://www.dropbox.com/s/mhp616pg8d9ylij/eventing.log?dl=0

I’ve also updated a cbcollect.

Thanks,
Tim

4

Yes, to the extent of the old logged messages, I don’t see any problem in the eventing.log file. I will look at the cbcollect to dig deeper what may have gone wrong.

Note - You can reset eventing to a clean state using “cbevent.exe” command that comes with the install, in the “bin” directory. If you run “cbevent -flush”, it will remove all event handlers and reset. This can be run on any node.

Thanks,
Siri

5

I ran cbevent and it appeared to delete the event and also restarted the Couchbase service, but it still is showing the same error message. “Something went wrong with the Eventing service.”
This is just for development so there is only one node.

Output of cbevent:
2019/10/13 18:25:56 Deleted /eventing/apps/OnUpdate/0
2019/10/13 18:25:56 Deleted /eventing/apps/ReportProcess/0
2019/10/13 18:25:56 Deleted /eventing/appsettings/ReportProcess
2019/10/13 18:25:56 Deleted /eventing/checksum/OnUpdate
2019/10/13 18:25:56 Deleted /eventing/checksum/ReportProcess
2019/10/13 18:25:56 Skipping deletion of /eventing/config/keepNodes
2019/10/13 18:25:56 Skipping deletion of /eventing/rebalanceToken/5304b5013aee8af3ecb694f6ffc596ce
2019/10/13 18:25:56 Skipping deletion of /eventing/settings/config
2019/10/13 18:25:56 Deleted /eventing/tempApps/ReportProcess/0
2019/10/13 18:25:56 Deleted /eventing/tempchecksum/ReportProcess
2019/10/13 18:25:57 Asking eventing on node https://localhost:18096/die to die
2019/10/13 18:25:59 Ignoring error asking eventing on node localhost:18096 to die: Get https://localhost:18096/die: dial tcp [::1]:18096: connectex: No connection could be made because the target machine actively refused it.

I’m assuming the last line/error wasn’t a problem deleting it, eventing simply wasn’t running.

Thanks,
-TIm

6

@Tim_Arheit , sorry for my late response. I’d need to see the cluster log files to help further. If you go to the Logs section of the Couchbase Console, you’ll see option to collect logs and upload it. If you do so with your username as the customer name and let me know, I can help further.

Thank you,
Siri