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. Login (Tim Polimeni)
2. Re: Login (Christian Ramseyer)
3. Re: Login (Christian Ramseyer)
4. Re: Login (Christian Ramseyer)
5. remote collector (Ricardo Stella)
6. Re: remote collector (Christian Ramseyer)
--- Begin Message ---
Hello, I havent messed with my netdisco setup in some time as it was a side
project, I can't recall what I used for a login. Is there any way that I
can reset the UID password to regain access?
--- End Message ---
--- Begin Message ---
Hi Tim
On 09.04.21 19:05, Tim Polimeni wrote:
> Hello, I havent messed with my netdisco setup in some time as it was a
> side project, I can't recall what I used for a login. Is there any way
> that I can reset the UID password to regain access?
>
If you remove the admin flag from all users and run netdisco-deploy
again, it will ask to create a new admin user:
$ netdisco-do psql
netdisco => update users set admin = false;
UPDATE 4 (can be any number depending on table content)
netdisco => \q
$ netdisco-deploy
This is the Netdisco 2 deployment script.
<sniped...>
So, is all of the above in place? [y/N]: y
Would you like to deploy the database schema? [y/N]: y
DB schema update complete.
Updating statistics... done.
We need to create a user for initial login. This user will be a full
Administrator.
Afterwards, you can go to Admin -> User Management to manage users.
Username: : admin2
Password: : hunter2
Cheers
Christian
--
Christian Ramseyer, netnea ag
Network Management. Security. OpenSource.
--- End Message ---
--- Begin Message ---
On 09.04.21 20:06, Tim Polimeni wrote:
> Thanks it looks like I have some challenges as well after I updated to
> the lasted version I get the following as well
>
>
>
> Before we continue, the following prerequisites must be in place:
> * Database added to PostgreSQL for Netdisco
> * User added to PostgreSQL with rights to the Netdisco Database
> * "~/environments/deployment.yml" file configured with Database
> dsn/user/pass
> * A full backup of any existing Netdisco database data
> * Internet access (for OUIs and MIBs)
>
> If you are upgrading Netdisco 2 read the release notes:
> https://github.com/netdisco/netdisco/wiki/Release-Notes
> <https://github.com/netdisco/netdisco/wiki/Release-Notes>
> There you will find required and incompatible changes
> which are not covered by this script.
>
> You will be asked to confirm all changes to your system.
>
> So, is all of the above in place? [y/N]: y
>
> Would you like to deploy the database schema? [y/N]: y
> DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
> unversioned. Please call upgrade on your schema to sync the DB. at
> /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed:
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
> connect('dbname=netdisco','netdisco',...) failed: FATAL: remaining
> connection slots are reserved for non-replication superuser connections
> at /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639.
> at /home/netdisco/perl5/bin/netdisco-db-deploy line 110 at
> /home/netdisco/perl5/bin/netdisco-db-deploy line 110
> DB schema update complete.
> DBIx::Class::Schema::Versioned::_on_connect(): Your DB is currently
> unversioned. Please call upgrade on your schema to sync the DB. at
> /home/netdisco/perl5/lib/perl5/DBICx/Sugar.pm line 121
> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
> connect('dbname=netdisco','netdisco',...) failed: FATAL: remaining
> connection slots are reserved for non-replication superuser connections
> at /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1639.
> at /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Statistics.pm line 37
> Updating statistics... [netdisco@netengsrv01 ~]$
>
>
> [netdisco@netengsrv01 ~]$ netdisco-do psql
> [3955495] 2021-04-09 18:06:06 info App::Netdisco version 2.047005 loaded.
> [3955495] 2021-04-09 18:06:06 info psql: started at Fri Apr 9
> 14:06:06 2021
> psql: FATAL: remaining connection slots are reserved for
> non-replication superuser connections
> [3955495] 2021-04-09 18:06:06 info psql: finished at Fri Apr 9
> 14:06:06 2021
> [3955495] 2021-04-09 18:06:06 info psql: status done: psql session closed.
> [netdisco@netengsrv01 ~]$
>
Yes looks like your database is in some trouble. If this is a local
database just for Netdisco I'd just stop the netdisco-backend, this will
likely solve the issue and it does not need to run for netdisco-deploy.
If it does not solve the issue, try to also restart postgres or the
whole server as a low-effort fix attempt.
If you want to dig into the details try to connect to the database
directly with psql as user postgres, and look at pg_stat_activity to see
what's going on.
Cheers
Christian
--- End Message ---
--- Begin Message ---
On 09.04.21 20:32, Tim Polimeni wrote:
> Thanks, I restarted the server and that fixed the DB issues...
>
> when trying to run the commands with the login issue I got the following
> message.
>
> [netdisco@netengsrv01 ~]$ netdisco-do psql
> [10900] 2021-04-09 18:29:03 info App::Netdisco version 2.047005 loaded.
> [10900] 2021-04-09 18:29:03 info psql: started at Fri Apr 9 14:29:03 2021
> psql (10.15)
> Type "help" for help.
>
> netdisco=> netdisco => update users set admin = false;
> ERROR: syntax error at or near "netdisco"
> LINE 1: netdisco => update users set admin = false;
You need to leave out the "netdisco =>", that was meant to symbolize the
"netdisco =>" prompt you already have there :)
Cheers
Christian
--- End Message ---
--- Begin Message ---
We had a site that was directly connected to us in the past that now it has
become a semi separate network and we no longer can directly see it's
devices. I found a thread where Oliver says you could run a remote
"netdisco-backend" and have it report to the main DB and web front end.
If so, would the process be just do a full install but then have
netdisco-backend point to the main system? How would this be done? Am I
missing a Wiki entry here?
Thanks in advance - Ricardo.
--
°(((=((===°°°(((================================================
--- End Message ---
--- Begin Message ---
On 09.04.21 22:56, Ricardo Stella wrote:
>
> We had a site that was directly connected to us in the past that now it
> has become a semi separate network and we no longer can directly see
> it's devices. I found a thread where Oliver says you could run a remote
> "netdisco-backend" and have it report to the main DB and web front end.
>
> If so, would the process be just do a full install but then have
> netdisco-backend point to the main system? How would this be done? Am I
> missing a Wiki entry here?
Hi Ricardo
Yes that is pretty much it, just install a second Netdisco but change
the database: settings in it to point to the "main" database. Use
devices_no/devices_only to distribute your networks between the two.
There is a short bit about it in the wiki here:
https://github.com/netdisco/netdisco/wiki/Install-Tips#run-multiple-poller-daemons
Cheers
Christian
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
