Hi,
In my case, ConfD7.7.3 was started in the foreground, but it was stuck in the phase0 for too long, at least 3 minutes, the related logs are shown below.
- ConfD phase0 started
devel-c New daemon connected (name: notification_sender, daemon id: 0)
devel-c New worker connected (daemon id: 0 worker id: 10)
devel-c New worker connected (daemon id: 0 worker id: 11)
=ERROR REPORT==== 13-Aug-2022::10:50:43.339043 ===
capi_server:2215: capi_server proto_request exit:{noproc,
{gen_server,call,
[notif_server,
{get_sh,
'DATA-CHANGE'},
infinity]}} for
\u003c\u003c131,104,7,97,170,119,20,69,82,73,67,83,83,79,78,45,68,65,84,65,45,67,72,65,
78,71,69,119,9,117,110,100,101,102,105,110,101,100,104,2,97,19,104,9,98,0,
0,7,230,97,8,97,13,97,10,97,50,97,43,98,0,5,15,97,97,0,97,0,97,0,104,2,119,
4,104,120,109,108,108,0,0,0,1,104,2,108,0,0,0,1,98,38,233,200,50,98,96,85,
251,148,119,4,108,101,97,102,106,106\u003e\u003e
[{gen_server,call,3,[{file,\"gen_server.erl\"},{line,234}]},
{notif_server,send_notification,6,[{file,\"notif_server.erl\"},{line,510}]},
{capi_server,send_notification,7,[{file,\"capi_server.erl\"},{line,2330}]},
{capi_server,socket_request,3,[{file,\"capi_server.erl\"},{line,2212}]},
{capi_server,socket_loop,5,[{file,\"capi_server.erl\"},{line,2140}]},
{proc_lib,init_p_do_apply,3,[{file,\"proc_lib.erl\"},{line,249}]}]
devel-c Internal error on API request
From the application’s point of view, it failed at confd_load_schemas which always returned error -1 during several times tries.
It seems like ConfD needed more memory to use than before, after increasing the assigned memory from default 500Mi to 1Gi, this issue doesn’t occur anymore.
Could you have a look at this issue and give me a hint to find the possible cause? Thanks.