Start appium Node siliently

TuHuynh 2017-08-31 03:03:48 UTC #1

Hi all, I got a question, any hints should be appreciated!
I followed this: https://github.com/appium/appium/blob/master/docs/en/advanced-concepts/grid.md#grid-node-configuration-example-json-file
And I could register appium node to my grid perfectly.

But I got a problem! If I close the session which was being used to start appium --nodeconfig /path/to/nodeconfig.json , the appium node down!

Anyone can tell me a way to fix that?
Thank s in advance!

TuHuynh 2017-08-31 12:13:13 UTC #2

Any helps…

TuHuynh 2017-09-01 09:15:45 UTC #3

@pr4bh4sh @Aleksei do you guys have any hints…?

pr4bh4sh 2017-09-01 10:14:12 UTC #4

Did not clearly understand what you want to do. Can you share step by step what are you doing and what are you expecting.

TuHuynh 2017-09-01 10:55:06 UTC #5

Step 01
I created a device.json file with the content followed the format described her: https://github.com/appium/appium/blob/master/docs/en/advanced-concepts/grid.md#grid-node-configuration-example-json-file

Step 02
I executed appium --nodeconfig /path/to/device.json

Everything is ok but once I close the terminal which was being used in the step 02 above, the appium node down.

I’m looking for another way to start it.

harshitj 2017-09-01 11:05:39 UTC #6

Do you want it to run in background and close the terminal ??

Use it like this nohup appium --nodeconfig /Path/to/nodeConfig.json -p 7026 -cp 7026 -bp 7026 --session-override -U emulator-5554_28 &

TuHuynh 2017-09-01 11:15:55 UTC #7

Thank you, but when I close the terminal, the appium node is down…

harshitj 2017-09-01 11:20:20 UTC #8

What is the output when you fired the above command?

is the output like
[1] 2884
appending output to nohup.out

TuHuynh 2017-09-01 11:24:47 UTC #9

That was exactly what I saw, I also checked on the Grid Console and the appium node was registered successfully but after I closed the terminal, it showed failed: Connection refused... on the Grid console. Hence the appium node was not alive node anymore…

pr4bh4sh 2017-09-01 11:29:27 UTC #10

Below thread might have what you are looking for

pr4bh4sh 2017-09-01 11:38:03 UTC #11

@harshitj What a coincidence, Didn’t we just discussed specifically about this yesterday?

harshitj 2017-09-01 11:45:11 UTC #12

Strange…! It always works …

Read more about nohup
http://linux.101hacks.com/unix/nohup-command/

Can you also try it with something else , example: start selenium standalone server

nohup java -jar selenium-server-standalone.jar &

And close the terminal once it started successfully and then check if it remain started

TuHuynh 2017-09-01 11:46:30 UTC #13

I will try to work around it, thanks @harshitj anyway.

harshitj 2017-09-01 12:03:31 UTC #14

@pr4bh4sh Yeah its a coincidence.

TuHuynh 2017-09-01 12:05:59 UTC #15

@harshitj @pr4bh4sh
lol, that’s so funny…

Aleksei 2017-09-01 13:42:21 UTC #16

@TuHuynh

Choices:

why you do not start your node automatically ones you start your test suite.
if you start it in jenkins you can start it as line before starting test suite.

TuHuynh 2017-09-01 15:45:06 UTC #17

[1] My testing structure is really complicated so I don;t want to integrate that step.
[2] I do believe that the rest commands will be stuck for appium....

Aleksei 2017-09-01 17:45:32 UTC #18

@TuHuynh sorry i do not understand how you want to start it… i prefere to start appium server (node in your case) when i start suite. and i am killing all running under port i want to open appium. thus mine appium session is always fresh (just started). and i avoid any issues of stack when it running long time.