[root@localhost data]# cat /root/Stolon/log/stolon_master_keeper_log_240417.log
2024-04-25T07:22:25.707-0400 INFO cmd/keeper.go:1893 exclusive lock on data dir taken
2024-04-25T07:22:25.715-0400 INFO cmd/keeper.go:501 keeper uid {“uid”: “agens0”}
2024-04-25T07:22:25.824-0400 INFO cmd/keeper.go:1002 our db boot UID is different than the cluster data one, waiting for it to be updated {“bootUUID”: “a8ee6132-a931-4ac9-aaad-ed271d40fae1”, “clusterBootUUID”: “74117e31-1fd9-4354-af71-3bb552452ca6”}
2024-04-25T07:22:25.832-0400 ERROR cmd/keeper.go:1004 failed to stop pg instance {“error”: “cannot get instance state: exit status 1”}
2024-04-25T07:22:30.840-0400 INFO cmd/keeper.go:1002 our db boot UID is different than the cluster data one, waiting for it to be updated {“bootUUID”: “a8ee6132-a931-4ac9-aaad-ed271d40fae1”, “clusterBootUUID”: “74117e31-1fd9-4354-af71-3bb552452ca6”}
2024-04-25T07:22:30.851-0400 ERROR cmd/keeper.go:1004 failed to stop pg instance {“error”: “cannot get instance state: exit status 1”}
2024-04-25T07:22:35.871-0400 INFO cmd/keeper.go:1049 current db UID different than cluster data db UID {“db”: “”, “cdDB”: “7aa24f04”}
2024-04-25T07:22:35.871-0400 INFO cmd/keeper.go:1053 initializing the database cluster
2024-04-25T07:22:36.000-0400 ERROR cmd/keeper.go:1079 failed to stop pg instance {“error”: “cannot get instance state: exit status 1”}
[root@localhost data]#
i have later fixed it this error was because i have deployed AgenSQL (PostgreSQL) with other user and installed stolon with root user so they both have different UID’s which were conflicting the master server