Jira (PUP-9074) Windows scheduled_task name cannot us a path
Title: Message Title Peter J Krawetzky commented on PUP-9074 Re: Windows scheduled_task name cannot us a path Any idea if this has been fixed? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.271714.1534514997000.82561.1567518420074%40Atlassian.JIRA.
Jira (PUP-9074) Windows scheduled_task name cannot us a path
Title: Message Title
Peter J Krawetzky created an issue
Puppet / PUP-9074
Windows scheduled_task name cannot us a path
Issue Type:
Bug
Affects Versions:
PUP 4.10.4
Assignee:
Unassigned
Components:
Windows
Created:
2018/08/17 7:09 AM
Priority:
Normal
Reporter:
Peter J Krawetzky
Puppet Version: 4.10.4 Puppet Server Version: 5.3.4 OS Name/Version: Windows 2016 10.0.14393 When trying to execute the follow resource on a Windows 2016 server an error is returned: scheduled_task { '\Puppet\PuppetKickoff': ensure => present, enabled => true, command => 'powershell.exe', arguments => ' E:Program Files\\PuppetLabs\\binrun_puppet_shell.bat -Verb runas', trigger => { schedule => daily, every => 1, # Specifies every other day. Defaults to 1 (every day). start_time => '08:${puppet_agent::params::cronminute}', # Must be specified minutes_interval => '60', # Repeat this task every 60 minutes minutes_duration => '300', # The task will run for a total of five hours } Error: Error: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified. Error: /Stage[main]/Puppet_agent::Init_windows/Scheduled_task[\Puppet\PuppetKickoff]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024893.: The system cannot find the path specified. When I only use PuppetKickoff in the name, it sucessfully creates a scheduled task but not in the path I desire. Desired Behavior: Allow a path structure in the scheduled_task name in order to place a task away from the main path Actual Behavior: See above
Jira (PDB-3602) Puppet Dashboard Question PuppetDB 3.0.2
Title: Message Title Peter J Krawetzky updated an issue PuppetDB / PDB-3602 Puppet Dashboard Question PuppetDB 3.0.2 Change By: Peter J Krawetzky Summary: Puppet Dashboard Question PuppetDB 3.0.2 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 (PDB-3602) Puppet Dashboard Question
Title: Message Title Peter J Krawetzky updated an issue PuppetDB / PDB-3602 Puppet Dashboard Question Change By: Peter J Krawetzky Can someone explain what each of the 3 values are in the attachment? I understand the command queue but not the other 2. Out Our queue keeps climbing and we are trying to figure out why. 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 (PDB-3602) Puppet Dashboard Question
Title: Message Title Peter J Krawetzky created an issue PuppetDB / PDB-3602 Puppet Dashboard Question Issue Type: Bug Assignee: Unassigned Attachments: puppetdb_dashboard.JPG Created: 2017/06/28 4:55 AM Priority: Normal Reporter: Peter J Krawetzky Can someone explain what each of the 3 values are in the attachment? I understand the command queue but not the other 2. Out queue keeps climbing and we are trying to figure out why. Add Comment
Jira (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Just curious for the size of our environment with 3500+ nodes, 4 puppet servers load balanced and initially one puppetDB server. How big should I expect our command queue depth to be? Maybe I'm just not sure how big it should be based on the way we are setup. I ended up moving the KahaDB data directory out of /opt to another filesystem so it has more room. 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors No. Open source 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors So we had Puppet out here last year and spent a week with an onsite person doing a walkthrough of our environment and configuration. I did ask if we can have more than one puppetdb server and he stated we couldn't do that. Now I'm reading we can and even more so based on your advice. The server itself is not running at 100% capacity so I'm just curious what splitting them apart would do. Other than load balance. Do you think it would reduce the queue? 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors One last question. We have about 3500 agents that point to one puppetdb server. We have 16GB of memory and currently running 4 virtual cpu's. Would adding additional CPUs help us in the this case? 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Here are a list of linux patches there were applied just before this started happening. Any ideas if one of these could have caused this? Without knowing the internals of KahaDB, i don't really know where to start. libsss_idmap-1.14.0-43.el7_3.14 python-firewall-0.4.3.2-8.1.el7_3.2 selinux-policy-3.13.1-102.el7_3.16 java-1.8.0-openjdk-headless-1.8.0.131-2.b11.el7_3 kernel-tools-libs-3.10.0-514.16.1.el7 tzdata-java-2017b-1.el7 libsss_nss_idmap-1.14.0-43.el7_3.14 NetworkManager-1.4.0-19.el7_3 NetworkManager-libnm-1.4.0-19.el7_3 nss-3.28.4-1.0.el7_3 nss-sysinit-3.28.4-1.0.el7_3 device-mapper-event-1.02.135-1.el7_3.4 grubby-8.28-21.el7_3 tcsh-6.18.01-13.el7_3.1 x86_64 kernel-headers-3.10.0-514.16.1.el7 tzdata-2017b-1.el7 yum-rhn-plugin-2.0.1-6.1.el7_3 dmidecode-3.0-2.1.el7_3 emacs-filesystem-24.3-19.el7_3 libtiff-4.0.3-27.el7_3 libtool-ltdl-2.4.2-22.el7_3 NetworkManager-config-server-1.4.0-19.el7_3 perf-3.10.0-514.16.1.el7 sudo-1.8.6p7-22.el7_3 irqbalance-1.0.7-6.el7_3.1 jasper-libs-1.900.1-30.el7_3 microcode_ctl-2.1-16.3.el7_3 nfs-utils-1.3.0-0.33.el7_3 python-perf-3.10.0-514.16.1.el7 systemd-python-219-30.el7_3.8 bind-libs-lite-9.9.4-38.el7_3.3 bind-utils-9.9.4-38.el7_3.3 net-snmp-5.7.2-24.el7_3.2 openssh-clients-6.6.1p1-35.el7_3 openssh-server-6.6.1p1-35.el7_3 openssl-1.0.1e-60.el7_3.1 open-vm-tools-desktop-10.0.5-4.el7_3 open-vm-tools-devel-10.0.5-4.el7_3 lvm2-libs-2.02.166-1.el7_3.4 x86_64 ntpdate-4.2.6p5-25.el7_3.2 polkit-0.112-11.el7_3 bind-libs-9.9.4-38.el7_3.3 bind-license-9.9.4-38.el7_3.3 net-snmp-agent-libs-5.7.2-24.el7_3.2 net-snmp-libs-5.7.2-24.el7_3.2 openssh-6.6.1p1-35.el7_3 open-vm-tools-10.0.5-4.el7_3 wpa_supplicant-2.0-21.el7_3 openssl-libs-1.0.1e-60.el7_3.1 ca-certificates-2017.2.11-70.1.el7_3 device-mapper-event-libs-1.02.135-1.el7_3.4 initscripts-9.49.37-1.el7_3.1 systemd-sysv-219-30.el7_3.8 device-mapper-1.02.135-1.el7_3.4 device-mapper-libs-1.02.135-1.el7_3.4 util-linux-2.23.2-33.el7_3.2 systemd-219-30.el7_3.8 libblkid-2.23.2-33.el7_3.2 libgudev1-219-30.el7_3.8 libmount-2.23.2-33.el7_3.2 libuuid-2.23.2-33.el7_3.2 nspr-4.13.1-1.0.el7_3 nss-util-3.28.4-1.0.el7_3 systemd-libs-219-30.el7_3.8 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Can I just upgrade the puppetdb or do I also have to do the puppetserver, ca servers, mcollective servers and puppet agents? I know there is a specific sequence that they recommend. We are running: puppet agent 4.2.1 puppet server 2.1.1 puppetdb 3.0.2 mcollective 2.8.2 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Also the grep command you gave did not reveal any output. I ran it in the wrong directory so KahaDB logs do not have any reference to that. Sorry for the confusion. 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Not sure what you mean by a report. 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Well with 4 cpu's i set it to 4 and the java service spiked to over 140%. I scaled it back to 3 and its running around 70-80%. But this kahadb log file is slowing increasing again. Any recommendations on setting in postgresql? I've updated a few: shared_buffers = 4GB work_mem = 8MB maintenance_work_mem = 1GB checkpoint_segments = 32 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Also why would the command queue depth increase when pointing a puppet server to a different puppetdb server? I know the queue depth is related to the number of threads. We current have 4 cpu's and the threads is set to 3. It started out fine but now the queue depth is growing again. 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Ok there are references in one of the KahaDB directory log file to that ActiveMQ.DLQ. What exactly does this mean? Could any of the linux patches have affected this behavior? 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors Russell thanks for replying! We are in the process of planning an upgrade to the latest puppet software. These issues and performance issues between kahadb and postgresql came out of no where after linux patches were applied. There isn't very much information on kahadb/activemq that has helped me try to determine our issue. What I do know is these messages correspond exactly to messages in the postgresql log about incompleted messages from client. There were no module changes that occurred immediately before this problem occurred. 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky commented on PDB-3597 Re: jdbc caught exception errors 3.0.2 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 (PDB-3597) jdbc caught exception errors
Title: Message Title Peter J Krawetzky created an issue PuppetDB / PDB-3597 jdbc caught exception errors Issue Type: Bug Assignee: Unassigned Created: 2017/06/27 5:46 AM Priority: Major Reporter: Peter J Krawetzky A few days ago we starting see the messages below in out puppetdb.log file. Since there is no additional information how do you debug something like this? My guess is it's impacting puppet agent runs. 2017-06-27 08:38:59,136 WARN [p.p.jdbc] Caught exception. Last attempt, throwing exception. 2017-06-27 08:39:02,383 WARN [p.p.jdbc] Caught exception. Last attempt, throwing exception. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3594) Message in Postgresql log: LOG: incomplete message from client
Title: Message Title Peter J Krawetzky updated an issue PuppetDB / PDB-3594 Message in Postgresql log: LOG: incomplete message from client Change By: Peter J Krawetzky Priority: Normal Major 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 (PDB-3594) Message in Postgresql log: LOG: incomplete message from client
Title: Message Title Peter J Krawetzky created an issue PuppetDB / PDB-3594 Message in Postgresql log: LOG: incomplete message from client Issue Type: Bug Assignee: Unassigned Created: 2017/06/26 7:23 AM Priority: Normal Reporter: Peter J Krawetzky We started getting several of these messages in our postgresql logs and not sure how to go about tracing down what it's referring to. Is there a troubleshooting guide that could help? Messages: < 2017-06-26 10:03:18.204 EDT >LOG: incomplete message from client < 2017-06-26 10:03:32.644 EDT >LOG: incomplete message from client < 2017-06-26 10:03:47.393 EDT >LOG: incomplete message from client < 2017-06-26 10:04:07.381 EDT >LOG: incomplete message from client < 2017-06-26 10:04:18.519 EDT >LOG: incomplete message from client < 2017-06-26 10:04:29.725 EDT >LOG: incomplete message from client < 2017-06-26 10:04:41.640 EDT >LOG: incomplete message from client < 2017-06-26 10:04:54.753 EDT >LOG: incomplete message from client < 2017-06-26 10:05:12.575 EDT >LOG: incomplete message from client < 2017-06-26 10:06:10.011 EDT >LOG: incomplete message from client < 2017-06-26 10:06:21.895 EDT >LOG: incomplete message from client < 2017-06-26 10:06:33.063 EDT >LOG: incomplete message from client < 2017-06-26 10:06:44.487 EDT >LOG: incomplete message from client < 2017-06-26 10:06:56.769 EDT >LOG: incomplete message from client < 2017-06-26 10:07:09.495 EDT >LOG: incomplete message from client < 2017-06-26 10:07:24.084 EDT >LOG: incomplete message from client < 2017-06-26 10:07:36.927 EDT >LOG: incomplete message from client < 2017-06-26 10:07:52.790 EDT >LOG: incomplete message from client < 2017-06-26 10:08:07.693 EDT >LOG: incomplete message from client < 2017-06-26 10:08:21.984 EDT >LOG: incomplete message from client < 2017-06-26 10:08:37.209 EDT >LOG: incomplete message from client < 2017-06-26 10:09:16.337 EDT >LOG: incomplete message from client < 2017-06-26 10:09:31.904 EDT >LOG: incomplete message from
