[GH-ISSUE #1648] web service can't get started after kill -9 #1305

Closed
opened 2026-05-05 12:49:47 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @satbirdd on GitHub (Feb 13, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/1648

What version of frp are you using (./frpc -v or ./frps -v)?
0.31.2

What operating system and processor architecture are you using (go env)?
ubuntu 18.04

Configures you used:
frps.ini
[common]
bind_port = 7000
vhost_http_port = 8080

Steps to reproduce the issue:
1.sudo netstat -apn | grep 8080; kill -9 {{pid}};
2../frps frps.ini
3.

Describe the results you received:
2020/02/13 14:45:13 [I] [service.go:152] frps tcp listen on 0.0.0.0:7000
2020/02/13 14:45:13 [I] [root.go:205] start frps success
2020/02/13 14:45:32 [I] [service.go:392] [a3e6a97d22112889] client login info: ip [183.215.190.171:39112] version [0.31.2] hostname [] os [linux] arch [amd64]
2020/02/13 14:45:33 [I] [tcp.go:63] [a3e6a97d22112889] [ssh] tcp proxy listen port [6000]
2020/02/13 14:45:33 [I] [control.go:445] [a3e6a97d22112889] new proxy [ssh] success
2020/02/13 14:45:33 [I] [tcp.go:63] [a3e6a97d22112889] [web00] tcp proxy listen port [40001]
2020/02/13 14:45:33 [I] [control.go:445] [a3e6a97d22112889] new proxy [web00] success

Describe the results you expected:
2020/02/13 12:23:05 [I] [service.go:152] frps tcp listen on 0.0.0.0:7000
2020/02/13 12:23:05 [I] [service.go:194] http service listen on 0.0.0.0:8080
2020/02/13 12:23:05 [I] [root.go:205] start frps success
2020/02/13 12:23:17 [I] [service.go:392] [722e8b854df8905e] client login info: ip [183.215.190.171:37154] version [0.31.2] hostname [] os [linux] arch [amd64]
2020/02/13 12:23:17 [I] [tcp.go:63] [722e8b854df8905e] [ssh] tcp proxy listen port [6000]
2020/02/13 12:23:17 [I] [control.go:445] [722e8b854df8905e] new proxy [ssh] success
2020/02/13 12:23:17 [I] [tcp.go:63] [722e8b854df8905e] [web00] tcp proxy listen port [40001]
2020/02/13 12:23:17 [I] [control.go:445] [722e8b854df8905e] new proxy [web00] success

Additional information you deem important (e.g. issue happens only occasionally):

Can you point out what caused this issue (optional)

Originally created by @satbirdd on GitHub (Feb 13, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/1648 **What version of frp are you using (./frpc -v or ./frps -v)?** 0.31.2 **What operating system and processor architecture are you using (`go env`)?** ubuntu 18.04 **Configures you used:** frps.ini [common] bind_port = 7000 vhost_http_port = 8080 **Steps to reproduce the issue:** 1.sudo netstat -apn | grep 8080; kill -9 {{pid}}; 2../frps frps.ini 3. **Describe the results you received:** 2020/02/13 14:45:13 [I] [service.go:152] frps tcp listen on 0.0.0.0:7000 2020/02/13 14:45:13 [I] [root.go:205] start frps success 2020/02/13 14:45:32 [I] [service.go:392] [a3e6a97d22112889] client login info: ip [183.215.190.171:39112] version [0.31.2] hostname [] os [linux] arch [amd64] 2020/02/13 14:45:33 [I] [tcp.go:63] [a3e6a97d22112889] [ssh] tcp proxy listen port [6000] 2020/02/13 14:45:33 [I] [control.go:445] [a3e6a97d22112889] new proxy [ssh] success 2020/02/13 14:45:33 [I] [tcp.go:63] [a3e6a97d22112889] [web00] tcp proxy listen port [40001] 2020/02/13 14:45:33 [I] [control.go:445] [a3e6a97d22112889] new proxy [web00] success **Describe the results you expected:** 2020/02/13 12:23:05 [I] [service.go:152] frps tcp listen on 0.0.0.0:7000 2020/02/13 12:23:05 [I] [service.go:194] http service listen on 0.0.0.0:8080 2020/02/13 12:23:05 [I] [root.go:205] start frps success 2020/02/13 12:23:17 [I] [service.go:392] [722e8b854df8905e] client login info: ip [183.215.190.171:37154] version [0.31.2] hostname [] os [linux] arch [amd64] 2020/02/13 12:23:17 [I] [tcp.go:63] [722e8b854df8905e] [ssh] tcp proxy listen port [6000] 2020/02/13 12:23:17 [I] [control.go:445] [722e8b854df8905e] new proxy [ssh] success 2020/02/13 12:23:17 [I] [tcp.go:63] [722e8b854df8905e] [web00] tcp proxy listen port [40001] 2020/02/13 12:23:17 [I] [control.go:445] [722e8b854df8905e] new proxy [web00] success **Additional information you deem important (e.g. issue happens only occasionally):** **Can you point out what caused this issue (optional)**
Author
Owner

@satbirdd commented on GitHub (Feb 13, 2020):

the reason if forgeting to use -c option

<!-- gh-comment-id:585585006 --> @satbirdd commented on GitHub (Feb 13, 2020): the reason if forgeting to use -c option
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#1305
No description provided.