dadarara

have CUPS working very well how about SCANNER on the network anyone knows if there is a docker for this? How would it coexist with CUPS ? thanks

have 6.4 installed the FCP initiated first scan the system FROZE !! only option was hard reset after reboot it looked as if the plugin was not installed at all. any particular history with such occurrences ? P.S. dont know how the diagnostics will help, as they are obviously after the fact and also I upgraded to 6.4.1 - didnt test it yet with this version tower-diagnostics-20180222-0833.zip

thanks, sounds great will try tomorrow.

thanks dmacias I will need to check if I have such settings in the bios of my supermicro board. I have my USB3 controllers passed through to my kids Gaming VMs. So I dont know if this is the right path for me.

the setup is very standard. both UPS and Bluetooth dongle ? not likely. maybe under the unRAID with passthrough to VM its more sensitive ? dont know changed ports -> same thing

actually I notice something . the reset is affecting ONLY the bluetooth and the UPS . you can see the Device # is getting sequentially increased numbering (now it 14 and 13) all the other USB devices stay the same

I didnt try. I was afraid to break it... sometimes when I reboot the UPS is not recognized and there is no connection. I need to reboot again. I think there is some timing issue when the UPS is expecting a response from the driver and not getting it. So there is a "miscommunication" happens. right now its blazer_usb driver. P.S I have the x9dai supermicro board and although the chipset has 2 USB2 controllers on it, they designed it in such a way that ALL the usb ports are connected via one controller only. so when it is getting a reset, all the usb devices are getting a reset. even the USB flash I am booting from is on it as well. so I am happy that it does not affect the overall server. it just disables the keyboard and mouse I have on the bluetooth dongle passed through to OSX VM. unless I can solve this reset problem , i will need to get a PCI USB controller Bus 1 --> 0000:00:1a.0 (IOMMU group 9)Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching HubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 2 --> 0000:00:1d.0 (IOMMU group 14)Bus 002 Device 014: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0Bus 002 Device 005: ID 0781:5567 SanDisk Corp. Cruzer BladeBus 002 Device 013: ID 0665:5161 Cypress Semiconductor USB to SerialBus 002 Device 003: ID 03f0:8c11 Hewlett-Packard Deskjet F4500 seriesBus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching HubBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

guys I am experiencing a problem. the USB device the UPS is connected to is resetting occasionally. see bellow. it seams that the reset is affecting the controller and all the USB devices on it are disconnecting. what can I do ? whats the reason for it? is it intentional or a bug? how can I investigate what it is? Dec 18 19:49:07 Tower kernel: usb 2-1.2: reset low-speed USB device number 11 using ehci-pci Dec 18 19:49:13 Tower kernel: usb 2-1.2: USB disconnect, device number 11 Dec 18 19:49:13 Tower kernel: usb 2-1.2: new low-speed USB device number 13 using ehci-pci Dec 18 19:49:13 Tower kernel: hid-generic 0003:0665:5161.0007: hiddev0,hidraw0: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0

Thank you GOD I was under the impression that the program is updating itself all the time from the Git... not the whole container. re UPS, its really a shame, maybe "running under a specific Docker user ..." solution will also help in this matter. Thanks for the info.

anyone, please?

how do I update the netdata ? its not autoupdating. how to actually install a plugin ? (looking to show UPS data)

how do I update the netdata ? its not autoupdating. how to actually install a plugin ? (looking to show UPS data)

how do I update the netdata ? its not autoupdating. how to actually install a plugin ? (looking to show UPS data)

amazing I have no clear idea what I did , but now it is working. restarted, reconfigured... my FSP FP1000 UPS is configured with Blazer_usb. ups.conf: [ups] driver = blazer_usb port = auto vendor = "INNO TECH" bus = "002" upsmon.conf: MONITOR [email protected] 1 monuser monpass master SHUTDOWNCMD "/sbin/poweroff" POWERDOWNFLAG /etc/nut/no_killpower NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYCMD "/usr/sbin/nut-notify" Key Value Key Value battery.charge 100 battery.voltage 27.10 battery.voltage.high 26.00 battery.voltage.low 20.80 battery.voltage.nominal 24.0 device.type ups driver.name blazer_usb driver.parameter.bus 002 driver.parameter.pollinterval 2 driver.parameter.port auto driver.parameter.synchronous no driver.parameter.vendor INNO TECH driver.version 2.7.4 driver.version.internal 0.12 input.current.nominal 5.0 input.frequency 50.0 input.frequency.nominal 50 input.voltage 230.8 input.voltage.fault 230.8 input.voltage.nominal 220 output.voltage 230.8 ups.beeper.status enabled ups.delay.shutdown 30 ups.delay.start 180 ups.load 33 ups.productid 5161 ups.status Online ups.type offline / line interactive ups.vendorid 0665

