dadarara

Members
  • Posts

    187
  • Joined

  • Last visited

Everything posted by dadarara

  1. 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
  2. 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
  3. thanks done it what is this error msg after restart of syslogd Tower liblogging-stdlog: [origin software="rsyslogd" swVersion="8.23.0" x-pid="8683" x-info="http://www.rsyslog.com"] start Dec 6 05:38:57 Tower liblogging-stdlog: $WorkDirectory: /rsyslog/spool can not be accessed, probably does not exist - directive ignored [v8.23.0 try http://www.rsyslog.com/e/2181 ] Dec 6 05:38:57 Tower liblogging-stdlog: error starting up disk queue, using pure in-memory mode [v8.23.0 try http://www.rsyslog.com/e/2036 ]
  4. https://www.monoprice.com/product?p_id=12959 #HDMI extension cable Cabernet Ultra CL2 Active High Speed HDMI® Cable, 35ft Cabernet Ultra CL2 Active High Speed HDMI® Cable, 50ft running games on max resolution no problem. http://www.ebay.com/itm/USB-Over-RJ45-Cat5-Cat5e-Cat6-Extension-Extender-Cable-Adapter-Set-Hot-Sale-/131952933702?hash=item1eb901fb46:g:Fi4AAOSwbsBXoWHc #USB Over RJ45 runs over 15m worked for me. the USB though has sometimes disconnections. I am planning to put a powered hub on the end
  5. I am having crashes every night. Please help to understand ! attached is the diagnostics "postmortem". not sure what it can show. bellow is the syslog last "dying messages". I had a syslog window open on remote pc... Dec 5 19:00:01 Tower speedtest: Internet bandwidth test started Dec 5 19:00:32 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 5 19:00:32 Tower speedtest: Ping (Lowest): 949.874 ms | Download (Max): 94.37 Mbit/s | Upload (Max): 1.81 Mbit/s Dec 5 19:00:32 Tower speedtest: Internet bandwidth test completed Dec 5 20:00:01 Tower speedtest: Internet bandwidth test started Dec 5 20:00:12 Tower speedtest: Host: Dec 5 20:00:12 Tower speedtest: Dec 5 20:00:12 Tower speedtest: Internet bandwidth test completed Dec 5 21:00:02 Tower speedtest: Internet bandwidth test started Dec 5 21:00:37 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 5 21:00:37 Tower speedtest: Ping (Lowest): 106.573 ms | Download (Max): 76.06 Mbit/s | Upload (Max): 1.47 Mbit/s Dec 5 21:00:37 Tower speedtest: Internet bandwidth test completed Dec 5 22:00:01 Tower speedtest: Internet bandwidth test started Dec 5 22:00:31 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 5 22:00:31 Tower speedtest: Ping (Lowest): 133.581 ms | Download (Max): 96.27 Mbit/s | Upload (Max): 1.63 Mbit/s Dec 5 22:00:31 Tower speedtest: Internet bandwidth test completed Dec 5 23:00:01 Tower speedtest: Internet bandwidth test started Dec 5 23:00:32 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 5 23:00:32 Tower speedtest: Ping (Lowest): 110.671 ms | Download (Max): 97.10 Mbit/s | Upload (Max): 1.72 Mbit/s Dec 5 23:00:32 Tower speedtest: Internet bandwidth test completed Dec 5 23:35:16 Tower kernel: vgaarb: device changed decodes: PCI:0000:04:00.0,olddecodes=io+mem,decodes=io+mem:owns=none Dec 5 23:35:16 Tower kernel: br0: port 5(vnet3) entered blocking state Dec 5 23:35:16 Tower kernel: br0: port 5(vnet3) entered disabled state Dec 5 23:35:16 Tower kernel: device vnet3 entered promiscuous mode Dec 5 23:35:16 Tower kernel: br0: port 5(vnet3) entered blocking state Dec 5 23:35:16 Tower kernel: br0: port 5(vnet3) entered forwarding state Dec 5 23:35:52 Tower kernel: vfio-pci 0000:04:00.0: enabling device (0140 -> 0143) Dec 5 23:35:52 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x19@0x270 Dec 5 23:35:52 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x1b@0x2d0 Dec 5 23:35:52 Tower kernel: vfio_ecap_init: 0000:04:00.0 hiding ecap 0x1e@0x370 Dec 5 23:36:07 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 5 23:36:07 Tower kernel: kvm: zapping shadow pages for mmio generation wraparound Dec 6 00:00:01 Tower speedtest: Internet bandwidth test started Dec 6 00:00:27 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 6 00:00:27 Tower speedtest: Ping (Lowest): 142.165 ms | Download (Max): 88.70 Mbit/s | Upload (Max): 1.90 Mbit/s Dec 6 00:00:27 Tower speedtest: Internet bandwidth test completed Dec 6 00:37:58 Tower afpd[19899]: afp_alarm: child timed out, entering disconnected state Dec 6 01:00:02 Tower speedtest: Internet bandwidth test started Dec 6 01:00:03 Tower root: /mnt/cache: 258.7 GiB (277808664576 bytes) trimmed Dec 6 01:00:35 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 6 01:00:35 Tower speedtest: Ping (Lowest): 123.046 ms | Download (Max): 88.93 Mbit/s | Upload (Max): 1.72 Mbit/s Dec 6 01:00:35 Tower speedtest: Internet bandwidth test completed Dec 6 02:00:01 Tower speedtest: Internet bandwidth test started Dec 6 02:00:39 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 6 02:00:39 Tower speedtest: Ping (Lowest): 171.166 ms | Download (Max): 98.26 Mbit/s | Upload (Max): 1.43 Mbit/s Dec 6 02:00:39 Tower speedtest: Internet bandwidth test completed Dec 6 02:07:02 Tower afpd[31875]: read: Connection reset by peer Dec 6 02:07:02 Tower afpd[20176]: read: Connection reset by peer Dec 6 02:07:02 Tower afpd[31875]: dsi_stream_read: len:-1, Connection reset by peer Dec 6 02:07:02 Tower afpd[20176]: dsi_stream_read: len:-1, Connection reset by peer Dec 6 03:00:01 Tower speedtest: Internet bandwidth test started Dec 6 03:00:01 Tower CA Backup/Restore: ####################################### Dec 6 03:00:01 Tower CA Backup/Restore: Community Applications appData Backup Dec 6 03:00:01 Tower CA Backup/Restore: Applications will be unavailable during Dec 6 03:00:01 Tower CA Backup/Restore: this process. They will automatically Dec 6 03:00:01 Tower CA Backup/Restore: be restarted upon completion. Dec 6 03:00:01 Tower CA Backup/Restore: ####################################### Dec 6 03:00:01 Tower CA Backup/Restore: Stopping binhex-delugevpn Dec 6 03:00:02 Tower kernel: docker0: port 1(vethc368c87) entered disabled state Dec 6 03:00:02 Tower kernel: vethe24010d: renamed from eth0 Dec 6 03:00:03 Tower kernel: docker0: port 1(vethc368c87) entered disabled state Dec 6 03:00:03 Tower kernel: device vethc368c87 left promiscuous mode Dec 6 03:00:03 Tower kernel: docker0: port 1(vethc368c87) entered disabled state Dec 6 03:00:03 Tower CA Backup/Restore: docker stop -t 60 binhex-delugevpn Dec 6 03:00:03 Tower CA Backup/Restore: Stopping CrashPlan Dec 6 03:00:03 Tower CA Backup/Restore: docker stop -t 60 CrashPlan Dec 6 03:00:03 Tower CA Backup/Restore: Stopping EmbyServer Dec 6 03:00:07 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.001 Dec 6 03:00:08 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.002 Dec 6 03:00:08 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.003 Dec 6 03:00:08 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.004 Dec 6 03:00:08 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.005 Dec 6 03:00:08 Tower move: skipping file in-use: ./Downloads/.AppleDB/__db.006 Dec 6 03:00:08 Tower move: rmdir: /mnt/cache/./Downloads/.AppleDB Directory not empty Dec 6 03:00:08 Tower move: rmdir: /mnt/cache/./Downloads Directory not empty Dec 6 03:00:08 Tower move: skipping file in-use: ./domains/talVM/vdisk1.img Dec 6 03:00:08 Tower move: rmdir: /mnt/cache/./domains/talVM Directory not empty Dec 6 03:00:08 Tower move: rmdir: /mnt/cache/./domains Directory not empty Dec 6 03:00:10 Tower CA Backup/Restore: docker stop -t 60 EmbyServer Dec 6 03:00:10 Tower CA Backup/Restore: Stopping PrinterCUPS Dec 6 03:00:10 Tower avahi-daemon[8708]: Files changed, reloading. Dec 6 03:00:10 Tower avahi-daemon[8708]: Service group file /services/AirPrint-HP_Deskjet_F4500_series.service vanished, removing services. Dec 6 03:00:10 Tower kernel: docker0: port 2(veth0dbb9f6) entered disabled state Dec 6 03:00:10 Tower kernel: vethd7554e3: renamed from eth0 Dec 6 03:00:10 Tower kernel: docker0: port 2(veth0dbb9f6) entered disabled state Dec 6 03:00:10 Tower kernel: device veth0dbb9f6 left promiscuous mode Dec 6 03:00:10 Tower kernel: docker0: port 2(veth0dbb9f6) entered disabled state Dec 6 03:00:10 Tower CA Backup/Restore: docker stop -t 60 PrinterCUPS Dec 6 03:00:10 Tower CA Backup/Restore: Backing up USB Flash drive config folder to Dec 6 03:00:10 Tower move: skipping file in-use: ./media/.AppleDB/__db.001 Dec 6 03:00:10 Tower move: skipping file in-use: ./media/.AppleDB/__db.002 Dec 6 03:00:10 Tower move: skipping file in-use: ./media/.AppleDB/__db.003 Dec 6 03:00:10 Tower move: skipping file in-use: ./media/.AppleDB/__db.004 Dec 6 03:00:10 Tower move: skipping file in-use: ./media/.AppleDB/__db.005 Dec 6 03:00:10 Tower move: skipping file in-use: ./media/.AppleDB/__db.006 Dec 6 03:00:11 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 6 03:00:11 Tower move: skipping file in-use: ./media/.AppleDB/log.0000001278 Dec 6 03:00:11 Tower move: rmdir: /mnt/cache/./media/.AppleDB Directory not empty Dec 6 03:00:11 Tower CA Backup/Restore: Backing Up appData from /mnt/user/appdata/ to /mnt/disks/WDC_WD10EAVS-00D7B0_WD-WCAU40879013/CommunityApplicationsAppdataBackup/[email protected] Dec 6 03:00:11 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 6 03:00:13 Tower ntpd[2282]: Deleting interface #3 docker0, 172.17.0.1#123, interface stats: received=0, sent=0, dropped=0, active_time=76771 secs Dec 6 03:00:16 Tower kernel: BTRFS info (device sde1): The free space cache file (379060224000) is invalid. skip it Dec 6 03:00:16 Tower kernel: Dec 6 03:00:17 Tower move: rmdir: /mnt/cache/./media Directory not empty Dec 6 03:00:34 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Dec 6 03:00:34 Tower speedtest: Ping (Lowest): 126.882 ms | Download (Max): 98.09 Mbit/s | Upload (Max): 2.08 Mbit/s Dec 6 03:00:34 Tower speedtest: Internet bandwidth test completed Dec 6 03:05:14 Tower afpd[19899]: afp_alarm: child timed out, entering disconnected state Dec 6 03:05:25 Tower afpd[20176]: afp_alarm: child timed out, entering disconnected state Dec 6 03:05:41 Tower afpd[31875]: afp_alarm: child timed out, entering disconnected state tower-diagnostics-20171206-0456.zip
  6. I got the same message but I am not playing games. only running 3 VMs not very loaded. and 2-3 dockers like Plex, CrashPlan. I have 32 cores total on dual XEON 2.6GHz with 64GB memory and I have 1600W Platinum PSU. when I got the message the parity check was also running (following the tonight's crash) so it doesn't look to me like heavy CPU use. what I do have lately is my system hangs once a few days. I am trying to isolate the issue. the logs dont say much. they dont catch the situation realtime. dont know too much how to debug this.
  7. smart people whats the procedure and the commands to make it work please? I have a PRTG monitoring software running on one of the VMs. I would like to save the unraid syslog there. so how do I duplicate the log messages to be sent to 10.0.0.50 port 154 ?
  8. have a windows VM running. the CPU-Z shows that I have no L3 CACHE on the CPUs. What am I missing ? can anyone check on their VMs if they have it show as active ? is it only me?
  9. Hi anyone can tell me what this is please? this I get in the console. Message from syslogd@Tower at Dec 1 04:02:40 ... kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0. Message from syslogd@Tower at Dec 1 04:02:40 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@Tower at Dec 1 04:02:40 ... kernel:Dazed and confused, but trying to continue Message from syslogd@Tower at Dec 1 04:02:40 ... kernel:Uhhuh. NMI received for unknown reason 21 on CPU 0. Message from syslogd@Tower at Dec 1 04:02:40 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@Tower at Dec 1 04:02:40 ... kernel:Dazed and confused, but trying to continue i have left the log open and I get there the bellow: Dec 1 03:05:04 Tower afpd[21598]: dsi_stream_read: len:-1, Connection reset by peer Dec 1 03:05:04 Tower afpd[21500]: read: Connection reset by peer Dec 1 03:05:04 Tower afpd[21500]: dsi_stream_read: len:-1, Connection reset by peer Dec 1 03:07:16 Tower afpd[13651]: dsi_stream_write: Broken pipe Dec 1 03:07:16 Tower afpd[13651]: dsi_stream_write: Broken pipe Dec 1 03:07:16 Tower afpd[13651]: dsi_stream_write: Broken pipe Dec 1 03:07:25 Tower afpd[13649]: dsi_stream_write: Broken pipe Dec 1 03:07:25 Tower afpd[13649]: dsi_stream_write: Broken pipe Dec 1 03:07:30 Tower afpd[13649]: dsi_stream_write: Broken pipe Dec 1 03:07:35 Tower afpd[13650]: dsi_stream_write: Broken pipe Dec 1 03:07:35 Tower afpd[13650]: dsi_stream_write: Broken pipe Dec 1 03:07:35 Tower afpd[13650]: dsi_stream_write: Broken pipe Dec 1 03:07:50 Tower afpd[13656]: dsi_stream_write: Broken pipe Dec 1 03:07:50 Tower afpd[13656]: dsi_stream_write: Broken pipe Dec 1 03:07:50 Tower afpd[13656]: dsi_stream_write: Broken pipe The WEBUI stops loading after the bellow title is done. nothing else I have access to the console. the diagnostics command works but I get nothing in the /boot/logs folder I have downloaded some logs from /var/log hope someone can see what this is. Archive.zip
  10. 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?
  11. short update for posterity .. reinstalled the unRAID on the same USB. done also MEMTEST 1 pass, just to make sure. took long time for the 64GB I have it kept all the data. after the process , the TIME settings and the user setting were sorted out OK. no issues there. after the process, 1st problem was that the parity was with error. so I run the parity check. (10 long hours) after that the party disk got disabled. had to remove the disk from configuration , stop start array and assign the disk again, then to run 10hours parity check again. brrrrrrrrrrrrr anyways, now it looks ok. Also the responsiveness of the WEBGUI is much better. I think it became faster.
  12. thanks will probably reinstall everything. need to find the right instructions so not to delete anything
  13. reviving this topic. I am yet to decide to reinstall ALL the server. can someone look at the log when the server starts? 1 - the NTP time service is not updating the time 2 - the users definitions are still missing 3 - SSH access always after reboot I need to delete the SSH.known user list from my remote pc. the identity of the unRAID is changing any ideas ? hopping for some "easier" fix rather than reinstall. tower-diagnostics-20171016-2232.zip
  14. the server is frozen. the VM screens are static no activity NIC lights blinking HD lights black just before crashing I captured the LOG bellow. any ideas ? what is this IRQ flags mismatch ? Oct 16 06:56:17 Tower upsmon[15220]: Poll UPS [ups@localhost] failed - Data stale Oct 16 06:56:17 Tower upsd[15217]: UPS [ups] data is no longer stale Oct 16 06:56:22 Tower upsmon[15220]: Communications with UPS ups@localhost established Oct 16 07:00:01 Tower speedtest: Internet bandwidth test started Oct 16 07:00:28 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Oct 16 07:00:28 Tower speedtest: Ping (Lowest): 158.76 ms | Download (Max): 60.89 Mbit/s | Upload (Max): 1.76 Mbit/s Oct 16 07:00:28 Tower speedtest: Internet bandwidth test completed Oct 16 07:11:39 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 16 07:11:39 Tower kernel: br0: port 5(vnet3) entered blocking state Oct 16 07:11:39 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:11:39 Tower kernel: device vnet3 entered promiscuous mode Oct 16 07:11:39 Tower kernel: br0: port 5(vnet3) entered blocking state Oct 16 07:11:39 Tower kernel: br0: port 5(vnet3) entered forwarding state Oct 16 07:11:57 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x19@0x900 Oct 16 07:11:57 Tower kernel: vfio-pci 0000:09:00.0: enabling device (0400 -> 0402) Oct 16 07:11:58 Tower kernel: genirq: Flags mismatch irq 18. 00000080 (vfio-intx(0000:09:00.0)) vs. 00000000 (vfio-intx(0000:0a:02.0)) Oct 16 07:11:59 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:11:59 Tower kernel: device vnet3 left promiscuous mode Oct 16 07:11:59 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:12:02 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 16 07:13:26 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 16 07:13:26 Tower kernel: br0: port 5(vnet3) entered blocking state Oct 16 07:13:26 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:13:26 Tower kernel: device vnet3 entered promiscuous mode Oct 16 07:13:26 Tower kernel: br0: port 5(vnet3) entered blocking state Oct 16 07:13:26 Tower kernel: br0: port 5(vnet3) entered forwarding state Oct 16 07:13:39 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x19@0x900 Oct 16 07:13:39 Tower kernel: vfio-pci 0000:09:00.0: enabling device (0400 -> 0402) Oct 16 07:13:40 Tower kernel: genirq: Flags mismatch irq 18. 00000080 (vfio-intx(0000:09:00.0)) vs. 00000000 (vfio-intx(0000:0a:02.0)) Oct 16 07:13:41 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:13:41 Tower kernel: device vnet3 left promiscuous mode Oct 16 07:13:41 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:13:44 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 16 07:16:54 Tower sshd[25917]: Accepted none for root from 10.0.0.148 port 64306 ssh2 Oct 16 07:18:17 Tower kernel: vgaarb: device changed decodes: PCI:0000:03:00.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem Oct 16 07:18:17 Tower kernel: br0: port 5(vnet3) entered blocking state Oct 16 07:18:17 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:18:17 Tower kernel: device vnet3 entered promiscuous mode Oct 16 07:18:17 Tower kernel: br0: port 5(vnet3) entered blocking state Oct 16 07:18:17 Tower kernel: br0: port 5(vnet3) entered forwarding state Oct 16 07:18:31 Tower kernel: vfio_ecap_init: 0000:03:00.0 hiding ecap 0x19@0x900 Oct 16 07:18:31 Tower kernel: vfio-pci 0000:09:00.0: enabling device (0400 -> 0402) Oct 16 07:18:32 Tower kernel: genirq: Flags mismatch irq 18. 00000080 (vfio-intx(0000:09:00.0)) vs. 00000000 (vfio-intx(0000:0a:02.0)) Oct 16 07:18:33 Tower kernel: br0: port 5(vnet3) entered disabled state Oct 16 07:18:33 Tower kernel: device vnet3 left promiscuous mode Oct 16 07:18:33 Tower kernel: br0: port 5(vnet3) entered disabled state
  15. I have OSX VM. MUST have, NEED to have, LOVE to have. No other OS than OSX for me. so how do I know if its something serious that I need to do something about ?
  16. anyone can tell me what this is? Oct 14 18:07:46 Tower upsmon[15220]: UPS ups@localhost battery is low Oct 14 18:31:17 Tower cnid_dbd[3274]: error deleting key/value from cnid2.db: Invalid argument Oct 14 18:31:17 Tower cnid_dbd[3274]: dbd_delete: Unable to delete entry for CNID 617667 Oct 14 18:31:18 Tower cnid_dbd[3274]: error closing database name.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:18 Tower cnid_dbd[3274]: error closing database didname.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:18 Tower cnid_dbd[3274]: error closing database devino.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:18 Tower cnid_dbd[3274]: error closing database cnid2.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:18 Tower cnid_dbd[3274]: error closing DB environment: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:19 Tower afpd[3263]: read: Connection reset by peer Oct 14 18:31:20 Tower cnid_dbd[29627]: error deleting key/value from cnid2.db: Invalid argument Oct 14 18:31:20 Tower cnid_dbd[29627]: dbd_delete: Unable to delete entry for CNID 617667 Oct 14 18:31:20 Tower afpd[3263]: Reopen volume /mnt/user/Software using in memory temporary CNID DB. Oct 14 18:31:20 Tower cnid_dbd[29627]: error closing database name.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:20 Tower cnid_dbd[29627]: error closing database didname.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:20 Tower cnid_dbd[29627]: error closing database devino.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:20 Tower cnid_dbd[29627]: error closing database cnid2.db: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 18:31:20 Tower cnid_dbd[29627]: error closing DB environment: DB_RUNRECOVERY: Fatal error, run database recovery Oct 14 19:00:01 Tower speedtest: Internet bandwidth test started tower-diagnostics-20171015-0051.zip
  17. 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 ?
  18. 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
  19. 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