Jira (PDB-3085) Cannot start Puppet DB because of filerights
Title: Message Title Yama updated an issue PuppetDB / PDB-3085 Cannot start Puppet DB because of filerights Change By: Yama After updating all packages, and even reinstalled PuppetDB the following happens:[root@foreman-01 puppetdb]# /etc/init.d/puppetdb restartStopping puppetdb: [ OK ]Starting puppetdb: bash: /var/log/puppetlabs/puppetdb/puppetdb-daemon.log: Permission denied [FAILED]cat: /var/run/puppetlabs/puppetdb/puppetdb: No such file or directoryWhen I remove and install puppetDB again /var/run/puppetlabs/puppetdb/ is recreated with the right rights. [root@foreman-01 ~]# ls -lna /var/run/puppetlabstotal 16drwxr-xr-x 4 52 52 4096 Oct 5 11:26 .drwxr-xr-x. 23 0 0 4096 Oct 5 13:00 ..drwxr-xr-x 2 496 495 4096 Oct 5 11:26 puppetdbdrwxr-xr-x 2 52 52 4096 Oct 5 10:45 puppetserver[root@foreman-01 ~]# ls -lna /var/log/puppetlabs/total 24drwxr-x--- 6 52 52 4096 Oct 5 11:26 .drwxr-xr-x. 16 0 0 4096 Oct 5 10:39 ..drwxr-x--- 2 52 52 4096 Sep 22 20:24 puppetdrwx-- 2 496 495 4096 Aug 24 22:18 puppetdbdrwxr-x--- 2 52 52 4096 Oct 5 01:57 puppetserverdrwxr-xr-x 2 0 0 4096 Sep 22 20:24 pxp-agentRights stay the same after reinstall. 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
Jira (PDB-3085) Cannot start Puppet DB because of filerights
Title: Message Title Yama created an issue PuppetDB / PDB-3085 Cannot start Puppet DB because of filerights Issue Type: Bug Affects Versions: PDB 4.2.2 Assignee: Unassigned Components: PuppetDB Created: 2016/10/05 3:28 AM Environment: CentOS 6.8 fully updated (with foreman) Priority: Major Reporter: Yama After updating all packages, and even reinstalled PuppetDB the following happens: [root@foreman-01 puppetdb]# /etc/init.d/puppetdb restart Stopping puppetdb: [ OK ] Starting puppetdb: bash: /var/log/puppetlabs/puppetdb/puppetdb-daemon.log: Permission denied [FAILED] cat: /var/run/puppetlabs/puppetdb/puppetdb: No such file or directory When I remove and install puppetDB again /var/run/puppetlabs/puppetdb/ is recreated with the right rights.
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama commented on PUP-3501 Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale OK, It seem that /etc/environment doesn't work then the system has rebooted. You need to manually restart puppet again to get it working. I think the only option is the puppet init script. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama commented on PUP-3501 Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale OK, I need to update this again. When I set this in my /etc/init.d/puppet and reboot the machine it doesn't work also. Restarting the puppet service makes it work again. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama updated an issue Puppet / PUP-3501 upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale Change By: Yama Priority: Minor Normal Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama commented on PUP-3501 Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale I'm facing the same issue on Ubuntu 14.04 LANG=en_US.UTF-8 via /etc/environment doesn't fix this for me. I have tried all found solutions on google, none works. Any idea where this goes wrong ? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
