Jira (PUP-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Allister Banks commented on PUP-5267 Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Have no puppetlabs employees chimed in on this thread? On an old CPU I'm seeing zero response from manually running puppet agent, or even as little as --version. iMac 11,3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5267 puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Change By: Kylo Ginsberg Scrum Team: Client Platform Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5267 puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Change By: Kylo Ginsberg Environment: Yosemite 10. 5 10 .5, including Yosemite 10. 5 10 .5 running under VMware Fusion 7 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Kylo Ginsberg commented on PUP-5267 Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Based on comments in the thread, I think the Environment field on this ticket has a typo and should probably be 10.10.5 not 10.5.5. I'm going to go ahead and make that change. /cc Jeffery Harrell Also, I'm moving this to the PA project and assigning to the team that works on the toolchains because it sounds like this may be something with a flag to gcc/clang at compile time. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5267 puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title
Jason Schroeder commented on PUP-5267
Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
I also have this issue on an older Mac Pro aluminum tower running OSX 10.10.5 Facter v3.8 (which works fine) provides this info about the hardware:
{{sp_cpu_type => 6-Core Intel Xeon sp_current_processor_speed => 2.4 GHz sp_kernel_version => Darwin 14.5.0 sp_l2_cache_core => 256 KB sp_l3_cache_processor => 12 MB sp_machine_model => MacPro5,1 sp_machine_name => Mac Pro sp_number_processors => 12 sp_os_version => OS X 10.10.5 (14F1509)}}
I have the same "Illegal instruction: 4" for all of these packages:
puppet-agent-1.2.0-osx-10.9-x86_64.dmg
puppet-agent-1.2.4-1.mavericks.dmg
puppet-agent-1.2.4-1.yosemite.dmg
puppet-agent-1.3.1-1.osx10.10.dmg
puppet-agent-1.3.2-1.osx10.10.dmg
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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
Jira (PUP-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title John Simpson commented on PUP-5267 Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host With puppet-agent-1.3.2-1.osx10.11.dmg, the installer finishes and both pxp-agent and mcollectived are running, but after adding /opt/puppetlabs/puppet/bin to my PATH, any puppet commands (including both puppet agent -t and puppet agent --fingerprint) both die with the "Illegal instruction: 4" message. This is on a Mac Mini (Mid 2010) running OSX 10.11.2. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Zach L commented on PUP-5267 Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Same issue here on a Core 2 Duo running OSX 10.11.1 with 1.3.0 puppet-agent-1.3.0-1. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Mark Tustin commented on PUP-5267 Re: puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host I have the same/similar issue on a Macbook Pro (Mid 2009) with a 2.26GHz Intel Core 2 Duo. I have tested both 10.10.5 and 10.11 puppet-agent. I used the puppet-agent-1.3.0-1, but I also tested briefly other versions on the 10.10.5 test. Here is some console output that repeats every so often when starting launchd service. 11/24/15 2:16:50.335 PM com.apple.xpc.launchd[1]: (mcollective[559]) Service exited with abnormal code: 1 11/24/15 2:16:50.335 PM com.apple.xpc.launchd[1]: (mcollective) Service only ran for 0 seconds. Pushing respawn out by 10 seconds. 11/24/15 2:16:50.388 PM com.apple.xpc.launchd[1]: (puppet[552]) Service exited due to signal: Illegal instruction: 4 As another test, I attempted installing on a VM hosted on an older Xserve. The VM ran OSX 10.10 and installed the puppet-agent-1.3.0-1 package. After installation, the same error occurred. I think the xserve runs a similar CPU and is about the same age. I am going to attempt to find a newer Mac device to test to confirm if it is related to CPU. Add Comment
Jira (PUP-5267) puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host
Title: Message Title Jeffery Harrell created an issue Puppet / PUP-5267 puppet dies with "Illegal instruction: 4" on Xeon 5500 Mac Pro, including VMs on that host Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Kylo Ginsberg Components: Client Created: 2015/09/18 9:20 PM Environment: Yosemite 10.5.5, including Yosemite 10.5.5 running under VMware Fusion 7 Priority: Normal Reporter: Jeffery Harrell The Puppet Agent from puppet-agent-1.2.4-1.yosemite.dmg works fine on my i7 MacBook Pro, but it fails to run at all on our Mac Pro (Early 2009) servers. We're running 10.5.5 everywhere, so it's not the OS; apparently the Puppet Agent software has been compiled to run specifically on certain CPUs and not on others. That's my guess, anyway. Would it be an awful lot of trouble for you guys to spin up a release that will run on any Mac with Yosemite? We're trying to make a strategic decision about whether to commit to Puppet, but it's tough if we can't put it through its paces on our Mac OS X VMs, which are legion.
