Running the FTL dev version and expecting to see hour increments on the 24 hour graph.
Hour axis only shows 21:00 and 9:00 as per the screenshot.
pq56iu904a
I read that before posting and think that the proposed issue/resolution doesn't apply. I set my pi up a few weeks ago, and I tested accessing the interface from my Mac and iPhone with same results. So i know it is not the browser clock and I know it can't be the Pi clock.
The pi was configured for the EDT TZ when I set it up weeks ago and my iPhone and Mac get time via NTP.
What is the output of this command?
echo ">ClientsoverTime" | nc localhost 4711 | tail
It should return some timestamps and numbers. Check that the timestamps are not in the future.
I let it run for a while but get no output.
pi@strat0varius:~ $ date
Sat Jul 14 21:13:12 EDT 2018
pi@strat0varius:~ $ echo ">ClientsoverTime" | nc localhost 4711 | tail
^C
pi@strat0varius:~ $ date
Sat Jul 14 21:14:22 EDT 2018
pi@strat0varius:~ $
Did a netstat to see if I have anything listening on 4711 but don't see anything.
pi@strat0varius:~ $ sudo netstat -nlup
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 0 0 0.0.0.0:53 0.0.0.0:* 3942/pihole-FTL
udp 0 0 0.0.0.0:67 0.0.0.0:* 3942/pihole-FTL
udp 0 0 0.0.0.0:44099 0.0.0.0:* 354/avahi-daemon: r
udp 0 0 0.0.0.0:68 0.0.0.0:* 602/dhcpcd
udp 0 0 0.0.0.0:5353 0.0.0.0:* 354/avahi-daemon: r
udp6 0 0 :::47461 :::* 354/avahi-daemon: r
udp6 0 0 :::53 :::* 3942/pihole-FTL
udp6 0 0 :::5353 :::* 354/avahi-daemon: r
pi@strat0varius:~ $
pi@strat0varius:~ $ sudo netstat -nltp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 3942/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 643/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 3942/pihole-FTL
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 621/sshd
tcp6 0 0 ::1:4711 :::* LISTEN 3942/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 643/lighttpd
tcp6 0 0 :::53 :::* LISTEN 3942/pihole-FTL
tcp6 0 0 :::22 :::* LISTEN 621/sshd
Your second command shows that it is listening on 127.0.0.1 and ::1 (IPv6 localhost). Try using 127.0.0.1 instead of localhost.
I missed that line. Tried 127.0.0.1, no change. Also checked to see if localhost resolves and it does.
pi@strat0varius:~ $ echo ">ClientsoverTime" | nc 127.0.0.1 4711 | tail
^C
pi@strat0varius:~ $ ping localhost
PING localhost(localhost (::1)) 56 data bytes
64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.127 ms
64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.081 ms
64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.071 ms
^C
--- localhost ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2054ms
rtt min/avg/max/mdev = 0.071/0.093/0.127/0.024 ms
pi@strat0varius:~ $
Anything interesting in FTL's log?
tail /var/log/pihole-FTL.log
Nope, not as far as I can tell.
The following command fixed it: sudo service pihole-FTL restart
Based on this behavior and the other user's experienced behavior...I wonder if it is a bug with the dev FTL version.
If you're able to reproduce the issue, share the full FTL log.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.