invalid magic sessionId 1

[mattn]

2014/07/10 22:14:03 util.go:215: [debug] magic not match 0x30343937
2014/07/10 22:14:03 session.go:58: [debug] invalid magic sessionId 1

I'm trying gearmand on windows7, but when start example/worker/worker, gearman always show an error above.

[ngaut]

which client did you use? and what's the command arguments?

[mattn]

https://github.com/mikespook/gearman-go

example/worker

command line is:

gearmand -storage=sqlite3 -sqlite3=:memory:

This issue occur with redis also.

On 7/10/14, goroutine [email protected] wrote:

which client did you use? and what's the command arguments?

---

Reply to this email directly or view it on GitHub: https://github.com/ngaut/gearmand/issues/7#issuecomment-48607191

• Yasuhiro Matsumoto

[ngaut]

i can't reproduce this problem.

everything works fine. here is my env: D:\study\3rdparty\src\github.com\ngaut\gearmand>gearmand -storage=sqlite3 -sqlit e3=:memory: [martini] Started GET /worker [martini] Completed 200 OK in 1.0001ms

D:\study\3rdparty\src\github.com\ngaut\gearman-go\example\worker>worker.exe 2014/07/10 22:42:42 Starting ...

open browser http://localhost:3000/worker, below is the output: [{"Id":"","canDo":["Foobar","ToUpper","ToUpperTimeOut5","ToUpperTimeOut20","SysInfo","MemInfo"],"runningJobs":[],"sessionId":1,"status":"sleep"}]

[ngaut]

do you have any more details that maybe help me tracking this issue?

[mattn]

I'm using 32bit OS. You too? And I'm on go1.3

On 7/10/14, goroutine [email protected] wrote:

do you have any more details that maybe help me tracking this issue?

---

Reply to this email directly or view it on GitHub: https://github.com/ngaut/gearmand/issues/7#issuecomment-48614887

• Yasuhiro Matsumoto

[ngaut]

oo, i just test 32bit windows xp, still fine. would you please use wireshark to capture tcp packets(port:4730) and send me dump file

[ngaut]

my email: goroutine at 126 dot com

[mattn]

I figured out this issue not on gearmand. It seems to be gearman-go. I tried to run gearmand on linux, and run worker on windows. This problem occur. But if run worker on linux, it works fine. Sorry.