RaspberryMatic 2.35.16.20180715 – Erfahrungsberichte

[MathiasZ]

genau!
Den blazer_usb habe ich genommen.
So neuer Versuch, neues Glück.
Habe mal etwas geändert. Es geht nicht.
Ich warte, bis eine neue Raspberrymatic-Version online ist. dann setze ich mal 2 Raspberrymatic neu auf.
Eine als produktives System, die andere zum spielen.
Gruß,
Mathias

[darkbrain85]

Laut Liste brauchst du für deine USV den blazer_usb Treiber statt dem usbhid-ups

Das funktioniert bei mir auch mit dem usbhid Treiber! Bei mir ist es eine APC Backups Pro im Einsatz!

[darkbrain85]

Laut Liste brauchst du für deine USV den blazer_usb Treiber statt dem usbhid-ups

Das funktioniert bei mir auch mit dem usbhid Treiber! Bei mir ist es eine APC Backups Pro im Einsatz!


Wie wäre es, wenn du mal eine Config Dateien hier postest? Dann könnte man mal einen Blick drauf werfen....

[LibertyX]

Laut Liste brauchst du für deine USV den blazer_usb Treiber statt dem usbhid-ups

Das funktioniert bei mir auch mit dem usbhid Treiber! Bei mir ist es eine APC Backups Pro im Einsatz!


Wie wäre es, wenn du mal eine Config Dateien hier postest? Dann könnte man mal einen Blick drauf werfen....

Schön... du hast aber auch eine andere USV!!
Und laut Hardware compatibility list des NUT https://networkupstools.org/stable-hcl.html

Läuft die Powerwalker VI 2000 mit dem blazer_usb Treiber und deine APC-Backups Pro mit dem usbhid-ups Treiber!

[darkbrain85]

Schön... du hast aber auch eine andere USV!!
Und laut Hardware compatibility list des NUT https://networkupstools.org/stable-hcl.html

Läuft die Powerwalker VI 2000 mit dem blazer_usb Treiber und deine APC-Backups Pro mit dem usbhid-ups Treiber!

Du hast recht, ich habe mich verlesen.

Das ändert aber nichts an der Tatsache, dass die Konfigurationsdateien extrem hilfreich wären wenn man helfen will.
Am besten alles aus /usr/local/etc/config/nut.

Edit:
Die Ausgabe von

Code: Alles auswählen

upsc ups

wäre auch sehr hilfreich. Sollte in der ups.conf ein anderer Name verwendet werden, so muss das "ups" natürlich gegen diesen ausgetauscht werden.

[MathiasZ]

Sorry für die späte Antwort.
Abei sende ich Euch die Codes:

ups.conf (Bitte ganz nach unten scrollen):

Code: Alles auswählen

# Network UPS Tools: example ups.conf
#
# --- SECURITY NOTE ---
#
# If you use snmp-ups and set a community string in here, you 
# will have to secure this file to keep other users from obtaining
# that string.  It needs to be readable by upsdrvctl and any drivers,
# and by upsd.
#
# ---
#
# This is where you configure all the UPSes that this system will be
# monitoring directly.  These are usually attached to serial ports, but
# USB devices and SNMP devices are also supported.
#
# This file is used by upsdrvctl to start and stop your driver(s), and
# is also used by upsd to determine which drivers to monitor.  The 
# drivers themselves also read this file for configuration directives.
#
# The general form is:
# 
# [upsname]
#       driver = <drivername>
#         port = <portname>
#	< any other directives here >
#
# The section header ([upsname]) can be just about anything as long as
# it is a single word inside brackets.  upsd uses this to uniquely 
# identify a UPS on this system.
#
# If you have a UPS called snoopy, your section header would be "[snoopy]".
# On a system called "doghouse", the line in your upsmon.conf to monitor
# it would look something like this:
#
# 	MONITOR snoopy@doghouse 1 upsmonuser mypassword master
#
# It might look like this if monitoring in slave mode:
#
# 	MONITOR snoopy@doghouse 1 upsmonuser mypassword slave
#
# Configuration directives
# ------------------------
# 
# These directives are common to all drivers that support ups.conf:
#
#  driver: REQUIRED.  Specify the program to run to talk to this UPS.  
#          apcsmart, bestups, and sec are some examples.
#
#    port: REQUIRED.  The serial port where your UPS is connected.  
#          /dev/ttyS0 is usually the first port on Linux boxes, for example.
#
# sdorder: optional.  When you have multiple UPSes on your system, you
#          usually need to turn them off in a certain order.  upsdrvctl
#          shuts down all the 0s, then the 1s, 2s, and so on.  To exclude
#          a UPS from the shutdown sequence, set this to -1.
#
#          The default value for this parameter is 0.
#
#  nolock: optional, and not recommended for use in this file.
#
#          If you put nolock in here, the driver will not lock the
#          serial port every time it starts.  This may allow other 
#          processes to seize the port if you start more than one by 
#          mistake.
#
#          This is only intended to be used on systems where locking
#          absolutely must be disabled for the software to work.
#
# maxstartdelay: optional.  This can be set as a global variable
#                above your first UPS definition and it can also be
#                set in a UPS section.  This value controls how long
#                upsdrvctl will wait for the driver to finish starting.
#                This keeps your system from getting stuck due to a
#                broken driver or UPS.
#
#                The default is 45 seconds.
#
#
# Anything else is passed through to the hardware-specific part of
# the driver.
# 
# Examples
# --------
#
# A simple example for a UPS called "powerpal" that uses the blazer_ser
# driver on /dev/ttyS0 is:
#
# [powerpal]
#	driver = blazer_ser
#	port = /dev/ttyS0
#	desc = "Web server"
#
# If your UPS driver requires additional settings, you can specify them
# here.  For example, if it supports a setting of "1234" for the
# variable "cable", it would look like this:
# 
# [myups]
# 	driver = mydriver
#	port = /dev/ttyS1
#	cable = 1234
#	desc = "Something descriptive"
#
# To find out if your driver supports any extra settings, start it with
# the -h option and/or read the driver's documentation.
#
# If you connect your UPS via USB you can try the following section:
#
# [myups]
# driver = usbhid-ups
# port = auto
# desc = "USB UPS"
[vi2000]
driver = blazer_usb
port = auto
desc = "Powerwalker VI 2000"

upsd.conf (Bitte ganz nach unten scrollen):

Code: Alles auswählen

# Network UPS Tools: example upsd configuration file
#
# This file contains access control data, you should keep it secure.
#
# It should only be readable by the user that upsd becomes.  See the FAQ.
#
# Each entry below provides usage and default value.

# =======================================================================
# MAXAGE <seconds>
# MAXAGE 15
#
# This defaults to 15 seconds.  After a UPS driver has stopped updating
# the data for this many seconds, upsd marks it stale and stops making
# that information available to clients.  After all, the only thing worse
# than no data is bad data.
#
# You should only use this if your driver has difficulties keeping
# the data fresh within the normal 15 second interval.  Watch the syslog
# for notifications from upsd about staleness.

# =======================================================================
# STATEPATH <path>
# STATEPATH /var/run/nut
#
# Tell upsd to look for the driver state sockets in 'path' rather
# than the default that was compiled into the program.

# =======================================================================
# LISTEN <address> [<port>]
# LISTEN 127.0.0.1 3493
# LISTEN ::1 3493
#
# This defaults to the localhost listening addresses and port 3493.
# In case of IP v4 or v6 disabled kernel, only the available one will be used.
#
# You may specify each interface you want upsd to listen on for connections,
# optionally with a port number.
#
# You may need this if you have multiple interfaces on your machine and
# you don't want upsd to listen to all interfaces (for instance on a
# firewall, you may not want to listen to the external interface).
#
# This will only be read at startup of upsd.  If you make changes here,
# you'll need to restart upsd, reload will have no effect.

# =======================================================================
# MAXCONN <connections>
# MAXCONN 1024
#
# This defaults to maximum number allowed on your system.  Each UPS, each
# LISTEN address and each client count as one connection.  If the server
# runs out of connections, it will no longer accept new incoming client
# connections.  Only set this if you know exactly what you're doing.

# =======================================================================
# CERTFILE <certificate file>
# CERTFILE /usr/local/ups/etc/upsd.pem
#
# When compiled with SSL support with OpenSSL backend,
# you can enter the certificate file here.
# The certificates must be in PEM format and must be sorted starting with
# the subject's certificate (server certificate), followed by intermediate
# CA certificates (if applicable_ and the highest level (root) CA. It should
# end with the server key. See 'docs/security.txt' or the Security chapter of
# NUT user manual for more information on the SSL support in NUT.
#
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.

# =======================================================================
# CERTPATH <certificate file or directory>
# CERTPATH /usr/local/ups/etc/cert/upsd
#
# When compiled with SSL support with NSS backend,
# you can enter the certificate path here.
# Certificates are stored in a dedicated database (splitted in 3 files).
# Specify the path of the database directory.
# 
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.

# =======================================================================
# CERTIDENT <certificate name> <database password>
# CERTIDENT "my nut server" "MyPasSw0rD"
#
# When compiled with SSL support with NSS backend,
# you can specify the certificate name to retrieve from database to
# authenticate itself and the password
# required to access certificate related private key.
# 
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.

