Issues communicating with minion

524 views
Skip to first unread message

Hera

unread,
Dec 8, 2014, 5:46:46 AM12/8/14
to salt-...@googlegroups.com
Hi,

I am new to salt. I am having an issue connecting to my minion. My minion is an aws ec2 instance that I provision using salt-cloud. To do this I followed the steps explained here:
https://pelle.io/provision-ec2-with-tomcat-and-deploy-a-web-application-using-salt/
After I successfully provision an aws ec2 instance I tried to send commands to my minion.
Here are the commands, with their results:
From the master side:
1.
 salt-key -L
Accepted Keys:
myminion
Unaccepted Keys:
Rejected Keys:

2.
salt -v '*' test.ping
Executing job with jid 20141208113834907796
-------------------------------------------

myminion:
    Minion did not return. [No response]

3.
salt '*' test.ping -l debug
[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: <my user name>
[DEBUG   ] Missing configuration file: ~/.saltrc
[DEBUG   ] Configuration file path: /etc/salt/master
[DEBUG   ] Reading configuration from /etc/salt/master
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: <my user name>
[DEBUG   ] Missing configuration file: ~/.saltrc
[DEBUG   ] MasterEvent PUB socket URI: ipc:///var/run/salt/master/master_event_pub.ipc
[DEBUG   ] MasterEvent PULL socket URI: ipc:///var/run/salt/master/master_event_pull.ipc
[DEBUG   ] LazyLoaded local_cache.get_load
[DEBUG   ] get_iter_returns for jid 20141208114954513187 sent to set(['myminion']) will timeout at 11:49:59.515437
[DEBUG   ] MasterEvent PUB socket URI: ipc:///var/run/salt/master/master_event_pub.ipc
[DEBUG   ] MasterEvent PULL socket URI: ipc:///var/run/salt/master/master_event_pull.ipc
[DEBUG   ] Checking whether jid 20141208114954513187 is still running

4.
salt-run manage.status
down:
    - myminion
up:

I would also like to point out that I ran the following command to open the ports:
 ufw allow salt

From the minion side:
1.
salt-minion -l debug
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] Configuration file path: /etc/salt/minion
[INFO    ] Setting up the Salt Minion "myminion"
[DEBUG   ] Created pidfile: /var/run/salt-minion.pid
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] Attempting to authenticate with the Salt Master at <myIp>
[DEBUG   ] Loaded minion key: /etc/salt/pki/minion/minion.pem
[ERROR   ] Attempt to authenticate with the salt master failed

Note: The OS for both the master and the minion are ubuntu

Any help would be greatly appreciated! Thank you for your time.

Best Regards,

Hera

Colton Myers

unread,
Dec 16, 2014, 12:44:10 PM12/16/14
to salt-...@googlegroups.com
Hrm, strange.

I guess the first step I would take is to run `salt-key -d myminion` on the master to delete the minion's key. Then restart the minion, and then run `salt-key -a myminion` on the master to accept the key again.

See if that resolves your problem, I'm curious if it's a key issue or some other issue.

--
Colton Myers
Platform Engineer, SaltStack
@basepi on Github/Twitter/IRC

--
You received this message because you are subscribed to the Google Groups "Salt-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salt-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc
Reply all
Reply to author
Forward
0 new messages