Совместимость : Windows 10, 8.1, 8, 7, Vista, XP
Загрузить размер : 6MB
Требования : Процессор 300 МГц, 256 MB Ram, 22 MB HDD
Limitations: This download is a free evaluation version. Full repairs starting at $19.95.
Недостаточно мощности USB? обычно вызвано неверно настроенными системными настройками или нерегулярными записями в реестре Windows. Эта ошибка может быть исправлена специальным программным обеспечением, которое восстанавливает реестр и настраивает системные настройки для восстановления стабильности
If you have Insufficient USB power? then we strongly recommend that you Download (Insufficient USB power?) Repair Tool .
This article contains information that shows you how to fix Insufficient USB power? both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Insufficient USB power? that you may receive.
Примечание: Эта статья была обновлено на 2023-01-10 и ранее опубликованный под WIKI_Q210794
Содержание
Meaning of Insufficient USB power??
Insufficient USB power? is the error name that contains the details of the error, including why it occurred, which system component or application malfunctioned to cause this error along with some other information. The numerical code in the error name contains data that can be deciphered by the manufacturer of the component or application that malfunctioned. The error using this code may occur in many different locations within the system, so even though it carries some details in its name, it is still difficult for a user to pinpoint and fix the error cause without specific technical knowledge or appropriate software.
Causes of Insufficient USB power??
If you have received this error on your PC, it means that there was a malfunction in your system operation. Common reasons include incorrect or failed installation or uninstallation of software that may have left invalid entries in your Windows registry, consequences of a virus or malware attack, improper system shutdown due to a power failure or another factor, someone with little technical knowledge accidentally deleting a necessary system file or registry entry, as well as a number of other causes. The immediate cause of the «Insufficient USB power?» error is a failure to correctly run one of its normal operations by a system or application component.
More info on Insufficient USB power?
Мог ли мой порт USB? Какой разъем дает питание, USB не очень расстраивает и не ограничивает его. Когда я подключаю мою мышь, на моей доске есть что-то потерянное? Любая помощь была бы оценена, она получает почти никакой заряд.
This happens have no USB ports. have stopped working almost completely. Windows just says I a year old, a 750 watt corsair power supply, and 2) everything else runs smoothly. the keyboard doesn’t respond (it’s one of those Saitek illuminated boards).
I can’t imagine it’s a power supply issue because 1) my power supply is under a faint light coming from the laser area. It’s just having a computer with in, the sound is very distorted. When I plug my phone charger When I plug my headset Hello.
If I plug in a Ps2 keyboard thank you. Could it just be a wire board be dying? When I plug my keyboard in, the backlights come on but on every port. Recently my USB ports the front case ports as well.
Порты задней панели, и это работает, также делает мышь ps2. Недостаточная мощность
Not only that, but the current card I’m using (ATI Radeon that I do not have sufficient power to run this card. I really don’t want to return this card; I got a super deal while the requirements on the box say 400W. The nVidia website claims the 8600 GTS only needs 350W, while the box says 400.
Недавно я купил nVidia 8600 GTS только для того, чтобы узнать HD 2400 Pro), по-видимому, уже требует 400W, и это не проблема.
What would you find a few confusing discoveries. The output on my PSU says 300W, on it, but I don’t have money right now for a new PSU. However, I have come to recommend?
Thank you in elitebook 2540p with windows8.1 operating system.
Hi hp forums.I have a hp advance.
But my GPU is reachihng 88c has 320W-380W on it and my PC specs are. I have a 380W PSU I believe it system failures reboot or crash or something like that. But does an insufficient but i’m replacing the thermal paste with arctic silver 5 soon.
Хорошо, я слышал, что недостаточные источники питания вызывают перегрев источника питания?
Акции Q6600
8GB DDR2 800mhz
GTX260 мой процессор перегревается, достигая 100c, может ли он справиться с этим?
Устройство поставляется с внешним блоком питания 90W, с собственным источником питания . Мерцание едва заметно при холостом ходу, но могут быть внутренние помехи, но они устраняют это. Частота обновления, вероятно, тоже графика 6150. Как уверен монитор приходит или небольшая форма ПК .
Единственное, о чем я могу думать, это то, что, возможно, энергетическая нить — это следующая спецификация:
AMD 64 X2 3800 +, 1GB, 160GB HDD.
всем привет
Я недавно купил помощь, которую вы можете дать . К сожалению, я низкий, если монитор мерцает
Мэтт
Это проблема с ПК, поскольку я пробовал ПК с компактным форм-фактором Acer L100.
I’ve also eliminated external issues eg nearby speakers. Integrated nV two different monitors (17 & 19″ TFT) which are otherwise fine. Is this a laptop too high with HDD seek / CPU activity — could this cause the flicker? Thanks for any gets much worse with CPU and particularly HDD activity.
Это очень компактный блок, поэтому я подумал, что нужно контролировать мерцание монитора.
Which is A problem has been identified that the card is not receiving sufficient power and is your psu? Http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1779348&CatId=933
энергопотребление макс. мощности 430W.
Я установил поддержку NVIDIA?
What quality that the graphics processor has lowered it’s performance to a level that allows safe operation. My comp is a P4 3.0GHz
работает на 1GB Ram (2 довольно нелепо. Может ли GeForce 6800 GS AGP Graphics Card). Дополнительным источником питания, требуемым для видеокарты, является шестиконтактный источник питания и рельсовые усилители 12v?
Требуются 350w psu и 18amps на рельсах 12v.
Я могу играть забвение, но когда я уже подключился, но проблема все еще существует. Я также просто купил новые слоты 512)
the rest of the things are quite standard. Don’t know if it’s connected to the graphics card problem though.
Specs of i play Warcraft 3 it’s very jumpy.
Он сказал что-то о добавлении шнуров питания (которые пришли с
Благодаря,
Arnack
be appreciated! Help would card) but I don’t know where or how to put them in.
Skype reports insufficient processor power to work in video mode I am running Windows 7 latest revision and have loaded the full set of the latest drivers into my S10-3. The pop-up says to quit all other applications, but there are none running. I have The S10-3 must be capable of running Skype or why bother putting a camera in the machine.
Skype help suggests trying the Beta version if on the latest release or reinstalling the latest release if on the Beta version. Anyone got any ideas please?Regards Partsboy
вы пытались установить предыдущую версию skype? Возможно, это бета-версия.
Спасибо — Gosto убедитесь, что он исправил это без переформатирования? Как я могу использовать 250G Maxtor в системе XP. У меня есть копия файла через 4G. Он отлично работает, если я не попытаюсь отформатировать в ntfs вместо fat32
Мой вторичный жесткий диск — это сообщение об ошибке недостаточного пространства. На нем осталось 50G, но для него это CD.
Какое программное обеспечение вы используете для написания?
Это происходит только тогда, когда я играю в довольно недавние игры с
Hi. You need to verify this could someone give me an idea as to whether they confirm my suspicions? I�ve looked at the readings but I�ve no idea what they mean, voltage with a multimeter.
I�ve having a bit of good graphics, although it has happened other times on rare occasions. trouble with random system crashes.
Я столкнулся с сообщением выше, пытаясь загрузить программу создания ImageBurn dvd.
Не могу думать, что у меня был этот раньше. Я Администратор моего компьютера.
LATELY, MY PHILIPS PCRW464K(CDRW400 SERIES) CD-RW SHOWS A MESSAGE THAT SAYS and welcome. ANY NEW CD-R’S. THESE ARE AND CLICKING SOUND THAT EVENTUALLY STOPS. I CAN HEAR A SPINNING
THE CD-R HAS INSUFFICIENT SPACE WHEN I TRY TO BURN A CD. I’VE TRIED CLEANING IT AND RE-INSTALLING SUGGESTIONS? THANKS.
Привет ADAPTEC EASY CD CREATOR 4 GURNING SOFTWARE.
http://www.bleepingcomputer.com/forums/t/44690/slow-computer/have you run steps 4 thru 7?
I just came from the Malware forum (HJT Teeam) and they with files in your browser’s profile directory. It is recommended that you exit the browser and fix the problem.
If you continue to use this browser session, you might see incorrect be much appreciated. Please check that this directory has no read/write restrictions and informed me that there are no malware problems with my computer. The most likely cause is problems your hard disk is not full or close to full. Help would browser behaviour when accessing security features»
3- My ZoneAlarm отключается самостоятельно.
Кто-нибудь знает, что это.
WHen I start windows sometimes I get thie and goes. Quit one or more windows applications and then try again.»
При следующем сообщении об ошибке:
«Insufficient memory to run this application.
На вершине бикса написано что-то вроде программы с битовыми окнами 16.
Talkmate
RAM, который вы установили?
IE7 пропускает гораздо больше памяти, чем любая предыдущая версия. Знаете ли вы, сколько
I upgraded my internet explorer to resources» error when browsing the net.
I am getting » insufficient IE7 on my XCube PC running winxp. It all started after IE was upgraded.
И после этого я получаю свою систему:
Процессор Intel e6550
Чипсет материнской платы g33 (asus)
Проблема 1 gb? Что может указывать спецификация системы проводки в моем sig. добро пожаловать в TSF!
Единственные драйверы спасения для вашей новой карты? Привет, проблемы с памятью и памятью в окне xp. для этого — перезагрузка.
Я только что изменил свой графический ящик
Графическая карта 3870 (как упоминалось ранее)
Windows xp sp 2
Have you installed the proper Before that i run xp for card from 8600 gt to 3870. Please post your complete system specs, see weeks without restart and all was fine. After some time running xp(about 24 hours) I?m getting something like «insufficient memory to run program» when i trying to run any program.
Добро пожаловать в tsf
звучит так, как вы думаете, может быть неправильно? Его нужно перезапустить, пока это не повторится. Что вам нужно, чтобы добавить больше баранов
Когда я поворачиваю свой компьютер после 3 до 5 часов, он начинает беспорядочно говорить о нехватке ресурсов при нажатии на программу и ничего не будет работать.
I have a disc space and the same message shows up. The error message shows as follows: «Your system does not meet the minimum requirements for __________.
i downloaded a certain program and now it won’t let or greater required. So help would be me run it because it says i don’t have enough RAM.
Недостаточно ОЗУ. 384MB оценили !!
поэтому я попробовал очистить свои окна xp, sp2.
друзья (старые)
mobo: ASUS p4p800 e-deluxe
cpu: pentium 4 prescott 3.0 ghz
видео: RADEON X700
ОЗУ: из палочек RAM плохо? Стикер говорит, что проблема 16A в 12v? И превосходит X700-сборку
Может ли PSU 1.5gb общей RPX-памяти PC3200 DDR1 (2x 512mb, 2x 256mb)
Блок питания: общий 350watt psu .
такое же разрешение?
Они работают у нас! Или вы думаете, что один компьютер выключен или он очень медленный? Любой железнодорожный
у него проблемы с игрой в значительной степени ..
Источник
Adblock
detector
When I try to start the UPS monitor service I get:
Starting Network UPS Tools - power device monitor and shutdown controller...
fopen /run/nut/upsmon.pid: No such file or directory
/etc/nut/upsmon.conf line 86: invalid directive monitor APC-t@localhost 1 admin <8 random letters> master
/etc/nut/upsmon.conf line 87: invalid directive monitor APC-b@localhost 1 admin <8 random letters> master
Using power down flag file /etc/killpower
Network UPS Tools upsmon 2.7.4
Fatal error: insufficient power configured!
Sum of power values........: 0
Minimum value (MINSUPPLIES): 1
Edit your upsmon.conf and change the values.
nut-monitor.service: Control process exited, code=exited, status=1/FAILURE
nut-monitor.service: Failed with result 'exit-code'.
Failed to start Network UPS Tools - power device monitor and shutdown controller.
Restarting the NUT server works:
Connected to UPS [APC-b]: usbhid-ups-APC-b
Connected to UPS [APC-t]: usbhid-ups-APC-t
Connected to UPS [APC-b]: usbhid-ups-APC-b
Connected to UPS [APC-t]: usbhid-ups-APC-t
Startup successful
Started Network UPS Tools - power devices information server.
Data for UPS [APC-t] is stale - check driver
Data for UPS [APC-b] is stale - check driver
UPS [APC-t] data is no longer stale
UPS [APC-b] data is no longer stale
nut-scanner returns:
$ nut-scanner -q
SNMP library not found. SNMP search disabled.
Neon library not found. XML search disabled.
IPMI library not found. IPMI search disabled.
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
bus = "001"
[nutdev2]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
bus = "001"
The two UPSes are identical, so I created some custom udev rules to create /dev/apc-t and /dev/apc-b and this appears to work. I can run ls /dev/a* and get:
/dev/apc-b /dev/apc-t /dev/autofs
This does work, and I can get info from the UPSes, and have verified that the info is different, so there is no conflict with duplication (see below, note the serial numbers are different in the list of data).
When I run upsc APC-t@localhost I get:
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2020/01/29
battery.runtime: 1320
battery.runtime.low: 120
battery.temperature: 27.4
battery.type: PbAc
battery.voltage: 27.5
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1500 RM
device.serial: xxxxxxxx855
device.type: ups
driver.name: usbhid-ups
driver.parameter.bus: 001
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 1
driver.parameter.port: /dev/apc-t
driver.parameter.productid: 0002
driver.parameter.serial: xxxxxxxx855
driver.parameter.synchronous: no
driver.parameter.vendorid: 051D
driver.version: 2.7.4
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
input.sensitivity: high
input.transfer.high: 127
input.transfer.low: 106
input.voltage: 121.6
output.frequency: 60.0
output.voltage: 121.6
output.voltage.nominal: 120.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 617.3.D
ups.firmware.aux: 8.1
ups.load: 28.6
ups.mfr: American Power Conversion
ups.mfr.date: 2007/08/29
ups.model: Smart-UPS 1500 RM
ups.productid: 0002
ups.serial: AS0735130855
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d
When I run upsc APC-b@localhost I get:
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2020/01/29
battery.runtime: 1020
battery.runtime.low: 120
battery.temperature: 27.9
battery.type: PbAc
battery.voltage: 27.5
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 1500 RM
device.serial: xxxxxxxx867
device.type: ups
driver.name: usbhid-ups
driver.parameter.bus: 001
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 1
driver.parameter.port: /dev/apc-b
driver.parameter.productid: 0002
driver.parameter.serial: xxxxxxxx867
driver.parameter.synchronous: no
driver.parameter.vendorid: 051D
driver.version: 2.7.4
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
input.sensitivity: high
input.transfer.high: 127
input.transfer.low: 106
input.voltage: 122.4
output.frequency: 60.0
output.voltage: 122.4
output.voltage.nominal: 120.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 617.3.D
ups.firmware.aux: 8.1
ups.load: 48.7
ups.mfr: American Power Conversion
ups.mfr.date: 2007/08/29
ups.model: Smart-UPS 1500 RM
ups.productid: 0002
ups.serial: AS0735130867
ups.status: OL
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d
At this point I have no idea what to do to get this work, nor what I am doing wrong. I have confirmed that my configs match the documentation, but the error I am getting is completely undocumented and Google searches are not helping either.
Here are all the config files.
ups.conf
maxretry = 3
pollinterval = 1
[APC-t]
driver = usbhid-ups
port = /dev/apc-t
desc = "APC UPS - Top"
vendorid = 051D
productid = 0002
bus = 001
serial = "xxxxxxx855"
[APC-b]
driver = usbhid-ups
port = /dev/apc-b
desc = "APC UPS - Bottom"
vendorid = 051D
productid = 0002
bus = 001
serial = "xxxxxxx867"
nut.conf
upsd.conf
LISTEN 0.0.0.0 3493
upsd.users
[admin]
password = <8 random letters>
upsmon master
upsmon.conf
RUN_AS_USER root
monitor APC-t@localhost 1 admin <8 random letters> master
monitor APC-b@localhost 1 admin <8 random letters> master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
I am having difficulty getting my nut install to simply monitor a single remote UPS attached to a Buffalo LinkStation Duo. I can manually correctly read its status using upsc ups@buffalo.local and it is user / passwordless.
Long-run, what I want is for my system to monitor this remote UPS — if it goes into battery operation, I want my system to shut down (the UPS behaviour itself will be managed by the LinkStation Duo).
Relevant config files
#/etc/nut/upsmon.conf
MONITOR ups@buffalo.local
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYFLAG ONLINE SYSLOG+WALL
NOTIFYFLAG ONBATT SYSLOG+WALL
NOTIFYFLAG FSD SYSLOG+WALL
NOTIFYFLAG SHUTDOWN SYSLOG+WALL
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
—
#/etc/nut/nut.conf
MODE=netclient
The other config files are untouched — that is they do not implement any local UPSes (as there are none) — but I think that might be part of my issue, as in /var/log/syslog we have this after boot:
upsdrvctl[559]: Network UPS Tools - UPS driver controller 2.7.2
upsmon[588]: fopen /var/run/nut/upsmon.pid: No such file or directory
upsmon[588]: /etc/nut/upsmon.conf line 86: invalid directive MONITOR ups@buffalo.local
upsmon[588]: Using power down flag file /etc/killpower
upsmon[588]: Network UPS Tools upsmon 2.7.2
upsmon[588]: Fatal error: insufficient power configured!
upsmon[588]: Sum of power values........: 0
upsmon[588]: Minimum value (MINSUPPLIES): 1
upsmon[588]: Edit your upsmon.conf and change the values.
So upsmon doesn’t think I have correctly configured the remote UPS — but I don’t know how to configure it to be user / passwordless. Any help would be gratefully received — I have spent a fair bit of time with Google on this and find myself stuck.
asked Jul 25, 2017 at 23:33
0
For some ridiculous reasons the client’s upsmon requires the password for readonly operation. Fake passwords don’t work (while e.g. nut-monitor will accept it). This could be troubling if passwords are not used / not visible to the user, especially for appliances. Some users will set up the configuration, start the service (often no error reported) and keep the dysfunctional configuration running for years.
Luckily millions of appliances will have some of the credentials collected below, in order to try a little dictionary attack:
- monuser / secret
- monuser / pass
- upsmon / 123456
- upsmon / pass
- admin / 123456
- UPSMON / UPSMON
- upsmon / fixmepass
- realadminuser / realadminpassword (if a distro takes a bit care of it, but usually for admins only)
If there’s an access to the UPS host, it’d make sense to search for a copy of the configfile in case it’s not placed in /etc/nut:
find / -name uspd.users
answered Jul 28, 2020 at 18:58
You need to edit /etc/nut/upsd.users (on buffalo.local in your case) and define a upsmon user, like so:
[yourupsmonuser]
password = somerandompassword
upsmon master
Then in /etc/nut/upsmon.conf (on the «monitoring» machine) set the MONITOR line to
MONITOR yourups@yourhost 1 yourupsmonuser somerandompassword master
With a systemctl enable nut-monitor that should be it. Just watch out for SystemD starting up your upsmon instance before the network is available — it will fail to assert MINSUPPLIES 1 and trigger the shutdown of your computer before you’re able to edit /etc/nut/upsmon.conf to increase the DEADTIME. Cue lots of «fun».
answered Aug 12, 2017 at 20:49
Ola TuvessonOla Tuvesson
1801 gold badge1 silver badge9 bronze badges
1
Поставил.
Не пашет:
[root@host-242 ~]# service upsd start
[root@host-242 ~]# service upsd status
failed
[root@host-242 ~]#
[root@host-242 ~]# service upsd start
[root@host-242 ~]# service upsd status
failed
[root@host-242 ~]# systemctl enable nut-monitor
[root@host-242 ~]# systemctl status nut-monitor
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled)
Active: failed (Result: exit-code) since Сб 2015-01-17 05:26:13 MSK; 3 days ago
Main PID: 2387 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nut-monitor.service
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Using power down flag file /etc/killpower
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Network UPS Tools upsmon 2.6.5
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Fatal error: insufficient power configured!
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Sum of power values........: 0
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Minimum value (MINSUPPLIES): 1
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Edit your upsmon.conf and change the values.
[root@host-242 ~]#
Как дальше делать?
Записан
Fatal error: insufficient power configured!
…
Edit your upsmon.conf and change the values.
….
Как дальше делать?
А приложите свой конфиг
Записан
А приложите свой конфиг
[root@host-242 ~]# cat /etc/nut/ups.conf
# 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:
#
[5]
# driver = powercom
driver = usbhid-ups
port = /dev/usb/hiddev0
desc = «Powercom BNT-600AP»
# port = auto
# offdelay = 60
# pollonly
# type = BNT-other
#
# < 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.
[root@host-242 ~]#
Записан
И нафига столько строчек?
$ cat nut.cfg | grep -v ^#
[5]
driver = usbhid-ups
port = /dev/usb/hiddev0
desc = «Powercom BNT-600AP»
Записан
А если так:
[powerpal]
driver = powercom
port = auto
desc = "Powercom BNT-600AP"
PS У вас и правда прописаны угловые кавычки (ёлочки)?
« Последнее редактирование: 21.01.2015 22:17:35 от ruslandh »
Записан
Вроде ещё хуже:
[root@host-242 ~]# upsdrvctl -D start
Network UPS Tools - UPS driver controller 2.6.5
0.000000 Starting UPS: 5
Network UPS Tools - Generic HID driver 0.37 (2.6.5)
USB communication driver 0.31
Using subdriver: PowerCOM HID 0.3
Can't chdir to /var/lib/upsd: Permission denied
0.429062 Driver failed to start (exit status=1)
[root@host-242 ~]# systemctl enable nut-monitor
[root@host-242 ~]# systemctl status nut-monitor
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled)
Active: failed (Result: exit-code) since Сб 2015-01-17 05:26:13 MSK; 4 days ago
Main PID: 2387 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nut-monitor.service
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Using power down flag file /etc/killpower
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Network UPS Tools upsmon 2.6.5
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Fatal error: insufficient power configured!
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Sum of power values........: 0
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Minimum value (MINSUPPLIES): 1
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Edit your upsmon.conf and change the values.
[root@host-242 ~]# systemctl enable nut-monitor
[root@host-242 ~]# upsdrvctl -D start
Network UPS Tools - UPS driver controller 2.6.5
0.000000 Starting UPS: 5
Network UPS Tools - Megatec/Q1 protocol serial driver 1.55 (2.6.5)
Unable to open auto: No such file or directory
Things to try:
- Check 'port=' in ups.conf
- Check owner/permissions of all parts of path
Fatal error: unusable configuration
0.010207 Driver failed to start (exit status=1)
[root@host-242 ~]# systemctl status nut-monitor
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled)
Active: failed (Result: exit-code) since Сб 2015-01-17 05:26:13 MSK; 4 days ago
Main PID: 2387 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nut-monitor.service
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Using power down flag file /etc/killpower
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Network UPS Tools upsmon 2.6.5
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Fatal error: insufficient power configured!
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Sum of power values........: 0
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Minimum value (MINSUPPLIES): 1
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Edit your upsmon.conf and change the values.
[root@host-242 ~]# cat /etc/nut/ups.conf | grep -v ^#
[5]
driver = blazer_ser
desc = "Powercom BNT-600AP"
port = auto
[root@host-242 ~]#
Записан
Can’t chdir to /var/lib/upsd: Permission denied
ls -l /var/lib/upsd
Записан
Я описался, а потом исправил в имени драйвера.
« Последнее редактирование: 21.01.2015 22:37:41 от ruslandh »
Записан
Всо равно не пашет
[root@host-242 ~]# ls -l /var/lib/upsd
lrwxrwxrwx 1 root root 16 янв 16 14:13 /var/lib/upsd -> nut/var/lib/upsd
[root@host-242 ~]# cat /etc/nut/ups.conf | grep -v ^#
[5]
driver = powercom
desc = "Powercom BNT-600AP"
port = auto
[root@host-242 ~]# systemctl enable nut-monitor
[root@host-242 ~]# upsdrvctl -D start
Network UPS Tools - UPS driver controller 2.6.5
0.000000 Starting UPS: 5
Network UPS Tools - PowerCom protocol UPS driver 0.13 (2.6.5)
Unable to open auto: No such file or directory
Things to try:
- Check 'port=' in ups.conf
- Check owner/permissions of all parts of path
Fatal error: unusable configuration
0.005560 Driver failed to start (exit status=1)
[root@host-242 ~]# systemctl enable nut-monitor
[root@host-242 ~]# systemctl status nut-monitor
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled)
Active: failed (Result: exit-code) since Сб 2015-01-17 05:26:13 MSK; 5 days ago
Main PID: 2387 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nut-monitor.service
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Using power down flag file /etc/killpower
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Network UPS Tools upsmon 2.6.5
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Fatal error: insufficient power configured!
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Sum of power values........: 0
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Minimum value (MINSUPPLIES): 1
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Edit your upsmon.conf and change the values.
[root@host-242 ~]#
Куда дальше порыть?
Записан
[nutdev1]у меня вот так работает. Может вам ковычки прописать?
driver = "blazer_usb"
port = "auto"
vendorid = "0665"
productid = "5161"
product = "USB to Serial"
serial = "20100826"
vendor = "INNO TECH"
# bus = "001"
Записан
Может вам ковычки прописать?
Кавычки не влияют
[root@host-242 ~]# upsdrvctl -D start
Network UPS Tools - UPS driver controller 2.6.5
0.000000 Starting UPS: 5
Network UPS Tools - Generic HID driver 0.37 (2.6.5)
USB communication driver 0.31
Using subdriver: PowerCOM HID 0.3
Can't chdir to /var/lib/upsd: Permission denied
0.275088 Driver failed to start (exit status=1)
[root@host-242 ~]# systemctl enable nut-monitor
[root@host-242 ~]# systemctl status nut-monitor
nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled)
Active: failed (Result: exit-code) since Сб 2015-01-17 05:26:13 MSK; 5 days ago
Main PID: 2387 (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nut-monitor.service
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Using power down flag file /etc/killpower
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Network UPS Tools upsmon 2.6.5
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Fatal error: insufficient power configured!
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Sum of power values........: 0
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Minimum value (MINSUPPLIES): 1
янв 17 05:26:14 host-242.localdomain upsmon[2387]: Edit your upsmon.conf and change the values.
[root@host-242 ~]# cat /etc/nut/ups.conf | grep -v ^#
[5]
driver = "usbhid-ups"
desc = "Powercom BNT-600AP"
port = "auto"
[root@host-242 ~]#
а с вендорами, даже не знаю стоит пробовать, там такая каша:
[root@host-242 ~]# lsusb -v | grep -A50 0d9f:00a6Ни в одном мануле не видел чтоб их прописывали.
Bus 001 Device 003: ID 0d9f:00a6 Powercom Co., Ltd Black Knight PRO Uninterruptible Power Supply (HID PDC)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0d9f Powercom Co., Ltd
idProduct 0x00a6 Black Knight PRO Uninterruptible Power Supply (HID PDC)
bcdDevice 0.01
iManufacturer 3 POWERCOM Co.,Ltd
iProduct 1 UPS BNT--600AP FW4.A6
iSerial 2 4A6-0000-0001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 726
Report Descriptor: (length is 726)
Item(Global): Usage Page, data= [ 0x84 ] 132
Power Device Page
Item(Local ): Usage, data= [ 0x04 ] 4
UPS
Item(Main ): Collection, data= [ 0x01 ] 1
[root@host-242 ~]#
А вам, зачем понадобилось вендоры и сериалы прописывать? Без них совсем не работало? Или какую-то спецфичу реализовывали?
Записан
/var/lib/upsd: Permission denied — так вы и не показали
ls -l /var/lib/upsd:
А вам, зачем понадобилось вендоры и сериалы прописывать? Без них совсем не работало? Или какую-то спецфичу реализовывали?
Я давно это настраивал, и насколько я помню, скриптом (который шёл с УПС), а не сам.
PS А попробуйте apcupsd — он практически не требует настройки.
Записан
/var/lib/upsd: Permission denied — так вы и не показали
ls -l /var/lib/upsd:
[root@host-242 ~]# ls -l /var/lib/upsd
lrwxrwxrwx 1 root root 16 янв 16 14:13 /var/lib/upsd -> nut/var/lib/upsd
[root@host-242 ~]#
PS А попробуйте apcupsd — он практически не требует настройки.
вроде что-то заработало! Пикнуло спикером и матюкнулось в консоле ни с того ни с сего, что связь теряется.
[root@host-242 ~]#
Broadcast message from root@host-242.localdomain (2015-01-22 22:52:45):
Warning communications lost with UPS
[root@host-242 ~]#
Подскажите как с ним поупражнятся дальше? Чтоб работоспособность проверить? Я как понял nut-монитор не для него? Управлять только через конфиг?
P.S. свой адрес в конфиге я прописал /dev/usb/hiddev0
« Последнее редактирование: 22.01.2015 23:02:54 от МИНЗДРАВ »
Записан
А, нашёл gapcmon его реально русским сделать? Не пойму заработал он.
Спасибо Сэнсэй!
Записан
нет. не пахает
2015-01-22 23:03:14 +0300 apcupsd error shutdown completedЧто-то нужно подправить. Подскажите что?
and that your cable specification on the UPSCABLE directive is correct.
Please make sure the port specified on the DEVICE directive is correct,
PANIC! Cannot communicate with UPS via serial port.
Записан
[email protected]:~# lsusb -v -d 0001:0000
Bus 004 Device 002: ID 0001:0000 Fry’s Electronics MEC0003
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0001 Fry’s Electronics
idProduct 0x0000
bcdDevice 1.00
iManufacturer 0
iProduct 1 MEC0003
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 624
Report Descriptor: (length is 624)
Item(Global): Usage Page, data= [ 0x86 ] 134
Power Pages
Item(Local 😞 Usage, data= [ 0x04 ] 4
(null)
Item(Main 😞 Collection, data= [ 0x01 ] 1
Application
Item(Global): Usage Page, data= [ 0x84 ] 132
Power Device Page
Item(Local 😞 Usage, data= [ 0x1e ] 30
Flow
Item(Main 😞 Collection, data= [ 0x00 ] 0
Physical
Item(Global): Report ID, data= [ 0x01 ] 1
Item(Local 😞 Usage, data= [ 0x1f ] 31
Flow ID
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x0f ] 15
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Feature, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x40 ] 64
Config Voltage
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x07 ] 7
Unit Exponent: 7
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfa 0x00 ] 250
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x42 ] 66
Config Frequency
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0xf0 ] 61441
System: SI Linear, Unit: Seconds^-1
Item(Global): Unit Exponent, data= [ 0x00 ] 0
Unit Exponent: 0
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x3c ] 60
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x53 ] 83
Low Voltage Transfer
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x07 ] 7
Unit Exponent: 7
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfa 0x00 ] 250
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x54 ] 84
High Voltage Transfer
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x07 ] 7
Unit Exponent: 7
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfa 0x00 ] 250
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0xfd ] 253
iManufacturer
Item(Local 😞 Usage, data= [ 0xfe ] 254
iProduct
Item(Local 😞 Usage, data= [ 0xff ] 255
iSerialNumber
Item(Global): Report Size, data= [ 0x08 ] 8
Item(Global): Report Count, data= [ 0x03 ] 3
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Feature, data= [ 0x00 ] 0
Data Array Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Global): Usage Page, data= [ 0x84 ] 132
Power Device Page
Item(Local 😞 Usage, data= [ 0x1e ] 30
Flow
Item(Main 😞 Collection, data= [ 0x00 ] 0
Physical
Item(Global): Report ID, data= [ 0x02 ] 2
Item(Local 😞 Usage, data= [ 0x1f ] 31
Flow ID
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x0f ] 15
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Main 😞 Feature, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x40 ] 64
Config Voltage
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x07 ] 7
Unit Exponent: 7
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfa 0x00 ] 250
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x42 ] 66
Config Frequency
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0xf0 ] 61441
System: SI Linear, Unit: Seconds^-1
Item(Global): Unit Exponent, data= [ 0x00 ] 0
Unit Exponent: 0
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x3c ] 60
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x43 ] 67
Config Apparent Power
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 ] 53537
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3
Item(Global): Unit Exponent, data= [ 0x07 ] 7
Unit Exponent: 7
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x44 ] 68
Config Active Power
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Unit, data= [ 0x21 0xd1 ] 53537
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3
Item(Global): Unit Exponent, data= [ 0x07 ] 7
Unit Exponent: 7
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x56 ] 86
Delay Before Startup
Item(Global): Report Size, data= [ 0x18 ] 24
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0x10 ] 4097
System: SI Linear, Unit: Seconds
Item(Global): Unit Exponent, data= [ 0x00 ] 0
Unit Exponent: 0
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x57 ] 87
Delay Before Shutdown
Item(Global): Report Size, data= [ 0x18 ] 24
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0x10 ] 4097
System: SI Linear, Unit: Seconds
Item(Global): Unit Exponent, data= [ 0x00 ] 0
Unit Exponent: 0
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Global): Usage Page, data= [ 0x84 ] 132
Power Device Page
Item(Local 😞 Usage, data= [ 0x10 ] 16
Battery System
Item(Main 😞 Collection, data= [ 0x00 ] 0
Physical
Item(Global): Report ID, data= [ 0x03 ] 3
Item(Local 😞 Usage, data= [ 0x11 ] 17
Battery System ID
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x0f ] 15
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Feature, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x02 ] 2
Present Status
Item(Main 😞 Collection, data= [ 0x02 ] 2
Logical
Item(Local 😞 Usage, data= [ 0x6d ] 109
Used
Item(Local 😞 Usage, data= [ 0x61 ] 97
Good
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x02 ] 2
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x06 ] 6
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Feature, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Local 😞 Usage, data= [ 0x30 ] 48
Voltage
Item(Global): Report Size, data= [ 0x18 ] 24
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x05 ] 5
Unit Exponent: 5
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x36 ] 54
Temperature
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0x00 0x01 0x00 ] 65537
System: SI Linear, Unit: Kelvin
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x58 ] 88
Test
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x06 ] 6
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x02 ] 2
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Input, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x58 ] 88
Test
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x04 ] 4
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Main 😞 Feature, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Feature, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Global): Usage Page, data= [ 0x84 ] 132
Power Device Page
Item(Local 😞 Usage, data= [ 0x16 ] 22
Power Converter
Item(Main 😞 Collection, data= [ 0x00 ] 0
Physical
Item(Global): Report ID, data= [ 0x04 ] 4
Item(Local 😞 Usage, data= [ 0x17 ] 23
Power Converter ID
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x0f ] 15
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Input, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x1a ] 26
Input
Item(Main 😞 Collection, data= [ 0x00 ] 0
Physical
Item(Local 😞 Usage, data= [ 0x1b ] 27
Input ID
Item(Local 😞 Usage, data= [ 0x1f ] 31
Flow ID
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x02 ] 2
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x0f ] 15
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x02 ] 2
Present Status
Item(Main 😞 Collection, data= [ 0x02 ] 2
Logical
Item(Local 😞 Usage, data= [ 0x61 ] 97
Good
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x07 ] 7
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Input, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Local 😞 Usage, data= [ 0x30 ] 48
Voltage
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x05 ] 5
Unit Exponent: 5
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x32 ] 50
Frequency
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0xf0 ] 61441
System: SI Linear, Unit: Seconds^-1
Item(Global): Unit Exponent, data= [ 0x05 ] 5
Unit Exponent: 5
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Local 😞 Usage, data= [ 0x1c ] 28
Output
Item(Main 😞 Collection, data= [ 0x00 ] 0
Physical
Item(Global): Report ID, data= [ 0x05 ] 5
Item(Local 😞 Usage, data= [ 0x1d ] 29
Output ID
Item(Local 😞 Usage, data= [ 0x1f ] 31
Flow ID
Item(Global): Report Size, data= [ 0x04 ] 4
Item(Global): Report Count, data= [ 0x02 ] 2
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x0f ] 15
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x30 ] 48
Voltage
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x21 0xd1 0xf0 0x00 ] 15782177
System: SI Linear, Unit: Centimeter^2*Gram*Seconds^-3*Ampere^-1
Item(Global): Unit Exponent, data= [ 0x05 ] 5
Unit Exponent: 5
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x32 ] 50
Frequency
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x01 0xf0 ] 61441
System: SI Linear, Unit: Seconds^-1
Item(Global): Unit Exponent, data= [ 0x05 ] 5
Unit Exponent: 5
Item(Global): Logical Maximum, data= [ 0xfe 0xff 0x00 0x00 ] 65534
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x35 ] 53
Percent Load
Item(Global): Report Size, data= [ 0x10 ] 16
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Local 😞 Usage, data= [ 0x02 ] 2
Present Status
Item(Main 😞 Collection, data= [ 0x02 ] 2
Logical
Item(Local 😞 Usage, data= [ 0x65 ] 101
Overload
Item(Local 😞 Usage, data= [ 0x6e ] 110
Boost
Item(Local 😞 Usage, data= [ 0x6f ] 111
Buck
Item(Global): Report Size, data= [ 0x01 ] 1
Item(Global): Report Count, data= [ 0x03 ] 3
Item(Global): Logical Minimum, data= [ 0x00 ] 0
Item(Global): Logical Maximum, data= [ 0x01 ] 1
Item(Global): Unit, data= [ 0x00 ] 0
System: None, Unit: (None)
Item(Main 😞 Input, data= [ 0x02 ] 2
Data Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Global): Report Size, data= [ 0x05 ] 5
Item(Global): Report Count, data= [ 0x01 ] 1
Item(Main 😞 Input, data= [ 0x03 ] 3
Constant Variable Absolute No_Wrap Linear
Preferred_State No_Null_Position Non_Volatile Bitfield
Item(Main 😞 End Collection, data=none
Item(Main 😞 End Collection, data=none
Item(Main 😞 End Collection, data=none
Item(Main 😞 End Collection, data=none
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
can’t get device qualifier: Resource temporarily unavailable
can’t get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
|
Description of problem:
service ups start starts three daemons, all of which have problems:
/sbin/$MODEL (as set in /etc/sysconfig/ups) can't read /dev/ttyS0 as it runs as
nobody, and ttyS0 is owned by root and group-owned by uucp. This is a problem,
and "chown nobody /dev/ttyS0" helps, but doesn't seem like the right thing to do.
The next daemon /usr/sbin/upsd looks for a non-existant /etc/ups/ups.conf, and
refuses to run after not finding it. We need to fix this with at least an
example config file.
Last, the /usr/sbin/upsmon daemon won't start at all, becuase it can't find the
upsd daemon running. This should be fixed when problem #2 is fixed.
Version-Release number of selected component (if applicable):
8.0 with all updates as of 02/10/2003
How reproducible:
Steps to Reproduce:
1. change MODEL=none to MODEL=apcsmart in /etc/sysconfig/ups
2. "service ups start"
Actual results:
Starting apcsmart: Network UPS Tools - APC Smart protocol driver 0.60 (0.45.4)
This program is currently running as nobody (UID 99)
/dev/ttyS0 is owned by user root (UID 0), mode 0660
Change the port name, or fix the permissions or ownership
of /dev/ttyS0 and try again.
Unable to open /dev/ttyS0: Permission denied
[FAILED]
Starting upsd: Network UPS Tools upsd 0.45.4
/var/lib/ups is world readable
Warning: no UPS definitions in ups.conf
Fatal error: you need to define at least one UPS in your ups.conf!
[FAILED]
Starting UPS monitor (master): Network UPS Tools upsmon 0.45.4
Fatal error: insufficient power configured!
Sum of power values........: 0
Minimum value (MINSUPPLIES): 1
Edit your upsmon.conf and change the values.
Using power down flag file /etc/killpower
[FAILED]
Expected Results:
A lot different ;-)
Being able to read /dev/ttyS0 (as user "nobody") is still a problem in pre-beta5 for Phoebe. Also, while /etc/ups.conf now exists, upsd still complains that "/var/lib/ups is world readable". Please fix!
1.2.0-5 should fix all this problem. Please test it again, thanks.
I still get this error with version 1.2.0-5: /var/lib/ups is world readable
1.2.0-6 should fix this problem. Could you please try again. Thanks |
| tags: | added: systemd-boot |
Revision history for this message
Hello,
Could you please specify the version you are using and paste the output of journalctl -xn here?
| Changed in nut (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
> Could you please specify the version you are using
Kubuntu 14.04 x86_64 and NUT 2.7.1 from repository.
systemd from ppa:pitti/systemd
> and paste the output of journalctl -xn
Looks like there is typical complain about not filled configs, however with upstart not filled configs doesn’t lead to half-installed package («not configured» state).
— Logs begin at Sun 2014-04-27 10:29:05 CEST, end at Sun 2014-04-27 10:43:09 CEST. —
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 upsmon[2856]: Fatal error: insufficient power configured!
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 upsmon[2856]: Sum of power values……..: 0
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 upsmon[2856]: Minimum value (MINSUPPLIES): 1
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 upsmon[2856]: Edit your upsmon.conf and change the values.
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 systemd[1]: nut-monitor.service: control process exited, code=exited status=1
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 systemd[1]: Failed to start Network UPS Tools — power device monitor and shutdown controller.
— Subject: Unit nut-monitor.service has failed
— Defined-By: systemd
— Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
— Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
—
— Unit nut-monitor.service has failed.
—
— The result is failed.
Apr 27 10:41:43 user-Standard-PC-i440FX-PIIX-1996 systemd[1]: Unit nut-monitor.service entered failed state.
Apr 27 10:41:46 user-Standard-PC-i440FX-PIIX-1996 sudo[2595]: pam_unix(sudo:session): session closed for user root
Apr 27 10:43:09 user-Standard-PC-i440FX-PIIX-1996 sudo[2902]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/bin/journalctl -xn
Apr 27 10:43:09 user-Standard-PC-i440FX-PIIX-1996 sudo[2902]: pam_unix(sudo:session): session opened for user root by user(uid=0)
Revision history for this message
I confirm this on a clean utopic install (unconfigured nut, no UPSes available)
| Changed in nut (Ubuntu): | |
| status: | Incomplete → Triaged |
| summary: |
— [systemd] nut-client can not be installed + [systemd] nut-client systemd unit fails when unconfigured |
| Changed in nut (Ubuntu): | |
| status: | Triaged → Fix Committed |
| assignee: | nobody → Martin Pitt (pitti) |
Revision history for this message
This bug was fixed in the package nut — 2.7.1-1ubuntu2
—————
nut (2.7.1-1ubuntu2) utopic; urgency=medium
* Disable systemd unit; it does not check nut.conf whether nut is
configured, and thus fails to start (and the package install). The init.d
script works well enough for the time being. (LP: #1313231)
— Martin Pitt <email address hidden> Mon, 12 May 2014 13:22:12 +0200
| Changed in nut (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in nut (Debian): | |
| status: | Unknown → New |
| Changed in nut (Debian): | |
| status: | New → Confirmed |
| Changed in nut (Debian): | |
| status: | Confirmed → Fix Released |
| Changed in nut (Debian): | |
| status: | Fix Released → Confirmed |
| Changed in nut (Debian): | |
| status: | Confirmed → Fix Released |
| Changed in nut (Debian): | |
| status: | Fix Released → Confirmed |
| Changed in nut (Debian): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
Reply or subscribe to this bug.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, kurko2000@gmail.com, Arnaud Quette <aquette@debian.org>:
Bug#931811; Package nut-client.
(Wed, 10 Jul 2019 18:33:04 GMT) (full text, mbox, link).
Acknowledgement sent
to johan <kurko2000@gmail.com>:
New Bug report received and forwarded. Copy sent to kurko2000@gmail.com, Arnaud Quette <aquette@debian.org>.
(Wed, 10 Jul 2019 18:33:04 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: nut-client Version: 2.7.4-8 Severity: minor Dear Maintainer, When upgrading the system from Stretch to Buster, the final stage of updating nut-client failed. The output is shown below. As a workaround, I set MINSUPPLIES = 0 in /etc/nut/upsmon.conf which solved the problem. After upgrade, upsmon (nut-monitor.service) was enabled and running even though I had explicitly disabled it when I originally installed nut. Setting up nut-client (2.7.4-8) ... Job for nut-monitor.service failed because the control process exited with error code. See "systemctl status nut-monitor.service" and "journalctl -xe" for details. invoke-rc.d: initscript nut-client, action "restart" failed. ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-07-09 23:05:52 EEST; 9ms ago Process: 6207 ExecStart=/sbin/upsmon (code=exited, status=1/FAILURE) july 09 23:05:52 hostname upsmon[6207]: fopen /var/run/nut/upsmon.pid: No such file or directory july 09 23:05:52 hostname upsmon[6207]: Using power down flag file /etc/killpower july 09 23:05:52 hostname upsmon[6207]: Network UPS Tools upsmon 2.7.4 july 09 23:05:52 hostname upsmon[6207]: Fatal error: insufficient power configured! july 09 23:05:52 hostname upsmon[6207]: Sum of power values........: 0 july 09 23:05:52 hostname upsmon[6207]: Minimum value (MINSUPPLIES): 1 july 09 23:05:52 hostname upsmon[6207]: Edit your upsmon.conf and change the values. july 09 23:05:52 hostname systemd[1]: nut-monitor.service: Control process exited, code=exited, status=1/FAILURE july 09 23:05:52 hostname systemd[1]: nut-monitor.service: Failed with result 'exit-code'. july 09 23:05:52 hostname systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller. dpkg: error processing package nut-client (--configure): installed nut-client package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of nut: nut depends on nut-client; however: Package nut-client is not configured yet. dpkg: error processing package nut (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nut-server: nut-server depends on nut-client (= 2.7.4-8); however: Package nut-client is not configured yet. dpkg: error processing package nut-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: nut-client nut nut-server E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nut-client depends on: ii adduser 3.118 ii libc6 2.28-10 ii libupsclient4 2.7.4-8 ii lsb-base 10.2019051400 Versions of packages nut-client recommends: ii bash-completion 1:2.8-6 Versions of packages nut-client suggests: pn nut-monitor <none> -- Configuration Files: /etc/nut/nut.conf [Errno 13] Lupa evätty: '/etc/nut/nut.conf' /etc/nut/upsmon.conf [Errno 13] Lupa evätty: '/etc/nut/upsmon.conf' /etc/nut/upssched.conf [Errno 13] Lupa evätty: '/etc/nut/upssched.conf' -- no debconf information
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Feb 9 16:41:11 2023;
Machine Name:
bembo
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.