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

server crash #5

Open
kailin4u opened this issue Sep 7, 2018 · 3 comments
Open

server crash #5

kailin4u opened this issue Sep 7, 2018 · 3 comments

Comments

@kailin4u
Copy link

kailin4u commented Sep 7, 2018

Hello ,I had a server side shadowtunnel crash, client and server version is v1.1
server cmd:

setsid ./shadowtunnel -u -e -f 127.0.0.1:38080 -l :50000 -p 123456 >shadow.log 2>&1 &

client cmd:

./shadowtunnel -E -U -f x.x.x.x:50000 -l :50000 -p 123456

following is key log from server:

runtime/debug.Stack(0xc42004acc8, 0x6c6dc0, 0x8cd2a0)
/usr/local/go/src/runtime/debug/stack.go:24 +0xa7
github.com/snail007/goproxy/core/dst.NewMux.func2.1()
/home/pengmeng/go/src/github.com/snail007/goproxy/core/dst/mux.go:85 +0x48
panic(0x6c6dc0, 0x8cd2a0)
/usr/local/go/src/runtime/panic.go:502 +0x229
encoding/binary.binary.bigEndian.Uint32(...)
/usr/local/go/src/encoding/binary/binary.go:111
github.com/snail007/goproxy/core/dst.unmarshalHeader(0xc420136000, 0x4, 0x1f4, 0x0, 0x0)
/home/pengmeng/go/src/github.com/snail007/goproxy/core/dst/packets.go:86 +0xcd
github.com/snail007/goproxy/core/dst.(*Mux).readerLoop(0xc420054360)
/home/pengmeng/go/src/github.com/snail007/goproxy/core/dst/mux.go:269 +0x101
github.com/snail007/goproxy/core/dst.NewMux.func2(0xc420054360)
/home/pengmeng/go/src/github.com/snail007/goproxy/core/dst/mux.go:88 +0x47
created by github.com/snail007/goproxy/core/dst.NewMux
/home/pengmeng/go/src/github.com/snail007/goproxy/core/dst/mux.go:82 +0x28f
2018/09/07 02:50:36 14.30.175.184:40483 <--> 127.0.0.1:38080 released

@snail007
Copy link
Owner

snail007 commented Sep 7, 2018

i have testing it on my own notbook , everything is ok, please upload your full log file , so that i can get more message about this error.

@kailin4u
Copy link
Author

kailin4u commented Sep 7, 2018

Thanks for you reply.

I'm sorry the original log was overwritten.

Acually, before those lines,there were lines saying "xxx released" and "xxx connected",nothing special.

@snail007
Copy link
Owner

snail007 commented Sep 7, 2018

if this error occurd againe , keep the log ,and show me .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants