On 08/15/2014 09:34 PM, Mark Gardner wrote: > I'm upgrading puppet from 3.3.1 to 3.6.2 on Suse Linux Enterprise 11 SP3 > > The puppet service wont start with this error collected error from > /var/log/puppet/puppet.conf > Fri Aug 15 13:12:35 -0500 2014 Puppet (err): Could not parse > application options: invalid option: --port=8140 > > It looks to me that the init script needs to be changed to use > masterport instead of port. I'm not sure that it's something that > needs to be changed in the file or something that needs to be fixed in > the spec file?
Holy monkey. Are those the packages that SuSE provides? In upstream puppet, there *never* was a --port option. That was likely a vendor patch then. Whee. What fun. I suppose you kept your old initscript during the package update (as you do), so that it didn't notice that this particular patch was reverted for the current version? I'm guessing wildly here, but it would at least make sense. Have you checked the package's change log? Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/53FBB0E5.2010002%40Alumni.TU-Berlin.de. For more options, visit https://groups.google.com/d/optout.
