Advanced Search

JT wrote:

The OS is Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-216-generic x86_64)

JT

NWE wrote:

Maybe install btop, then you can watch a lot more stuff, including network and disk usage. When I learned of btop, I pretty much dropped using top because btop is sorta nice. sudo apt install btop

hope that helps
 

root@forum:~# man btop
No manual entry for btop
root@forum:~# apt install btop
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package btop

tommylight wrote:

Log in to SSH, start "top" and monitor CPU usage and see if "log" appears often near the top of the screen.
If high CPU usage and no logs = DDOS
If both = brute force = someone trying to find user passwords using automated software
-
We had no brute force for quite a while as the result of that was the influx of existing member accounts being hijacked and used to post spam.
Or also possible, users using stronger passwords so much harder to crack. This is highly likely as nowadays wherever you register there are several warnings to use stronger mixed passwords.
 

This kindof makes a mess if you want to use sheet cam or something similar.

aswell as theres not really a great way to run sheetcam via linux as far a i know.

-what should i monitor for the issue where the machine moves to a cut position and just stays there? This happens sometimes even when doing a manual cut where pressing F9 shows the machine running on screen but nothing moves. DRO does not change, machine state does. Again this happens a lot on QtPlasmaC, do not recall this happening on PlasmaC so might be a QT thing.

Again, I'd want to know if motion.eoffset-limited goes true when this occurs. I am also curious what state it's stuck in, so I would want you to turn on plasmac.debug-print before starting any cutting, etc. and copy and paste the terminal output from when it hung up.

• update tooltips to included missing GUI elements and remove duplicate translations
• fix RFL string comparisons
• fix interlock for Material Parameters
• add z-motion watchdog to GUI to catch any state-change hang ups not caught by monitoring motion.eoffset-limited

• monitor motion.eoffset-limited to determine if the commanded motion is outside of the soft limits

tommylight wrote:

JT wrote:

Also, from time to time the forum has high CPU usage that slows down the forum but I don't know why.

DDOS and "brute force" attacks, from what i gathered.