Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. [Netdot - Feature #1781] Adding the possibility to
authenticate using LDAP with differents subordinates groups
([email protected])
2. odd PostgreSQL ping tests in v1.0.4 (William Bulley)
3. Re: odd PostgreSQL ping tests in v1.0.4 (Anton Berezin)
4. Re: odd PostgreSQL ping tests in v1.0.4 (William Bulley)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 Apr 2014 05:17:07 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Feature #1781] Adding the
possibility to authenticate using LDAP with differents subordinates
groups
To: [email protected], [email protected],
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1781 has been updated by Blakkheim GW.
Hello,
It doesn't work even when commenting this line. Looking on LDAP server side, it
tries to bind with only "uid=myname" without the rest of the DN.
----------------------------------------
Feature #1781: Adding the possibility to authenticate using LDAP with
differents subordinates groups
https://osl.uoregon.edu/redmine/issues/1781#change-3171
Author: Blakkheim GW
Status: Feedback
Priority: Normal
Assignee: Carlos Vicente
Category: Netdot
Target version:
Resolution:
We would like to be able to authenticate using our LDAP server with multiple
subordinates groups. In the latest version of Netdot, the application append
the NetdotLDAPSearchBase to the user DN so if you have differents users in
differents groups, the auth fails.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 2
Date: Tue, 29 Apr 2014 12:10:07 -0400
From: William Bulley <[email protected]>
Subject: [Netdot-devel] odd PostgreSQL ping tests in v1.0.4
To: [email protected]
Cc: Carlos Vicente <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
I'm not quite sure what to make of this... :-(
Today I just discovered several (more than a dozen) so-called "idle"
sessions after running this sub-command from within the psql(1) command:
netdot=# select * from pg_stat_activity;
There are "sub ping" and "sub pg_ping" methods inside DBD::Pg and
that is the ultimate source of the rows generated as output from
the above SELECT command.
During the morning I was logging into and logging out of Netdot v1.0.4
while doing some testing.
The user name on all the output is "netdot_user" which seems to imply
that Netdot is in some "idle" state (which in some sense it is once
I log out!). But this is still confusing to me. Can anyone shed any
light on this (Anton perhaps?) and tell me this is normal or not?
Thanks in advance.
Regards,
web...
--
William Bulley Email: [email protected]
72 characters width template ----------------------------------------->|
------------------------------
Message: 3
Date: Tue, 29 Apr 2014 18:37:26 +0200
From: Anton Berezin <[email protected]>
Subject: Re: [Netdot-devel] odd PostgreSQL ping tests in v1.0.4
To: William Bulley <[email protected]>
Cc: Carlos Vicente <[email protected]>,
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi web,
On Tue, Apr 29, 2014 at 12:10:07PM -0400, William Bulley wrote:
> Today I just discovered several (more than a dozen) so-called "idle"
> sessions after running this sub-command from within the psql(1) command:
>
> netdot=# select * from pg_stat_activity;
>
> There are "sub ping" and "sub pg_ping" methods inside DBD::Pg and
> that is the ultimate source of the rows generated as output from
> the above SELECT command.
>
> During the morning I was logging into and logging out of Netdot v1.0.4
> while doing some testing.
>
> The user name on all the output is "netdot_user" which seems to imply
> that Netdot is in some "idle" state (which in some sense it is once
> I log out!). But this is still confusing to me. Can anyone shed any
> light on this (Anton perhaps?) and tell me this is normal or not?
"Idle" is totally harmless and totally normal, it just tells you that there
is a connection to the DB (most likely the Netdot mod_perl Apache
instances).
"Idle in transaction" would be a cause of some concern though.
\Anton.
--
Our society can survive even a large amount of irrational regulation.
-- John McCarthy
------------------------------
Message: 4
Date: Tue, 29 Apr 2014 13:06:20 -0400
From: William Bulley <[email protected]>
Subject: Re: [Netdot-devel] odd PostgreSQL ping tests in v1.0.4
To: Anton Berezin <[email protected]>
Cc: Carlos Vicente <[email protected]>,
[email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
According to Anton Berezin <[email protected]> on Tue, 04/29/14 at 12:37:
>
> "Idle" is totally harmless and totally normal, it just tells you that there
> is a connection to the DB (most likely the Netdot mod_perl Apache
> instances).
>
> "Idle in transaction" would be a cause of some concern though.
Thanks for the prompt reply! ;-)
You say "Idle" is 'harmless' but in other databases, there are limits
on the number of sessions (even though there is only one connection
as in the case of Netdot). Does the PostgreSQL server have any limits
on the number of such sessions?
Another problem occurs when, after several hours/days of testing,
we issue the following command as "root" from the top of the Netdot
file tree:
# make dropdb (to be later followed by "# make installdb")
the make(1) session complains with the error that there are "n"
sessions still using the PostgreSQL server and therefore the "drop"
action cannot be completed.
At this point, the "postgres" user must intervene and clear the
offending "sessions".
BTW, each "login" to Netdot causes two such "ping" entries, and each
"logout" from Netdot by a user causes two more "ping" entries to be added.
Regards,
web...
--
William Bulley Email: [email protected]
72 characters width template ----------------------------------------->|
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 85, Issue 17
********************************************
