search

linuxserver / docker-smokeping

GNU General Public License v3.0
347 stars 95 forks source link

ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*) #113

Closed PPCM closed 3 years ago

PPCM commented 3 years ago

Smokeping doesn't start

Expected Behavior

A functional Smokeping

Current Behavior

In Docker's log file:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Your DockerHost is most likely running an outdated version of libseccomp

To fix this, please visit https://docs.linuxserver.io/faq#libseccomp

Some apps might not behave correctly without this

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*)
 at (eval 71) line 1.

ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*)
 at (eval 71) line 1.

When the dig command is runned directly in the container

root@50708294fadc:/# /usr/bin/dig localhost
time.c:126: Operation not permitted
timer.c:634: fatal error: RUNTIME_CHECK(isc_time_now((&now)) == 0) failed
Aborted (core dumped)

The date of the container is still 

root@50708294fadc:/# date
Thu Jan  1 01:00:00 CET 1970

And when I try to display a page with ping results, in apache2 logs, the following errors are throwned

[Wed Jun 17 05:46:09.994467 2037] [fcgid:warn] [pid 293] [client 192.168.2.5:53120] mod_fcgid: stderr: [Wed Sep 26 23:35:28 46542] smokeping_cgi [client 192.168.2.5]: the first entry to fetch should be after 1980 (-1), referer: http://172.20.255.10/smokeping/?target=XXXXX
[Wed Jun 17 05:46:09.994467 2037] [fcgid:warn] [pid 293] [client 192.168.2.5:53120] mod_fcgid: stderr: [Wed Sep 26 23:35:28 46542] smokeping_cgi [client 192.168.2.5]: the first entry to fetch should be after 1980 (-1), referer: http://172.20.255.10/smokeping/?target=XXXXX
[Wed Jun 17 05:46:09.994467 2037] [fcgid:warn] [pid 293] [client 192.168.2.5:53120] mod_fcgid: stderr: [Wed Sep 26 23:35:28 46542] smokeping_cgi [client 192.168.2.5]: the first entry to fetch should be after 1980 (-1), referer: http://172.20.255.10/smokeping/?target=XXXXX
[Wed Jun 17 05:46:09.994467 2037] [fcgid:warn] [pid 293] [client 192.168.2.5:53120] mod_fcgid: stderr: [Wed Sep 26 23:35:28 46542] smokeping_cgi [client 192.168.2.5]: the first entry to fetch should be after 1980 (-1), referer: http://172.20.255.10/smokeping/?target=XXXXX
[Wed Jun 17 05:46:09.994467 2037] [fcgid:warn] [pid 293] [client 192.168.2.5:53120] mod_fcgid: stderr: [Wed Sep 26 23:35:28 46542] smokeping_cgi [c, referer: http://172.20.255.10/smokeping/?target=XXXXX
[Wed Jun 17 05:49:13.994467 2037] [core:error] [pid 293] [client 192.168.2.5:53120] malformed header from script 'smokeping.cgi': Bad header: <p>the first entry to fetch sh, referer: http://172.20.255.10/smokeping/?target=XXXXX

Previously, the Target file worked fine of standard Smokeping installation (without Docker)

Steps to Reproduce

  1. Fresh install of the OS 2.Fresh install of Docker
  2. Fresh install of the Smokeping Container

Environment

OS: Raspbian GNU/Linux 10 CPU architecture: arm32 (RPi 3B) How docker service was installed: from the official docker repo

Command used to create docker container (run/create/compose/screenshot)

docker run -d \ --name=smokeping \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Europe/Paris \ -p 80:80 \ -v /smokeping/config:/config \ -v /smokeping/data:/data \ --restart unless-stopped \ ghcr.io/linuxserver/smokeping

github-actions[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

thespad commented 3 years ago

Please read your container log output again, it tells you how to resolve this issue.

PPCM commented 3 years ago

Your answer is to quick

You are talking about

Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message

This doesn't block Apache execution

The problem is more with

ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*)
 at (eval 71) line 1.

and

root@50708294fadc:/# /usr/bin/dig localhost
time.c:126: Operation not permitted
timer.c:634: fatal error: RUNTIME_CHECK(isc_time_now((&now)) == 0) failed
Aborted (core dumped)

Otherwise, how do you set the name of your container?

thespad commented 3 years ago

Yes, and if you read the container logs you posted it will tell you how to fix it.

PPCM commented 3 years ago

OK, I had an entry for Servername in httpd.conf. It corrects the error line for 

AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive globally to suppress this message
ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*)
 at (eval 71) line 1.

ERROR: output of '/usr/bin/dig localhost' does not match (?^i:query time:\s+([0-9.]+)\smsec.*)
 at (eval 71) line 1.

No more errors in docker logs

But nothing is generated. I will open an other ticket because the ping fails (clock_gettime errors)

j0nnymoe commented 3 years ago

@PPCM could you post an updated copy of your docker log smokeping please? It sounds like the error is still there.

PPCM commented 3 years ago

Docker logs output

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Your DockerHost is most likely running an outdated version of libseccomp

To fix this, please visit https://docs.linuxserver.io/faq#libseccomp

Some apps might not behave correctly without this

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

It displays no error

But the problem is else where I can ping a server from the host, but not from the container

From the host

pi@smokeping:~ $ ping 172.20.0.1
PING 172.20.0.1 (172.20.0.1) 56(84) bytes of data.
64 bytes from 172.20.0.1: icmp_seq=1 ttl=64 time=1.55 ms
64 bytes from 172.20.0.1: icmp_seq=2 ttl=64 time=1.45 ms
^C
--- 172.20.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 1.447/1.500/1.554/0.066 ms

From the container

root@5746c88d9910:/# ping 172.20.0.1
PING 172.20.0.1 (172.20.0.1): 56 data bytes
ping: clock_gettime(MONOTONIC) failed

Another strange things

root@5746c88d9910:/# date
Thu Jan  1 01:00:00 CET 1970
root@5746c88d9910:/# uptime
Segmentation fault (core dumped)

Thanks for your help

j0nnymoe commented 3 years ago

Your docker logs are still showing a clear error and it mentions a link to fix.

Roxedus commented 3 years ago 
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Your DockerHost is most likely running an outdated version of libseccomp

To fix this, please visit https://docs.linuxserver.io/faq#libseccomp

Some apps might not behave correctly without this

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

This is the one you need to look at.

PPCM commented 3 years ago

It is written to large Thanks, I take a look how to fix it

PPCM commented 3 years ago

Thanks a lot After installing libseccomp2_2.5.1-1_armhf, all problems are gone