(Solved) Slashed pnode is unstaking again after troubleshoot

Please follow what the Node Monitor indicates for now.

Ok so the unstaking status is incorrect right

Yes that is correct. The Node Monitor and re-stake queue pool both indicate your pNode is re-staked. Sorry for the confusion.

Appreciate it thanks for ur help

1 Like

The monitor is showing both of my pnodes sync state as “Shard Stall” but i dnt see any shards stalling. Here are a few screenshots

Use each pNode’s web interface to restart Docker.
Wait five minutes.
Refresh the Node Monitor page and check each Node’s status.

If the Nodes still aren’t syncing the assigned shard, use each pNode’s web interface to reboot.
Wait five minutes.
Refresh the Node Monitor page and check each Node’s status.

It’s important to wait five minutes. You need to allow time for your pNode to report its status to the Node Monitor server. The Node Monitor will then in turn update the displayed status. This is not instantaneous. Hence wait five minutes.

1 Like

Ok thanks i have restarted the docker for both pnodes and now they both are showing a sync state of “shard syncing”

1 Like

For both of my nodes the sync state showed “latest” now my sync state shows " beacon syncing" for both pnodes and the assigned shard for each node shows “not syncing”… Is that an issue or is that apart of the process

How long ago did you delete data on this pNode?

Maybe a week ago when i restaked both of my pnodes

Please open a support ticket by messaging @Support.

Can u tell me what my support ticket should consist of? Im not sure if there is a issue or wat the issue is

@Joshuatroutman,

I went ahead and created one for you. Please follow that ticket for more information. Looks like your pNode has an issue and this needs to be looked into further.

Is there data loss for both of my pnodes?.. Wat are my next steps

Please wait for a reply on your support ticket that I created for you. I have someone bringing up this during the daily dev meeting.

Ok appreciate it

1 Like

Only thing i did was restart the docker for both nodes when i realized that the shards assigned to both pnodes showed “not syncing”

1 Like

Both of my pnodes are now showing offline… Should i troubleshoot or should i wait for a response from the support ticket

Let’s just wait. A dev is probably going to want to do a remote session. Let me reach out to one now.

Ok i will wait

1 Like