12 identified posts by JamesT, in their original words. Other authors’ replies are not reproduced. Available uploaded images are preserved below each post; original attachment links remain for provenance. Avatars and external link previews are not archived. Historical commands are retained as evidence, not current installation instructions.
JamesT · 2024-07-16 · Post 1
Welcome to the Lite-Node Bug Report forum! The primary function of this forum is to collect reports on issues currently affecting Lite-Nodes. Our goal is that this forum will become an extremely valuable tool to the development team, allowing all of us to help make diode the best network it can be.
The quality assurance team will be monitoring this forum continuously, looking for new issues and then adding them to our bug tracking database.
While you may not see us post here very often, please know that your reports are read and appreciated. In the event that the amount of information in a bug report proves to be insufficient during our investigation, you may be asked for additional information (like your hardware configuration or what time you encountered a specific issue)—so keep an eye out!
Please keep all posts on topic. This means threads should center around bug reports, workarounds, and discussion of impacting issues.
When providing information on a bug report, it is okay to post on an existing thread if your issue is exactly the same as the original post. If you are experiencing a similar issue with slight variations, please create your own topic.
If you find multiple bugs, create a separate thread for each one. While this may seem tedious, it is essential to our workflow as it allows our internal tools track which specific bugs have been investigated and it helps us share the workload among our team.
Do not hijack threads with your new topic. Posting an issue which is similar but different from the original topic means that your request may be missed or the original request ignored.
Please post a subject with a clear summary of your issue. Starting posts with “I need help!” or “Can’t play no matter what” only serves to make your issue harder to resolve.
We understand that emotions can run high while dealing with technical issues, but posting in an abusive or disparaging manner will not be tolerated, and does not advance our goal of providing assistance to the widest audience of customers in this forum.
Please do not post direct contact info for other companies. It is acceptable to post links to websites where contact info can be found, but posting the information here on the forum is not permitted.
As always, community forums work best when all participants treat each other with respect and courtesy before posting.
I wrote a script for listing oom values, Just copy and paste the script into an executable script like oom.sh
#!/bin/bash
# This script retrieves and displays the OOM (Out Of Memory) score and the OOM adjusted score
# for each running process, sorted in descending order by the OOM score.
printf 'PID\tOOM Score\tOOM Adj\tCommand\n'
# Read each process ID and command, check if a corresponding oom_score file exists and its value is not zero.
# If so, print the process ID, OOM score, OOM adjusted score, and command.
while read -r pid comm
do
if [ -f /proc/$pid/oom_score ] && [ $(cat /proc/$pid/oom_score) != 0 ]
then
printf '%d\t%d\t\t%d\t%s\n' "$pid" "$(cat /proc/$pid/oom_score)" "$(cat /proc/$pid/oom_score_adj)" "$comm"
fi
done < <(ps -e -o pid= -o comm=) | sort -k 2nr
example output, this shows my beam.smp is using a lot of cpu, to avoid crashes I activated a swap file
I provisioned a GCP instance and noticed the following. the node picks up the private ip address instead of the public ip when exposed through the firewall on Google Compute Cloud.
try snap set diode-node host=public ip address and it should resolve any issue, I noticed sometimes that it picks up the private ip and doesnt route properly
![[Attachment: Screenshot 2024-07-24 at 23.09.48 — see original post]Screenshot 2024-07-24 at 23.09.481885×206 49.8 KB](https://forum.diode.io/uploads/db7388/original/1X/4fc6cb5845774531138b70b5cbea37154fe71d1d.png){kind=link}