@tjaalton What happened to 4.7.0~pre2-0~ppa3 in the staging PPA?
Today I wanted to repeat the installation of freeipa-server on 18.04 (now that
the bind9 update is available in -proposed). I wanted to use the staging PPA,
because the current package in bionic is unusable.
Notice that the fix went
@ahasenack When you said "Uploaded to bionic unapproved", did you mean
1:9.11.3+dfsg-1ubuntu1.3?
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - na
Since not everyone knows about the staging PPA (I just found it),
the PPA can be found here:
https://launchpad.net/~freeipa/+archive/ubuntu/staging
With the PPA (4.7.0~pre2-0~ppa3) the installation completes
without a problem.
--
You received this bug notification because you are a member of F
Side note for Timo. There is no tag in the git repo for
debian/4.7.0~pre1+git20180411-2 (commit fb666595)
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1772447
Title:
freeipa installation - d
Sorry for the duplicate in https://bugs.launchpad.net/bugs/1791325. I
should have paid more attention.
Anyway, there is a fix, what's holding it up? Right now FreeIPA server
is useless in 18.04
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to free
There was a discussion on the freeipa users list and Alexander Bokovoy was
kind enough to explain what was happening.
"We need access to the KDC's public certificate in case we are dealing
with a KDC certificate issued by a local certmonger (self-signed) which
is not trusted by the machine.
You c
Public bug reported:
After installing freeipa-server you cannot login via the browser. You'll get
a message: "Login failed due to an unknown reason."
In /var/log/apache2/error.log there is this:
-8X-8X--
[Thu Sep 06 12:00:28.720410 2018] [wsgi:e
Can we have this fix in bionic, please.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - named-pkcs11 fails to run
Status in bind9 package in Ubunt
Installing libdns-export1100-dbgsym libdns1100-dbgsym libisc-export169-dbgsym
helped. I now have debug symbols in view.c
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa s
No symbol info for the library :-(
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - Configuring the web interface, setting
up ssl
Status in freei
I have debug symbols, I installed bind9-dbgsym libisc169-dbgsym, but you
probably did that as well, right?
Reading symbols from /usr/sbin/named-pkcs11...Reading symbols from
/usr/lib/debug/.build-
id/a6/b02914ac626d6db7786c640335d7e674d21dcc.debug...done.
Not that it helped me any further without
@Timo what is the named command that you used to debug? I can't get named
to produce the same error (at view.c:962) when I run it as follows (this
is the command I found in the log):
/usr/sbin/named-pkcs11 -f -u bind
or
/usr/sbin/named-pkcs11 -g -u bind
It crashes at:
08-May-2018 07:07:41.154 .
When you said: "yep, that's a known issue" you referred to the non-FQDN. But
the above
error is after I corrected that. So, with a FQDN.
BTW, I'm doing the install with --setup-dns. Is that what you do as well?
At the end of the installation the nameserver (bind9-pkcs11) does not start
anymore.
Do you want me to create a bugreport for that non-FQDN?
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - Configuring the web interface, setting
up
In syslog there is this:
May 6 20:18:01 usrv1 named-pkcs11[25219]: ../../../lib/dns-pkcs11/view.c:962:
REQUIRE(view->zonetable != ((void *)0)) failed, back trace
May 6 20:18:01 usrv1 named-pkcs11[25219]: #0 0x55ceb0cb4cc0 in ??
May 6 20:18:01 usrv1 named-pkcs11[25219]: #1 0x7f4ae89007fa in ??
My hostname was not a FQDN. After I changed it to be FQDN, and made sure the
entry
is in /etc/hosts, the installation continues.
However, there is still a problem. The nameserver fails to (re)start.
Configuring DNS (named)
[1/11]: generating rndc key file
[2/11]: adding DNS container
[3/11
I'm doing this in a LXC container. Could that be of influence?
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - Configuring the web interface, setti
Public bug reported:
Setting up FreeIPA server fails at "Configuring the web interface", step
12/21
It's in a cleanly started LXC Ubuntu Bionic container. The
ppa:freeipa/ppa is also used to get tomcat 8.5.30-1ubuntu1.2
Configuring the web interface (httpd)
[1/21]: stopping httpd
[2/21]: bac
See also
https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1765616/comments/9
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa in Ubuntu.
https://bugs.launchpad.net/bugs/1769440
Title:
freeipa server install fails - Configuring the
To confirm, with the PPA the installation continues, and "Configuring
certificate server" succeeds.
However, now "Configuring the web interface" fails with
[12/21]: setting up ssl
[error] RuntimeError: Certificate issuance failed (CA_REJECTED)
ipapython.admintool: ERRORCertificate issuanc
Public bug reported:
Installing freeipa server fails at configuring certificate server (pki-
tomcatd).
...
Configuring kadmin
[1/2]: starting kadmin
[2/2]: configuring kadmin to start on boot
Done configuring kadmin.
Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes
[
@Timo at what point can we expect that the freeipa packages are back in
bionic? I'm not being impatient, just curious when I can start doing
some experiments with freeipa (+samba) on bionic.
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to freeipa
Public bug reported:
When doing ipa-backup it will eventually want to do a backup of
authconfig. This is a RedHat specific tool, but there is no
Ubuntu/Debian replacement. ipa-backup will fail with a Python stack
trace.
2016-12-30T10:36:02Z DEBUG Starting external process
2016-12-30T10:36:02Z DEB
23 matches
Mail list logo
