Skip to content
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

It is not working with ARM cpu, Oracle #451

Open
boka003 opened this issue Jan 19, 2025 · 5 comments
Open

It is not working with ARM cpu, Oracle #451

boka003 opened this issue Jan 19, 2025 · 5 comments
Labels
troubleshooting Maybe bug, maybe not

Comments

@boka003
Copy link

boka003 commented Jan 19, 2025

Hello there,

I have installed Beszel on my Oracle ARM VM, and it is working fine at port 8090.
But if i try to add my ARM VM's for monitoring, it will not work.
I have some Ryzen VM's and they are working fine.

`

ubuntu@ch1:~$ curl -sL https://raw.githubusercontent.com/henrygd/beszel/main/sup                                                     plemental/scripts/install-agent.sh -o install-agent.sh && chmod +x install-agent                                                     .sh && ./install-agent.sh -p 45876 -k "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPItw                                                     mURNgWC9hpiGFLKMFTJEVyOgK2MxiGszTTzk0U4"
Creating a dedicated user for the Beszel Agent service...
usermod: group 'docker' does not exist
Creating the directory for the Beszel Agent...
Downloading and installing the agent...
Downloading and installing agent version 0.9.1 from https://github.com ...
######################################################################### 100.0%
Creating the systemd service for the agent...

Loading and starting the agent service...
Created symlink /etc/systemd/system/multi-user.target.wants/beszel-agent.service                                                      → /etc/systemd/system/beszel-agent.service.

Would you like to enable automatic daily updates for beszel-agent? (y/n): Y
Setting up daily automatic updates for beszel-agent...
Created symlink /etc/systemd/system/timers.target.wants/beszel-agent-update.time                                                     r → /etc/systemd/system/beszel-agent-update.timer.

Automatic daily updates have been enabled.

Beszel Agent has been installed successfully! It is now running on port 45876.
ubuntu@ch1:~$ ^C
ubuntu@ch1:~$ sudo systemctl status beszel-agent
● beszel-agent.service - Beszel Agent Service
     Loaded: loaded (/etc/systemd/system/beszel-agent.service; enabled; vendor >
     Active: active (running) since Sun 2025-01-19 12:26:30 UTC; 1min 11s ago
   Main PID: 4123240 (beszel-agent)
      Tasks: 6 (limit: 28690)
     Memory: 5.1M
        CPU: 517ms
     CGroup: /system.slice/beszel-agent.service
             └─4123240 /opt/beszel-agent/beszel-agent

Jan 19 12:26:30 ch1.hosting.eu systemd[1]: Started Beszel Agent Service.
Jan 19 12:26:30 ch1.hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30>
Jan 19 12:26:30 ch1.hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30>
Jan 19 12:26:30 ch1.hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30>
...skipping...
● beszel-agent.service - Beszel Agent Service
     Loaded: loaded (/etc/systemd/system/beszel-agent.service; enabled; vendor >
     Active: active (running) since Sun 2025-01-19 12:26:30 UTC; 1min 11s ago
   Main PID: 4123240 (beszel-agent)
      Tasks: 6 (limit: 28690)
     Memory: 5.1M
        CPU: 517ms
     CGroup: /system.slice/beszel-agent.service
             └─4123240 /opt/beszel-agent/beszel-agent

Jan 19 12:26:30 ch1.hosting.eu systemd[1]: Started Beszel Agent Service.
Jan 19 12:26:30 ch1.hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30>
Jan 19 12:26:30 ch1.hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30>
Jan 19 12:26:30 ch1.hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30>
~
~
~
~
~
~
~
~
~

ubuntu@ch1:~$ sudo lsof -i :45876
COMMAND       PID   USER   FD   TYPE     DEVICE SIZE/OFF NODE NAME
beszel-ag 4123240 beszel    3u  IPv6 1333255145      0t0  TCP *:45876 (LISTEN)
ubuntu@ch1:~$ sudo ufw allow 45876/tcp
Rules updated
Rules updated (v6)
ubuntu@ch1:~$ sudo ufw status
Status: inactive
ubuntu@ch1:~$ telnet ch1.hosting.eu 45876
Trying 127.0.1.1...
Connected to ch1.hosting.eu.
Escape character is '^]'.
SSH-2.0-Go

`

Hosting.eu is example.

@henrygd
Copy link
Owner

henrygd commented Jan 19, 2025

Is the hub also hosted on this machine?

Please check the logs page in PocketBase (/_/#/logs) for information about the connection error and let me know what it says.

@henrygd henrygd added the troubleshooting Maybe bug, maybe not label Jan 19, 2025
@boka003
Copy link
Author

boka003 commented Jan 20, 2025

It is the same if i use the main server (with a hub) or an additional server without hub.

It is working fine on https://fivenines.io/


ubuntu@ch1:~$ sudo journalctl -u beszel-agent -f
Jan 19 12:26:30 ch1.arena-hosting.eu systemd[1]: Started Beszel Agent Service.
Jan 19 12:26:30 ch1.arena-hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30 INFO Detected root device name=sda1
Jan 19 12:26:30 ch1.arena-hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30 INFO Detected network interface name=enp0s6 sent=356146249593 recv=169640840171
Jan 19 12:26:30 ch1.arena-hosting.eu beszel-agent[4123240]: 2025/01/19 12:26:30 INFO Starting SSH server address=:45876

https://prnt.sc/TqwJIsK3JdYy

https://prnt.sc/Z50LsMXnOex4

I can provide you login as this is test server, can ARM CPU be a problem?

@henrygd
Copy link
Owner

henrygd commented Jan 21, 2025

Sure, you can send a login to hank at henrygd.me

ARM CPU should not be a problem. I have an arm64 Oracle VM myself and have not had issues monitoring it, though I did need to unblock the port in the Oracle cloud interface.

@boka003
Copy link
Author

boka003 commented Jan 22, 2025

Thanks i have send it from [email protected]

Hmm i have unblocked ports: https://i.postimg.cc/xC4mVyMP/image-1.png

And it is working fine on fivenines.io for example, but self hosted solution is better :)

@henrygd
Copy link
Owner

henrygd commented Jan 22, 2025

Thanks, took a quick look and it definitely appears to be a network issue.

From the monitoring VM, we can connect to the working system with telnet:

telnet <ip> 45876

This does not work for any of the Oracle VMs. However it does work using port 80:

telnet <ip> 80

This is a strong indication that port 45876 is still being blocked by a firewall.

Try running this directly on one of the Oracle machines:

telnet localhost 45876

If you can connect, the agent is working properly. It's a problem with external connections.

My Oracle VM had iptables active and I had to unblock the port in that as well, so I recommend trying that.

Save your current rules:

sudo iptables-save > ~/ipt.fw

Unblock port 45876:

sudo iptables -I INPUT -p tcp --dport 45876 -j ACCEPT

Then try telnet again from the monitoring VM. Hopefully your agent can now connect. If so, use iptables-persistent to save the rules.

Let me know if this doesn't solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
troubleshooting Maybe bug, maybe not
Projects
None yet
Development

No branches or pull requests

2 participants