Discontinuance in smokeping graph
2011-06-06 12:05:31 GMT
Hi,
_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi,
_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi Guys,
_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hello fellow smokers,
I have a question about loss_colors usage. I would like the loss colors to be different for each probe. For instance, I have an curl probe that has only 5 pings and an fping probe that does 10. I want to set colors for 1 through 10 (green fade to red) for the fping probe but only 1 through 5 (again green fade to red) for the curl probe. Can I do a loss_colors section under each of those probes or is there some other way to handle this?
TIA,
Eric
_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi all,
Trying to get CiscoRTTMonEchoICMP working and have run into a strange issue.
When I have it configured, it runs fine (see log output below) but when I try to see the results, I get an error message from the web server:
ERROR: /opt/smokeping/etc/config, line 286: unknown variable 'ioshost'
When I remove the ioshost variable, I can see the web pages just fine – and I can even see the results from CiscoRTTMonEchoICMP while it was running graphed – but, of course CiscoRTTMonEchoICMP no longer runs.
Here’s the relevant config:
*** Probes ***
+ FPing
binary = /usr/sbin/fping
blazemode = true
+ CiscoRTTMonEchoICMP
forks = 5
*** Targets ***
+ local
menu = Local
title = local
++ Internet_A
probe = CiscoRTTMonEchoICMP
menu = Internet_A
title = Internet_67.64.149.129
alerts = someloss
host = 67.64.149.129
ioshost = community <at> 67.227.90.130
And here is the log output:
Jun 16 10:11:34 prinetmon01 smokeping[30733]: Starting syslog logging
Jun 16 10:11:34 prinetmon01 smokeping[30736]: Smokeping version 2.004002 successfully launched.
Jun 16 10:11:34 prinetmon01 smokeping[30736]: Entering multiprocess mode.
Jun 16 10:11:34 prinetmon01 smokeping[30736]: Child process 30738 started for probe CiscoRTTMonEchoICMP.
Jun 16 10:11:34 prinetmon01 smokeping[30738]: CiscoRTTMonEchoICMP: probing 1 targets with step 300 s and offset 95 s.
Jun 16 10:11:34 prinetmon01 smokeping[30739]: FPing: probing 6 targets with step 300 s and offset 100 s.
Jun 16 10:11:34 prinetmon01 smokeping[30736]: Child process 30739 started for probe FPing.
Jun 16 10:11:34 prinetmon01 smokeping[30736]: All probe processes started successfully.
Jun 16 10:11:35 prinetmon01 smokeping[30740]: smokeping <at> 67.227.90.130:::::2 supports 2.2.0 Round Trip Time MIB
Jun 16 10:16:35 prinetmon01 smokeping[30783]: smokeping <at> 67.227.90.130:::::2 supports 2.2.0 Round Trip Time MIB
Jun 16 10:21:35 prinetmon01 smokeping[30841]: smokeping <at> 67.227.90.130:::::2 supports 2.2.0 Round Trip Time MIB
Jun 16 10:26:35 prinetmon01 smokeping[30908]: smokeping <at> 67.227.90.130:::::2 supports 2.2.0 Round Trip Time MIB
Thanks in advance for your help,
Chris
_______________________________________________
Chris Moore
Network Engineer
Presilient, LLC
720-566-5056
_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi, I'm a SmokePing beginner. I have gotten as far as to setup three machines. One as master (master) and two slaves. I have configured my Targets file and added the slaves. I set the permission on the file /etc/smokeping/smokeping_secrets as follows: sudo chmod 0440 /etc/smokeping/smokeping_secrets then I start SmokePing sudo service smokeping restart On the slave I then execute this: /usr/sbin/smokeping --master-url=http://master/smokeping/smokeping.cgi --cache-dir=/var/smokeping/ --shared-secret=/var/smokeping/secret.txt -debug and I get this error: WARNING: Opening secrets file /etc/smokeping/smokeping_secrets: Permission denied If I change the permission on the file /etc/smokeping/smokeping_secrets on the master (while SMokePing is running) : sudo chmod 0444 /etc/smokeping/smokeping_secrets It works at the slave. But after a while SmokePing complains that the file is world readable... I understand that the file shouldn't be world readable... but since I am no good at Python and Linux permissions I really need help with this! Can anyone give me a clue as to how the permissions should be set for the master/slave to work OK? I am doing this with 2.004002 and Perl v5.10.1 on Ubuntu 11.04 Cheers, Joakim _______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi there, On Sat, 18 Jun 2011, Joakim Westin wrote: > sudo chmod 0440 /etc/smokeping/smokeping_secrets > ... > WARNING: Opening secrets file /etc/smokeping/smokeping_secrets: > Permission denied > ... > Can anyone give me a clue as to how the permissions should be set for > the master/slave to work OK? It's probably the file ownership that's the problem, not the permissions. The file should be owned by the UID that's running the process which is complaining about reading it. Try using chown user /etc/smokeping/smokeping_secrets where "user" is the userid of the smokeping process.
The file needs to be readable by the user that Smokeping is running as on the master. If the file is owned by root and you set permissions 0440 on it, then the Smokeping user can't read it. You should change the ownersip of the file so that your Smokeping user can read it; for example, if Smokeping runs as _smokeping, you could do: chown _smokeping:root /etc/smokeping/smokeping_secrets chmod 0660 /etc/smokeping/smokeping_secrets - Peter On 6/18/2011 6:33 AM, Joakim Westin wrote: > Hi, I'm a SmokePing beginner. > > I have gotten as far as to setup three machines. One as master > (master) and two slaves. I have configured my Targets file and added > the slaves. I set the permission on the file > /etc/smokeping/smokeping_secrets as follows: > > sudo chmod 0440 /etc/smokeping/smokeping_secrets > > then I start SmokePing > > sudo service smokeping restart > > On the slave I then execute this: > > /usr/sbin/smokeping --master-url=http://master/smokeping/smokeping.cgi > --cache-dir=/var/smokeping/ --shared-secret=/var/smokeping/secret.txt > -debug > > and I get this error: > > WARNING: Opening secrets file /etc/smokeping/smokeping_secrets: > Permission denied > > If I change the permission on the file > /etc/smokeping/smokeping_secrets on the master (while SMokePing is > running) : > > sudo chmod 0444 /etc/smokeping/smokeping_secrets > > It works at the slave. But after a while SmokePing complains that the > file is world readable... > > I understand that the file shouldn't be world readable... but since I > am no good at Python and Linux permissions I really need help with > this! > > Can anyone give me a clue as to how the permissions should be set for > the master/slave to work OK? > > I am doing this with 2.004002 and Perl v5.10.1 on Ubuntu 11.04 > > Cheers, > Joakim > > _______________________________________________ > smokeping-users mailing list > smokeping-users <at> lists.oetiker.ch > https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
_______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi, Many thanks both og you for pointing me in the right direction! I did give the smokeping user ownership of the file but still got the permission problem. After a while I realised that the issue was that the SpeedyCGI module was running as www-data. Once I gave www-data access to the file it all worked fineThanks for helping me learn! Cheers, Joakim 2011/6/18 G.W. Haywood <ged <at> jubileegroup.co.uk>: > Hi there, > > On Sat, 18 Jun 2011, Joakim Westin wrote: > >> sudo chmod 0440 /etc/smokeping/smokeping_secrets >> ... >> WARNING: Opening secrets file /etc/smokeping/smokeping_secrets: >> Permission denied >> ... >> Can anyone give me a clue as to how the permissions should be set for >> the master/slave to work OK? > > It's probably the file ownership that's the problem, not the permissions. > The file should be owned by the UID that's running the process which is > complaining about reading it. Try using > > chown user /etc/smokeping/smokeping_secrets > > where "user" is the userid of the smokeping process. > > -- > > 73, > Ged. > _______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi. Smokeping is fantastic, but configuration has given me an issue... I started with a tiny config file with only one alert, 'someloss'. Next, I built out my config file for my network, with probes, targets and a range of alerts. The original alert 'someloss' was removed. Yet, when I watch the smokeping logs, the ONLY alert I see active is 'someloss': Jun 21 15:57:47 sstromer smokeping[92450]: Alert someloss is active for LAN_to_DOMAIN_HOST_Pings.Mail_Server_url Jun 21 15:57:48 sstromer smokeping[92450]: Alert someloss is active for LAN_to_LAN.to_Router_ip I've performed a string search through the file contents of all relevant directories for the term 'someloss', and can't find a single instance in any file containing this term. I've, of course, both reloaded and restarted smokeping to no avail. Is there something more aggressive I have to do, such as removing all of the .rdd files from existing targets? Also, for future reference, what does it mean when an alert is logged as 'active'? Is the log activity triggered by the beginning of an alert pattern being met, by the full pattern being met, by the alert meeting all of the conditions necessary to trigger an email/application launch, or something other? Thanks for the attention, Steven Stromer _______________________________________________ smokeping-users mailing list smokeping-users <at> lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
Hi List,
I've Googled all around for the better part of the day, and found multiple instances of this error, all
unresolved. If anyone can help, it would be much appreciated! smokeping is continuously restarting with
the following two messages in an endless loop:
org.macports.smokeping[30235] Error: RRD parameter mismatch ('Different number of data sources:
/opt/local/var/smokeping/LAN_to_DOMAIN_HOST_Pings/Mail_Server_url.rrd has 23, create string
has 8'). You must delete /opt/local/var/smokeping/LAN_to_DOMAIN_HOST_Pings/Mail_Server_url.rrd
or fix the configuration parameters.
com.apple.launchd[1] (org.macports.smokeping) Throttling respawn: Will start in 9 seconds
Deleting the file 'Mail_Server_url.rrd' does not resolve the issue. Where can I correct the
configuration parameters, or otherwise repair this issue?
Your assist is much appreciated!
Steven Stromer
_______________________________________________
smokeping-users mailing list
smokeping-users <at> lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
RSS Feed21 | |
|---|---|
54 | |
10 | |
18 | |
27 | |
38 | |
24 | |
24 | |
42 | |
32 | |
121 | |
30 | |
33 | |
25 | |
28 | |
39 | |
28 | |
42 | |
42 | |
62 | |
29 | |
14 | |
39 | |
14 | |
21 | |
15 | |
16 | |
6 | |
21 | |
14 | |
29 | |
35 | |
26 | |
16 | |
16 | |
15 | |
27 | |
12 | |
52 | |
27 | |
59 | |
26 | |
55 | |
3 | |
21 | |
20 | |
20 | |
43 | |
32 | |
46 | |
55 | |
47 | |
54 | |
30 | |
38 | |
20 | |
42 | |
64 | |
79 | |
159 | |
62 | |
106 | |
104 | |
64 | |
44 | |
47 | |
52 | |
84 | |
78 | |
30 | |
12 | |
26 | |
16 | |
34 | |
26 | |
21 | |
46 | |
53 | |
23 | |
40 | |
30 | |
65 | |
61 | |
26 | |
30 | |
21 | |
36 | |
22 | |
22 | |
48 | |
19 | |
31 | |
34 | |
61 | |
60 | |
44 | |
57 | |
29 | |
32 | |
33 | |
40 | |
27 | |
36 | |
32 | |
32 | |
27 | |
34 | |
59 | |
48 | |
23 | |
23 | |
56 | |
49 | |
47 | |
32 | |
33 | |
43 | |
56 | |
24 | |
28 | |
39 | |
42 | |
36 | |
45 | |
14 | |
30 | |
13 | |
34 | |
51 | |
14 | |
30 | |
24 | |
23 | |
31 | |
30 | |
41 | |
72 | |
15 | |
3 | |
1 |