Hey @cureau @fiend138 Are you guys still having this issue? There was an update that was just pushed out, can you check with the latest update to see if you are still having this issue? There was a small display issue with nodes not displaying properly which has been fixed.
@fiend138 does the node show offline on the app and on one of our Community-built Node management tools ? Or just in the app?
I have not tested it to see if it still earns. Once I notice the offline status I’ve power cycled the pNode. If the issue persists I will wait and see if it’s still earning. Knowing my luck, that will be the time I have to wait for more than 2 weeks to process a block haha.
Just the app. I haven’t tried any of the community tools. I don’t check my app very often. I look in about once a week or so.
Node status in the app has been a long standing problem. Always use Nito bot or Ensi to check the status of your node. 99.9% of the time, it’s fine.
I have kept track, it greys out on average every 12 days. It does not affect the earning or really do anything more than drive me crazy. I just unplug, count to ten and replug. They have spend some time trying to figure out what is going on but after a year it does not really bother me as much. If your node goes offline for real Nitto bot would tell you. You can sooth your nerves by inquiring node status on Nito by typing : /status
I’m still having this issue with the latest app update (4.0.1) - it happened this morning again. And I confirm - it’s NOT connected with earning finish. I think, it happens with both of my nodes every 7-8 days. Grey status in app, “waiting” status at Node Watcher, Nito and Ensi bots. Could it be some issue with router DHCP lease over or something like that?
Wait, your nodes are grey in the incog app, but say waiting when you look at their status in node watcher, Nito, and Ensi correct? I can check your node status if you provide your public key.
Ok, I have to clear it up. I mean both appear grey in the app not in the same time, it depends on last power cycle time of concrete node. For example, My node 1 was powered on 17th of Jan, became grey in the app last weekend and earned nothing this time. My node 2 was powered on 18th of Jan, earned twice on last Saturday and appeared grey this Monday. And yes - “waiting to be selected” in node watcher, Nito, and Ensi , when it’s grey. When it happens again, I just cycle power and after power up - everything is ok. If you convince me, that I don’t have to do it, ok - next time I try to wait. Should I have to tell support to check it remotely in that grey state?
Why I mentioned DHCP lease? Just my thought.
The status displayed in the app just isn’t reliable. This has been an issue with the project since the beginning.
The app will report your Node offline when your Node is, in fact, NOT offline. The community-built node watch apps such as Nito and ENSI are reliable indicators where the official app is most certainly not reliable.
Thus, if the app is reporting your Node is offline but either (or both) Nito or ENSI are reporting the same Node as Waiting, you may rest assured your Node is online and waiting.
The dev team may try (again) to fix the issue with the app. However there are many tasks on their agenda – including protocol improvements and new features – so it’s anyone’s guess as to when the app status reporting issues will be resolved.
Succintly – use Nito and/or ENSI to monitor the status of your Node. The app is unreliable in this regard.
This ^
Ok, I get it. One more thing to ask.
If node’s power will be shortly cycled in the middle of epoch due to any reasons, could it decrease node’s chance to be randomly selected for the committee somehow? Is node alive time used for chance determination?
No.
When dynamic committee size via slashing is released to mainnet in the near feature, perhaps. But now, the answer is definitively, no.
To be certain – Nodes are selected to committee through a random number generator algorithm.
External factors such as “Node alive time” generally would not affect this random selection. It will be after this random selection, when a (future) Node may be slashed due to criteria such as “node alive time”. To a (future) validator operator, the end result appears identical: the Node did not participate in committee because it failed to meet an online availability threshold (aka “node alive time” in your example). The distinction is important because the slashing criteria does not affect random selection. It will be applied after random selection.
I did not know what most of this means, is there a way to tell me f the node is active by what’s given in the picture? Thank you
Click on watch my node and you will have the answer
Once it is done you should find the status of your node as in the picture:
That is a (useful) service run by a community builder, not by the core team. It is best to visit the post of the builder to ask questions and make suggestions, in case you have some. They will appreciate it and it will keep things in one spot.
I am not using any of the community builder products myself, so I can’t really tell you what the provided information means.
Hello, everyone.
I’ve encountered another pnode offline issue.
I’ve got two nodes on the same home local network. Both of them are configured with wifi and are connected with a lan cable to my home router. I’ve already got used to grey (offline) status in the app, so I haven’t checked my local network for the last two weeks. In the same time Node watcher and Nito bot show me ‘waiting to be selected’ status for both of the nodes.
But yesterday I found out, that Node 1 is not available on the lan. It used two local IP addresses some time before: 192.168.1.60 and 192.168.1.226, one for lan and one for wifi. I’ve also checked node wifi hotspot is also unavailable now. Blue led is on, but it’s offline in app and not available by ping request. This node never earned from the very beginning (it was added on 17th of January), so I can’t tell exactly, when it disappeared from the lan. So I tried to cycle power a few times, no luck there. It’s still offline.
Peter told me, that my pnode (I’ve sent him node id and public key) had been offline since 27th of Jan. As for the wifi/lan config: my wifi router with auto DHCP is directly connected to provider switch with symmetric 100Mb lan channel. I have two clients with static ip among others with dynamic ip, but it’s not for pnodes, nothing specific on config. I use wifi wpa2 with mac filtering, but I use also direct lan cables for pnodes. I have two nodes in my home lan, so other one after power cycle seems ok and online. But the first one stays offline even after few power cycles and now i can’t reach it on the lan. As for the internet - it is fast and rather stable, my home ac power also seems stable. Maybe sometimes router reconnection happens, that’s all. Please, help.
Now I’m pretty sure, that neither Node Watcher nor Nito can determine current pnode status properly. My Node 1 has been offline for a few days, it’s not available on LAN, but it still ‘waiting to be selected’ according to Node Watcher and Nito. I have even powered it off for one hour, it is still ‘waiting to be selected’. So if your node status in app becomes grey you can’t be sure it’s waiting or in hibernation mode, or offline, or anything else.
I’ve even checked with the different router, same problem persists - pnode,connected by lan cable, is offline in the local grid. Power cycling also doesn’t help. I’ve tried connecting my laptop with the direct lan cable to pnode, it shows 1 Gb connection but no response (zero bytes received), BOOTP/DHCP tools can’t see any MAC at the other side.
I’m really stuck for now. I believe this pnode doesn’t boot properly or continuously reboots at power up. Is there any way to check it?
[UPDATE] It’s curious, but my problem Node earned last night three times in a row. Nito informed, that it was pending, and after 1.5 epochs its status (In Nito and Node Watcher) changed to earning, meanwhile the app has still shown grey (offline) during earning. After that it’s still not reachable on the lan (I can’t see it with router console or in dhcp lease list, or using IP scan utilities), and power cycling doesn’t make it green in the app. I really wonder, how it can communicate with the Internet without IP address being assigned. Should I power it off and wait for the next earning? Just joking.
It has already passed 1 month after my Node 1 repair, and it seems OK.
So here is the story:
I was waiting too long for help, so I decided to dissasemble pnode myself and try to diagnose it myself.
After connecting display and keyboard to pnode, I found out, that it hungs at the attempt of ubuntu kernel loading. Even selection of recovery boot variants through Advanced options for Ubuntu ended with same result. At the same time I was able to enter NUC bios, it seems ok. I’ve made few bootable usbs in order to check hardware and software: with ubuntu, acronis disk director, memtest86 and etc. All of them failed to boot at different steps, except memtest86. After running that test, I found out that installed Kingston 4gb 1600 ddr3l sodimm is faulty severely (check screens, memory cells show wrong value comparing to original).
So I took same type ddr3l 1600 8gb hynix sodimm from my laptop, installed it temporary instead of old one and launched same test with it. It completed single run successfully (showed on the memtest screen below with hynix module).
So I tried to boot pnode from built-in ssd - everything is ok now, it appeared in lan and I was able to connect to [IP:5000] by browser, and finally it’s green in app, check the screens! So I’ve bought new 4gb kingston ddr3l sodimm, it’s around $30 here. It’s less expensive than sending it back to Incognito Team, diagnose and then back, and takes less time and shipping risks for sure. I understand, that my warranty is void, but it’s not ok to keep me waiting with damaged equipment for more than one month without proper support. My pnode worked properly only two weeks after delivery (January 17 2021), shame on Kingston. However I requested rebate the sodimm value. Still waiting for it.
In the same time Peter extended the warranty for month since sodimm installation till April 19 2021.
Please keep in mind, if your pnode doesn’t appear in LAN after reboot, it is not a good sign 
. You should send it back to Incognito for check and repair.
This is still happening btw. I’ve had a pNode live for 3 weeks and it has gone down twice (rebooting fixed it). Appears grey in the node list in the app but the blue power light is on, internet is up, monitor reporting up and synced/waiting, so it is very likely just an app UI bug.
Add me to the list of those who experience a grey dot offline status in the incognito app while the node monitor (both in the app and on website https://monitor.incognito.org/node-monitor) indicate vnode is online synced to latest and the vnode still earns rewards normally which confirms it is still connected to the network. It is simply the app displaying the vnode offline when it is definitely online and earning. And even in the app if one goes to monitor detail, vnode is online with latest sync state or sometime Beacon syncing state.
Given all the amazing upgrades the core dev team have just accomplished in V2 and with the node monitor, I consider this a minor issue, but it will disturb and annoy new users. With the helpful node monitor detail, I am not sure those colored dots are even that important now.