@megaron leider nicht ich nutze zum Auslesen den TR-064 Adapter, sowie den fritzbox Adapter und Fritzbox CheckPresence das fritzcollect nutze ich nur wegen dem Grafana Dashboard!
@Master67 .. Hab fritzcollect installiert. Leider bekomme ich folgende Fehlermeldung. Hast du eine Idee woran es liegen könnte?
root@Grafana:~# systemctl restart collectd
Job for collectd.service failed because the control process exited with error code.
See "systemctl status collectd.service" and "journalctl -xe" for details.
root@Grafana:~# systemctl status collectd.service
* collectd.service - Statistics collection and monitoring daemon
Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sat 2021-01-02 11:03:34 UTC; 6s ago
Docs: man:collectd(1)
man:collectd.conf(5)
https://collectd.org
Process: 1169 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=0/SUCCESS)
Process: 1170 ExecStart=/usr/sbin/collectd (code=exited, status=1/FAILURE)
Main PID: 1170 (code=exited, status=1/FAILURE)
Jan 02 11:03:34 Grafana systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
Jan 02 11:03:34 Grafana systemd[1]: collectd.service: Failed with result 'exit-code'.
Jan 02 11:03:34 Grafana systemd[1]: Failed to start Statistics collection and monitoring daemon.
root@Grafana:~# journalctl -xe
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit collectd.service has begun execution.
--
-- The job identifier is 18647.
Jan 02 11:04:35 Grafana collectd[1184]: Parse error in file `/etc/collectd/collectd.conf', line 1662 near `': syntax error, unexpected $end, expecting UNQUOTED_STRING or O
Jan 02 11:04:35 Grafana collectd[1184]: yyparse returned error #1
Jan 02 11:04:35 Grafana collectd[1184]: configfile: Cannot read file `/etc/collectd/collectd.conf'.
Jan 02 11:04:35 Grafana collectd[1184]: Unable to read config file /etc/collectd/collectd.conf.
Jan 02 11:04:35 Grafana collectd[1184]: Error: Reading the config file failed!
Jan 02 11:04:35 Grafana collectd[1184]: Read the logs for details.
Jan 02 11:04:35 Grafana systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit collectd.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jan 02 11:04:35 Grafana systemd[1]: collectd.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit collectd.service has entered the 'failed' state with result 'exit-code'.
Jan 02 11:04:35 Grafana systemd[1]: Failed to start Statistics collection and monitoring daemon.
-- Subject: A start job for unit collectd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit collectd.service has finished with a failure.
--
-- The job identifier is 18647 and the job result is failed.
@megaron sagte in [web-speedy] Teste deine Internetverbindung 
:
schau da mal rein, da scheint das ` nicht zu stimmen, ich kenne mich aber leider mit der Syntax zu wenig aus.
Parse error in file `/etc/collectd/collectd.conf', line 1662 near `': syntax error, unexpected $end, expecting UNQUOTED_STRING or O
Edit: ich schau mir mal die Zeile bei mir an.... Warte
@megaron .... Ach ja... ich doof Kopf
Ich hatte ja den gleichen Fehler (Sorry bei dem ganzen Zeug das ich nutze vergesse ich sowas schon mal) .....
Ersetze den Code in der "collectd.conf" mit folgenden Code, deine IP und PW eintragen.
LoadPlugin syslog
<Plugin syslog>
LogLevel info
</Plugin>
LoadPlugin battery
LoadPlugin cpu
LoadPlugin df
LoadPlugin disk
LoadPlugin entropy
LoadPlugin interface
LoadPlugin irq
LoadPlugin load
LoadPlugin memory
LoadPlugin network
LoadPlugin netlink
LoadPlugin processes
LoadPlugin python
LoadPlugin rrdtool
LoadPlugin swap
LoadPlugin users
<Plugin df>
# ignore rootfs; else, the root file-system would appear twice, causing
# one of the updates to fail and spam the log
FSType rootfs
# ignore the usual virtual / temporary file-systems
FSType sysfs
FSType proc
FSType devtmpfs
FSType devpts
FSType tmpfs
FSType fusectl
FSType cgroup
IgnoreSelected true
</Plugin>
<Plugin network>
Server "127.0.0.1" "25826"
</Plugin>
<Plugin python>
Import "fritzcollectd"
<Module fritzcollectd>
Address "192.168.178.XX"
Port 49000
User "megaron"
Password "Dein PW"
Hostname "FritzBox"
Instance "1"
Verbose "False"
</Module>
</Plugin>
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
</Plugin>
<Include "/etc/collectd/collectd.conf.d">
Filter "*.conf"
</Include>
<Module fritzcollectd>
Address "192.168.178.XX"
Port 49000
User "megaron"
Password "Dein PW"
Hostname "FritzBox"
Instance "1"
Verbose "False"
</Module>
</Plugin>
<Plugin rrdtool>
DataDir "/var/lib/collectd/rrd"
</Plugin>
<Include "/etc/collectd/collectd.conf.d">
Filter "*.conf"
</Include>
Angaben ohne Gewähr
@Master67 .. habs ersetzt. Leider keine Verbesserung. Meldungen analog wie vorher.
Nur der Sicherheit halber: Die Angaben zur User und Password sind die Fritz!box-Benutzerdaten (neuer Benutzer). Richtig?
Edit: Hab noch etwas rumprobiert und siehe da die Konfiguration (systemctl restart collectd) wird ohne Fehlermeldung durchgeführt.
Vielen lieben Dank für deine Unterstützung.
Jetzt werde ich erstmal ein paar Daten in Influx ankommen lassen. und mich dann an das dashboard machen. Kannst du mir evtl deine json als Anregung zur Verfügung stellen?
`
@megaron ..... Klar.... Mache ich heute etwas später 
@Master67 ... jetzt müsste ich dich leider nochmal belästigen.
In der InfluxDB kommen keine Daten an.
Grafana und auch die eingebunden InfluxDB "fritzbox" zeigen keine Auffälligkeiten.
Wenn ich ein neues Panel anlege, dann über die Query Daten unter measurement einbinden möchte, werden keine Auswahlmöglichkeiten angeboten.
Hab den LXC Container rebootet. Ohne Erfolg.
Hast du eine Idee woran das liegen könnte. Anbei meine Influxdb.config. Sollte eigentlich alles so sein wie in der Vorgabe beschrieben.
### Welcome to the InfluxDB configuration file.
# The values in this file override the default values used by the system if
# a config option is not specified. The commented out lines are the configuration
# field and the default value used. Uncommenting a line and changing the value
# will change the value used at runtime when the process is restarted.
# Once every 24 hours InfluxDB will report usage data to usage.influxdata.com
# The data includes a random ID, os, arch, version, the number of series and other
# usage data. No data from user databases is ever transmitted.
# Change this option to true to disable reporting.
# reporting-disabled = false
# Bind address to use for the RPC service for backup and restore.
# bind-address = "127.0.0.1:8088"
###
### [meta]
###
### Controls the parameters for the Raft consensus group that stores metadata
### about the InfluxDB cluster.
###
[meta]
# Where the metadata/raft database is stored
dir = "/var/lib/influxdb/meta"
# Automatically create a default retention policy when creating a database.
# retention-autocreate = true
# If log messages are printed for the meta service
# logging-enabled = true
###
### [data]
###
### Controls where the actual shard data for InfluxDB lives and how it is
### flushed from the WAL. "dir" may need to be changed to a suitable place
### for your system, but the WAL settings are an advanced configuration. The
### defaults should work for most systems.
###
[data]
# The directory where the TSM storage engine stores TSM files.
dir = "/var/lib/influxdb/data"
# The directory where the TSM storage engine stores WAL files.
wal-dir = "/var/lib/influxdb/wal"
# The amount of time that a write will wait before fsyncing. A duration
# greater than 0 can be used to batch up multiple fsync calls. This is useful for slower
# disks or when WAL write contention is seen. A value of 0s fsyncs every write to the WAL.
# Values in the range of 0-100ms are recommended for non-SSD disks.
# wal-fsync-delay = "0s"
# The type of shard index to use for new shards. The default is an in-memory index that is
# recreated at startup. A value of "tsi1" will use a disk based index that supports higher
# cardinality datasets.
# index-version = "inmem"
# Trace logging provides more verbose output around the tsm engine. Turning
# this on can provide more useful output for debugging tsm engine issues.
# trace-logging-enabled = false
# Whether queries should be logged before execution. Very useful for troubleshooting, but will
# log any sensitive data contained within a query.
# query-log-enabled = true
# Validates incoming writes to ensure keys only have valid unicode characters.
# This setting will incur a small overhead because every key must be checked.
# validate-keys = false
# Settings for the TSM engine
# CacheMaxMemorySize is the maximum size a shard's cache can
# reach before it starts rejecting writes.
# Valid size suffixes are k, m, or g (case insensitive, 1024 = 1k).
# Values without a size suffix are in bytes.
# cache-max-memory-size = "1g"
# CacheSnapshotMemorySize is the size at which the engine will
# snapshot the cache and write it to a TSM file, freeing up memory
# Valid size suffixes are k, m, or g (case insensitive, 1024 = 1k).
# Values without a size suffix are in bytes.
# cache-snapshot-memory-size = "25m"
# CacheSnapshotWriteColdDuration is the length of time at
# which the engine will snapshot the cache and write it to
# a new TSM file if the shard hasn't received writes or deletes
# cache-snapshot-write-cold-duration = "10m"
# CompactFullWriteColdDuration is the duration at which the engine
# will compact all TSM files in a shard if it hasn't received a
# write or delete
# compact-full-write-cold-duration = "4h"
# The maximum number of concurrent full and level compactions that can run at one time. A
# value of 0 results in 50% of runtime.GOMAXPROCS(0) used at runtime. Any number greater
# than 0 limits compactions to that value. This setting does not apply
# to cache snapshotting.
# max-concurrent-compactions = 0
# CompactThroughput is the rate limit in bytes per second that we
# will allow TSM compactions to write to disk. Note that short bursts are allowed
# to happen at a possibly larger value, set by CompactThroughputBurst
# compact-throughput = "48m"
# CompactThroughputBurst is the rate limit in bytes per second that we
# will allow TSM compactions to write to disk.
# compact-throughput-burst = "48m"
# If true, then the mmap advise value MADV_WILLNEED will be provided to the kernel with respect to
# TSM files. This setting has been found to be problematic on some kernels, and defaults to off.
# It might help users who have slow disks in some cases.
# tsm-use-madv-willneed = false
# Settings for the inmem index
# The maximum series allowed per database before writes are dropped. This limit can prevent
# high cardinality issues at the database level. This limit can be disabled by setting it to
# 0.
# max-series-per-database = 1000000
# The maximum number of tag values per tag that are allowed before writes are dropped. This limit
# can prevent high cardinality tag values from being written to a measurement. This limit can be
# disabled by setting it to 0.
# max-values-per-tag = 100000
# Settings for the tsi1 index
# The threshold, in bytes, when an index write-ahead log file will compact
# into an index file. Lower sizes will cause log files to be compacted more
# quickly and result in lower heap usage at the expense of write throughput.
# Higher sizes will be compacted less frequently, store more series in-memory,
# and provide higher write throughput.
# Valid size suffixes are k, m, or g (case insensitive, 1024 = 1k).
# Values without a size suffix are in bytes.
# max-index-log-file-size = "1m"
# The size of the internal cache used in the TSI index to store previously
# calculated series results. Cached results will be returned quickly from the cache rather
# than needing to be recalculated when a subsequent query with a matching tag key/value
# predicate is executed. Setting this value to 0 will disable the cache, which may
# lead to query performance issues.
# This value should only be increased if it is known that the set of regularly used
# tag key/value predicates across all measurements for a database is larger than 100. An
# increase in cache size may lead to an increase in heap usage.
series-id-set-cache-size = 100
###
### [coordinator]
###
### Controls the clustering service configuration.
###
[coordinator]
# The default time a write request will wait until a "timeout" error is returned to the caller.
# write-timeout = "10s"
# The maximum number of concurrent queries allowed to be executing at one time. If a query is
# executed and exceeds this limit, an error is returned to the caller. This limit can be disabled
# by setting it to 0.
# max-concurrent-queries = 0
# The maximum time a query will is allowed to execute before being killed by the system. This limit
# can help prevent run away queries. Setting the value to 0 disables the limit.
# query-timeout = "0s"
# The time threshold when a query will be logged as a slow query. This limit can be set to help
# discover slow or resource intensive queries. Setting the value to 0 disables the slow query logging.
# log-queries-after = "0s"
# The maximum number of points a SELECT can process. A value of 0 will make
# the maximum point count unlimited. This will only be checked every second so queries will not
# be aborted immediately when hitting the limit.
# max-select-point = 0
# The maximum number of series a SELECT can run. A value of 0 will make the maximum series
# count unlimited.
# max-select-series = 0
# The maximum number of group by time bucket a SELECT can create. A value of zero will max the maximum
# number of buckets unlimited.
# max-select-buckets = 0
###
### [retention]
###
### Controls the enforcement of retention policies for evicting old data.
###
[retention]
# Determines whether retention policy enforcement enabled.
# enabled = true
# The interval of time when retention policy enforcement checks run.
# check-interval = "30m"
###
### [shard-precreation]
###
### Controls the precreation of shards, so they are available before data arrives.
### Only shards that, after creation, will have both a start- and end-time in the
### future, will ever be created. Shards are never precreated that would be wholly
### or partially in the past.
[shard-precreation]
# Determines whether shard pre-creation service is enabled.
# enabled = true
# The interval of time when the check to pre-create new shards runs.
# check-interval = "10m"
# The default period ahead of the endtime of a shard group that its successor
# group is created.
# advance-period = "30m"
###
### Controls the system self-monitoring, statistics and diagnostics.
###
### The internal database for monitoring data is created automatically if
### if it does not already exist. The target retention within this database
### is called 'monitor' and is also created with a retention period of 7 days
### and a replication factor of 1, if it does not exist. In all cases the
### this retention policy is configured as the default for the database.
[monitor]
# Whether to record statistics internally.
# store-enabled = true
# The destination database for recorded statistics
# store-database = "_internal"
# The interval at which to record statistics
# store-interval = "10s"
###
### [http]
###
### Controls how the HTTP endpoints are configured. These are the primary
### mechanism for getting data into and out of InfluxDB.
###
[http]
# Determines whether HTTP endpoint is enabled.
enabled = true
# Determines whether the Flux query endpoint is enabled.
# flux-enabled = false
# Determines whether the Flux query logging is enabled.
# flux-log-enabled = false
# The bind address used by the HTTP service.
bind-address = ":8086"
# Determines whether user authentication is enabled over HTTP/HTTPS.
auth-enabled = true
# The default realm sent back when issuing a basic auth challenge.
# realm = "InfluxDB"
# Determines whether HTTP request logging is enabled.
log-enabled = true
# Determines whether the HTTP write request logs should be suppressed when the log is enabled.
# suppress-write-log = false
# When HTTP request logging is enabled, this option specifies the path where
# log entries should be written. If unspecified, the default is to write to stderr, which
# intermingles HTTP logs with internal InfluxDB logging.
#
# If influxd is unable to access the specified path, it will log an error and fall back to writing
# the request log to stderr.
# access-log-path = ""
# Filters which requests should be logged. Each filter is of the pattern NNN, NNX, or NXX where N is
# a number and X is a wildcard for any number. To filter all 5xx responses, use the string 5xx.
# If multiple filters are used, then only one has to match. The default is to have no filters which
# will cause every request to be printed.
# access-log-status-filters = []
# Determines whether detailed write logging is enabled.
write-tracing = false
# Determines whether the pprof endpoint is enabled. This endpoint is used for
# troubleshooting and monitoring.
pprof-enabled = false
# Enables authentication on pprof endpoints. Users will need admin permissions
# to access the pprof endpoints when this setting is enabled. This setting has
# no effect if either auth-enabled or pprof-enabled are set to false.
# pprof-auth-enabled = false
# Enables a pprof endpoint that binds to localhost:6060 immediately on startup.
# This is only needed to debug startup issues.
# debug-pprof-enabled = false
# Enables authentication on the /ping, /metrics, and deprecated /status
# endpoints. This setting has no effect if auth-enabled is set to false.
# ping-auth-enabled = false
# Determines whether HTTPS is enabled.
https-enabled = false
# The SSL certificate to use when HTTPS is enabled.
https-certificate = "/etc/ssl/influxdb.pem"
# Use a separate private key location.
# https-private-key = ""
# The JWT auth shared secret to validate requests using JSON web tokens.
# shared-secret = ""
# The default chunk size for result sets that should be chunked.
# max-row-limit = 0
# The maximum number of HTTP connections that may be open at once. New connections that
# would exceed this limit are dropped. Setting this value to 0 disables the limit.
# max-connection-limit = 0
# Enable http service over unix domain socket
# unix-socket-enabled = false
# The path of the unix domain socket.
# bind-socket = "/var/run/influxdb.sock"
# The maximum size of a client request body, in bytes. Setting this value to 0 disables the limit.
# max-body-size = 25000000
# The maximum number of writes processed concurrently.
# Setting this to 0 disables the limit.
# max-concurrent-write-limit = 0
# The maximum number of writes queued for processing.
# Setting this to 0 disables the limit.
# max-enqueued-write-limit = 0
# The maximum duration for a write to wait in the queue to be processed.
# Setting this to 0 or setting max-concurrent-write-limit to 0 disables the limit.
# enqueued-write-timeout = 0
# User supplied HTTP response headers
#
# [http.headers]
# X-Header-1 = "Header Value 1"
# X-Header-2 = "Header Value 2"
###
### [logging]
###
### Controls how the logger emits logs to the output.
###
[logging]
# Determines which log encoder to use for logs. Available options
# are auto, logfmt, and json. auto will use a more a more user-friendly
# output format if the output terminal is a TTY, but the format is not as
# easily machine-readable. When the output is a non-TTY, auto will use
# logfmt.
# format = "auto"
# Determines which level of logs will be emitted. The available levels
# are error, warn, info, and debug. Logs that are equal to or above the
# specified level will be emitted.
# level = "info"
# Suppresses the logo output that is printed when the program is started.
# The logo is always suppressed if STDOUT is not a TTY.
# suppress-logo = false
###
### [subscriber]
###
### Controls the subscriptions, which can be used to fork a copy of all data
### received by the InfluxDB host.
###
[subscriber]
# Determines whether the subscriber service is enabled.
# enabled = true
# The default timeout for HTTP writes to subscribers.
# http-timeout = "30s"
# Allows insecure HTTPS connections to subscribers. This is useful when testing with self-
# signed certificates.
# insecure-skip-verify = false
# The path to the PEM encoded CA certs file. If the empty string, the default system certs will be used
# ca-certs = ""
# The number of writer goroutines processing the write channel.
# write-concurrency = 40
# The number of in-flight writes buffered in the write channel.
# write-buffer-size = 1000
###
### [[graphite]]
###
### Controls one or many listeners for Graphite data.
###
[[graphite]]
# Determines whether the graphite endpoint is enabled.
# enabled = false
# database = "graphite"
# retention-policy = ""
# bind-address = ":2003"
# protocol = "tcp"
# consistency-level = "one"
# These next lines control how batching works. You should have this enabled
# otherwise you could get dropped metrics or poor performance. Batching
# will buffer points in memory if you have many coming in.
# Flush if this many points get buffered
# batch-size = 5000
# number of batches that may be pending in memory
# batch-pending = 10
# Flush at least this often even if we haven't hit buffer limit
# batch-timeout = "1s"
# UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
# udp-read-buffer = 0
### This string joins multiple matching 'measurement' values providing more control over the final measurement name.
# separator = "."
### Default tags that will be added to all metrics. These can be overridden at the template level
### or by tags extracted from metric
# tags = ["region=us-east", "zone=1c"]
### Each template line requires a template pattern. It can have an optional
### filter before the template and separated by spaces. It can also have optional extra
### tags following the template. Multiple tags should be separated by commas and no spaces
### similar to the line protocol format. There can be only one default template.
# templates = [
# "*.app env.service.resource.measurement",
# # Default template
# "server.*",
# ]
###
### [collectd]
###
### Controls one or many listeners for collectd data.
###
[[collectd]]
enabled = true
bind-address = "127.0.0.1:25826"
database = "collectd"
# retention-policy = ""
#
# The collectd service supports either scanning a directory for multiple types
# db files, or specifying a single db file.
typesdb = "/usr/share/collectd/types.db"
#
# security-level = "none"
# auth-file = "/etc/collectd/auth_file"
# These next lines control how batching works. You should have this enabled
# otherwise you could get dropped metrics or poor performance. Batching
# will buffer points in memory if you have many coming in.
# Flush if this many points get buffered
# batch-size = 5000
# Number of batches that may be pending in memory
# batch-pending = 10
# Flush at least this often even if we haven't hit buffer limit
# batch-timeout = "10s"
# UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
# read-buffer = 0
# Multi-value plugins can be handled two ways.
# "split" will parse and store the multi-value plugin data into separate measurements
# "join" will parse and store the multi-value plugin as a single multi-value measurement.
# "split" is the default behavior for backward compatibility with previous versions of influxdb.
# parse-multivalue-plugin = "split"
###
### [opentsdb]
###
### Controls one or many listeners for OpenTSDB data.
###
[[opentsdb]]
# enabled = false
# bind-address = ":4242"
# database = "opentsdb"
# retention-policy = ""
# consistency-level = "one"
# tls-enabled = false
# certificate= "/etc/ssl/influxdb.pem"
# Log an error for every malformed point.
# log-point-errors = true
# These next lines control how batching works. You should have this enabled
# otherwise you could get dropped metrics or poor performance. Only points
# metrics received over the telnet protocol undergo batching.
# Flush if this many points get buffered
# batch-size = 1000
# Number of batches that may be pending in memory
# batch-pending = 5
# Flush at least this often even if we haven't hit buffer limit
# batch-timeout = "1s"
###
### [[udp]]
###
### Controls the listeners for InfluxDB line protocol data via UDP.
###
[[udp]]
# enabled = false
# bind-address = ":8089"
# database = "udp"
# retention-policy = ""
# InfluxDB precision for timestamps on received points ("" or "n", "u", "ms", "s", "m", "h")
# precision = ""
# These next lines control how batching works. You should have this enabled
# otherwise you could get dropped metrics or poor performance. Batching
# will buffer points in memory if you have many coming in.
# Flush if this many points get buffered
# batch-size = 5000
# Number of batches that may be pending in memory
# batch-pending = 10
# Will flush at least this often even if we haven't hit buffer limit
# batch-timeout = "1s"
# UDP Read buffer size, 0 means OS default. UDP listener will fail if set above OS max.
# read-buffer = 0
###
### [continuous_queries]
###
### Controls how continuous queries are run within InfluxDB.
###
[continuous_queries]
# Determines whether the continuous query service is enabled.
# enabled = true
# Controls whether queries are logged when executed by the CQ service.
# log-enabled = true
# Controls whether queries are logged to the self-monitoring data store.
# query-stats-enabled = false
# interval for how often continuous queries will be checked if they need to run
# run-interval = "1s"
###
### [tls]
###
### Global configuration settings for TLS in InfluxDB.
###
[tls]
# Determines the available set of cipher suites. See https://golang.org/pkg/crypto/tls/#pkg-constants
# for a list of available ciphers, which depends on the version of Go (use the query
# SHOW DIAGNOSTICS to see the version of Go used to build InfluxDB). If not specified, uses
# the default settings from Go's crypto/tls package.
# ciphers = [
# "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
# "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
# ]
# Minimum version of the tls protocol that will be negotiated. If not specified, uses the
# default settings from Go's crypto/tls package.
# min-version = "tls1.2"
# Maximum version of the tls protocol that will be negotiated. If not specified, uses the
# default settings from Go's crypto/tls package.
# max-version = "tls1.3"
@megaron .... https://grafana.com/grafana/dashboards/713 findest du das "original" meine Kopie müsstest du anpassen.
Ich glaube dein o.g. Problem wird sich mit dem einfügen des Deshbords von selbst lösen, weil bei mir läuft es ja auch genauso
Es kann aber schon mal 30 Minuten dauern bis die ersten Daten Angezeigt werden.....
@Master67 ... so nach langem ausprobieren läuft die Installation. Mein Problem war das ich nicht realisiert hatte das die database collectd angelegt wurde bzw. gestern Abend noch nicht angezeigt wurde.. Na ja, bin halt noch im "Dauerlernmodus". Vor einem Jahr konnte ich Begriffe wie Homematic, IoBroker, Grafana, ... noch nicht mal zuordnen.
Dein Dashboard habe bei mir mit eingebunden. Da ist ja alles an Information zum Datendurchsatz drin was wichtig ist. Tolle Arbeit. 
Vielen Dank nochmal für deine Unterstützung.
@megaron habe ich gerne gemacht, nur das Dashboard ist nicht von mir, habe es selber dort "gefunden" wie auch die anderen, deren Link ich dir Gestern per PN zu kommen lassen habe... den... man muss ja das "Rad" nicht immer neu Erfinden 
Hallo, gibt es schon Neuerungen hinsichtlich der Multi Connection Messung?
Gibt es zu der Meldung was neues?
Tests laufen brav durch.
Aber es kommt bei jedem Durchlauf immer
Heute 18:25 error web-speedy.0 TypeError: Cannot read property 'id' of undefined
Heute 16:25 error web-speedy.0 TypeError: Cannot read property 'id' of undefined
Heute 14:25 error web-speedy.0 TypeError: Cannot read property 'id' of undefined
Heute 12:25 error web-speedy.0 TypeError: Cannot read property 'id' of undefined
Version 0.2.0
@negalein sagte in [web-speedy] Teste deine Internetverbindung :
@Negalein sagte in [web-speedy] Teste deine Internetverbindung
@DutchmanIch bekomm bei jedem Speedtest folgende Error-Meldung.
Test wird aber eiwandfrei mit der fixen ID durchgeführt.
TypeError: Cannot read property 'id' of undefined@bjoernb sagte in [web-speedy] Teste deine Internetverbindung
@Dutchman said in [web-speedy] Teste deine Internetverbindung@Negalein sagte in [web-speedy] Teste deine Internetverbindung
Ich bekomm bei jedem Speedtest folgende Error-Meldung.
Test wird aber eiwandfrei mit der fixen ID durchgeführt.
TypeError: Cannot read property 'id' of undefinedKann ich mir kaum vorstellen
Dank für den reminder, fixe ich heute im laufe des tages/abendGibt es dafür schon eine Lösung, weil ich habe mit der Version 0.2.0 noch das gleiche Problem.
@Negalein sagte in [web-speedy] Teste deine Internetverbindung
@bjoernb sagte in [web-speedy] Teste deine InternetverbindungGibt es dafür schon eine Lösung, weil ich habe mit der Version 0.2.0 noch das gleiche Problem.
Dito! Problem besteht weiterhin. Habs erst jetzt wieder gesehen.
Ansonsten läuft alles super.
Hallo an alle,
kann leider kein Update mehr von irgendwelchen Adaptern durchführen.
Möchte nicht alles neu aufsetzen......!
Bekomme die folgende Fehlermeldung:
"npm ERR! Error while executing:npm ERR! /usr/bin/git ls-remote -h -t ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.gitnpm ERR! npm ERR! git@github.com: Permission denied (publickey).npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.npm ERR! npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehennpm ERR! und das Repository existiert.npm ERR! npm ERR! exited with error code: 128"
Sorry, habe schon einiges probiert, alles leider ohne Erfolg.
Danke für eure Unterstützung!
Wie hast du denn den Adapter versucht zu installieren?
@thomas-braun war damals eine Quelle direkt aus dem github, aber es ist jetzt offenbar alles weg. Aber ich bekommen diese Fehlermeldung nicht mehr weg. Bin am verzweifeln!!!!
@buehlis
Versuch mal
iobroker del web-speedy
@thomas-braun habe ich auch leider schon versucht 
Delete adapter "web-speedy"
host.raspberrypi object web-speedy deleted
host.raspberrypi object web-speedy.admin deleted
Error deleting adapter web-speedy from disk: Error: Cannot find module 'iobroker.web-speedy/io-package.json'
Require stack:
- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupInstall.js
- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js
- /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js
You might have to delete it yourself!
Ich habe keine Ahnung... was ich da machen soll.
@buehlis sagte in [web-speedy] Teste deine Internetverbindung :
Ich habe keine Ahnung... was ich da machen soll.
Ich auch nicht.
@buehlis
Mir ist doch noch was eingefallen:
iobroker update
iobroker upgrade iobroker.web-speedy@0.2.0
Would you like to upgrade web-speedy from @0.0.0 to @0.2.0 now? [(y)es, (n)o]: y
Update web-speedy from @0.0.0 to @0.2.0
NPM version: 6.14.12
npm install iobroker.web-speedy@0.2.0 --loglevel error --prefix "/opt/iobroker" (System call)
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://git@github.com/TA2k/ioBroker.mercedesme.git
npm ERR!
npm ERR! git@github.com: Permission denied (publickey).
npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.
npm ERR!
npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehen
npm ERR! und das Repository existiert.
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /home/iobroker/.npm/_logs/2021-05-01T12_28_07_856Z-debug.log
host.raspberrypi Cannot install iobroker.web-speedy@0.2.0: 1
Danke nachmals für die Hilfe....! Aber ich werde den iobroker bei Gelegenheit mal neu installieren und werde mir einen zweiten zum Testen holen.
Mod-Edit: Code in </> Code-Tag gepackt!
@buehlis sagte in [web-speedy] Teste deine Internetverbindung :
mercedesme
Da spuckt dir aber auch mercedesme noch in die Suppe.
Welche Adapter hast du denn noch aus git gefischt?
Ich glaube
iobroker list adapters
zeigt das.
system.adapter.admin : admin - v4.2.1
system.adapter.alarm : alarm - v2.0.0
system.adapter.alias-manager : alias-manager - v1.0.0
system.adapter.backitup : backitup - v2.1.0
system.adapter.bring : bring - v1.7.7
system.adapter.bshb : bshb - v0.1.13
system.adapter.chromecast : chromecast - v2.3.1
system.adapter.coronavirus-statistics : coronavirus-statistics - v0.7.0-4
system.adapter.countdown : countdown - v1.1.0
system.adapter.daswetter : daswetter - v3.0.4
system.adapter.devices : devices - v0.3.16
system.adapter.discovery : discovery - v2.6.1
system.adapter.dwd : dwd - v2.7.5
system.adapter.email : email - v1.0.9
system.adapter.fb-checkpresence : fb-checkpresence - v1.1.0
system.adapter.feiertage : feiertage - v1.0.17
system.adapter.flot : flot - v1.10.6
system.adapter.fullybrowser : fullybrowser - v2.0.8
system.adapter.geofency : geofency - v1.0.3
system.adapter.heos : heos - v1.7.7
system.adapter.history : history - v1.9.12
system.adapter.homeconnect : homeconnect - v0.0.32
system.adapter.ical : ical - v1.9.3
system.adapter.icons-icons8 : icons-icons8 - v0.0.1
system.adapter.icons-mfd-svg : icons-mfd-svg - v1.0.2
system.adapter.influxdb : influxdb - v1.9.4
system.adapter.info : info - v1.7.14
system.adapter.javascript : javascript - v5.0.14
system.adapter.lgtv : lgtv - v1.1.10
system.adapter.material : material - v0.13.9
system.adapter.mercedesme : mercedesme - v0.0.51
system.adapter.netatmo-crawler : netatmo-crawler - v0.3.9
system.adapter.nina : nina - v0.0.24
system.adapter.parser : parser - v1.0.7
system.adapter.ping : ping - v1.4.12
system.adapter.rpi2 : rpi2 - v1.2.0
system.adapter.snmp : snmp - v0.5.0
system.adapter.statistics : statistics - v1.0.2
system.adapter.tankerkoenig : tankerkoenig - v2.0.5
system.adapter.tr-064 : tr-064 - v4.2.11
system.adapter.trashschedule : trashschedule - v1.1.1
system.adapter.vis : vis - v1.3.8
system.adapter.vis-icontwo : vis-icontwo - v0.60.0
system.adapter.vis-inventwo : vis-inventwo - v2.8.3
system.adapter.vis-jqui-mfd : vis-jqui-mfd - v1.0.12
system.adapter.vis-keyboard : vis-keyboard - v0.0.2
system.adapter.vis-material-advanced : vis-material-advanced - v1.6.0
system.adapter.vis-weather : vis-weather - v2.5.2
system.adapter.web : web - v3.3.0
Mod-Edit: Code in </> Code-Tag gepackt!
Dann war es wohl wonanders...
Dann versuch mal den
iobroker update
iobroker del mercedesme
Auf welchem Repo bist du da eigentlich unterwegs?
iobroker repo list
@thomas-braun
stable : http://download.iobroker.net/sources-dist.json
beta : http://download.iobroker.net/sources-dist-latest.json
Active repo: stable
@buehlis
Jetzt ist der MercedesMe zwar irgendwie weg,... aber er kann den nicht ganz löschen.
$ ./iobroker del mercedesme
Delete adapter "mercedesme"
host.raspberrypi Counted 2 states (system.adapter.mercedesme.*) from states
host.raspberrypi object mercedesme deleted
host.raspberrypi object mercedesme.admin deleted
host.raspberrypi Deleting 2 state(s).
npm uninstall iobroker.mercedesme --loglevel error --prefix "/opt/iobroker" (System call)
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.gitnpm ERR! npm ERR! git@github.com: Permission denied (publickey).npm ERR! fatal: Konnte nicht vom Remote-Repository lesen.npm ERR! npm ERR! Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen bestehennpm ERR! und das Repository existiert.npm ERR! npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2021-05-01T17_21_39_650Z-debug.log
ERROR: Error deleting adapter mercedesme from disk: Error: host.raspberrypi: Cannot uninstall iobroker.mercedesme: 1
ERROR: You might have to delete it yourself!
process exited with code 0
Mod-Edit: Code in </> Code-Tag gepackt!
@buehlis sagte in [web-speedy] Teste deine Internetverbindung :
Keine Ahnung wie man das richtig sauber macht.
Vielleicht mal per npm versuchen:
cd /opt/iobroker
npm uninstall iobroker.mercedesme
@thomas-braun
Danke für deine Hilfe und Unterstützung, aber ich gebe auf....!!!!
@dutchman wie und wo trage ich die Werte ein für Server-ID (test-specific-id) und Server-URL(test-specific-url) ein ?
Hallo,
ich habe eben gesehen, dass ich beim testen der Bandbreite gefühlt hunderte von dieser Meldung bekomme.
web-speedy.02021-08-05 22:07:09.001info(14077) State value to set for "web-speedy.0.running_upload_speed" has to be type "number" but received type "string"
Habe heute auf den JS Controller 3.3 aktualisiert. Kann es damit zusammen hängen?
@david-g sagte in [web-speedy] Teste deine Internetverbindung :
Kann es damit zusammen hängen?
Ja. Siehe den entsprechenden Thread zu js-controller 3.3
Dann schreibe ich das mal auf git zum Adapter.
Dann kann man das ggf anpassen.
EDIT:
Gibt's sogar schon.
Moin,
ich bekomme irgendwie für mich nicht nachvollziehbare ergebnisse:
Klar können die immer etwas schwanken, aber da stimmt doch etwas nicht oder 
Leider klappt der test nach id nicht, deshalb habe ich im browser den gleichen server gewält, welcher zwar nicht optimal ist, aber zumindest sollten sich die ergebnisse ähnlich sein, test direkt im anschluss gemacht und ein paar mal widerholt, auch mit verschiedenen zeiten (5s-15s).
Die suche bringt leider tausende ergebnisse, die wirklich nur leicht außeinanderliegen, wo ich mir kein kopf drüber zerbrechen würde!
Woran kann das liegen? Internet läuft über Kabel...
Zum vergleich ein server in der nähe:
Ich nutze bei meinem Kabelanschluss das Testskript von kreyenborg.koeln
Das ist sehr konstant, wenn man da einen dicken Server per ID festpinnt.
Ok danke, werde ich mal testen 
@newpicsel
Du musst allerdings die speedtest-bin austauschen. Vielleicht schreib ich mal ein HowTo wie das am besten gemacht wird.
Ich denke das wäre hilfreich, auf der Seite von Kreyenborg.koeln steht nichts darüber 
@newpicsel
Doch steht schon drin, allerdings etwas umständlich. Mittlerweile kann man das sauberer machen als dort erwähnt.
@thomas-braun sagte in [web-speedy] Teste deine Internetverbindung :
@newpicsel
Du musst allerdings die speedtest-bin austauschen. Vielleicht schreib ich mal ein HowTo wie das am besten gemacht wird.
Das wäre Klasse. Habe einen PC (i3) auf dem Proxmox ist und IO läuft in einem lxc.
Bei speedtest.net werden zum Download i386, x86_64, arm32, arm32hf und arm64 angeboten,
welchen muß ich da nehmen?
@nashra
Gar keins. Das installiert man über den Paketmanager.
Repo richtig anlegen, das zieht dann die richtige Architektur nach.
