On Mon, Oct 13, 2014 at 10:08:55PM -0700, Janelle wrote:
Actually, I did find a fix and forgot to post.
I was able to mirror the COPR repo, and after reviewing it, found that
simply removing the pki-base...fc21 directory, and regenning the repo data
with createrepo, fixed the problem. It
On Tue, 14 Oct 2014, Orkhan Gasimov wrote:
Thanks to both of you for the interest.
Here`s the info you asked:
1. Putting debug_level = 7 either in [domain] or/and [nss] section
of the /usr/local/etc/sssd/sssd.conf file gives nothing in the log.
The log file located at /var/log/sssd/sssd.log
On Mon, Oct 13, 2014 at 9:39 PM, Natxo Asenjo natxo.ase...@gmail.com wrote:
But if I get it from the crl generator using /ipa/crl/MasterCRL.bin I
still get the old crl dated june 28th last year.
Should I modify ipa-pki-proxy.conf as well on the CRL generator host
to point to the
With help from Alexander Bokovoy I found correct log destinations:
sssd-domain-log:
https://cloud.mail.ru/public/1e803a00989e%2Fsssd_eurosel.az.log
sssd-nss-log: https://cloud.mail.ru/public/ae41ae3b44b6%2Fsssd_nss.log
These files are from my second Fedora - FreeBSD setup, they have
With help from Alexander Bokovoy I found correct log destinations:
sssd-domain-log:https://cloud.mail.ru/public/1e803a00989e%2Fsssd_eurosel.az.log
sssd-nss-log:https://cloud.mail.ru/public/ae41ae3b44b6%2Fsssd_nss.log
These files are from my second Fedora - FreeBSD setup, they have
different
On Tue, Oct 14, 2014 at 12:34:09PM +0500, Orkhan Gasimov wrote:
With help from Alexander Bokovoy I found correct log destinations:
sssd-domain-log:
https://cloud.mail.ru/public/1e803a00989e%2Fsssd_eurosel.az.log
sssd-nss-log: https://cloud.mail.ru/public/ae41ae3b44b6%2Fsssd_nss.log
These
On Tue, 14 Oct 2014, Orkhan Gasimov wrote:
With help from Alexander Bokovoy I found correct log destinations:
sssd-domain-log:https://cloud.mail.ru/public/1e803a00989e%2Fsssd_eurosel.az.log
sssd-nss-log:https://cloud.mail.ru/public/ae41ae3b44b6%2Fsssd_nss.log
These files are from my second
Thanks for taking time to find a solution.
1. Location of log files is /var/log/sssd , I just didn`t know that each
section of sssd.conf file produced its own log file:
/var/log/sssd/sssd_your.domain.log
/var/log/sssd/sssd_nss.log
2. For the client side, here again the list of snapshots
On (14/10/14 10:23), Orkhan Gasimov wrote:
Thanks to both of you for the interest.
Here`s the info you asked:
1. Putting debug_level = 7 either in [domain] or/and [nss] section of the
/usr/local/etc/sssd/sssd.conf file gives nothing in the log. The log file
located at /var/log/sssd/sssd.log is
I suspected that problems could arise with DNS, and here they are...
In fact, this entire string: ipa_server = _srv_ #our FreeIPA server has
DNS SRV entries was taken as-is from the how-to on FreeBSD forums.
First I commented it out, because was unsure sure if it was appropriate
for my simple
I tried to avoid setting up a third VM to serve as a DNS server for my
test scenario. Thought it would be possible to set up working FreeIPA
client-server interaction with just 2 VMs correct hostnames
/etc/hosts files in them.
Do I correctly understand your idea that it`s a MUST to set up a
On 14.10.2014 11:49, Orkhan Gasimov wrote:
I suspected that problems could arise with DNS, and here they are...
In fact, this entire string: ipa_server = _srv_ #our FreeIPA server has DNS
SRV entries was taken as-is from the how-to on FreeBSD forums. First I
commented it out, because was unsure
On Tue, 14 Oct 2014, Orkhan Gasimov wrote:
I tried to avoid setting up a third VM to serve as a DNS server for my
test scenario. Thought it would be possible to set up working FreeIPA
client-server interaction with just 2 VMs correct hostnames
/etc/hosts files in them.
Many applications
I`ll try such a test setup, then share information about results.
14-Oct-14 15:04, Petr Spacek пишет:
On 14.10.2014 11:49, Orkhan Gasimov wrote:
I suspected that problems could arise with DNS, and here they are...
In fact, this entire string: ipa_server = _srv_ #our FreeIPA server
has DNS
On 14.10.2014 11:49, Orkhan Gasimov wrote:
I suspected that problems could arise with DNS, and here they are...
In fact, this entire string: ipa_server = _srv_ #our FreeIPA server has DNS
SRV entries was taken as-is from the how-to on FreeBSD forums. First I
commented it out, because was unsure
I need further assistance with this moment:
specify IPA domain name which is sub-domain of you existing domain
(e.g. ipa.eurosel.az) .
Currently my FreeIPA server's hostname is ipa1.eurosel.az, and client's
hostname is bsd1.eurosel.az.
So when running this command:
ipa-server-install
On 14.10.2014 13:48, Orkhan Gasimov wrote:
I need further assistance with this moment:
specify IPA domain name which is sub-domain of you existing domain (e.g.
ipa.eurosel.az) .
Currently my FreeIPA server's hostname is ipa1.eurosel.az, and client's
hostname is bsd1.eurosel.az.
So when running
So which way do I go?
1) Change the server VM`s hostname from ipa1.eurosel.az to
ipa1.ipa.eurosel.az prior to issuing IPA installation command
2) or leave my hostname and contents of /etc/hosts file intact and
specify a different FQDN and domain part of the IPA server after issuing
IPA
On Tue, 14 Oct 2014, Orkhan Gasimov wrote:
So which way do I go?
1) Change the server VM`s hostname from ipa1.eurosel.az to
ipa1.ipa.eurosel.az prior to issuing IPA installation command
2) or leave my hostname and contents of /etc/hosts file intact and
specify a different FQDN and domain part
quest monger wrote:
makes sense.
i will still try out that cert add command in my test environment, just
to see if it works.
looks like for now, 4.1 upgrade is my best option.
IPA 3.x includes a command, ipa-server-certinstall, which will do what
you need. This can be a bumpy process with
Janelle wrote:
Hi again,
A lot of this information has been very useful. I did have a question I
could not answer. I noticed in the Deployment Recommendations docs, it
says not to have any more than 4 replication agreements. Perhaps I am
missing something, but I don't see how to get a
Hi Rob,
Thanks for that - it clears up one point - and explains why the replica
manage command shows all masters, but what I don't understand is how to
get the CA to a replica once it is created? I don't see anything in
the docs on that. Am I missing something very obvious here? I am coming
Janelle wrote:
Hi Rob,
Thanks for that - it clears up one point - and explains why the replica
manage command shows all masters, but what I don't understand is how to
get the CA to a replica once it is created? I don't see anything in
the docs on that. Am I missing something very obvious
On (14/10/14 16:03), Fraser Tweedale wrote:
On Mon, Oct 13, 2014 at 10:08:55PM -0700, Janelle wrote:
Actually, I did find a fix and forgot to post.
I was able to mirror the COPR repo, and after reviewing it, found that
simply removing the pki-base...fc21 directory, and regenning the repo data
On 14.10.2014 15:06, Alexander Bokovoy wrote:
On Tue, 14 Oct 2014, Orkhan Gasimov wrote:
So which way do I go?
1) Change the server VM`s hostname from ipa1.eurosel.az to
ipa1.ipa.eurosel.az prior to issuing IPA installation command
2) or leave my hostname and contents of /etc/hosts file intact
Ok, friends, you helped me to understand one thing. My test scenario with 2 VMs
and no DNS server introduces problems with DNS resolution, which seems to be
almost necessary. So now I have 2 tasks:
1) properly configure IPA server to work with DNS;
2) make a FreeBSD host (which is a non-native
On Tue, Oct 14, 2014 at 03:13:06PM +0200, Lukas Slebodnik wrote:
On (14/10/14 17:48), Fraser Tweedale wrote:
On Tue, Oct 14, 2014 at 12:34:09PM +0500, Orkhan Gasimov wrote:
With help from Alexander Bokovoy I found correct log destinations:
sssd-domain-log:
27 matches
Mail list logo
