-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device becomes unavailable (PCIe version) #230
Comments
The logs are full of (unrelated) spam
|
Found Tailscale hogging the memory, while it itself was dead. Tailscale is known to be a big blob on low-end devices. Possibly could be worked around with using swap (will wear out the SD/TF card, edit: does not 'solve' the problem). edit: Reproducible by transferring 'larger' data via Tailscale, ie rsync from/to device. |
Maybe adding more memory to the hardware would be a better idea in the long run. |
On the surface, I was not able to replicate your experience with my PCIe card. Unfortunately though, I don't think it is an apples to apples comparison because I am not using tailscale and both virtual disk and network are disabled. When I went back to my console after being left 30 minutes idle, it was still responsive. To be clear, I have my own problems with random HID issues, so I am not saying its perfect. I think where we have overlap is that I have noticed that on occasion, I will connect to the console and it will be unresponsive to HID input. The video is working, but HID is unresponsive and even with soft reboot remains unresponsive. While I love the concept of this card and having it all bundled up in a board in my system, it seems flaky. While probably completely unrelated, I have no removed the board from a PCIe slot, taped up the 1x connector and have it mounted in an expansion slot, but its just dangling, just drawing power from external power via 5v USBC and it seems to be fine so far (knock on wood). |
HID issues are likely by bad design, the usb-c on the card needs to be in a specific position (hot glue it). Contact support for claims or open another issue. This is not a forum, it's a bug tracker. |
I am having the same issue. Came with latest firmware, worked for 20-30 min and now refuses any connection via port 80 UI. |
Is this with tailscale enabled? (just because it seemed to be a point of contention before) |
This is without any changes. Received the unit today, installed it, logged into the UI, checked for updates (none where found) and had one KVM session that I left open. Device is now just pingable and I can log into it using SSH (but it does not seem to accept my user / password combination). As I cannot reach the device now, I have no idea what is enabled / disabled. Update: using root / root with SSH worked. Tailscale seems to be running (but I did not configure anything): 556 root /usr/sbin/tailscaled --state=/var/lib/tailscale/tailscaled.state |
I manually rebooted the device via SSH and it seems to be working for now...weird In the bugged state, tailscaped showed 771% CPU usage and 1.2G of RAM usage: |
LAN SSH stays available. The device does not recover without removing power. When trying to use again right away, it dies after two minutes.
Temps are not abnormal, otherwise I'd suspect overheating.
/var/log/messages
doesn't have anything.Latency while idle is 40 ms, before loss of communication, it jumps to 200-300 ms. Is there any watchdog?
Possibly related: #226, #172, #160, #193
Now it dies on its own, even on idle:
GitHub Etiquette
The text was updated successfully, but these errors were encountered: