Issue #11510 has been reported by System Administrator.

----------------------------------------
Bug #11510: [PE] - [Ubuntu 10.04LTS] - MCollective daemon not binding a network 
socket
https://projects.puppetlabs.com/issues/11510

Author: System Administrator
Status: Unreviewed
Priority: Normal
Assignee: 
Category: agent
Target version: 
Affected Puppet version: 
Keywords: 
Branch: 


I've just installed PE using on Ubuntu 10.04 LTS using 
**puppet-enterprise-2.0-ubuntu-10.04-amd64.tar.gz** (downloaded from 
http://puppetlabs.com/misc/pe-files/) and right now the same machine is running 
the master, the console, and the agent roles.

I seem to have an issue with the MCollective server, which even though it seems 
to be starting fine, doesn't open up **port 61613** as it should.

Daemon starting fine
<pre>
$ sudo /etc/init.d/pe-mcollective start
 * Starting mcollective daemon                  [ OK ] 
</pre>

Showing up is PS
<pre>
$ ps aux | grep mcol | grep -v grep
root     25636  0.0  0.5  64680 12056 ?        S    07:21   0:00 
/opt/puppet/bin/ruby /opt/puppet/sbin/mcollectived --pid 
/var/run/pe-mcollective.pid
</pre>

Pid file contains correct value
<pre>
$ sudo cat /var/run/pe-mcollective.pid
25636
</pre>

However I don't see any process listening on port 61613
<pre>
$ sudo netstat -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
PID/Program name
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      
2395/mysqld     
tcp        0      0 127.0.0.1:11211         0.0.0.0:*               LISTEN      
25542/memcached 
tcp        0      0 0.0.0.0:8140            0.0.0.0:*               LISTEN      
25620/pe-httpd  
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      
10096/apache2   
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      
2345/sshd       
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      
2822/master     
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      
25620/pe-httpd  
</pre>

When I look at the logs I see errors in both mcollective server and client logs
<pre>
$ sudo tail -f /var/log/pe-*/*
==> /var/log/pe-puppet-dashboard/mcollective_client.log <==
I, [2011-12-20T07:26:22.731870 #30944]  INFO -- : stomp.rb:79:in 
`on_connectfail' Connction to 
stomp://[email protected]:61613 failed on attempt 1646

==> /var/log/pe-mcollective/mcollective.log <==
I, [2011-12-20T07:26:24.852641 #25636]  INFO -- : stomp.rb:79:in 
`on_connectfail' Connction to 
stomp://[email protected]:61613 failed on attempt 20
</pre>

When I inspect the mcollective ruby script **/opt/puppet/sbin/mcollectived** I 
can see it references the configuration file 
**/etc/puppetlabs/mcollective/server.cfg** which has the following 
configuration directives:
<pre>
plugin.stomp.pool.size = 1
plugin.stomp.pool.host1 = puppetmaster.example.org
plugin.stomp.pool.port1 = 61613
plugin.stomp.pool.user1 = mcollective
plugin.stomp.pool.password1 = ***************
plugin.stomp.pool.ssl1 = true
plugin.stomp.base64 = true
</pre>

I can resolve **plugin.stomp.pool.host1**, if I change 
**plugin.stomp.pool.port1** for instance to 61614 I see it reflected in the 
**mcollective.log** errors mentioned above. I set **loglevel = debug** but it 
doesn't give me more hints. I run the script manually (/opt/puppet/bin/ruby 
/opt/puppet/sbin/mcollectived) but it doesn't give me any clue either.

**Q: How can I troubleshoot this issue further?** 




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to