[Support] Linuxserver.io - SmokePing

[SauRoN]

Thanks @CHBMB and @sparklyballs for resolving this.

 

Amazing how simple it seems in hindsight.

 

I guess it's one of the pitfalls of open source vs closed source.

 

 

Now I finally have some ammunition to take on my ISP regarding packet loss.

Edited August 1, 2017 by SauRoN

[lovingHDTV]

Fixed cgi-bin to be smokeping, so it could find the location.

 

 

 

I dusted this off today and can't get connected to the webserver any longer.  When I attach to the docker it appears that everything is running. the log file appears clean.  

 

I just can get to: 

http://192.168.1.107:8080/cgi-bin/smokeping.cgi

 

I get a message

The requested URL /cgi-bin/smokeping.cgi was not found on this server.

 

If I just go http://192.168.1.107:8080 I get a message "it works"

 

Makes me think I've got something wrong in a config file somewhere.

 

Ideas?

 

thanks

david

Edited January 14, 2018 by lovingHDTV
updated

[spyd4r]

is it possible to get dig added to this container? or is there a way of pushing it in without cloning the github?

[wgstarks]

This is a really minor issue, but I notice that the support thread link for this docker in CA points to an old thread which has been closed. Same for the support thread link when clicking the docker icon.

[jaj08]

Am I overlooking a setting somewhere, or is there no setting to adjust how frequently the pings are done? Would love to increase the frequency to check smaller bits of packet loss and latency.

[mattw]

That is done in your Probes file.  The step and count control the frequency and quantity.  Be aware when you change the step or count you will have to delete the .rrd files associated with the probes you change as the database is governed by the time/count.

[mattw]

I am having a problem with my .rrd data going away, sometimes after a reboot.  I suspect that some part of the container is not pointed to the right place as I do not see a data directory in the smokeping folder on my cache drive.

 

 

My server is up 24/7 and all of my graphs should go back months.

[bamy]

Is it possible to assign a hostname to this Docker container via Unraid? Saw this question asked on the Github but solution was to set it via the Compose file. https://github.com/linuxserver/docker-smokeping/issues/96

 

EDIT: Solved - had to enable 'Advanced View', then add the following in Extra Parameters: 

--hostname="DESIRED_HOSTNAME"

 

Edited November 15, 2023 by bamy

[SauRoN]

Is it possible to assign a hostname to this Docker container via Unraid? Saw this question asked on the Github but solution was to set it via the Compose file. https://github.com/linuxserver/docker-smokeping/issues/96
 
EDIT: Solved - had to enable 'Advanced View', then add the following in Extra Parameters: 

--hostname="DESIRED_HOSTNAME"

 

Out of interest why did you want this?


Sent from my iPhone using Tapatalk Pro

[bamy]

On 11/16/2023 at 11:29 PM, SauRoN said:

Out of interest why did you want this?

 

The graphs use the hostname in the title. For example "Last 3 hours from HOSTNAME to Domain". Looks better to have a named hostname than Docker's random one.

[ChrisW1337]

On 7/2/2023 at 7:08 AM, mattw said:

 

 

How did you manage to get multiple ping into one graph.
I cant find neither Info nor example to get e.g. 192.168.1.1 and 192.168.1.2 into ONE graph.
FPing says it cant resolve the Hostname "192.168.1.1 192.168.1.2".... ?

 

another example:
https://smokeping.oetiker.ch/?target=multi

 

 

Edited January 28 by ChrisW1337

[mattw]

On 1/28/2024 at 8:05 AM, ChrisW1337 said:

 

How did you manage to get multiple ping into one graph.
I cant find neither Info nor example to get e.g. 192.168.1.1 and 192.168.1.2 into ONE graph.
FPing says it cant resolve the Hostname "192.168.1.1 192.168.1.2".... ?

 

another example:
https://smokeping.oetiker.ch/?target=multi

 

 

So, the magic is in the Targets file... You build the following it paths to the queries you want to include in the multigraph like so...

++ MultiHostAPPings
menu = MultiHost AP ICMP
title = Consolidated AP Ping Responses
host = /Local/AP/AP1 /Local/AP/AP2 /Local/AP/AP4 /Local/AP/AP5

[ChrisW1337]

On 2/5/2024 at 3:55 AM, mattw said:

So, the magic is in the Targets file... You build the following it paths to the queries you want to include in the multigraph like so...

++ MultiHostAPPings
menu = MultiHost AP ICMP
title = Consolidated AP Ping Responses
host = /Local/AP/AP1 /Local/AP/AP2 /Local/AP/AP4 /Local/AP/AP5

 

yes, thank you. but what is "/Local/AP/AP1"?
when my pings are for example:

 

+ Local

menu = Local
Title = Local

++ Switch1
menu = Switch1
title = Switch1
host = 192.168.2.3
++ Switch2
menu = Switch2
title = Switch2
host = 192.168.2.4
++ Switch3
menu = Switch3
title = Switch3
host = 192.168.2.5

i dont seem to have any path like this one "/Local/AP/AP1"

[ChrisW1337]

3 hours ago, ChrisW1337 said:

 

yes, thank you. but what is "/Local/AP/AP1"?
when my pings are for example:

 

+ Local

menu = Local
Title = Local

++ Switch1
menu = Switch1
title = Switch1
host = 192.168.2.3
++ Switch2
menu = Switch2
title = Switch2
host = 192.168.2.4
++ Switch3
menu = Switch3
title = Switch3
host = 192.168.2.5

i dont seem to have any path like this one "/Local/AP/AP1"

 

DUH - forget it - I see it now - thanks

 

host = Local/Switch1 Local/Switch2 ....

[mattyx]

Hi,

I've had smokeping running for several months, but something seems to have broken recently, and no pings are hitting the graphs (historical data is still visible).

 

The logs show:
 

ERROR: we did not get config from the master. Maybe we are not configured as a slave for any of the targets on the master ?
WARNING: No secret found for slave 8090ceb9b10d

 

I dont recall ever messing with a master/slave config, so I'm at a loss.  Anyone have any pointers for where I should investigate?

 

Many thanks!

Edited March 24 by mattyx
Changing quote to code for readability.