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. Re: OS Upgrade options on customized Netdisco install (brian)
--- Begin Message ---
Hi Christian,
Thanks for the great debugging tips!
It ended up being fairly simple once I had some better error output.
It turns out there was a change in the way non-string data was handled
in one of the javascript libraries (I think in jquery), which had been
patched in newer netdisco, but was still the old mechanism in my
install.
I just had to run "sed -i 's/return data.replace/return
data.toString().replace/g'" in the
netdisco/perl5/lib/perl5/auto/share/dist/App-Netdisco/views/ajax/report/
directory and everything went back to working as expected.
Thanks again for all your help!
-Brian
On 2023-01-31 16:43, Christian Ramseyer wrote:
On 30.01.23 20:10, brian wrote:
I've managed to get everything working on Debian Buster
nice!
The only remaining problem I have with this setup is that some of the
reports go away and never come back, just showing "Processing..."
forever. Most of the inventory type reports but also things like "Port
Utilization". Seems like about half the reports aren't working and
there isn't an error that hits any of the logs. Any idea what would
have changed on the underlying perl etc side to wreck the reporting
for me? Any extra debugging I should turn on to help troubleshoot?
You can check the postgres logs to see if an illegal query hits the
database. The file should be somewhere in /var/log/postgresql/ on
Debian.
You can enable the developer tools in the browser (e.g. F12 in
Firefox), there is a Console tab there that will show javascript/ajax
crashes.
You can start the web server with some debugging and sql output like
so:
~/perl5/bin/localenv bash
DBIC_TRACE=1 plackup -p 5001 -R share,lib,~/environments
bin/netdisco-web-fg
(this is from https://github.com/netdisco/netdisco/wiki/Developing,
maybe you need to fiddle with the PATH and -R flags for it to work on
the cpan installation instead of the git checkout)
In one of these you should be able to see what's going wrong.
Good luck!
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net
https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