hi bellow is the output but I think there is currently a problem in the system. it started only a few hours ago. something to do with all the back and forth I am doing with the system. the messages run all the time while the UPS is connected to the USB port... Dec 7 10:07:28 Tower kernel: usb 2-1.2: USB disconnect, device number 123 Dec 7 10:07:29 Tower kernel: usb 2-1.2: new low-speed USB device number 124 using ehci-pci Dec 7 10:07:30 Tower kernel: hid-generic 0003:0665:5161.0730: hiddev0,hidraw0: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0 Dec 7 10:07:39 Tower kernel: usb 2-1.2: USB disconnect, device number 124 Dec 7 10:07:41 Tower kernel: usb 2-1.2: new low-speed USB device number 125 using ehci-pci Dec 7 10:07:41 Tower kernel: hid-generic 0003:0665:5161.0731: hiddev0,hidraw0: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0 after I configured as suggested, the messages are now diffrent Dec 7 10:09:17 Tower upsmon[10803]: UPS [[email protected]]: connect failed: Connection failure: Connection refused d# /etc/rc.d/rc.nut start Writing nut config Updating permissions... Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic Q* USB/Serial driver 0.28 (2.7.4) USB communication driver 0.33 Using protocol: Voltronic-QS 0.07 No values for battery high/low voltages Using 'guesstimation' (low: 20.800000, high: 26.000000)! Battery runtime will not be calculated (runtimecal not set) nut upsd is running... Network UPS Tools upsmon 2.7.4 fopen /var/run/nut/upsmon.pid: No such file or directory UPS: [email protected] (master) (power value 1) Using power down flag file /etc/nut/no_killpower Broadcast message from root@Tower (somewhere) (Thu Dec 7 10:07:47 2017): Communications with UPS [email protected] lost Broadcast message from root@Tower (somewhere) (Thu Dec 7 10:07:52 2017): UPS [email protected] is unavailable

found this: http://www.evilbox.ro/linux/how-to-monitor-mustek-powermust-2012-ups-with-ubuntu-server-14/ how can it help? You may receive the error message below : 1 2 3 Can't claim USB device [0665:5161]: could not detach kernel driver from interface 0: Operation not permitted Driver failed to start (exit status=1) This means that there is a problem with permissions, so we need to set the permission and then reboot. Set permissions for UPS, remember the descriptor noted above, 0665:5161 in my case: root@erp:/# nano /etc/udev/rules.d/10-must-pa-2012.rules Add the line : 1 SYSFS{idVendor}=='0665', SYSFS{idProduct}=='5161', MODE='0666'

I assumed I need to choose Manual config ? otherwise the ups.conf is overwritten. in any case it didnt work. both changes I get : Dec 6 22:52:11 Tower upsmon[22300]: UPS [[email protected]]: connect failed: Connection failure: Connection refused BTW in the upsd.conf I have listen 0.0.0.0 is it ok? digging and googling , I have seen someone suggesting to use subdriver definition ?!?! phoenix, ippon,krauler. dont know if makes sense and how to do it

guys bought a new UPS FSP FP1000. I dont know what I am doing actually. what needs to be the configuration ? I didnt do any changes in the conf files. should I ? nut-scanner shows: Neon library not found. XML search disabled. Scanning USB bus. No start IP, skipping SNMP No start IP, skipping NUT bus (old connect method) [nutdev1] driver = "nutdrv_qx" port = "auto" vendorid = "0665" productid = "5161" product = "USB to Serial" vendor = "INNO TECH" bus = "002" when I set the type to Blazer_usb the driver starts but shows errors. Dec 6 21:44:43 Tower upsmon[4274]: UPS [[email protected]]: connect failed: Connection failure: Connection refused root@Tower:~# /etc/rc.d/rc.nut start Writing nut config Updating permissions... Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4) Supported UPS detected with mustek protocol Vendor information unavailable No values provided for battery high/low voltages in ups.conf Using 'guestimation' (low: 20.800000, high: 26.000000)! Battery runtime will not be calculated (runtimecal not set) nut upsd is running... Network UPS Tools upsmon 2.7.4 fopen /var/run/nut/upsmon.pid: No such file or directory UPS: [email protected] (master) (power value 1) Using power down flag file /etc/nut/no_killpower Broadcast message from root@Tower (somewhere) (Wed Dec 6 21:43:48 2017): Communications with UPS [email protected] lost Broadcast message from root@Tower (somewhere) (Wed Dec 6 21:43:53 2017): UPS [email protected] is unavailable

