If a service appears normal in the Enterprise Distributed Application Service (EDAS) service list but fails when called, use the following steps to identify the root cause.
Verify group configuration
Check whether the group that corresponds to the service provider is already created. If the group does not exist, authentication between the service consumer and provider fails, which causes call failures.
Open the EDAS console. In the left-side navigation pane, choose Traffic Management > Microservice Governance > HSF. On the Service Query tab, locate the target service.
Check whether the group that corresponds to the service provider is already created.
If the group is not created, create one before you retry the call.
Note: If you use Container 3.0 or later, service group restrictions are removed. You do not need to create service groups. This step applies only to earlier versions.
Check High-speed Service Framework (HSF) error logs
If the group configuration is correct, check the HSF log file at /home/admin/logs/hsf/hsf.log to view the error code. For more information about HSF error codes and solutions, see Locate and solve HSF problems.