Bug 233766 - sysutils/puppetserver6 doesn't start on FreeBSD 12.0-RC3
Summary: sysutils/puppetserver6 doesn't start on FreeBSD 12.0-RC3
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: FreeBSD Puppet Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-04 07:32 UTC by bas
Modified: 2019-02-18 10:24 UTC (History)
11 users (show)

See Also:
bugzilla: maintainer-feedback? (puppet)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bas 2018-12-04 07:32:48 UTC
Install puppetserver6 using pkg on a clean 12.0-RC3 system, enable the puppetserver service and start it. Monitor /var/log/puppetserver/puppetserver.log. You'll see a stream of errors relating to Puppet's inability to modify certain files and/or directories on the system and the service won't start up.

Perform the exact same actions on 11.2-RELEASE and the Puppet server starts without any issues.
Comment 1 Zach Leslie freebsd_committer 2018-12-10 20:34:45 UTC
I'll spend some time in the coming weeks getting a 12 box up.  The motherboard for my build box is currently on my dining table, so some things need addressing first, but I'll try to reproduce this here shortly.
Comment 2 blahblah.1981 2018-12-13 09:26:53 UTC
Just to add to the initial report, I've installed a clean 12.0-RELEASE and am also having the same problems with puppet6-6.0.4, puppetserver5-5.3.6, and even puppetserver-2.8.0_1.

They all seem to have similar errors in /var/log/puppetserver/puppetserver.log like the following.

If you need help testing, I will try to help if I can.

2018-12-13 18:19:08,045 ERROR [clojure-agent-send-pool-0] [puppetserver] /File[/var/run/puppetserver]/ensure change from socket to directory failed: Could not back up files of type socket
2018-12-13 18:19:08,089 INFO  [clojure-agent-send-pool-0] [puppetserver] /File[/var/log/puppetserver/masterhttp.log] Dependency File[/var/log/puppetserver] has failures: true
2018-12-13 18:19:08,090 WARN  [clojure-agent-send-pool-0] [puppetserver] /File[/var/log/puppetserver/masterhttp.log] Skipping because of failed dependencies
RuntimeError: Got 3 failure(s) while initializing: File[/usr/local/etc/puppet]: change from socket to directory failed: Could not back up files of type socket; File[/var/log/puppetserver]: change from unknown to directory failed: Could not back up files of type unknown; File[/var/run/puppetserver]: change from socket to directory failed: Could not back up files of type socke
Comment 3 Zach Leslie freebsd_committer 2018-12-17 01:41:10 UTC
I've filed https://tickets.puppetlabs.com/browse/SERVER-2402 though, if you're seeing the issue with all versions of puppetserver, this could be something else to do with FreeBSD 12.  I'll test puppetserve5 on 12 shortly, which has been working without issue on 11 for quite some time.
Comment 4 Andre Rikkert de Koe - ARK-ICT 2018-12-20 06:14:41 UTC
same with puppetserver6-6.1.0 :

root@infra2:~ # grep ERROR /var/log/puppetserver/puppetserver.log 
2018-12-20T07:10:45.829+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] Puppet Could not remove files of type unknown
2018-12-20T07:10:45.845+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] /File[/usr/local/etc/puppet]/ensure change from 'unknown' to 'directory' failed: Could not remove files of type unknown
2018-12-20T07:10:45.854+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] Puppet Could not remove files of type unknown
2018-12-20T07:10:45.866+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] /File[/var/puppet/server/data/puppetserver]/ensure change from 'unknown' to 'directory' failed: Could not remove files of type unknown
2018-12-20T07:10:45.880+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] Puppet Could not remove files of type unknown
2018-12-20T07:10:45.891+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] /File[/var/log/puppetserver]/ensure change from 'unknown' to 'directory' failed: Could not remove files of type unknown
2018-12-20T07:10:45.899+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] Puppet Could not remove files of type unknown
2018-12-20T07:10:45.913+01:00 ERROR [clojure-agent-send-pool-0] [puppetserver] /File[/var/run/puppetserver]/ensure change from 'unknown' to 'directory' failed: Could not remove files of type unknown
2018-12-20T07:10:46.048+01:00 ERROR [clojure-agent-send-pool-0] [p.t.internal] shutdown-on-error triggered because of exception!
2018-12-20T07:10:46.049+01:00 ERROR [async-dispatch-2] [p.t.internal] Error during service init!!!
2018-12-20T07:10:46.068+01:00 ERROR [async-dispatch-3] [p.t.internal] Encountered error during shutdown sequence
root@infra2:~ # freebsd-version
12.0-RELEASE-p1
root@infra2:~ #
Comment 5 Joseph Mulloy 2018-12-30 03:24:13 UTC
This is actually a jruby/jnr-posix bug.

https://github.com/jruby/jruby/issues/5521
https://github.com/jnr/jnr-posix/issues/126

---

root@puppet:~ # jirb
irb(main):001:0> File.stat("/usr/local/etc/puppet").ftype()
=> "blockSpecial"
irb(main):002:0> File.stat("/usr/local/etc/puppet/puppet.conf").ftype()
=> "unknown"

---

root@puppet:~ # irb
irb(main):001:0> File.stat("/usr/local/etc/puppet").ftype()
=> "directory"
irb(main):002:0> File.stat("/usr/local/etc/puppet/puppet.conf").ftype()
=> "file"
Comment 6 Muhammad al-iman 2019-01-28 04:01:25 UTC
is there any way for quick fix for this.. I saw there is quick fix for FreeBSD 12 but I dont know how to implement it.
Comment 7 Romain Tartière freebsd_committer 2019-01-28 05:45:51 UTC
(In reply to Muhammad al-iman from comment #6)
> is there any way for quick fix for this.. I saw there is quick fix for FreeBSD 12 but I dont know how to implement it.


For now, the "reliable" way of running puppetserver6 on FreeBSD 12+ seems to be to build a 11.2 jail and run puppetserver from this jail.

If you have some Java skills, jumping head-first in the issues referenced by  Joseph Mulloy and submitting Pull-Requests upstream is likely the most efficient way to see some motion :-)
Comment 8 mikael.urankar 2019-02-18 10:24:33 UTC
Hi puppet@
When can we expect to have a fix for this issue?