Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title
Venkat commented on PUP-7056
Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Earlier linux config was using iso-8859-1 and the current config has utf-8
I changed from output.split(splitstr).each do |line| to output.force_encoding("iso-8859-1").split(splitstr).each do |line|
This worked. Thanks Closing the ticket
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Venkat commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 Sorry, it didn't paste that correctly. All the lines preceded with numbers are supposed to be commented with #. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title
Venkat commented on PUP-7056
Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Thanks Josh, I will upgrade the facter and try ?
So, here is what I did to move further with the existing facter itself ( just for now to understand the implications) This is progressing the deployment further, but not sure of the other impacts. Any suggestions here ?
def self.dmi_find_system_info(name) splitstr= Facter.value(:kernel) == 'SunOS' ? "ID SIZE TYPE" : /^Handle/ output = self.get_dmi_table() return if output.nil? name.each_pair do |key,v| v.each do |v2| v2.each_pair do |value,facterkey|
output.split(splitstr).each do |line|
if line =~ /# {key}
/ and line =~ /\n\s+# {value}
(.+)\n/
result = $1.strip
Facter.add(facterkey) do
confine :kernel => [ :linux, :freebsd, :netbsd, :sunos, :"gnu/kfreebsd", :dragonfly ]
setcode do
result
end
end
end
end end end end end
Add Comment
Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Venkat commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 I am using centOS based Fuel Jump Server with ARM64 based Fuel nodes using Ubuntu 14.04 + 4.7.0-2 Kernel. Here is the /etc/default/locale content cat /etc/default/locale Created by cloud-init v. 0.7.5 on Wed, 04 Jan 2017 09:35:22 + LANG="en_US.UTF-8" Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Venkat commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 Above log was detailed. The high level error is as below and stops the deployment Error Deployment has failed. All nodes are finished. Failed tasks: Task[rsync_core_puppet/7], Task[rsync_core_puppet/6] Stopping the deployment process! Ruby version used : ruby 1.9.3p484 (2013-11-22 revision 43786) [aarch64-linux] Facter version used : 1.7.5 Pl. let me know. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Venkat commented on PUP-7056 Re: Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 Hi Henrik, Thanks for the response. I am using Ubuntu 14.04 Trustry + 4.7.0-2 Kernel. Thanks -Venkat Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7056) Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8
Title: Message Title Venkat created an issue Puppet / PUP-7056 Could not retrieve facts for node-5.domain.tld: invalid byte sequence in UTF-8 Issue Type: Bug Affects Versions: PUP 3.8.5 Assignee: Unassigned Components: Language Specification Created: 2017/01/02 8:42 PM Priority: Blocker Reporter: Venkat Hi, I am trying to deploy Fuel-OpenStack with OPNFV. I got the below error while deploying OPNFV. The version of Puppet is Puppet v3.8.5. Could someone let me know the resolution on this ? 2017-01-03 02:38:07 ERR /usr/bin/puppet:8:in `' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:92:in `execute' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:146:in `run' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `run' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/util.rb:496:in `exit_on_fail' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block in run' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:507:in `plugin_hook' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/application.rb:381:in `block (2 levels) in run' 2017-01-03 02:38:07 ERR /usr/lib/ruby/vendor_ruby/puppet/application/apply.rb:159:in `run_command' 2017-01-03 02:38:07 ERR
Jira (PUP-6666) Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Title: Message Title Venkat updated an issue Puppet / PUP- Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details. Change By: Venkat Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6666) Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Title: Message Title Venkat updated an issue Puppet / PUP- Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details. Change By: Venkat Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6666) pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Title: Message Title
Venkat updated an issue
Puppet / PUP-
pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Change By:
Venkat
I have installed the puppet enterprise in my HyperV Box, testing out some trails for my department in eBay It security, to manage the Linux client machines. I have been getting lots and loads of issues. This is the issue that I am facing for now. I have some how able to install the PE in Centos7, and I was able to attach some nodes. As soon I restart the server I was getting the #502 bad gateway error, but some how i fixed it and was running smoothly. The second time I restarted it throwing me the below error. I am not able to restart the service it's not allowing me to do so. I really need some permanent fix for this. Please.Redirecting to /bin/systemctl status pe-nginx.service● pe-nginx.service - pe-nginx - Puppet Enterprise web server Loaded: loaded (/usr/lib/systemd/system/pe-nginx.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-08-31 15:59:05 CDT; 17min ago Docs: http://docs.puppetlabs.com/pe/latest/index.htmlAug 31 15:59:05 puppetcentos systemd[1]: Starting pe-nginx - Puppet Enterprise web server...Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/opt/puppetlabs/server/data/console-se...smatch)Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: configuration file /etc/puppetlabs/nginx/nginx.conf test failedAug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service: control process exited, code=exited status=1Aug 31 15:59:05 puppetcentos systemd[1]: Failed to start pe-nginx - Puppet Enterprise web server.Aug 31 15:59:05 puppetcentos systemd[1]: Unit pe-nginx.service entered failed state.Aug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service failed.Hint: Some lines were ellipsized, use -l to show in full.[root@puppetcentos puppet]# service pe-nginx startRedirecting to /bin/systemctl start pe-nginx.serviceJob for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details. [root@puppetcentos puppet]# systemctl --all | grep pe- session-c1.scopeloadedactive abandonedSession c1 of user pe-activemq pe-activemq.service loadedactive running Puppet Enterprise ActiveMQ pe-console-services.service loadedactivating start-post start pe-console-services Service● pe-nginx.serviceloadedfailed failed pe-nginx - Puppet Enterprise web server pe-orchestration-services.service loadedactive running pe-orchestration-services Service pe-postgresql.service loadedactive
Jira (PUP-6666) Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Title: Message Title Venkat updated an issue Puppet / PUP- Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details. Change By: Venkat Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6666) Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Title: Message Title
Venkat updated an issue
Puppet / PUP-
Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Change By:
Venkat
I have installed the puppet enterprise in my HyperV Box, testing out some trails for my department in eBay It security, to manage the Linux client machines. I have been getting lots and loads of issues. This is the issue that I am facing for now. I have some how able to install the PE in Centos7, and I was able to attach some nodes. As soon I restart the server I was getting the #502 bad gateway error, but some how i fixed it and was running smoothly. The second time I restarted it throwing me the below error. I am not able to restart the service it's not allowing me to do so. I really need some permanent fix for this. Please.Redirecting to /bin/systemctl status pe-nginx.service● pe-nginx.service - pe-nginx - Puppet Enterprise web server Loaded: loaded (/usr/lib/systemd/system/pe-nginx.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-08-31 15:59:05 CDT; 17min ago Docs: http://docs.puppetlabs.com/pe/latest/index.htmlAug 31 15:59:05 puppetcentos systemd[1]: Starting pe-nginx - Puppet Enterprise web server...Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/opt/puppetlabs/server/data/console-se...smatch)Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: configuration file /etc/puppetlabs/nginx/nginx.conf test failedAug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service: control process exited, code=exited status=1Aug 31 15:59:05 puppetcentos systemd[1]: Failed to start pe-nginx - Puppet Enterprise web server.Aug 31 15:59:05 puppetcentos systemd[1]: Unit pe-nginx.service entered failed state.Aug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service failed.Hint: Some lines were ellipsized, use -l to show in full.[root@puppetcentos puppet]# service pe-nginx startRedirecting to /bin/systemctl start pe-nginx.serviceJob for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.[root@puppetcentos puppet]# systemctl --all | grep pe- session-c1.scopeloadedactive abandonedSession c1 of user pe-activemq pe-activemq.service loadedactive running Puppet Enterprise ActiveMQ pe-console-services.service loadedactivating start-post start pe-console-services Service● pe-nginx.serviceloadedfailed failed pe-nginx - Puppet Enterprise web server pe-orchestration-services.service loadedactive running pe-orchestration-services Service pe-postgresql.service
Jira (PUP-6666) Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Title: Message Title Venkat updated an issue Puppet / PUP- Job for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details. Change By: Venkat Summary: Job for pe-nginx.service loaded failed failed because the control process exited with error code. See "systemctl status pe-nginx .service" and "journalctl - Puppet Enterprise web server xe" for details. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6666) pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Title: Message Title
Venkat updated an issue
Puppet / PUP-
pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Change By:
Venkat
I have installed the puppet enterprise in my HyperV Box, testing out some trails for my department in eBay It security, to manage the Linux client machines. I have been getting lots and loads of issues. This is the issue that I am facing for now. I have some how able to install the PE in Centos7, and I was able to attach some nodes. As soon I restart the server I was getting the #502 bad gateway error, but some how i fixed it and was running smoothly. The second time I restarted it throwing me the is the issue I am facing below error . Even I am not able to restart the service it's not allowing me to do so. I really need some permanent fix for this. Please.Redirecting to /bin/systemctl status pe-nginx.service● pe-nginx.service - pe-nginx - Puppet Enterprise web server Loaded: loaded (/usr/lib/systemd/system/pe-nginx.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-08-31 15:59:05 CDT; 17min ago Docs: http://docs.puppetlabs.com/pe/latest/index.htmlAug 31 15:59:05 puppetcentos systemd[1]: Starting pe-nginx - Puppet Enterprise web server...Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/opt/puppetlabs/server/data/console-se...smatch)Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: configuration file /etc/puppetlabs/nginx/nginx.conf test failedAug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service: control process exited, code=exited status=1Aug 31 15:59:05 puppetcentos systemd[1]: Failed to start pe-nginx - Puppet Enterprise web server.Aug 31 15:59:05 puppetcentos systemd[1]: Unit pe-nginx.service entered failed state.Aug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service failed.Hint: Some lines were ellipsized, use -l to show in full.[root@puppetcentos puppet]# service pe-nginx startRedirecting to /bin/systemctl start pe-nginx.serviceJob for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Add Comment
Jira (PUP-6666) pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Title: Message Title
Venkat updated an issue
Puppet / PUP-
pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Change By:
Venkat
I have installed the puppet enterprise in my HyperV Box, testing out some trails for my department in eBay It security, to manage the Linux client machines. I have been getting lots and loads of issues. This is the issue that I am facing for now . I have some how able to install the PE in Centos7, and I was able to attach some nodes. As soon I restart the server I was getting the #502 bad gateway error, but some how i fixed it and was running smoothly. The second time I restarted it the is the issue I am facing. Even I am not able to restart the service it's not allowing me to do so. I really need some permanent fix for this. Please.Redirecting to /bin/systemctl status pe-nginx.service● pe-nginx.service - pe-nginx - Puppet Enterprise web server Loaded: loaded (/usr/lib/systemd/system/pe-nginx.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-08-31 15:59:05 CDT; 17min ago Docs: http://docs.puppetlabs.com/pe/latest/index.htmlAug 31 15:59:05 puppetcentos systemd[1]: Starting pe-nginx - Puppet Enterprise web server...Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/opt/puppetlabs/server/data/console-se...smatch)Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: configuration file /etc/puppetlabs/nginx/nginx.conf test failedAug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service: control process exited, code=exited status=1Aug 31 15:59:05 puppetcentos systemd[1]: Failed to start pe-nginx - Puppet Enterprise web server.Aug 31 15:59:05 puppetcentos systemd[1]: Unit pe-nginx.service entered failed state.Aug 31 15:59:05 puppetcentos systemd[1]: pe-nginx.service failed.Hint: Some lines were ellipsized, use -l to show in full.[root@puppetcentos puppet]# service pe-nginx startRedirecting to /bin/systemctl start pe-nginx.serviceJob for pe-nginx.service failed because the control process exited with error code. See "systemctl status pe-nginx.service" and "journalctl -xe" for details.
Add Comment
Jira (PUP-6666) pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Title: Message Title
Venkat created an issue
Puppet / PUP-
pe-nginx.service loaded failed failed pe-nginx - Puppet Enterprise web server
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/08/31 2:18 PM
Environment:
CENTOS 7
Priority:
Major
Reporter:
Venkat
I have installed the puppet enterprise in my HyperV Box, testing out some trails for my department in eBay It security, to manage the Linux client machines. I have been getting lots and loads of issues. This is the issue that I am facing. I have some how able to install the PE in Centos7, and I was able to attach some nodes. As soon I restart the server I was getting the #502 bad gateway error, but some how i fixed it and was running smoothly. The second time I restarted it the is the issue I am facing. Even I am not able to restart the service it's not allowing me to do so. I really need some permanent fix for this. Please.
Redirecting to /bin/systemctl status pe-nginx.service ● pe-nginx.service - pe-nginx - Puppet Enterprise web server Loaded: loaded (/usr/lib/systemd/system/pe-nginx.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-08-31 15:59:05 CDT; 17min ago Docs: http://docs.puppetlabs.com/pe/latest/index.html
Aug 31 15:59:05 puppetcentos systemd[1]: Starting pe-nginx - Puppet Enterprise web server... Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/opt/puppetlabs/server/data/console-se...smatch) Aug 31 15:59:05 puppetcentos nginx[4866]: nginx: configuration file /etc/puppetlabs/nginx/nginx.conf test failed Aug 31 15:59:05
