Error in infrasetup

[Farzad Farshchi]

Hi,

I get an error when I run: firesim infrasetup

The following is from infrasetup log file;

2018-10-08 21:40:55,564 [instance_liv] [INFO ]  [192.168.3.180] Checking if host instance is up...

2018-10-08 21:40:55,564 [flush       ] [DEBUG]  [192.168.3.180] run: uname -a

2018-10-08 21:40:55,668 [flush       ] [DEBUG]  Fatal error: Needed to prompt for a connection or sudo password (host: 192.168.3.180), but input would be ambiguous in parallel mode

2018-10-08 21:40:55,668 [flush       ] [DEBUG]  Aborting.

2018-10-08 21:40:55,685 [<module>    ] [ERROR]  Fatal error.

Traceback (most recent call last):

  File "/home/centos/firesim/deploy/firesim", line 302, in <module>

    main(args)

  File "/home/centos/firesim/deploy/firesim", line 251, in main

    globals()[args.task](simconf)

  File "/home/centos/firesim/deploy/firesim", line 68, in infrasetup

    runtime_conf.infrasetup()

  File "/home/centos/firesim/deploy/runtools/runtime_config.py", line 240, in infrasetup

    self.firesim_topology_with_passes.infrasetup_passes(use_mock_instances_for_testing)

  File "/home/centos/firesim/deploy/runtools/firesim_topology_with_passes.py", line 302, in infrasetup_passes

    execute(instance_liveness, hosts=all_runfarm_ips)

  File "/usr/lib64/python2.7/site-packages/fabric/tasks.py", line 420, in execute

    error(err)

  File "/usr/lib64/python2.7/site-packages/fabric/utils.py", line 358, in error

    return func(message)

  File "/usr/lib64/python2.7/site-packages/fabric/utils.py", line 62, in abort

    raise e

SystemExit: 1

I've also attached the full log.

Thank,

Farzad

[Howard Mao]

You should check whether you can SSH from the manager to all of your nodes (including the manager itself) using their private IPs without needing a password. 

--
You received this message because you are subscribed to the Google Groups "FireSim" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firesim+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firesim.
To view this discussion on the web visit https://groups.google.com/d/msgid/firesim/be1df91c-e2c0-44d8-954a-0c94d30c08c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[aleksandar...@gmail.com]

Hello,

I am facing the very same issue Farzad pointed to. This is the first time I am trying to run firesim on AWS, so I hope some help will be provided, as it seems this wasn't solved, at least not in the thread.

I've successfully followed all the steps shown in the firesim instructions, to the point where I successfully run the lunchrunfarm using: firesim launchrunfarm

However, when I do firesim infrasetup - I get exactly the same output like Farzad.

I've tried contacting the instance created by the launchfarm command, however it responds to ping, but I get permission denied for ssh. I repeat that I didn't do anything else neither to the manager nor the instance created by the manager (the one refusing ssh), except the steps given in FireSim docs.

Please, is there any obvious way to sort this out?

Thanks,

Aleksandar

[Sagar Karandikar]

Hi Aleksandar,

This suggests that there is something wrong with the ~/firesim.pem key that you've copied to the instance, which should be used automatically once you've sourced sourceme-f1-manager.sh. Just to confirm, is this the same key that you use to login to the manager instance itself? Are you able to ssh localhost on the manager instance? This is a good way to debug the issue without having to launch any additional instances. When everything is setup properly, you should be able to ssh localhost with no prompt.

-Sagar

To view this discussion on the web visit https://groups.google.com/d/msgid/firesim/2073a0d1-e3d7-40f2-a347-0060814b9057%40googlegroups.com.

[aleksandar...@gmail.com]

Hi Sagar,

thank you so much for taking the time to point me towards the solution.

Yes, as a matter of fact, it turned out that the firesim.pem I was using was the wrong one.

Thanks,

Aleksandar