Registration tasks section missing in Registration client menu

21

Hi @Anusha_sunkadh how can I do masterdata sync ?
I can’t send the complete response because it’s too long.

22

Hi @hamid , Can you keep the response JSON in a drive location and share the drive link here? This will help us understand your ID schema and UI specification.

23

Hi @nayakrounak
Here is the link

24

ok @hamid

we’ll check and come back on this

25

The schema and UI spec seem to be correct.

@hamid Start with fresh setup of the registration client, and share the registration client logs here.

26

Hi @Anusha_sunkadh
here is the logs

27

@hamid Based on the logs provided, seems like the “sync_job_def” table is empty or might be all inactive.

Can you check “sync_job_def” table in local derby as well as in mosip_master DB.

28

Hi @Anusha_sunkadh

master.sync_job_def

image
image1520×506 40.5 KB

reg.sync_job_def

image
image1474×342 21.6 KB

29

Hi @Anusha_sunkadh
I’ve added all data in master.sync_job_def into reg.sync_job_def
Now I’m gettin this error when synchronizing data:

image
image1392×605 38 KB

and I still don’t see the buttons.

here is the sync_job_def tables:

master.sync_job_def:

image
image1661×432 36.2 KB

reg.sync_job_def:

image
image1686×359 39 KB

and in reg.sync_transaction I have this:

image
image1010×829 80.1 KB

30

Hi @hamid,

We were able to reproduce the issue in our local.

Kindly delete “.mosipkeys” and “db” folder from your local machine
and add “MANIFEST.MF” file in the registration directory as seen in the below screenshot.

image
image1028×397 56 KB

Content in MANIFEST.MF must be as below
Manifest-Version: 1.2.0

then start the registration-client you should be able to proceed with initial sync.

Server expects clientVersion in sync endpoint as query param to return data compatible with registration client version 1.2.0 or above. If not it returns data w.r.t reg-client versions <= 1.1.5.5

31

Hi @Anusha_sunkadh I did all what you’ve said but I still have the same issue.
here is the logs:

32

@hamid Based on the logs I see clientVersion is still null.

{“@timestamp”:“2023-06-01T14:43:43.013+01:00”,“@version”:“1”,“message”:“Checking for current version completed : null”,“logger_name”:“io.mosip.registration.update.SoftwareUpdateHandler”,“thread_name”:“JavaFX-Launcher”,“level”:“INFO”,“level_value”:20000}

{“@timestamp”:“2023-06-01T14:44:35.899+01:00”,“@version”:“1”,“message”:"UNKNOWN ERROR >> http://dev.mosip.local/v1/syncdata/v2/clientsettings?keyindex=44:13:65:b5:54:90:fa:33:a4:50:9a:48:ef:ed:58:1f:1d:71:1b:3a:96:b9:3a:9e:e9:1d:03:07:ba:ef:cf:94&version&regcenterId=10006

are you sure you followed the steps provided? where did you place the MANIFEST.MF file?

33

Also @hamid,

What is the version of kernel-syncdata-service?
if you are running 1.2.0 reg-client then pls use 1.2.0 kernel-syncdata-service.

Because 1.2.0 reg-client will not send the clientVersion in the server requests but syncdata-service with a version greater than 1.2.0 requires clientVersion.

If you are using kernel-syncdata-service with version > 1.2.0 then kindly use reg-client 1.2.0.1 or above.

Please check this link

thanks,
Anusha

34

Hi @Anusha_sunkadh
I have version 1.2.0 for both syncdata and registration-client.
I’ve deleted .mosipkeys and db folders:
image

And I’ve added MANIFEST.MF as bellow:

image

unfortunately I still have the same issue.

35

Ok, please send the recording or logs (both server and client)

if possible can you try with release-1.2.0.1 version of registration-client and docker.io/mosipid/kernel-syncdata-service:1.2.0.1-B1

36

@Anusha_sunkadh
The problem is that the manifest file is not found.
I’ve hard coded the version as bellow but I still have the issue:

image
image976×433 35.7 KB

{“@timestamp”:“2023-06-02T12:00:48.669+01:00”,“@version”:“1”,“message”:“Checking for current version completed : 1.2.0”,“logger_name”:“io.mosip.registration.update.SoftwareUpdateHandler”,“thread_name”:“Thread-24”,“level”:“INFO”,“level_value”:20000}

37

Please share the complete log file of both server and client.

Also, can you once try copying the MANIFEST.MF file under “registration-client” folder. please revert any of your local changes before trying this.

38

@Anusha_sunkadh here is the logs:

I’ve copied the manifes file into registration-client folder.

39

@Anusha_sunkadh
MANIFEST.MF now is found but I have 401 error here :
“UNKNOWN ERROR >> http://dev.mosip.local/v1/syncdata/v2/clientsettings?keyindex=44:13:65:b5:54:90:fa:33:a4:50:9a:48:ef:ed:58:1f:1d:71:1b:3a:96:b9:3a:9e:e9:1d:03:07:ba:ef:cf:94&version=1.2.0&regcenterId=10006”

image
image1139×568 47 KB

40

ok great,

Kindly check the roles assigned to “mosip-syncdata-client” and “mosip-reg-client” in keycloak.
Below roles are required for mosip-reg-client

Below roles are required for mosip-syncdata-client