Registration issues starting Jul 27
Atlas mailed me a while ago for probe downtime (ID 1000023), though my network is still working. I also have seen a high amount of (re-)connections from today (July 27th) which is also weird. You can see them on https://atlas.ripe.net/probes/1000023/#!tab-network I also got a journalctl snippet available on https://paste.debian.net/plainh/cacd78f8 Regards, Ilteris
On 2020/07/27 17:34 , İlteriş Yağıztegin Eroğlu wrote:
Atlas mailed me a while ago for probe downtime (ID 1000023), though my network is still working.
There should be a process called '/usr/local/atlas/bb-13.3/usr/sbin/telnetd' that is listening on port 2023. From our logs it seems that that process is not running on your probe. Philip Homburg
On Mon, Jul 27, 2020, 18:45 Philip Homburg wrote:
There should be a process called '/usr/local/atlas/bb-13.3/usr/sbin/telnetd' that is listening on port 2023. From our logs it seems that that process is not running on your probe.
I have checked that my probe is indeed running it. linuxgemini at centos in ~ $ netstat -tulpn | grep :2023 tcp 0 0 127.0.0.1:2023 0.0.0.0:* LISTEN 1189/telnet linuxgemini at centos in ~ $ ps aux | grep telnetd atlas 1189 0.0 0.0 46892 752 ? Ss 18:09 0:00 /usr/local/atlas/bb-13.3/usr/sbin/telnetd -b 127.0.0.1 -p 2023 -P /var/atlas-probe/run/telnetd-port2023-pid.vol
On 2020/07/27 18:29 , İlteriş Yağıztegin Eroğlu wrote:
linuxgemini at centos in ~ $ netstat -tulpn | grep :2023 tcp 0 0 127.0.0.1:2023 <http://127.0.0.1:2023> 0.0.0.0:* LISTEN 1189/telnet
I'll try to figure out if it is an issue on our end Philip Homburg
participants (2)
-
İlteriş Yağıztegin Eroğlu -
Philip Homburg