# =======================================================================
# CERTREQUEST <certificate request level>
# CERTREQUEST REQUIRE
#
# When compiled with SSL support with NSS backend and client certificate
# validation (disabled by default, see 'docs/security.txt'),
# you can specify if upsd requests or requires client's' certificates.
# Possible values are :
#  - 0 to not request to clients to provide any certificate
#  - 1 to require to all clients a certificate
#  - 2 to require to all clients a valid certificate
# 
# See 'docs/security.txt' or the Security chapter of NUT user manual
# for more information on the SSL support in NUT.
LISTEN localhost 3493
LISTEN 192.168.xxx.xxx 3493

upsd.users (Bitte ganz nach unten scrollen):

Code: Alles auswählen

# Network UPS Tools: Example upsd.users
#
# This file sets the permissions for upsd - the UPS network daemon.
# Users are defined here, are given passwords, and their privileges are
# controlled here too.  Since this file will contain passwords, keep it
# secure, with only enough permissions for upsd to read it.

# --------------------------------------------------------------------------

# Each user gets a section.  To start a section, put the username in
# brackets on a line by itself.  To set something for that user, specify
# it under that section heading.  The username is case-sensitive, so
# admin and AdMiN are two different users.
#
# Possible settings:
#
# password: The user's password.  This is case-sensitive.
#
# --------------------------------------------------------------------------
#
# actions: Let the user do certain things with upsd.  
# 
# Valid actions are:
#
# SET	- change the value of certain variables in the UPS
# FSD   - set the "forced shutdown" flag in the UPS
# 
# --------------------------------------------------------------------------
#
# instcmds: Let the user initiate specific instant commands.  Use "ALL"
# to grant all commands automatically.  There are many possible  
# commands, so use 'upscmd -l' to see what your hardware supports.  Here
# are a few examples:
#
# test.panel.start	- Start a front panel test
# test.battery.start	- Start battery test
# test.battery.stop	- Stop battery test
# calibrate.start	- Start calibration
# calibrate.stop	- Stop calibration
#
# --------------------------------------------------------------------------
#
# Example:
#
#	[admin]
#		password = mypass
#		actions = SET
#		instcmds = ALL
#

#
# --- Configuring for a user who can execute tests only
#
#	[testuser]
#		password  = pass
#		instcmds  = test.battery.start
#		instcmds  = test.battery.stop

#
# --- Configuring for upsmon
#
# To add a user for your upsmon, use this example:
#
#	[upsmon]
#		password  = pass
#		upsmon master
# or
#		upsmon slave
#
# The matching MONITOR line in your upsmon.conf would look like this:
#
# MONITOR myups@localhost 1 upsmon pass master	(or slave)
[upsmon]
password = 1111
upsmon master

Datei upsmon.conf (Änderungen ganz oben):

Code: Alles auswählen

MONITOR vi2000@localhost 1 upsmon 1111 slave
MINSUPPLIES 1
SHUTDOWNCMD /sbin/poweroff
NOTIFYCMD /etc/config/nut/nut_notify.sh
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /var/tmp/killpower
NOTIFYFLAG ONLINE   SYSLOG+EXEC
NOTIFYFLAG ONBATT   SYSLOG+EXEC
NOTIFYFLAG LOWBATT  SYSLOG+EXEC
NOTIFYFLAG FSD      SYSLOG+EXEC
NOTIFYFLAG COMMOK   SYSLOG+EXEC
NOTIFYFLAG COMMBAD  SYSLOG+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+EXEC
NOTIFYFLAG NOCOMM   SYSLOG+EXEC
NOTIFYFLAG NOPARENT SYSLOG+EXEC
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5

Gruß,
Mathias

[LibertyX]

Das

Code: Alles auswählen

MODE=netserver

hast du in der nut.conf auch eingetragen?

Was bekommst du denn über ssh als Ausgabe auf

Code: Alles auswählen

upsc vi2000

[MathiasZ]

Sorry, habe ich vergessen hier zu erwähnen.
Ja in der nut.conf steht

Code: Alles auswählen

Mode=netserver

wenn ich

Code: Alles auswählen

upsc vi2000

eingebe, bekomme ich zurück:

Code: Alles auswählen

connection faillure Connection refused

Gruß,
Mathias

[darkbrain85]

Kannst Du mal in der upsd.conf

Code: Alles auswählen

LISTEN 192.168.xxx.xxx 3493

in

Code: Alles auswählen

LISTEN 0.0.0.0 3493

ändern und es nochmal versuchen? Natürlich am besten einen neustart machen.

Waren die "XXX" in der IP Absicht, oder wolltest Du da völlig unnötig die Interface IP "anonymisieren"?

[MathiasZ]

Ich werde es heute Nachmittag nach der Arbeit mit
LISTEN 0.0.0.0 versuchen.
Meine IP ist natürlich in Klartext in der Config.
Ich habe mit den x-en meine IP hier nur unkenntlich gemacht.
Gruß,
Mathias