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. Using MakeRancidConf for Oxidized (Ricardo Stella)
2. Re: how to modify report: add column to ip inventory
(Christian Ramseyer)
--- Begin Message ---
I was hoping I could take advantage of the Rancid worker to create a
routers.db for Oxidized (which is running on another box at this time)
It seems the worker is looking for a Rancid installation and complains
about not finding rancid.types.base and rancid.types.conf. Is there a way
to create the routers.db or do some sort of csv export that I could then
use with oxidized? At a minimum IP address and system name?
Thanks in advance.
--
°(((=((===°°°(((================================================
--- End Message ---
--- Begin Message ---
Hi
On 08.05.20 10:57, Adrian Sevcenco wrote:
>> lib/App/Netdisco/Web/Plugin/Report/IpInventory.pm
>> share/views/ajax/report/ipinventory.tt
>> share/views/ajax/report/ipinventory_csv.tt
> so, i tried these files and, while i doubt is related to, now i have an
> empty netdisco installation.
Yes sounds unlikely to be the cause, excluding some freak accident :)
>
> the postgres tables seem to be fine, in the netdisco logs i have no
> errors and i spent days trying to debug this ...
>
> is there a increase debug info option for both backend and web services?
>
I think it's easiest to use the netdisco-do command to see what's really
going on. It has various debug switches [-DISQ]. To see you can still
discover a device:
netdisco-do discover -D -d <ip>
Same for macsuck and arpnip actions.
Then if this terminates without error, you can check what ended up in
the database:
netdisco-do psql, then in the sql prompt:
select * from device where ip = '<ip>';
To get debug output from the gui, you can start it in the foreground on
an alternate port like this:
./localenv starman ./netdisco-web-fg \
--workers=1 --disable-keepalive -p 7000
Then point your browser at localhost:7000
Hard to tell what really happened, but if you play around with these a
little bit and see anything suspicious, that might help further.
You might also want to check your config for the schedule, device_auth
and database sections, to see if you're talking to the DB and devices
you expect. Maybe also check if netdisco-backend is still running and
started on boot (the processes show as e.g. "nd2: #4 poll: idle" in ps
output).
Just some stabs in the dark..
Cheers
Christian
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
