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.

Sign up for GitHub

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

Jump to bottom

noproc error when call to gen_server2:call(false, {add_route,Topic,<0.685.0>}, infinity) #446

Closed
Prots opened this issue Feb 5, 2016 · 3 comments
Closed

noproc error when call to gen_server2:call(false, {add_route,Topic,<0.685.0>}, infinity) #446

Prots opened this issue Feb 5, 2016 · 3 comments
Assignees
@emqplus
Labels
BUG Discussion
Milestone
0.16.0

Comments

@Prots
Copy link

Prots commented Feb 5, 2016

Hi @Erylee, I have strange error, when I try to subscribe to MQTT topic with emqttd 0.14.0 or 0.15.0 on the AWS t2.micro

16:11:36.872 [error] gen_server emqttd_pubsub_1 terminated with reason: no such process or port in call to gen_server2:call(false, {add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>}, infinity)
16:11:36.872 [error] CRASH REPORT Process emqttd_pubsub_1 with 0 neighbours exited with reason: no such process or port in call to gen_server2:call(false, {add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>}, infinity) in gen_server2:terminate/3 line 1151
16:11:36.873 [error] Supervisor pubsub_pool_sup had child {emqttd_pubsub,1} started with emqttd_pubsub:start_link(pubsub, 1, #Fun<emqttd_pubsub_sup.2.36068814>, []) at <0.196.0> exit with reason no such process or port in call to gen_server2:call(false, {add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>}, infinity) in context child_terminated
16:11:36.873 [error] gen_server <0.685.0> terminated with reason: {{noproc,{gen_server2,call,[false,{add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>},infinity]}},{gen_server2,call,[<0.196.0>,{subscribe,{<<"aid-0ef8f522-cc23-11e5-9a3d-94de80a3f30e">>,<0.685.0>},[{<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,2}]},infinity]}}
16:11:36.873 [error] CRASH REPORT Process <0.685.0> with 1 neighbours exited with reason: {{noproc,{gen_server2,call,[false,{add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>},infinity]}},{gen_server2,call,[<0.196.0>,{subscribe,{<<"aid-0ef8f522-cc23-11e5-9a3d-94de80a3f30e">>,<0.685.0>},[{<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,2}]},infinity]}} in gen_server2:terminate/3 line 1151
16:11:36.874 [error] Supervisor emqttd_session_sup had child session started with {emqttd_session,start_link,undefined} at <0.685.0> exit with reason {{noproc,{gen_server2,call,[false,{add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>},infinity]}},{gen_server2,call,[<0.196.0>,{subscribe,{<<"aid-0ef8f522-cc23-11e5-9a3d-94de80a3f30e">>,<0.685.0>},[{<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,2}]},infinity]}} in context child_terminated
16:11:36.874 [error] Supervisor 'esockd_connection_sup - <0.563.0>' had child connection started with emqttd_client:start_link([{packet,[{max_clientid_len,1024},{max_packet_size,65536}]},{client,[{idle_timeout,20}]},{session,...},...]) at <0.680.0> exit with reason {{noproc,{gen_server2,call,[false,{add_route,<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,<0.685.0>},infinity]}},{gen_server2,call,[<0.196.0>,{subscribe,{<<"aid-0ef8f522-cc23-11e5-9a3d-94de80a3f30e">>,<0.685.0>},[{<<"mobile/secure/input/21a4816e-cc23-11e5-b505-06777b4a51b9">>,2}]},infinity]}} in context connection_crashed
16:11:36.874 [debug] Supervisor pubsub_pool_sup started emqttd_pubsub:start_link(pubsub, 1, #Fun<emqttd_pubsub_sup.2.36068814>, []) at pid <0.687.0>

But on my local machine it works fine. Could you please help me, thanks.
@emqplus
Copy link
Contributor

emqplus commented Feb 6, 2016

Hi @Prots, please 'grep crasher log/*'. It seems some services crashed when the broker started.

BTW, we could discuss the issue by Skype: feng.emqtt.io

@emqplus emqplus added this to the 0.16.0 milestone Feb 6, 2016
@emqplus emqplus self-assigned this Feb 6, 2016
@Prots
Copy link
Author

Prots commented Feb 8, 2016

Crasher log is empty after start.
The AWS machine is empty, without Erlang. I've just copied release from my workstation and try to run.
With sudo or without - the result is same: start OK, but when try to subscribe - get an error listed below.

@Prots
Copy link
Author

Prots commented Feb 8, 2016

Thanks, @Erylee
The issue was with

%% PubSub
        {pubsub, [
            %% default should be scheduler numbers
             {pool_size, 2}
        ]},

Just set {pool_size, 2} if you use one core server.

@Prots Prots closed this as completed Feb 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@emqplus emqplus

Labels
BUG Discussion
Projects
None yet
Milestone
0.16.0
Development

No branches or pull requests
2 participants
@emqplus @Prots