> Are you just toying with this or did something go horribly wrong and
you're trying to restore a production environment?
This. :-(
I have actually rebuilt the environment from scratch, then wrote a
perl script that just recreated all users from the ldif using ipa
user-add and reset password for
On 24/02/16 17:20, lejeczek wrote:
On 24/02/16 14:22, Sumit Bose wrote:
On Wed, Feb 24, 2016 at 12:45:55PM +, lejeczek wrote:
On 24/02/16 11:26, Sumit Bose wrote:
On Wed, Feb 24, 2016 at 11:21:13AM +, lejeczek wrote:
he everybody,
my first tampering with install gets me:
Feb 24
On (24/02/16 13:45), Torsten Harenberg wrote:
>Hi,
>
>we had some trouble with sssd in the past as well on machines which
>suffer from a high IO load (cluster nodes running scientific calculations).
>
>Following a suggestion from the list here, we moved the local sssd cache
>into a tmpfs, so our
W dniu 2016-02-24 15:34, Sumit Bose napisał(a):
The error indicates that there already is a trust on the AD side to a
domain which either has linux.test.local as domain name or the same
NetBIOS domain name. The default NetBIOS domain name in your case would
be LINUX.
You can check the names of
On 24/02/16 14:22, Sumit Bose wrote:
On Wed, Feb 24, 2016 at 12:45:55PM +, lejeczek wrote:
On 24/02/16 11:26, Sumit Bose wrote:
On Wed, Feb 24, 2016 at 11:21:13AM +, lejeczek wrote:
he everybody,
my first tampering with install gets me:
Feb 24 11:04:22 my.host.fake
On Wed, Feb 24, 2016 at 01:30:11PM +0100, Daniel wrote:
> Hello,
>
> I'm trying to setup trust with our AD domain in test environment, but I've
> got an error:
> ipa trust-add --type=ad test.local --two-way=1 --admin Administrator
> --password
>
> ipa: ERROR: CIFS server communication error:
On Wed, Feb 24, 2016 at 12:45:55PM +, lejeczek wrote:
> On 24/02/16 11:26, Sumit Bose wrote:
> >On Wed, Feb 24, 2016 at 11:21:13AM +, lejeczek wrote:
> >>he everybody,
> >>my first tampering with install gets me:
> >>
> >>Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]: Starting up
David Kupka wrote:
> On 23/02/16 20:21, Marat Vyshegorodtsev wrote:
>> Hi!
>>
>> I've been doing backups using the tool like this:
>> ipa-backup --data --online
>>
>> I didn't want any configuration to be backed up, since it is managed
>> from a chef recipe.
>>
>> However, when I tried to recover
On 24/02/16 11:26, Sumit Bose wrote:
On Wed, Feb 24, 2016 at 11:21:13AM +, lejeczek wrote:
he everybody,
my first tampering with install gets me:
Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]: Starting up
Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]: Failed to read
Hi,
we had some trouble with sssd in the past as well on machines which
suffer from a high IO load (cluster nodes running scientific calculations).
Following a suggestion from the list here, we moved the local sssd cache
into a tmpfs, so our fstab contains now a
tmpfs /var/lib/sss/db tmpfs
On 24.02.2016 12:53, Alexandre Borges wrote:
Dear colleagues,
How are you?
I’ve been facing a horrible problem with RHEL 7.2 (and Oracle Linux
7.2) when configuring IPA dnsforwardzone during the Active Directory
integration.
My configuration follows:
IPA Server: 192.168.1.195
On 23/02/16 20:21, Marat Vyshegorodtsev wrote:
Hi!
I've been doing backups using the tool like this:
ipa-backup --data --online
I didn't want any configuration to be backed up, since it is managed
from a chef recipe.
However, when I tried to recover the backup to a fresh FreeIPA
install,
Adding a forward zone like Martin suggested works.
I will definitely read the section you linked to get a better understanding of
the differences between both.
Doing a dig for google.com won't work in our case, because the servers are not
internet-facing.
Stijn
-Original Message-
Dear colleagues,
How are you?
Ive been facing a horrible problem with RHEL 7.2 (and Oracle Linux 7.2)
when configuring IPA dnsforwardzone during the Active Directory integration.
My configuration follows:
IPA Server: 192.168.1.195 (rhel72-1.example.com)
Win2012 (AD): 192.168.1.229
On Wed, Feb 24, 2016 at 11:21:13AM +, lejeczek wrote:
> he everybody,
> my first tampering with install gets me:
>
> Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]: Starting up
> Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]: Failed to read
> keytab [default]: Bad address
>
he everybody,
my first tampering with install gets me:
Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]:
Starting up
Feb 24 11:04:22 my.host.fake sssd[be[host.fake]][17425]:
Failed to read keytab [default]: Bad address
Feb 24 11:04:22 my.host.fake sssd[17406]: Exiting the SSSD.
Could
On 02/23/2016 05:38 PM, lejeczek wrote:
> On 23/02/16 15:04, Rob Crittenden wrote:
>> lejeczek wrote:
>>> hi everybody
>>>
>>> I'm trying server installation but it fails, I think very last leg, and
>>> I was hoping you could suggest places which I should start looking at.
>>>
>>>[7/7]:
On 23.02.2016 20:41, Olivier Cervello wrote:
Hello,
I am trying to delete DNS record with the /--updatedns/ options of
/ipa host-del/ command.
The steps I followed were:
/
/
/root@server$ kinit admin/
/root@server$ ipa host-del --updatedns/
/'ipa: ERROR: : host not found'./
The
On (23/02/16 23:50), Harald Dunkel wrote:
>Hi Lukas,
>
>On 02/23/16 13:46, Lukas Slebodnik wrote:
>> On (23/02/16 13:01), Harald Dunkel wrote:
>>> On 02/23/2016 11:58 AM, Lukas Slebodnik wrote:
I would rather focus on different thing. Why is sssd_be process blocked
for long time?
On Tue, Feb 23, 2016 at 11:50:10PM +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Lukas,
>
> On 02/23/16 13:46, Lukas Slebodnik wrote:
> > On (23/02/16 13:01), Harald Dunkel wrote:
> >> On 02/23/2016 11:58 AM, Lukas Slebodnik wrote:
> >>> I would rather
20 matches
Mail list logo
