Rachel's Yard

| A New Continuation

Let say that you created a network, and it contains owner UUID. But if you edit the network via AdminUI and empty out the owner UUID, network API (napi) is going to greet you with a nasty 500 Internal Error message.

To fix this problem, we are going to do an open heart surgery. There is no way to fix the problem via AdminUI and/or napi. We need to login to Manatee and manually delete the troublemaker.

DISCLAIMER: ALWAYS BACKUP BEFORE DOING ANYTHING STUPID/POTENTIALLY DANGEROUS/DESTROYING THE WHOLE UNIVERSE. YOUR WARRANTY IS NOW VOIDED.

If you only have one Manatee instance, just do sdc-login manatee0 on the headnode.

But if you are like me doing HA ZooKeeper+HA Manatee, you need to find out which instance is the primary instance, run manatee-adm status | json and see which IP is running the primary.

Once you are in the Manatee node, run:

1
2
3
4
su - postgres
psql
\connect moray
select * from public.napi_networks;

Take a note of the _key and _id of the network causing the problem. We are going to delete it: delete from napi_networks where _id=[id];

Next, drop table napi_ips_[_key];

Now you should be good. AdminUI is not showing Load Error, and napi should now be functional again.

Weightless Theme
Rocking Basscss
RSS