Ask Your Question
0

puppet enterprise error

asked 2016-02-29 09:10:03 -0500

chaitanya gravatar image

Hi All,

I have installed 4.3 puppet enterprise. It was running till yesterday but suddenly it stopped running. Please let me know where to look and what to do.

puppet agent --test error message

Error:

Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140 Info: Retrieving pluginfacts Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'evalgenerate': Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140 Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140 Info: Retrieving plugin Error: /File[/opt/puppetlabs/puppet/cache/lib]: Failed to generate additional resources using 'evalgenerate': Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140 Error: /File[/opt/puppetlabs/puppet/cache/lib]: Could not evaluate: Could not retrieve file metadata for puppet:///plugins: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140 Info: Loading facts Error: Could not retrieve catalog from remote server: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Error: Could not send report: Connection refused - connect(2) for "245.77.154.104.bc.googleusercontent.com" port 8140

Thanks,

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2016-03-02 13:04:55 -0500

chaitanya gravatar image

When I tried to restart the service I faced this issue. Please help me how to solve this.

[root@babam manifests]# service puppetserver start Redirecting to /bin/systemctl start puppetserver.service Failed to start puppetserver.service: Unit puppetserver.service failed to load: No such file or directory. [root@babam manifests]# service pe-puppetserver restart Redirecting to /bin/systemctl restart pe-puppetserver.service Job for pe-puppetserver.service failed because the control process exited with error code. See "systemctl status pe-puppetserver.service" and "journalctl -xe" for details. [root@babam manifests]# journalctl -xe Mar 02 19:00:47 babam bash[8109]: Try 'ps --help <simple|list|output|threads|misc|all>' Mar 02 19:00:47 babam bash[8109]: or 'ps --help <s|l|o|t|m|a>' Mar 02 19:00:47 babam bash[8109]: for additional help text. Mar 02 19:00:47 babam bash[8109]: For more details see ps(1). Mar 02 19:00:47 babam polkitd[586]: Unregistered Authentication Agent for unix-process:8092:18491915 (system bus name :1.571, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, lo Mar 02 19:00:47 babam systemd[1]: pe-puppetserver.service: control process exited, code=exited status=1 Mar 02 19:00:47 babam systemd[1]: Failed to start pe-puppetserver Service. -- Subject: Unit pe-puppetserver.service has failed -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit pe-puppetserver.service has failed.

-- The result is failed. Mar 02 19:00:47 babam systemd[1]: Unit pe-puppetserver.service entered failed state. Mar 02 19:00:47 babam systemd[1]: pe-puppetserver.service failed. Mar 02 19:01:01 babam kernel: SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs Mar 02 19:01:01 babam systemd[1]: Created slice user-0.slice. -- Subject: Unit user-0.slice has finished start-up -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit user-0.slice has finished starting up.

-- The start-up result is done. Mar 02 19:01:01 babam systemd[1]: Starting user-0.slice. -- Subject: Unit user-0.slice has begun start-up -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit user-0.slice has begun starting up. Mar 02 19:01:01 babam systemd[1]: Started Session 265 of user root. -- Subject: Unit session-265.scope has finished start-up -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit session-265.scope has finished starting up.

-- The start-up result is done. Mar 02 19:01:01 babam systemd[1]: Starting Session 265 of user root. -- Subject: Unit session-265.scope has begun start-up -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/...

-- Unit session-265.scope has begun starting up. Mar 02 19:01:01 babam CROND[8119]: (root) CMD (run-parts /etc/cron.hourly) Mar 02 19:01:01 babam run-parts(/etc/cron.hourly)[8122]: starting 0anacron Mar 02 19:01:01 babam run-parts(/etc/cron.hourly)[8128]: finished 0anacron Mar 02 19:01:01 babam run-parts(/etc/cron.hourly)[8130]: starting 0yum-hourly.cron lines 1507-1555/1555 (END) [root@babam manifests]#

edit flag offensive delete link more

Comments

Chaitanya, your output is unfortunately unreadable without linefeeds. if you can fix that, perhaps we can help. Otherwise, just read the output of journalctl and follow the guidelines it gives you.

rnelson0 gravatar imagernelson0 ( 2016-03-03 09:05:18 -0500 )edit
0

answered 2016-03-01 01:27:14 -0500

rajeevsharma gravatar image

Hi Chaitanya,

It seems your puppet agent is not able to talk to master as it is not listening on default port 8140. Did you try restarting your puppet server? service pe-puppetserver restart

once puppet server starts, check nestat -nap | grep 8140 if it is listening on the default port it would be able to connect with agents.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-02-29 09:10:03 -0500

Seen: 836 times

Last updated: Mar 02 '16