dadarara

installed clean server v6.4. precleared all the HDs before using created new VMs and also used some existing vdisk files. it was running for 2 days now was in the middle of using Krusader comparing some directories, when was hit by a call trace. one of the VMs (OSX Sierra) crashed. others are ok. hope someone can look into this. thanks tower-diagnostics-20180130-1458.zip

?

is there any plugin or docker to quickly and visually show the assignment of CPU cores between the VMs and dockers ? I mean I am assigning the cores in the XML to be used in VMs and I have multiple VMs, some active all the time and some not. I am looking to have a screen to see how the cores are assigned between the VMs so that if I am doing some changes I am not overlapping the configuration and mixing between the VMs

what are the ways to check disk corruptions pls? I have XFS on data disks and BTRFS on the cache.

please help me to understand what this is I think its related to "fix common problems" addon. the diagnostics was run before getting the call traces. after the error, it was impossible to run the diagnostics. syslog 13Jan18.rtf tower-diagnostics-20180113-1749.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?

I have moved the CA backup to run at 12PM. the crashes stopped for now. what does this mean? if its only in my server, than so be it. but if its some bug than maybe need to investigate ?

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)

anyone? BTW I did run MEMtest. it passed ok one pass (long one) and as it happens once a day at night around 3am my time, it doesn't look to me as a hardware problem that can occur anytime.

how do i do that? whats the correct commands pls? not very experienced linux user...

