Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. How do I debug LDAP for web (Daryl Fonseca-Holt)
2. Re: How do I debug LDAP for web (Oliver Gorwits)
3. Re: netdisco 2 and Dell Powerconnect 5524 and 5548 Hardware
Status (Oliver Gorwits)
4. Re: How do I debug LDAP for web (Daryl Fonseca-Holt)
5. Re: How do I debug LDAP for web (Oliver Gorwits)
6. netdisco 2 scheduling (Federici, Marc)
7. Re: netdisco 2 scheduling (Oliver Gorwits)
--- Begin Message ---
Hello All,
When I add a new user from the admin account with full name Daryl
Fonseca-Holt, username Daryl Fonseca-Holt, Password <blank>, and checked
LDAP Auth, Port Control, and Administrator when I click +Add Action the
orignal page is displayed with no error message and the user is not added.
I tried increasing the logging level (see below) and also did what the
Troubleshooting Guide suggested:
[netdisco@umbriel ~]$ ~netdisco/bin/localenv cpanm --notest Dancer::Debug
DANCER_DEBUG=1 ~/bin/netdisco-web restart
But I get nothing useful in the web.log or the side panel that
DANCER_DEBUG adds.
The admins told me the fully distinguished name should look like:
CN=Daryl Fonseca-Holt,OU=Users,OU=Information Services and
Technology,OU=CORP,DC=ad,DC=umanitoba,DC=ca
I've set the LDAP section in deployment.yml as follows:
ldap:
servers:
- 'umce3addc01.ad.umanitoba.ca'
- 'umce3addc02.ad.umanitoba.ca'
- 'umcv1addc03.ad.umanitoba.ca'
base: 'OU=Users,OU=Information Services and
Technology,OU=CORP,DC=ad,DC=umanitoba,DC=ca'
user_string: 'CN=%USER%'
opts:
debug: 3
log: debug
Can anyone suggest how to debug this? The documentation is not clear where the
opts: debug 3 logging ends up.
Thanks,
Daryl
--
--
Daryl Fonseca-Holt, Network Architect, University of Manitoba, 204.480.1079
--- End Message ---
--- Begin Message ---
Hi Daryl,
On 2015-02-25 19:06, Daryl Fonseca-Holt wrote:
When I add a new user from the admin account with full name Daryl
Fonseca-Holt, username Daryl Fonseca-Holt, Password <blank>, and
checked
LDAP Auth, Port Control, and Administrator when I click +Add Action
the
orignal page is displayed with no error message and the user is not
added.
The LDAP user needs to exist in Netdisco's database with a username,
and only then will LDAP authentication work.
However you're failing to get the user into Netdisco, and the reason is
that we didn't permit usernames with whitespace in. According the the DN
from your colleague, the CN is your full name including whitespace.
Therefore you should use the following settings for your Netdisco user
(NB username):
Full Name: Daryl Fonseca-Holt
Username: Daryl Fonseca-Holt
LDAP Auth: ticked
Administrator: ticked
The admins told me the fully distinguished name should look like:
CN=Daryl Fonseca-Holt,OU=Users,OU=Information Services and
Technology,OU=CORP,DC=ad,DC=umanitoba,DC=ca
I've just released version 2.031009 of Netdisco to CPAN with a fix. It
should be on the mirrors in a couple of hours, and you can follow the
upgrade instructions here:
https://metacpan.org/pod/App::Netdisco#Upgrading-from-2.x
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hi David,
On 2015-02-23 22:51, David Weise wrote:
No, I'm saying it's not displaying in Netdisco 2. (I have no idea
if it's working in our Netdisco 1.x, but I'll take a look). The
class displayed in Netdisco 2 is SNMP::Info::Layer3::Dell [1]
Yeah, it looks like that Layer3::Dell class does nothing for Fan and
PSU status. Oddly it *does* expose the MIB leafs with friendly names,
but then never provides a fan(), ps1_status() or ps2_status().
https://metacpan.org/source/OLIVER/SNMP-Info-3.24/Info/Layer3/Dell.pm
Could you provide please the output of the following for the relevant
device-IP, if they look sensible?
for leaf in dell_pwr_src dell_pwr_state dell_pwr_desc dell_fan_state
dell_fan_desc
do
~netdisco/bin/netdisco-do show -d 1.2.3.4 -e $leaf
done
regards,
oliver.
--- End Message ---
--- Begin Message ---
On 02/25/15 15:24, Oliver Gorwits wrote:
Hi Daryl,
On 2015-02-25 19:06, Daryl Fonseca-Holt wrote:
When I add a new user from the admin account with full name Daryl
Fonseca-Holt, username Daryl Fonseca-Holt, Password <blank>, and
checked
LDAP Auth, Port Control, and Administrator when I click +Add Action
the
orignal page is displayed with no error message and the user is not
added.
The LDAP user needs to exist in Netdisco's database with a username,
and only then will LDAP authentication work.
However you're failing to get the user into Netdisco, and the reason is
that we didn't permit usernames with whitespace in. According the the DN
from your colleague, the CN is your full name including whitespace.
Therefore you should use the following settings for your Netdisco user
(NB username):
Full Name: Daryl Fonseca-Holt
Username: Daryl Fonseca-Holt
LDAP Auth: ticked
Administrator: ticked
The admins told me the fully distinguished name should look like:
CN=Daryl Fonseca-Holt,OU=Users,OU=Information Services and
Technology,OU=CORP,DC=ad,DC=umanitoba,DC=ca
I've just released version 2.031009 of Netdisco to CPAN with a fix. It
should be on the mirrors in a couple of hours, and you can follow the
upgrade instructions here:
https://metacpan.org/pod/App::Netdisco#Upgrading-from-2.x
regards,
oliver.
Thanks Oliver. I upgraded and the usernames with blanks are
authenticating just fine. I couldn't just change the username from their
old Unix userid without blanks to their full names. Instead I had to
delete their old record then add a new one with the username containing
blanks. Not a big task we only have a dozen users that are allowed access.
Regards,
Daryl
--- End Message ---
--- Begin Message ---
On 2015-02-26 15:20, Daryl Fonseca-Holt wrote:
Thanks Oliver. I upgraded and the usernames with blanks are
authenticating just fine. I couldn't just change the username from
their
old Unix userid without blanks to their full names. Instead I had to
delete their old record then add a new one with the username
containing
blanks. Not a big task we only have a dozen users that are allowed
access.
Okay, many thanks for letting me know it's working now.
I'll check that username edit works correctly as well.
regards,
oliver.
--- End Message ---
--- Begin Message ---
Hello,
I seem to be having a problem with the scheduler not kicking off correctly.
The discoverall kicks off at 7AM but none of the others want to run after that.
I've tried formatting the schedule jobs per the example posted on cpan and
still no luck. Other than the scheduler not kicking off the app seems to be
running fine. I can manually run all of the jobs individually with no errors.
environments/deployment.yml
schedule:
discoverall:
when: '5 7 * * *'
arpwalk:
when: '5 09-18 * * *'
macwalk:
when: '10 09-18 * * *'
nbtwalk:
when: '15 09-18 * * *'
expire:
when: '20 09-18 * * *'
~/bin/localenv cpanm Algorithm::Cron
Algorithm::Cron is up to date. (0.09)
Thanks,
-marc
This E-mail, along with any attachments, is considered confidential and may
well be legally privileged. If you have received it in error, you are on notice
of its status. Please notify us immediately by reply e-mail or call
215-931-0300 / 800-228-8801 and then delete this message from your system.
Please do not copy it or use it for any purposes, or disclose its contents to
any other person. Thank you for your cooperation.
--- End Message ---
--- Begin Message ---
Hi Marc,
On 2015-02-26 16:07, Federici, Marc wrote:
I seem to be having a problem with the scheduler not kicking off
correctly. The discoverall kicks off at 7AM but none of the others
want to run after that. I've tried formatting the schedule jobs per
the example posted on cpan and still no luck. Other than the
scheduler
not kicking off the app seems to be running fine. I can manually run
all of the jobs individually with no errors.
I suspect that, from the way your snippet is formatted in your email,
that you tripped over the whitespace sensitivity in the config file.
The word schedule should have no leading whitespace. The words
discoverall,arpwalk,macsuck,nbtwalk,expire should have *the same*
leading whitespace, at least one space. The "when" lines should have
some leading whitespace, more than the other lines. Watch out for TAB
characters in your editor which might make it look like indentation is
the same, when it isn't.
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Configuration.pod#schedule
A rather more involved way to check the parsing of the configuration is
to follow the instructions under "Debug HTTP Requests and Configuration"
on this page, which provides an option in a sidebar to show the parsed
deployment.yml file:
https://metacpan.org/pod/distribution/App-Netdisco/lib/App/Netdisco/Manual/Troubleshooting.pod#Debug-HTTP-Requests-and-Configuration
regards,
oliver.
environments/deployment.yml
schedule:
discoverall:
when: '5 7 * * *'
arpwalk:
when: '5 09-18 * * *'
macwalk:
when: '10 09-18 * * *'
nbtwalk:
when: '15 09-18 * * *'
expire:
when: '20 09-18 * * *'
~/bin/localenv cpanm Algorithm::Cron
Algorithm::Cron is up to date. (0.09)
Thanks,
-marc
This E-mail, along with any attachments, is considered confidential
and may well be legally privileged. If you have received it in error,
you are on notice of its status. Please notify us immediately by
reply
e-mail or call 215-931-0300 / 800-228-8801 and then delete this
message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person. Thank you for
your cooperation.
--- End Message ---
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
