No Remote Connection Available

Eggplant Functional
1

Hello, All.

I’m trying to run a script from the command line via runscript. I can run the script from the GUI just fine, but the second I try to run it via the CLI, I get:

2008-09-22 16:38:56.763 runscript[349:10b] <snip>: failed hostid
2008-09-22 16:38:56.765 runscript[349:10b] <snip>: failed hostid
2008-09-22 16:38:56.775 runscript[349:10b] <snip>: failed hostid
2008-09-22 16:38:56.777 runscript[349:10b] <snip>: failed hostid
2008-09-22 16:38:57.222 runscript[349:10b] <snip>: failed hostid
2008-09-22 16:38:57.223 runscript[349:10b] <snip>: failed hostid
2008-09-22 16:38:57.224 runscript[349:10b] Approved License: Name = <snipped>, Remark = , Serial = <snipity>, Users = 1
runscript (4.12) running in FULL mode on Host:cbaf5b82.
2008-09-22 16:38:58.294 runscript[349:10b] No Remote Connection:
movetoeach Error - Remote Connection Unavailable
2008-09-22 16:38:59.296 runscript[349:10b] Completed EggplantTestScript PerformanceSM.suite - PartialPerformanceMaster.script
eggplanttd2:EggplantScripts qalab$

The moveToEach is the first action the script performs (to wake from screen saver). The connect command works just fine from the GUI. Any idears?

Thanks

2

So, a couple of questions:

  • is the command line being run from the same account as the GUI session?
  • are you sure the connect command in the script is being executed? if so, is it using an IP address, or name from your Connection List?
  • what does it show in the log for the failed run?

Maybe one of those will help turn up something…

3

[quote=“SenseTalkDoug”]So, a couple of questions:

  • is the command line being run from the same account as the GUI session?[/quote]
    Yes.

I believe so. I’m using a name from the connection list

[quote=“Finally, SenseTalkDoug said”]

  • what does it show in the log for the failed run?[/quote]

2008-09-22 16:38:58.294 runscript[349:10b] No Remote Connection: 
movetoeach Error - Remote Connection Unavailable
4

Actually, what I was looking for was the log file for the run. That will show all of Eggplant’s actions related to the SUT, including any Connect commands that were run.

Keep in mind that when you run Eggplant through the GUI you may have a connection open already, and your script can run against that connection. When you run from the command line, Eggplant doesn’t automatically reconnect to any SUTs that were open in the GUI, so you’ll need to either supply the connection information on the runscript command line, or else include a Connect command within the script.

If your script executes a Connect command, it will log if it succeeds in connecting. Any Disconnect commands will also be logged, so examining the log for the run should provide some clues to what’s going on.