Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Perhaps it is a Fedora issue. In any case, I'm moving away from using puppet so feel free to close as I won't be able to provide any more information. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Matthaus Owens commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Orion Poplawski I'm unable to reproduce this issue. Are these packages from fedora? Using Puppet Labs' puppet-agent packages on fedora 22 I don't see any old processes sticking around, it restarts just fine. I don't know what /usr/bin/start-puppet-agent is that is mentioned in the output above, but it could be preventing systemd from correctly identify the pid of the main process. Here is the output from my tests. [root@vgryvwpwlkjx7kt ~]# systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2015-09-16 13:13:32 PDT; 3min 13s ago Main PID: 9248 (puppet) CGroup: /system.slice/puppet.service └─9248 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/puppet agent --no-daemonize Sep 16 13:13:32
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Matthaus Owens assigned an issue to Orion Poplawski Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Matthaus Owens Assignee: Ryan McKern Orion Poplawski Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Matthaus Owens updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Matthaus Owens Sprint: RE 2015-10-07 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Michael Stahnke updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Michael Stahnke Sprint: RE 2015- 09 10 - 23 07 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Kenn Hussey Story Points: 3 Sprint: RE 2015-09-23 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Kenn Hussey assigned an issue to Ryan McKern Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Kenn Hussey Assignee: Ryan McKern Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Josh Cooper Component/s: RE 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Eric Sorenson Scrum Team: ReleaseEngineering Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Actually, with Fedora 22, puppet 4.0.0, the restart completes fine, but the old child process sticks around: systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2015-05-01 11:09:17 MDT; 2min 3s ago Main PID: 844 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─844 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize └─849 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize systemctl restart puppet systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2015-05-01 11:11:54 MDT; 16s ago Main PID: 1622 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─ 849 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize ├─1622 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize └─1623 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize so now there are two puppet agents running. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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,
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski created an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Issue Type: Bug Affects Versions: PUP 4.0.0, PUP 3.7.5 Assignee: Unassigned Created: 2015/05/01 10:07 AM Environment: Fedora Linux Labels: systemd Priority: Critical Reporter: Orion Poplawski Adding KillMode=process to puppet.service to fix PUP-3931 appears to have broken systemctl restart puppet for me. systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled) Active: active (running) since Fri 2015-05-01 11:02:35 MDT; 11s ago Main PID: 18662 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─18662 /bin/sh /usr/bin/start-puppet-agent agent
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski updated an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Change By: Orion Poplawski AddingKillMode=processtopuppet.servicetofixPUP-3931appearstohavebrokensystemctlrestartpuppetforme. {noformat} #systemctlstatuspuppet●puppet.service-PuppetagentLoaded:loaded(/usr/lib/systemd/system/puppet.service;enabled)Active:active(running)sinceFri2015-05-0111:02:35MDT;11sagoMainPID:18662(start-puppet-ag)CGroup:/system.slice/puppet.service├─18662/bin/sh/usr/bin/start-puppet-agentagent--no-daemonize└─18665/usr/bin/ruby-mri/usr/bin/puppetagent--no-daemonize#systemctlrestartpuppet#systemctlstatuspuppet●puppet.service-PuppetagentLoaded:loaded(/usr/lib/systemd/system/puppet.service;enabled)Active:failed(Result:exit-code)sinceFri2015-05-0111:03:03MDT;4sagoProcess:19066ExecStart=/usr/bin/start-puppet-agentagent${PUPPET_EXTRA_OPTS}--no-daemonize(code=exited,status=1/FAILURE)MainPID:19066(code=exited,status=1/FAILURE)CGroup:/system.slice/puppet.service└─18665/usr/bin/ruby-mri/usr/bin/puppetagent--no-daemonize {noformat} Theoldchildpuppetprocessisstillaround.Straceshows: {noformat} 19199restart_syscall(...resuminginterruptedcall...unfinished...19245restart_syscall(...resuminginterruptedcall...unfinished...19198wait4(-1,unfinished...19199...restart_syscallresumed)=-1ETIMEDOUT(Connectiontimedout)19199futex(0xb556d0,FUTEX_WAKE_PRIVATE,1)=019199futex(0xb55654,FUTEX_WAIT_BITSET_PRIVATE,15,{359644,166273339},unfinished...19198...wait4resumed0x7ffc8ab93080,0,NULL)=?ERESTARTSYS(ToberestartedifSA_RESTARTisset)19198---SIGTERM{si_signo=SIGTERM,si_code=SI_USER,si_pid=1,si_uid=0}---19198+++killedbySIGTERM+++19199...futexresumed)=-1ETIMEDOUT(Connectiontimedout)19199futex(0xb556d0,FUTEX_WAKE_PRIVATE,1)=019199futex(0xb55654,FUTEX_WAIT_BITSET_PRIVATE,17,{359649,166794009},detached... {noformat} I'mseeingthiswithFedora21and3.7.5andFedora22w/4.0.0. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)