I have posted before about the issue of the version upgrade that came up due to the problem of backing up to the central.. since then, it started to work again, but now it has an issue once more. (says the files are being maintained...) the support guys at crashplan say I need to make sure I a running on the latest version (4.8.3 for HOME) I see in the logs that it did upgrade to 4.8.3 at some point. but after a few restarts, it reverted to the 4.8.0. I did not update the DOCKER image. so why does it do that? what is the way to force the application to update itself? I can make an upgrade via the linux command prompt, but the upgrade script is asking locations for backups and I am afraid to make any changes so not to totally destroy the installation. so any ideas? how to force the upgrade? or what are the instructions I need to give to the crashplan install.sh script running manual upgrade?

do people have the version 4.8.3 updated ? (these who did not move to business....) I dont see anything in the history tab though I might miss is. there are no RED error lines. hard to see. cant copy this history msg list. which log files can I look at? in any case. can I update manually ?

Please advise ? How to upgrade the 4.8.0 version in the docker to the 4.8.3 Home version ? I have downloaded the CrashPlan_4.8.3_Linux.tgz file. I can copy it to the docker via SSH/Hash access can I simply uninstall the old versiona and install the new ? will I lose all the configuration ? will I need to adopt backups etc... Uncompress the TGZ file to Downloads. Open Terminal and enter: cd ~/Downloads/crashplan-install Press Enter. Then enter: sudo ./uninstall.sh -i /usr/local/crashplan Press Enter. At the prompt, type YES to uninstall and press Enter. Install latest copy Make sure you are in the crashplan-install folder in terminal Then enter: sudo ./install.sh Press Enter. I have my subscription expire in one year, so I am staying with what I have for now. But recently I see the CP only synchronizing the data to the cloud without actually backing. it already 6 days without backup and I get notifications about it. So the CP support advised to upgrade to the 4.8.3 version. thanks

all left as is. no, dont have conf file. also tried to make manual config. also didnt work what should I do with the config editor? I chose ups.conf while starting up the plugin. not clear how it should work really in the log I have: see the change after I chose the manual config. no diff... BTW, it sounds strange that it tries to address the localhost as this UPS is not connected to network. only USB. ErrorWarningSystemArrayLogin Sep 21 13:28:15 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:20 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:25 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:30 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:35 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:40 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:45 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:50 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:28:55 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:00 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:05 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:10 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:15 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:20 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:25 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:30 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:35 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:40 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:45 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:50 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:29:55 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:30:00 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:30:05 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:30:10 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:30:15 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:30:19 Tower php: /usr/local/emhttp/plugins/nut/scripts/stop Sep 21 13:30:20 Tower upsmon[21015]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:30:21 Tower upsmon[21015]: Signal 15: exiting Sep 21 13:30:21 Tower upsmon[21014]: upsmon parent: read Sep 21 13:30:23 Tower usbhid-ups[20999]: Signal 15: exiting Sep 21 13:37:09 Tower php: /usr/local/emhttp/plugins/nut/scripts/start Sep 21 13:37:14 Tower usbhid-ups[11551]: Startup successful Sep 21 13:37:15 Tower upsmon[11570]: Startup successful Sep 21 13:37:15 Tower upsmon[11571]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:37:15 Tower upsmon[11571]: Communications with UPS ups@localhost lost Sep 21 13:37:20 Tower upsmon[11571]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:37:20 Tower upsmon[11571]: UPS ups@localhost is unavailable Sep 21 13:37:25 Tower upsmon[11571]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:37:30 Tower upsmon[11571]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused Sep 21 13:37:35 Tower upsmon[11571]: UPS [ups@localhost]: connect failed: Connection failure: Connection refused

deleted the old Plugin and installed new. now its not working. have old UPS. the driver I used before is upbhid-ups no IPs, no user names . it just worked. Scanning for UPS...Scanning USB bus.Scanning NUT bus (avahi method).[nutdev1]driver = "usbhid-ups"port = "auto"vendorid = "0D9F"productid = "0001"bus = "002" so now what ?

Hi all thanks for the comments. the board is about 2m above my desk. so no one is touching. in principle there is no problem to touch any of the electronic parts as they are coated with protective lacquer (usually). the problem might be "the fingers in the fans" though and touching the pci connector pins . anyhow, the biggest problem is to blow air on it once a day or two to clean the dust away. truthfully I forget sometimes. But to compare to a closed case, there is actually less dust. In the closed case the fans suck it in and it accumulates there. on an open board like mine, it doesnt. Regarding the GTX1070 I have. well its RMA. had to send it to California USA for replacement. But it turned even to a longer story when the UPS lost the newly sent card. So now I am in negotiations with Gigabyte ...

Thanks appreciate your comment