OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: LDAP in 4.11.1


Thank you Daan. I figured this out.. But I am running into another issue now..

I am trying to add a primary storage for XCP-ng and I am getting an error. This is a pre-setup SR with multipath and the hosts see it fine. But when I go to add it to CLoudstack as a pre-setup primary, I get:

2018-08-02 17:03:20,102 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-19:ctx-9a3e5577) (logid:dec346aa) SR retrieved for ST1-iSCSI
2018-08-02 17:03:20,106 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-19:ctx-9a3e5577) (logid:dec346aa) Checking ST1-iSCSI or SR 61b7c55f-ce1c-7218-be52-ce04a5abc8e6 on XS[fb21ae16-4dad-4a8d-8056-9568711bf9bb-10.10.24.29]
2018-08-02 17:03:20,114 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-19:ctx-9a3e5577) (logid:dec346aa) Setting up the heartbeat sr for host 10.10.24.29 and sr 61b7c55f-ce1c-7218-be52-ce04a5abc8e6
2018-08-02 17:03:20,380 WARN  [c.c.h.x.r.w.x.CitrixModifyStoragePoolCommandWrapper] (DirectAgent-19:ctx-9a3e5577) (logid:dec346aa) ModifyStoragePoolCommand add XenAPIException:Unable to setup heartbeat sr on SR 61b7c55f-ce1c-7218-be52-ce04a5abc8e6 due to #7# volume hb-fb21ae16-4dad-4a8d-8056-9568711bf9bb is not created host:fb21ae16-4dad-4a8d-8056-9568711bf9bb pool: localhost/ST1-iSCSI
com.cloud.utils.exception.CloudRuntimeException: Unable to setup heartbeat sr on SR 61b7c55f-ce1c-7218-be52-ce04a5abc8e6 due to #7# volume hb-fb21ae16-4dad-4a8d-8056-9568711bf9bb is not created

The hosts see it with no issues.

Thoughts?

-----Original Message-----
From: Daan Hoogland <daan.hoogland@xxxxxxxxx> 
Sent: Thursday, August 2, 2018 4:47 PM
To: users@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: LDAP in 4.11.1

Marty, Ilya is right I worked on this a few months ago, so let me try and help you.

It sounds like you are mixing two types of ldap integration, There are
three:
1: link individual account
2: link a domain for which auto import will be enabled, this one will auto create an account for each user
3: link a domain and accounts within it to administer your users in ldap

Which of the three are you trying?
Where did you add the basedn, globally or on the domain?


On Thu, Aug 2, 2018 at 10:01 PM, Rafael Weingärtner < rafaelweingartner@xxxxxxxxx> wrote:

> What is the content of your "ldap.basedn" parameter?
>
> On Thu, Aug 2, 2018 at 4:58 PM, ilya musayev 
> <ilya.mailing.lists@xxxxxxxxx
> >
> wrote:
>
> > You are most likely getting incorrect query to ldap.
> >
> > If you can - use ldap connectivity without ssl and do tcpdump to see 
> > if
> you
> > can capture the ldapquery.
> >
> > You can then identify the issue. Alternately, you can look into 
> > enabling trace logging for ldap module and perhaps it prints the query.
> >
> > Daan can shed more details on this issue as he was the one working on it.
> >
> > On Thu, Aug 2, 2018 at 12:55 PM <martygodsey@xxxxxxxxxxxxx> wrote:
> >
> > > Yes, full restart of management server to be safe. I have tried 
> > > putting
> > in
> > > the LDAP name, the Pre-Windows name, etc..
> > >
> > > -----Original Message-----
> > > From: Rafael Weingärtner <rafaelweingartner@xxxxxxxxx>
> > > Sent: Thursday, August 2, 2018 1:22 PM
> > > To: users <users@xxxxxxxxxxxxxxxxxxxxx>
> > > Subject: Re: LDAP in 4.11.1
> > >
> > > Did you restart ACS after configuring it?
> > >
> > > On Thu, Aug 2, 2018 at 2:03 PM, <martygodsey@xxxxxxxxxxxxx> wrote:
> > >
> > > > Hello guys,
> > > >
> > > >
> > > >
> > > > I am attempting to bind an ACS domain to an LDAP domain and I 
> > > > get the error "can not link a domain unless a basedn is configured for it"
> but
> > > > this is set in the settings. Anyone seen this?
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>



--
Daan