On 2011-02-21, at 15:09, Rob Crittenden wrote:
> Boy, it could be a lot of things. I'd start by checking the SELinux log
> in /var/log/audit.log. Are you running in permissive or enforcing mode?
SELinux was disabled during the test
> telnet is not very effective on SSL ports, you might want to
On 02/21/2011 07:10 AM, Simo Sorce wrote:
On Mon, 21 Feb 2011 02:07:36 +0100
"tomasz.napier...@allegro.pl" wrote:
Feb 20 23:47:19 Updated: 389-ds-base-1.2.7.5-1.fc13.x86_64
Any one have an idea what could be the reason?
If I remember correctly, some people reported similar issues with 1.2.7
On Mon, 21 Feb 2011 02:07:36 +0100
"tomasz.napier...@allegro.pl" wrote:
> Feb 20 23:47:19 Updated: 389-ds-base-1.2.7.5-1.fc13.x86_64
>
> Any one have an idea what could be the reason?
If I remember correctly, some people reported similar issues with 1.2.7
It doesn't affect everyone but afaik th
tomasz.napier...@allegro.pl wrote:
Hi,
Although I was very happy with FreeIPA on F12, due to compliance issues I had
to upgrade our master server from F12 to F13. I tried several methods, and only
yum upgrade was semi succesful.
After upgrade 389 seems to be running fine, with one exception: i
Hi,
Although I was very happy with FreeIPA on F12, due to compliance issues I had
to upgrade our master server from F12 to F13. I tried several methods, and only
yum upgrade was semi succesful.
After upgrade 389 seems to be running fine, with one exception: it stops
responding queries after few