Send netdisco-users mailing list submissions to
[email protected]
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
[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 netdisco-users digest..."
Today's Topics:
1. Re: No more MAC to IP resolution on remote campus(es)!
(Nikolaos Milas)
--- Begin Message ---
Thank you Christian for your feedback. See some more info inline:
On 24/10/2019 3:06 μ.μ., Christian Ramseyer wrote:
I imagine that's because the entries did not get updated anymore, at
some point the expiration kicks in and deletes them. This depends on
your expire_nodes and expire_nodeip_freshness, by default they would
disappear after 90 days.
Nothing like that; right after upgrade, Netdisco immediately seems to
have lost all old data regarding the IP addresses which were not found
by sshcollector.
I hope this is not a bug, but it deserves a bit of attention just in
case, so as to not cause disaster to others like me.
Yes you can do both. The restore and deploy should work exactly as you
wrote.
I thought I could try to create a new postgres database to restore the
backed-up database, then change the deployment.yml to point to that db.
I will have to clean the dump-all backup sql file to only include what
is necessary for the db restore and then try to restore the initial db.
Knowing very little about postgresql I feel very uneasy working with it
(I mainly have a mysql background). I will have to find some time to try
things out.
Thank you again,
Nick
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