I am having crashes every night. (didnt post the the 7th) please please help. attached is the Fix Common Problems log bellow is the syslog window I left open, that shows even more. yesterday was the first time I have successfully installed and connected the UPS. So its strange that there are related errors. The system crashed for the last few days without the UPS. I have changed the MOVER schedule from 3am to 12pm. SO it shouldn't be related. next idea is to change the backup schedule. any other ideas ? Dec 8 00:15:34 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 12.31.20.png Dec 8 00:15:34 Tower root: .d..t...... media/Photos/2017-12-December/ Dec 8 00:15:34 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.38.25.jpg Dec 8 00:15:35 Tower root: .d..t...... media/Photos/2017-12-December/ Dec 8 00:15:35 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.38.48.jpg Dec 8 00:15:35 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.39.17.jpg Dec 8 00:15:35 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.46.32.jpg Dec 8 00:15:36 Tower root: .d..t...... media/Photos/2017-12-December/ Dec 8 00:15:36 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.47.05.jpg Dec 8 00:15:36 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.47.45.jpg Dec 8 00:15:36 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-06 19.51.09.jpg Dec 8 00:15:36 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.17.04.jpg Dec 8 00:15:37 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.22.12.jpg Dec 8 00:15:37 Tower root: .d..t...... media/Photos/2017-12-December/ Dec 8 00:15:37 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.22.17.jpg Dec 8 00:15:37 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.22.20.jpg Dec 8 00:15:37 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.22.25.jpg Dec 8 00:15:37 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.22.27.jpg Dec 8 00:15:37 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 09.22.34.jpg Dec 8 00:15:38 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 11.40.33.jpg Dec 8 00:15:38 Tower root: .d..t...... media/Photos/2017-12-December/ Dec 8 00:15:38 Tower root: >f+++++++++ media/Photos/2017-12-December/2017-12-07 11.40.45.jpg Dec 8 00:15:38 Tower root: .d..t...... media/Photos/ Dec 8 00:15:38 Tower root: .d..t...... media/ Dec 8 00:15:38 Tower move: rmdir: /mnt/cache/./media Directory not empty Dec 8 00:15:38 Tower root: mover finished Dec 8 01:00:01 Tower speedtest: Internet bandwidth test started Dec 8 01:00:02 Tower root: /mnt/cache: 258.7 GiB (277808664576 bytes) trimmed Dec 8 01:00:31 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 8 01:00:31 Tower speedtest: Ping (Lowest): 212.445 ms | Download (Max): 97.85 Mbit/s | Upload (Max): 1.81 Mbit/s Dec 8 01:00:31 Tower speedtest: Internet bandwidth test completed Dec 8 02:00:01 Tower speedtest: Internet bandwidth test started Dec 8 02:00:32 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 8 02:00:32 Tower speedtest: Ping (Lowest): 188.11 ms | Download (Max): 98.11 Mbit/s | Upload (Max): 1.84 Mbit/s Dec 8 02:00:32 Tower speedtest: Internet bandwidth test completed Dec 8 02:12:34 Tower kernel: md: recovery thread: P corrected, sector=3907515136 Dec 8 02:27:22 Tower afpd[8760]: Reconnect: invalidated child[10349] Dec 8 02:27:27 Tower afpd[12573]: afp_disconnect: primary reconnect failed Dec 8 02:27:33 Tower kernel: mdcmd (40): spindown 2 Dec 8 02:32:48 Tower root: Fix Common Problems Version 2017.11.25 Dec 8 02:32:51 Tower root: Fix Common Problems: Warning: Docker Application binhex-delugevpn has an update available for it Dec 8 02:32:51 Tower root: Fix Common Problems: Warning: Docker Application EmbyServer has an update available for it Dec 8 02:32:51 Tower root: Fix Common Problems: Warning: Docker Application nextcloud has an update available for it Dec 8 02:32:51 Tower root: Fix Common Problems: Warning: Docker Application plex has an update available for it Dec 8 02:32:54 Tower root: Fix Common Problems: Other Warning: Docker application CrashPlan has moderator comments listed ** Ignored Dec 8 02:36:01 Tower root: Fix Common Problems: Troubleshooting mode activated Dec 8 02:36:01 Tower root: Fix Common Problems: Capturing diagnostics. When uploading diagnostics to the forum, also upload /logs/FCPsyslog_tail.txt on the flash drive Dec 8 02:36:03 Tower root: Fix Common Problems Version 2017.11.25 Dec 8 02:36:04 Tower root: Fix Common Problems: /var/log currently 3 % full Dec 8 02:36:04 Tower root: Fix Common Problems: rootfs (/) currently 2 % full Dec 8 02:40:45 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Dec 8 02:40:45 Tower kernel: br0: port 3(vnet1) entered blocking state Dec 8 02:40:45 Tower kernel: br0: port 3(vnet1) entered disabled state Dec 8 02:40:45 Tower kernel: device vnet1 entered promiscuous mode Dec 8 02:40:45 Tower kernel: br0: port 3(vnet1) entered blocking state Dec 8 02:40:45 Tower kernel: br0: port 3(vnet1) entered forwarding state Dec 8 02:40:57 Tower kernel: vfio-pci 0000:00:1b.0: enabling device (0000 -> 0002) Dec 8 02:40:57 Tower kernel: vfio_ecap_init: 0000:00:1b.0 hiding ecap 0x5@0x130 Dec 8 02:40:57 Tower kernel: vfio-pci 0000:0a:02.0: enabling device (0000 -> 0002) Dec 8 02:40:57 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x19@0x900 Dec 8 02:40:59 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:41:00 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none Dec 8 02:41:00 Tower kernel: br0: port 4(vnet2) entered blocking state Dec 8 02:41:00 Tower kernel: br0: port 4(vnet2) entered disabled state Dec 8 02:41:00 Tower kernel: device vnet2 entered promiscuous mode Dec 8 02:41:00 Tower kernel: br0: port 4(vnet2) entered blocking state Dec 8 02:41:00 Tower kernel: br0: port 4(vnet2) entered forwarding state Dec 8 02:41:01 Tower kernel: vfio-pci 0000:03:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff Dec 8 02:41:01 Tower kernel: vfio-pci 0000:03:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff Dec 8 02:41:05 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:41:05 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:41:05 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:41:10 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 8 02:41:10 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 8 02:41:31 Tower kernel: vfio-pci 0000:04:00.0: enabling device (0140 -> 0143) Dec 8 02:41:31 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x19@0x270 Dec 8 02:41:31 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x1b@0x2d0 Dec 8 02:41:31 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x1e@0x370 Dec 8 02:41:35 Tower kernel: br0: port 5(vnet3) entered blocking state Dec 8 02:41:35 Tower kernel: br0: port 5(vnet3) entered disabled state Dec 8 02:41:35 Tower kernel: device vnet3 entered promiscuous mode Dec 8 02:41:35 Tower kernel: br0: port 5(vnet3) entered blocking state Dec 8 02:41:35 Tower kernel: br0: port 5(vnet3) entered forwarding state Dec 8 02:41:41 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 8 02:41:41 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 8 02:41:48 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 8 02:41:48 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 8 02:41:54 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:42:01 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:45:06 Tower emhttp: shcmd (8772): /usr/local/sbin/mover |& logger & Dec 8 02:45:06 Tower root: mover started Dec 8 02:45:06 Tower root: moving "Downloads" to array Dec 8 02:45:06 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.001 Dec 8 02:45:06 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.002 Dec 8 02:45:06 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.003 Dec 8 02:45:06 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.004 Dec 8 02:45:07 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.005 Dec 8 02:45:07 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.006 Dec 8 02:45:07 Tower move: rmdir: /mnt/cache/./Downloads/.AppleDB Directory not empty Dec 8 02:45:07 Tower move: rmdir: /mnt/cache/./Downloads Directory not empty Dec 8 02:45:07 Tower root: moving "media" to array Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/log.0000001293 Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/__db.001 Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/__db.002 Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/__db.003 Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/__db.004 Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/__db.005 Dec 8 02:45:07 Tower move: skipping file in-use: ./media/.AppleDB/__db.006 Dec 8 02:45:07 Tower move: rmdir: /mnt/cache/./media/.AppleDB Directory not empty Dec 8 02:45:07 Tower move: rmdir: /mnt/cache/./media Directory not empty Dec 8 02:45:07 Tower root: mover finished Dec 8 02:46:04 Tower root: Fix Common Problems Version 2017.11.25 Dec 8 02:46:06 Tower root: Fix Common Problems: /var/log currently 3 % full Dec 8 02:46:06 Tower root: Fix Common Problems: rootfs (/) currently 2 % full Dec 8 02:50:34 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:50:38 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:50:38 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:50:39 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:51:18 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:51:25 Tower kernel: usb 2-1.4: reset full-speed USB device number 5 using ehci-pci Dec 8 02:56:06 Tower root: Fix Common Problems Version 2017.11.25 Dec 8 02:56:08 Tower root: Fix Common Problems: /var/log currently 3 % full Dec 8 02:56:08 Tower root: Fix Common Problems: rootfs (/) currently 2 % full Dec 8 03:00:01 Tower speedtest: Internet bandwidth test started Dec 8 03:00:01 Tower CA Backup/Restore: ####################################### Dec 8 03:00:01 Tower CA Backup/Restore: Community Applications appData Backup Dec 8 03:00:01 Tower CA Backup/Restore: Applications will be unavailable during Dec 8 03:00:01 Tower CA Backup/Restore: this process. They will automatically Dec 8 03:00:01 Tower CA Backup/Restore: be restarted upon completion. Dec 8 03:00:01 Tower CA Backup/Restore: ####################################### Dec 8 03:00:01 Tower CA Backup/Restore: Stopping binhex-delugevpn Dec 8 03:00:02 Tower kernel: docker0: port 1(vethef3bc61) entered disabled state Dec 8 03:00:02 Tower kernel: vethfbed941: renamed from eth0 Dec 8 03:00:02 Tower kernel: docker0: port 1(vethef3bc61) entered disabled state Dec 8 03:00:02 Tower kernel: device vethef3bc61 left promiscuous mode Dec 8 03:00:02 Tower kernel: docker0: port 1(vethef3bc61) entered disabled state Dec 8 03:00:03 Tower CA Backup/Restore: docker stop -t 60 binhex-delugevpn Dec 8 03:00:03 Tower CA Backup/Restore: Stopping CrashPlan Dec 8 03:00:03 Tower CA Backup/Restore: docker stop -t 60 CrashPlan Dec 8 03:00:03 Tower CA Backup/Restore: Stopping EmbyServer Dec 8 03:00:08 Tower CA Backup/Restore: docker stop -t 60 EmbyServer Dec 8 03:00:08 Tower CA Backup/Restore: Stopping Netdata Dec 8 03:00:09 Tower CA Backup/Restore: docker stop -t 60 Netdata Dec 8 03:00:09 Tower CA Backup/Restore: Stopping PrinterCUPS Dec 8 03:00:09 Tower avahi-daemon[8767]: Files changed, reloading. Dec 8 03:00:09 Tower avahi-daemon[8767]: Service group file /services/AirPrint-HP_Deskjet_F4500_series.service vanished, removing services. Dec 8 03:00:09 Tower kernel: veth79783fd: renamed from eth0 Dec 8 03:00:09 Tower kernel: docker0: port 2(vethbff74b0) entered disabled state Dec 8 03:00:10 Tower kernel: docker0: port 2(vethbff74b0) entered disabled state Dec 8 03:00:10 Tower kernel: device vethbff74b0 left promiscuous mode Dec 8 03:00:10 Tower kernel: docker0: port 2(vethbff74b0) entered disabled state Dec 8 03:00:10 Tower CA Backup/Restore: docker stop -t 60 PrinterCUPS Dec 8 03:00:10 Tower CA Backup/Restore: Backing up USB Flash drive config folder to Dec 8 03:00:10 Tower CA Backup/Restore: Using command: /usr/bin/rsync -avXHq --delete --log-file="/var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log" /boot/ "/mnt/disks/WDC_WD10EAVS-00D7B0_WD-WCAU40879013/USB FLASH backup/" > /dev/null 2>&1 Dec 8 03:00:10 Tower CA Backup/Restore: Backing Up appData from /mnt/user/appdata/ to /mnt/disks/WDC_WD10EAVS-00D7B0_WD-WCAU40879013/CommunityApplicationsAppdataBackup/[email protected] Dec 8 03:00:10 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -cvaf '/mnt/disks/WDC_WD10EAVS-00D7B0_WD-WCAU40879013/CommunityApplicationsAppdataBackup/[email protected]/CA_backup.tar' --exclude 'docker.img' * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress Dec 8 03:00:12 Tower ntpd[2289]: Deleting interface #3 docker0, 172.17.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=21324 secs Dec 8 03:00:30 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 8 03:00:30 Tower speedtest: Ping (Lowest): 137.571 ms | Download (Max): 98.54 Mbit/s | Upload (Max): 1.92 Mbit/s Dec 8 03:00:30 Tower speedtest: Internet bandwidth test completed Dec 8 03:03:53 Tower upsd[7191]: Data for UPS [ups] is stale - check driver Dec 8 03:03:56 Tower upsmon[7195]: Poll UPS [[email protected]] failed - Data stale Dec 8 03:03:56 Tower upsmon[7195]: Communications with UPS [email protected] lost Dec 8 03:04:04 Tower upsd[7191]: UPS [ups] data is no longer stale Dec 8 03:04:04 Tower upsmon[7195]: Poll UPS [[email protected]] failed - Data stale Dec 8 03:04:12 Tower upsmon[7195]: Communications with UPS [email protected] established Dec 8 03:04:41 Tower upsd[7191]: Data for UPS [ups] is stale - check driver Dec 8 03:05:01 Tower upsd[7191]: UPS [ups] data is no longer stale Dec 8 03:05:20 Tower upsd[7191]: Data for UPS [ups] is stale - check driver Dec 8 03:05:59 Tower afpd[11625]: afp_alarm: child timed out, entering disconnected state Dec 8 03:05:59 Tower afpd[11629]: afp_alarm: child timed out, entering disconnected state Dec 8 03:06:02 Tower upsmon[7195]: Poll UPS [[email protected]] failed - Data stale Dec 8 03:06:02 Tower upsmon[7195]: Communications with UPS [email protected] lost Dec 8 03:06:06 Tower afpd[12573]: afp_alarm: child timed out, entering disconnected state Dec 8 03:06:06 Tower afpd[8760]: child[12573]: asev_del_fd: 11 Dec 8 03:07:46 Tower blazer_usb[7089]: Communications with UPS lost: status read failed! Dec 8 03:07:49 Tower upsd[7191]: UPS [ups] data is no longer stale Dec 8 03:08:15 Tower upsd[7191]: Data for UPS [ups] is stale - check driver Dec 8 03:08:23 Tower upsmon[7195]: Poll UPS [[email protected]] failed - Write error: Broken pipe Dec 8 03:09:19 Tower upsd[7191]: User [email protected] logged into UPS [ups] Dec 8 03:09:23 Tower upsd[7191]: User [email protected] logged out from UPS [ups] Dec 8 03:09:23 Tower upsmon[7195]: Can't login to UPS [[email protected]]: Server disconnected Dec 8 03:09:31 Tower upsmon[7195]: Poll UPS [[email protected]] failed - Driver not connected Dec 8 03:09:38 Tower upsd[7191]: User [email protected] logged into UPS [ups] Dec 8 03:09:38 Tower upsmon[7195]: Poll UPS [[email protected]] failed - Data stale Dec 8 03:09:38 Tower kernel: unregister_netdevice: waiting for lo to become free. Usage count = 1 Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 31 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: INFO: NMI handler (perf_event_nmi_handler) took too long to run: 199.444 msecs Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: hrtimer: interrupt took 2219098372 ns Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue Dec 8 03:09:38 Tower kernel: Uhhuh. NMI received for unknown reason 21 on CPU 0. Dec 8 03:09:38 Tower kernel: Do you have a strange power saving mode enabled? Dec 8 03:09:38 Tower kernel: Dazed and confused, but trying to continue tower-diagnostics-20171208-0809.zip FCPsyslog_tail.txt

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

experience for me and my kids is very good. though I still need to add the powered hub to stop disconnections. the solutions above aim to do the same as what you need. I think that the HDMI over RJ45 is good for very long distances (100m) if you are working in the range of 15m you dont need it. and you need cat6 not cat5e. forget about the cat5e for the remaining of your life . its not a life and death issue, for upto 5m its not . but if you have a better technology. why not use it , ha? hdmi and USB combined? if you have the money. the solutions are there, just cost by a multiple factors higher. in the end you have one HDMI extension cable and one cat6 cable running to the monitor. BTW very important . the SOUND. you have the sound in the HDMI cable. so if you are using a monitor with the speakers , you are good to go. but if you want to connect external ones. than you need the USB connection really stable and good. didnt go that way myself so dont have the experience. you have other options to extract the sound from HDMI. Either the monitor does that for you in some models, or you need a peace of HW that does it.

is it normal the /etc/rsyslog.conf is overwritten on reboot ? the parameters for the forwarding canceled again after the reboot should I edit something on the USB stick ?

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'