mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #3167] x86 ubuntu server 报二进制不可用 #2536
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#2536
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cryyin on GitHub (Nov 11, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3167
Bug Description
cpu是intel7920x,系统ubuntu,下的frp_0.45.0_linux_amd64,报./frpc: ./frpc: cannot execute binary file,之前还跑起来过,中间学校所有server重启后就不行了
frpc Version
0.45.0
frps Version
0.45.0
System Architecture
linux/amd64
Configurations
[7920x-ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 20002
Logs
(base) cshen6@coe379705lws:
/App/frp$ arch/App/frp$ sudo bash ./frpc -c frpc.inix86_64
(base) cshen6@coe379705lws:
./frpc: ./frpc: cannot execute binary file
(base) cshen6@coe379705lws:
/App/frp$ bash ./frpc -c frpc.ini/App/frp$./frpc: ./frpc: cannot execute binary file
(base) cshen6@coe379705lws:
Steps to reproduce
...
Affected area
@cryyin commented on GitHub (Nov 11, 2022):
补充下系统版本:
Welcome to Ubuntu 20.04.5 LTS (GNU/Linux 5.4.0-131-generic x86_64)
System information as of Fri Nov 11 19:05:46 UTC 2022
System load: 0.06 Temperature: 36.0 C
Usage of /home: 9.5% of 365.39GB Processes: 485
Memory usage: 2% Users logged in: 0
Swap usage: 0% IPv4 address for
Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
just raised the bar for easy, resilient and secure K8s cluster deployment.
https://ubuntu.com/engage/secure-kubernetes-at-the-edge