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: How does netdisco-web resolve its hostname? (Stuart Kendrick)
--- Begin Message ---
FWIW: IPv6 is disabled on this system ...
[new-server etc]$ tail /etc/sysctl.conf
[...]
# Disable IPv6
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.lo.disable_ipv6=1
[stuartk@ganesh etc]$
[new-server ~]$ ip a | grep inet6
[new-server ~]$
Perhaps this is relevant, perhaps not
--sk
From: Oliver Gorwits <oli...@cpan.org>
Sent: Wednesday, December 20, 2023 3:26 AM
To: Stuart Kendrick <stua...@alleninstitute.org>
Cc: netdisco-users@lists.sourceforge.net
Subject: Re: [Netdisco] How does netdisco-web resolve its hostname?
CAUTION: This email originated from outside the Allen Institute. Please do not
click links or open attachments unless you've validated the sender and know the
content is safe.
________________________________
I'm glad to hear! Many thanks for letting us know,
Oliver.
On Wed, 20 Dec 2023 at 11:22, Stuart Kendrick
<stua...@alleninstitute.org<mailto:stua...@alleninstitute.org>> wrote:
This solved the issue
I have added
Environment=IPV=4
to /etc/systemd/system/netdisco-web.service
thank you
--sk
From: Oliver Gorwits <oli...@cpan.org<mailto:oli...@cpan.org>>
Sent: Wednesday, November 15, 2023 11:41 AM
To: Stuart Kendrick
<stua...@alleninstitute.org<mailto:stua...@alleninstitute.org>>
Cc:
netdisco-users@lists.sourceforge.net<mailto:netdisco-users@lists.sourceforge.net>
Subject: Re: [Netdisco] How does netdisco-web resolve its hostname?
CAUTION: This email originated from outside the Allen Institute. Please do not
click links or open attachments unless you've validated the sender and know the
content is safe.
________________________________
Hi Stuart
I wonder if IPv6 is interfering. Perhaps try with IPV=4 environment variable
set?
https://github.com/netdisco/netdisco/wiki/Environment-Variables#ipv
Regards
Oliver.
On Wed, 15 Nov 2023 at 18:27, Stuart Kendrick
<stua...@alleninstitute.org<mailto:stua...@alleninstitute.org>> wrote:
BRIEF
* How does netdisco-web resolve its hostname?
BACKGROUND
* I am currently running NetDisco under CentOS 7.9
* I have a built a new box running Rocky 9.2 and am installing NetDisco
DETAIL
On the new box ('new-server'), when I load the Web front-end:
[netdisco@new-server ~]$ ~/bin/netdisco-web start
Netdisco Web [Started]
config watcher: watching /home/netdisco/environments for updates.
[netdisco@new-server ~]$
I see the following in /home/netdisco/logs/netdisco-web.log
Resolved [*]:5000 to [::]:5000, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::]
IPv6
Binding to TCP port 5000 on host :: with IPv6
2023/11/14-10:47:44 Can't connect to TCP port 5000 on :: [Invalid argument] at
line 66 in file /home/netdisco/perl5/lib/perl5/Net/Server/Proto/TCP.pm
2023/11/14-10:47:44 Received QUIT. Running a graceful shutdown
2023/11/14-10:47:44 Worker processes cleaned up
2023/11/14-10:47:44 Server closing!
And nothing is listening on TCP 5000
[root@new-server ~]# lsof -nP -i:5000
[root@new-server ~]#
So, examining those logs messages ... seems to me that the Web front-end is
having trouble resolving its hostname ...
If I specify host, the Web front-end loads fine:
[netdisco@new-server ~]$ bin/netdisco-web start --host 127.0.0.1
Netdisco Web [Started]
config watcher: watching /home/netdisco/environments for updates.
[netdisco@new-server ~]$ bin/netdisco-web stop
config watcher: sending TERM to the web server (pid:411033)...
Netdisco Web [Stopped]
[netdisco@new-server ~]$ bin/netdisco-web start --host new-server
config watcher: watching /home/netdisco/environments for updates.
Netdisco Web [Started]
[netdisco@new-server ~]$
And I see comforting feedback in the log:
Binding to TCP port 5000 on host 127.0.0.1 with IPv4
[411034] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411035] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411038] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411037] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411036] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
2023/11/15-09:39:01 Server closing!
2023/11/15-09:39:14 Starman::Server (type Net::Server::PreFork) starting!
pid(445758)
Resolved [ganesh]:5000 to [10.1.2.3]:5000, IPv4
Binding to TCP port 5000 on host 10.1.2.3with IPv4
[445760] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445759] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445761] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445762] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445763] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
And I can point a browser at the appropriate hostname and get in fine:
[cid:image001.png@01DA32F4.B7F24D50]
How does netdisco-web figure out what IP address to bind to?
--sk
Stuart Kendrick
_______________________________________________
Netdisco mailing list
netdisco-users@lists.sourceforge.net<mailto: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
