SPOautos

Members
  • Posts

    373
  • Joined

  • Last visited

Everything posted by SPOautos

  1. But all of my containers added together are only 19.9GB disk utilization, right? How is that so high? Is this just based on a setting somewhere that I'm only allowing a certain amount of space dedicated to containers?
  2. I recently set up a Syslog file that runs and this is what it shows for the 11th, 12th, 13th but I dont think I'm seeing anything in here that would be causing a issue of docker image disk utilization being high. I do have mining running and its been running for months so I doubt that is the cause, it doesn't use much memory, it uses the GPU and half the CPU. I have no idea what all these entries are regarding port numbers and entering blacking/forwarding/disabled states. Jun 11 00:00:32 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 01:01:14 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 02:00:14 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 03:00:11 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 04:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 04:00:47 Tower root: /var/lib/docker: 12.9 GiB (13833793536 bytes) trimmed on /dev/loop2 Jun 11 04:00:47 Tower root: /mnt/cache: 331.4 GiB (355793293312 bytes) trimmed on /dev/nvme0n1p1 Jun 11 04:40:01 Tower root: Fix Common Problems Version 2021.05.03 Jun 11 05:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 06:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 07:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered blocking state Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered disabled state Jun 11 07:44:09 Tower kernel: device veth2de21d8 entered promiscuous mode Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered blocking state Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered forwarding state Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered disabled state Jun 11 07:44:09 Tower kernel: eth0: renamed from veth5f484ab Jun 11 07:44:09 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2de21d8: link becomes ready Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered blocking state Jun 11 07:44:09 Tower kernel: docker0: port 5(veth2de21d8) entered forwarding state Jun 11 08:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 08:24:45 Tower kernel: docker0: port 6(veth00d4a84) entered blocking state Jun 11 08:24:45 Tower kernel: docker0: port 6(veth00d4a84) entered disabled state Jun 11 08:24:45 Tower kernel: device veth00d4a84 entered promiscuous mode Jun 11 08:24:46 Tower kernel: eth0: renamed from veth164898c Jun 11 08:24:46 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth00d4a84: link becomes ready Jun 11 08:24:46 Tower kernel: docker0: port 6(veth00d4a84) entered blocking state Jun 11 08:24:46 Tower kernel: docker0: port 6(veth00d4a84) entered forwarding state Jun 11 08:53:06 Tower kernel: docker0: port 6(veth00d4a84) entered disabled state Jun 11 08:53:06 Tower kernel: veth164898c: renamed from eth0 Jun 11 08:53:06 Tower kernel: docker0: port 6(veth00d4a84) entered disabled state Jun 11 08:53:06 Tower kernel: device veth00d4a84 left promiscuous mode Jun 11 08:53:06 Tower kernel: docker0: port 6(veth00d4a84) entered disabled state Jun 11 08:53:07 Tower kernel: docker0: port 6(vetha6de89e) entered blocking state Jun 11 08:53:07 Tower kernel: docker0: port 6(vetha6de89e) entered disabled state Jun 11 08:53:07 Tower kernel: device vetha6de89e entered promiscuous mode Jun 11 08:53:07 Tower kernel: docker0: port 6(vetha6de89e) entered blocking state Jun 11 08:53:07 Tower kernel: docker0: port 6(vetha6de89e) entered forwarding state Jun 11 08:53:07 Tower kernel: eth0: renamed from veth61b0ff9 Jun 11 08:53:07 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha6de89e: link becomes ready Jun 11 09:00:08 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 09:00:37 Tower kernel: docker0: port 6(vetha6de89e) entered disabled state Jun 11 09:00:37 Tower kernel: veth61b0ff9: renamed from eth0 Jun 11 09:00:37 Tower kernel: docker0: port 6(vetha6de89e) entered disabled state Jun 11 09:00:37 Tower kernel: device vetha6de89e left promiscuous mode Jun 11 09:00:37 Tower kernel: docker0: port 6(vetha6de89e) entered disabled state Jun 11 09:00:37 Tower kernel: docker0: port 6(veth3969633) entered blocking state Jun 11 09:00:37 Tower kernel: docker0: port 6(veth3969633) entered disabled state Jun 11 09:00:37 Tower kernel: device veth3969633 entered promiscuous mode Jun 11 09:00:37 Tower kernel: docker0: port 6(veth3969633) entered blocking state Jun 11 09:00:37 Tower kernel: docker0: port 6(veth3969633) entered forwarding state Jun 11 09:00:38 Tower kernel: eth0: renamed from vethfd855b4 Jun 11 09:00:38 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3969633: link becomes ready Jun 11 09:11:08 Tower kernel: docker0: port 6(veth3969633) entered disabled state Jun 11 09:11:08 Tower kernel: vethfd855b4: renamed from eth0 Jun 11 09:11:08 Tower kernel: docker0: port 6(veth3969633) entered disabled state Jun 11 09:11:08 Tower kernel: device veth3969633 left promiscuous mode Jun 11 09:11:08 Tower kernel: docker0: port 6(veth3969633) entered disabled state Jun 11 09:11:09 Tower kernel: docker0: port 6(veth3cc4ddf) entered blocking state Jun 11 09:11:09 Tower kernel: docker0: port 6(veth3cc4ddf) entered disabled state Jun 11 09:11:09 Tower kernel: device veth3cc4ddf entered promiscuous mode Jun 11 09:11:09 Tower kernel: docker0: port 6(veth3cc4ddf) entered blocking state Jun 11 09:11:09 Tower kernel: docker0: port 6(veth3cc4ddf) entered forwarding state Jun 11 09:11:09 Tower kernel: eth0: renamed from veth83942c3 Jun 11 09:11:09 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3cc4ddf: link becomes ready Jun 11 09:19:24 Tower kernel: docker0: port 6(veth3cc4ddf) entered disabled state Jun 11 09:19:24 Tower kernel: veth83942c3: renamed from eth0 Jun 11 09:19:24 Tower kernel: docker0: port 6(veth3cc4ddf) entered disabled state Jun 11 09:19:24 Tower kernel: device veth3cc4ddf left promiscuous mode Jun 11 09:19:24 Tower kernel: docker0: port 6(veth3cc4ddf) entered disabled state Jun 11 09:19:25 Tower kernel: docker0: port 6(veth6bc6288) entered blocking state Jun 11 09:19:25 Tower kernel: docker0: port 6(veth6bc6288) entered disabled state Jun 11 09:19:25 Tower kernel: device veth6bc6288 entered promiscuous mode Jun 11 09:19:25 Tower kernel: docker0: port 6(veth6bc6288) entered blocking state Jun 11 09:19:25 Tower kernel: docker0: port 6(veth6bc6288) entered forwarding state Jun 11 09:19:25 Tower kernel: eth0: renamed from vethfac2dbd Jun 11 09:19:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6bc6288: link becomes ready Jun 11 09:22:54 Tower kernel: docker0: port 6(veth6bc6288) entered disabled state Jun 11 09:22:54 Tower kernel: vethfac2dbd: renamed from eth0 Jun 11 09:22:54 Tower kernel: docker0: port 6(veth6bc6288) entered disabled state Jun 11 09:22:54 Tower kernel: device veth6bc6288 left promiscuous mode Jun 11 09:22:54 Tower kernel: docker0: port 6(veth6bc6288) entered disabled state Jun 11 09:22:55 Tower kernel: docker0: port 6(vethb4fba36) entered blocking state Jun 11 09:22:55 Tower kernel: docker0: port 6(vethb4fba36) entered disabled state Jun 11 09:22:55 Tower kernel: device vethb4fba36 entered promiscuous mode Jun 11 09:22:55 Tower kernel: docker0: port 6(vethb4fba36) entered blocking state Jun 11 09:22:55 Tower kernel: docker0: port 6(vethb4fba36) entered forwarding state Jun 11 09:22:55 Tower kernel: eth0: renamed from vethcd82465 Jun 11 09:22:55 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb4fba36: link becomes ready Jun 11 10:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 11:00:08 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 12:00:09 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 13:00:01 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 14:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 15:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 16:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 17:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 18:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 19:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 20:00:09 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 21:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 22:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 11 23:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 00:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 01:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 02:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 03:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 04:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 04:00:43 Tower root: /var/lib/docker: 3.1 GiB (3280904192 bytes) trimmed on /dev/loop2 Jun 12 04:00:43 Tower root: /mnt/cache: 326.5 GiB (350595309568 bytes) trimmed on /dev/nvme0n1p1 Jun 12 04:40:01 Tower root: Fix Common Problems Version 2021.05.03 Jun 12 04:40:15 Tower root: FCP Debug Log: root 25980 1198 0.8 3598248 274764 ? Sl Jun11 13867:55 ./xmrig --url=xmr-us-east1.nanopool.org:14433 --coin=monero --user= *I removed the user data from the copy/paste* Jun 12 04:40:15 Tower root: Fix Common Problems: Warning: Possible mining software running ** Ignored Jun 12 05:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 06:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 07:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 08:00:25 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 09:00:23 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 10:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 11:00:09 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 12:00:09 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 13:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 14:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 15:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 16:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 17:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 18:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 19:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 20:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 21:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 22:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 12 23:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 00:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 01:00:09 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 02:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 03:00:07 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 04:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 04:00:42 Tower root: /var/lib/docker: 3 GiB (3194228736 bytes) trimmed on /dev/loop2 Jun 13 04:00:42 Tower root: /mnt/cache: 326.7 GiB (350819770368 bytes) trimmed on /dev/nvme0n1p1 Jun 13 04:40:01 Tower root: Fix Common Problems Version 2021.05.03 Jun 13 04:40:14 Tower root: FCP Debug Log: root 25980 1198 0.8 3596196 277248 ? Sl Jun11 31122:13 ./xmrig --url=xmr-us-east1.nanopool.org:14433 --coin=monero --user= *I removed the user data from the copy/paste* Jun 13 04:40:14 Tower root: Fix Common Problems: Warning: Possible mining software running ** Ignored Jun 13 04:40:15 Tower apcupsd[6677]: apcupsd exiting, signal 15 Jun 13 04:40:15 Tower apcupsd[6677]: apcupsd shutdown succeeded Jun 13 04:40:18 Tower apcupsd[11753]: apcupsd 3.14.14 (31 May 2016) slackware startup succeeded Jun 13 04:40:18 Tower apcupsd[11753]: NIS server startup succeeded Jun 13 05:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 06:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 07:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 08:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 08:56:11 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unassigned.devices.plg Jun 13 08:56:11 Tower root: plugin: running: anonymous Jun 13 08:56:11 Tower root: plugin: creating: /boot/config/plugins/unassigned.devices/unassigned.devices-2021.06.11.tgz - downloading from URL https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices-2021.06.11.tgz Jun 13 08:56:12 Tower root: plugin: checking: /boot/config/plugins/unassigned.devices/unassigned.devices-2021.06.11.tgz - MD5 Jun 13 08:56:12 Tower root: plugin: creating: /tmp/start_unassigned_devices - from INLINE content Jun 13 08:56:12 Tower root: plugin: setting: /tmp/start_unassigned_devices - mode to 0770 Jun 13 08:56:12 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/unassigned.devices.cfg already exists Jun 13 08:56:12 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/samba_mount.cfg already exists Jun 13 08:56:12 Tower root: plugin: skipping: /boot/config/plugins/unassigned.devices/iso_mount.cfg already exists Jun 13 08:56:12 Tower root: plugin: skipping: /tmp/unassigned.devices/smb-settings.conf already exists Jun 13 08:56:12 Tower root: plugin: skipping: /tmp/unassigned.devices/config/smb-extra.conf already exists Jun 13 08:56:12 Tower root: plugin: skipping: /tmp/unassigned.devices/add-smb-extra already exists Jun 13 08:56:12 Tower root: plugin: setting: /tmp/unassigned.devices/add-smb-extra - mode to 0770 Jun 13 08:56:12 Tower root: plugin: skipping: /tmp/unassigned.devices/remove-smb-extra already exists Jun 13 08:56:12 Tower root: plugin: setting: /tmp/unassigned.devices/remove-smb-extra - mode to 0770 Jun 13 08:56:12 Tower root: plugin: running: anonymous Jun 13 09:00:45 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null Jun 13 10:00:16 Tower crond[2908]: exit status 1 from user root /usr/local/sbin/mover &amp;&gt; /dev/null </pre> </body> </html>
  3. Also, if it makes a difference, everything is up to date....6.9.2 with all containers and plugins updated. I'm pretty sure this is going to keep getting higher and higher over a couple day period. I'm pretty sure this happened a couple weeks ago and eventually made my server crash (well it crashed and I never found out why and it was running fine when it booted back up, and I just *think* it must have been because of this). I've looked through the log but I don't see anything jumping out at me....but I also don't know enough about what all is going on behind the scenes to know what everything means. I'm not a IT/Computer guy.....We have a children's clothing store and I do construction lol. To be honest I don't even know how I got all this working and being useful except that the forum community is awesome.
  4. Hey guys, on the Dashboard under Memory then Docker, its a 71% and growing, its normally a very low number. I attached a diagnostic, can anyone tell what's causing it? I also have a notification of "Warning [TOWER] - Docker image disk utilization of 71%". When I look under the Docker tab and advanced view, none of the containers are using a lot of memory. Thanks... tower-diagnostics-20210613-0439.zip
  5. Were you ever able to get this resolved? I seem to be having a similar issue after updating. I cant find the server from the other devices in the Workgroup. Wondering what fixed it for you. Similarly my settings have "yes" for Workgroup.
  6. Feel like a dumb ass lol....the bubble to the right you have to click was off the screen. Thank You!
  7. In the syslinux configuration section, how do you switch it to boot in GUI mode?
  8. During bootup, I missed selecting GUI so it just went through normal process of not entering GUI and I've been just using the GUI over the network. Is there a way at this point, to access the GUI locally without rebooting the server? Thanks!
  9. I have a xeon e5-2690v3 and had --asm intel and --randomx-1gb-pages but I could never seem to get the 1gb pages to work. When I removed those two arguements my H/s actually went UP about 200 H/s. I have no idea why. Have you done before/after to see what difference they are making? Also, can you tell in your container log that your actually getting 1gb pages?
  10. My XMrig log was also showing real high ram usage....like 26GB out of 32GB but it was related to me having Plex transcoding in ram and I had a large chunk of my ram allocated for that purpose so XMrig was seeing that and considering it as being used eventhough my actual usage was only like 7GB. HOWEVER, that said, even after I made some changes and XMrig only sees my usage as like 7GB out of 32GB, I still cant use the 1GB pages. For some reason RandomX 1GB pages fails. Not sure why. Anyway, are you doing Plex transcoding in ram? If so, pull up the script, click edit, see how much ram you have allocated to it.....I had way more than I needed allocated so I changed it to like 4GB then restarted my array so it would change (just running the script didnt seem to work but stopping then starting the array did change how much was allocated).
  11. Mine has been working great for months but sometime in March it stopped connecting. I set up the 2 way authentication for the web login but something else must be messed up. I've looked through everything and it all seems good but in Unraid when you go to the WebUI and login it says "Unable to connect to destination for 10 days". Any ideas on where I should look? I restarted the container and here is a log from where it started back up....maybe it has some useful info [services.d] starting app... [app] starting CrashPlan for Small Business... 07/04/2021 11:19:26 X DAMAGE available on display, using it for polling hints. 07/04/2021 11:19:26 To disable this behavior use: '-noxdamage' 07/04/2021 11:19:26 07/04/2021 11:19:26 Most compositing window managers like 'compiz' or 'beryl' 07/04/2021 11:19:26 cause X DAMAGE to fail, and so you may not see any screen 07/04/2021 11:19:26 updates via VNC. Either disable 'compiz' (recommended) or 07/04/2021 11:19:26 supply the x11vnc '-noxdamage' command line option. 07/04/2021 11:19:26 X COMPOSITE available on display, using it for window polling. 07/04/2021 11:19:26 To disable this behavior use: '-noxcomposite' 07/04/2021 11:19:26 07/04/2021 11:19:26 Wireframing: -wireframe mode is in effect for window moves. 07/04/2021 11:19:26 If this yields undesired behavior (poor response, painting 07/04/2021 11:19:26 errors, etc) it may be disabled: 07/04/2021 11:19:26 - use '-nowf' to disable wireframing completely. 07/04/2021 11:19:26 - use '-nowcr' to disable the Copy Rectangle after the 07/04/2021 11:19:26 moved window is released in the new position. 07/04/2021 11:19:26 Also see the -help entry for tuning parameters. 07/04/2021 11:19:26 You can press 3 Alt_L's (Left "Alt" key) in a row to 07/04/2021 11:19:26 repaint the screen, also see the -fixscreen option for 07/04/2021 11:19:26 periodic repaints. 07/04/2021 11:19:26 GrabServer control via XTEST. [services.d] done. 07/04/2021 11:19:26 07/04/2021 11:19:26 Scroll Detection: -scrollcopyrect mode is in effect to 07/04/2021 11:19:26 use RECORD extension to try to detect scrolling windows 07/04/2021 11:19:26 (induced by either user keystroke or mouse input). 07/04/2021 11:19:26 If this yields undesired behavior (poor response, painting 07/04/2021 11:19:26 errors, etc) it may be disabled via: '-noscr' 07/04/2021 11:19:26 Also see the -help entry for tuning parameters. 07/04/2021 11:19:26 You can press 3 Alt_L's (Left "Alt" key) in a row to 07/04/2021 11:19:26 repaint the screen, also see the -fixscreen option for 07/04/2021 11:19:26 periodic repaints. 07/04/2021 11:19:26 07/04/2021 11:19:26 XKEYBOARD: number of keysyms per keycode 7 is greater 07/04/2021 11:19:26 than 4 and 51 keysyms are mapped above 4. 07/04/2021 11:19:26 Automatically switching to -xkb mode. 07/04/2021 11:19:26 If this makes the key mapping worse you can 07/04/2021 11:19:26 disable it with the "-noxkb" option. 07/04/2021 11:19:26 Also, remember "-remap DEAD" for accenting characters. 07/04/2021 11:19:26 07/04/2021 11:19:26 X FBPM extension not supported. 07/04/2021 11:19:26 X display is not capable of DPMS. 07/04/2021 11:19:26 -------------------------------------------------------- 07/04/2021 11:19:26 07/04/2021 11:19:26 Default visual ID: 0x21 07/04/2021 11:19:26 Read initial data from X display into framebuffer. 07/04/2021 11:19:26 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120 07/04/2021 11:19:26 07/04/2021 11:19:26 X display :0 is 32bpp depth=24 true color 07/04/2021 11:19:26 07/04/2021 11:19:26 Listening for VNC connections on TCP port 5900 07/04/2021 11:19:26 07/04/2021 11:19:26 Xinerama is present and active (e.g. multi-head). 07/04/2021 11:19:26 Xinerama: number of sub-screens: 1 07/04/2021 11:19:26 Xinerama: no blackouts needed (only one sub-screen) 07/04/2021 11:19:26 07/04/2021 11:19:26 fb read rate: 861 MB/sec 07/04/2021 11:19:26 fast read: reset -wait ms to: 10 07/04/2021 11:19:26 fast read: reset -defer ms to: 10 07/04/2021 11:19:26 The X server says there are 10 mouse buttons. 07/04/2021 11:19:26 screen setup finished. 07/04/2021 11:19:26 The VNC desktop is: bceeb4c88123:0 0 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching 07/04/2021 11:20:04 Got connection from client 127.0.0.1 07/04/2021 11:20:04 other clients: 07/04/2021 11:20:04 Got 'ws' WebSockets handshake 07/04/2021 11:20:04 Got protocol: binary 07/04/2021 11:20:04 - webSocketsHandshake: using binary/raw encoding 07/04/2021 11:20:04 - WebSockets client version hybi-13 07/04/2021 11:20:04 Disabled X server key autorepeat. 07/04/2021 11:20:04 to force back on run: 'xset r on' (3 times) 07/04/2021 11:20:04 incr accepted_client=1 for 127.0.0.1:45350 sock=10 07/04/2021 11:20:04 Client Protocol Version 3.8 07/04/2021 11:20:04 Protocol version sent 3.8, using 3.8 07/04/2021 11:20:04 rfbProcessClientSecurityType: executing handler for type 1 07/04/2021 11:20:04 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 07/04/2021 11:20:04 Pixel format for client 127.0.0.1: 07/04/2021 11:20:04 32 bpp, depth 24, little endian 07/04/2021 11:20:04 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 07/04/2021 11:20:04 no translation needed 07/04/2021 11:20:04 Enabling NewFBSize protocol extension for client 127.0.0.1 07/04/2021 11:20:04 Enabling full-color cursor updates for client 127.0.0.1 07/04/2021 11:20:04 Using image quality level 6 for client 127.0.0.1 07/04/2021 11:20:04 Using JPEG subsampling 0, Q79 for client 127.0.0.1 07/04/2021 11:20:04 Using compression level 9 for client 127.0.0.1 07/04/2021 11:20:04 Enabling LastRect protocol extension for client 127.0.0.1 07/04/2021 11:20:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC) 07/04/2021 11:20:04 Using tight encoding for client 127.0.0.1 07/04/2021 11:20:05 client_set_net: 127.0.0.1 0.0000 07/04/2021 11:20:05 created xdamage object: 0x40002c 07/04/2021 11:20:05 copy_tiles: allocating first_line at size 41 07/04/2021 11:20:05 client_set_net: 127.0.0.1 0.0000 07/04/2021 11:20:05 created xdamage object: 0x40002c 07/04/2021 11:20:05 copy_tiles: allocating first_line at size 41 07/04/2021 11:20:14 created selwin: 0x40002d 07/04/2021 11:20:14 called initialize_xfixes() 07/04/2021 11:20:14 created selwin: 0x40002d 07/04/2021 11:20:14 called initialize_xfixes() 07/04/2021 11:20:14 client 1 network rate 523.3 KB/sec (18317.5 eff KB/sec) 07/04/2021 11:20:14 client 1 latency: 1.8 ms 07/04/2021 11:20:14 dt1: 0.0061, dt2: 0.0244 dt3: 0.0018 bytes: 15462 07/04/2021 11:20:14 link_rate: LR_LAN - 1 ms, 523 KB/s 07/04/2021 11:23:19 got closure, reason 1001 07/04/2021 11:23:19 rfbProcessClientNormalMessage: read: Connection reset by peer 07/04/2021 11:23:19 client_count: 0 07/04/2021 11:23:19 Restored X server key autorepeat to: 1 07/04/2021 11:23:19 Client 127.0.0.1 gone 07/04/2021 11:23:19 Statistics events Transmit/ RawEquiv ( saved) 07/04/2021 11:23:19 ServerCutText : 1 | 8/ 8 ( 0.0%) 07/04/2021 11:23:19 FramebufferUpdate : 234 | 0/ 0 ( 0.0%) 07/04/2021 11:23:19 LastRect : 21 | 252/ 252 ( 0.0%) 07/04/2021 11:23:19 tight : 430 | 313154/ 8603816 ( 96.4%) 07/04/2021 11:23:19 RichCursor : 1 | 1374/ 1374 ( 0.0%) 07/04/2021 11:23:19 TOTALS : 687 | 314788/ 8605450 ( 96.3%) 07/04/2021 11:23:19 Statistics events Received/ RawEquiv ( saved) 07/04/2021 11:23:19 KeyEvent : 30 | 240/ 240 ( 0.0%) 07/04/2021 11:23:19 PointerEvent : 92 | 552/ 552 ( 0.0%) 07/04/2021 11:23:19 FramebufferUpdate : 235 | 2350/ 2350 ( 0.0%) 07/04/2021 11:23:19 SetEncodings : 1 | 56/ 56 ( 0.0%) 07/04/2021 11:23:19 SetPixelFormat : 1 | 20/ 20 ( 0.0%) 07/04/2021 11:23:19 TOTALS : 359 | 3218/ 3218 ( 0.0%) 07/04/2021 11:23:19 destroyed xdamage object: 0x40002c 07/04/2021 11:23:19 Got connection from client 127.0.0.1 07/04/2021 11:23:19 other clients: 07/04/2021 11:23:19 Got 'ws' WebSockets handshake 07/04/2021 11:23:19 Got protocol: binary 07/04/2021 11:23:19 - webSocketsHandshake: using binary/raw encoding 07/04/2021 11:23:19 - WebSockets client version hybi-13 07/04/2021 11:23:19 Disabled X server key autorepeat. 07/04/2021 11:23:19 to force back on run: 'xset r on' (3 times) 07/04/2021 11:23:19 incr accepted_client=2 for 127.0.0.1:49534 sock=10 07/04/2021 11:23:19 Client Protocol Version 3.8 07/04/2021 11:23:19 Protocol version sent 3.8, using 3.8 07/04/2021 11:23:19 rfbProcessClientSecurityType: executing handler for type 1 07/04/2021 11:23:19 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 07/04/2021 11:23:19 Pixel format for client 127.0.0.1: 07/04/2021 11:23:19 32 bpp, depth 24, little endian 07/04/2021 11:23:19 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 07/04/2021 11:23:19 no translation needed 07/04/2021 11:23:19 Enabling NewFBSize protocol extension for client 127.0.0.1 07/04/2021 11:23:19 Enabling full-color cursor updates for client 127.0.0.1 07/04/2021 11:23:19 Using image quality level 6 for client 127.0.0.1 07/04/2021 11:23:19 Using JPEG subsampling 0, Q79 for client 127.0.0.1 07/04/2021 11:23:19 Using compression level 9 for client 127.0.0.1 07/04/2021 11:23:19 Enabling LastRect protocol extension for client 127.0.0.1 07/04/2021 11:23:19 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC) 07/04/2021 11:23:19 Using tight encoding for client 127.0.0.1 07/04/2021 11:23:19 client_set_net: 127.0.0.1 0.0000 07/04/2021 11:23:19 created xdamage object: 0x40002e 07/04/2021 11:23:24 client 2 network rate 663.8 KB/sec (17817.9 eff KB/sec) 07/04/2021 11:23:24 client 2 latency: 2.4 ms 07/04/2021 11:23:24 dt1: 0.0115, dt2: 0.0210 dt3: 0.0024 bytes: 20780 07/04/2021 11:23:24 link_rate: LR_LAN - 2 ms, 663 KB/s
  12. I'm having some kind of mapping issue with Sonarr. The shows are not making it to my folder for all the shows and it seems like I have some completed/incomplete folders that are duplicated. Sonarr seemed to be working fine until lately. Another thing is that when I start downloading shows in Sonarr my docker % of memory shows on the dashboard starts going up high....its at 65% but shouldn't be anywhere close to that. I dont know if some settings somehow got messed up or what. Everything SEEMS to be in order but its not working quite right.
  13. @lnxd since you have the same rx580 card I'm curious to know if the GPU statistics shows your gpu memory usage at around 50%? My GPU has 8GB but while it's at 100% its showing 4350MB being used. You would think the mining software could utilize all of it. Is that how yours is doing?
  14. Thanks! I'll run that next time it starts getting high. I suppose stopping docker and restarting it reset the issue, so I need to wait until it starts getting slow then run it at that time.
  15. Oh yeah, meant to say I updated the Stats app and it's awesome now. It looks great...I was just happy to have the data, even in text....but to have it look nice is just icing on the cake! Looks great!
  16. Is there a good way to see if that is happening? If I had this happening wouldnt I be downloading files that I then wouldnt be able to find? For instance if Radarr had a path that didnt match up with a share, where would the downloaded file go? Does it get stored in ram or something like that? 20GB should be plenty, I just increased it because the server was running slow....it got my speed back to normal. Hopefully I can get it fixed before it fills up again.
  17. I have that same Noctua CPU fan you do so I'd imagine it would run too hot if it was working a heavy load 24/7. I suppose I could move the server to a closet or something where I didnt care if all the fans were running 100%, panels off, fan blowing on it. BUT I really dont want to compromise my server with so much heat. Might be a good idea for a dedicated box! Man, I turned off the container for like 5 minutes and my current hashrate fell from like 33MH/s down to 15.3MH/s. They really hit it hard when you stop for a few minutes! Man, thanks for taking the time to put this together, it's pretty cool....I always like finding more ways for my server to be useful for more than movies lol. It's a great use of the wasted video card and doesnt put any strain on any other parts of the server. Awesome job man! If you decide to mess with other stuff a real good wallet stored on Unraid would be cool. One that also has mobile access. Coinomi has a Linux version....I suppose that could be made into a Unraid container. But I'd imagine theres better ones than Coinomi but its rated high and not really any fees except direct miner fees.
  18. I have 32GB of ram and on the dashboard it showed 77% under docker and my server started running slow. I turned off the docker, its ram utilization max was set up 20GB and I changed it to 25GB and reenabled it. Now the server is running fine and its showing 55% usage for docker. HOWEVER when I look in the docker tab in advanced mode and add up all of the apps usage its only around 1.5-2 GB so I'm barely using any of my ram. I do not have a VM. What could be causing this problem? I attached a diagnostics log.... Also, I'm running 6.9.1 tower-diagnostics-20210325-2228.zip
  19. Oh awesome, I didnt know I could pull it up like that....Thanks for the link! Well $70 a month would actually be more than I figured it would be. I thought it would be like half that. You have any thoughts on how long a GPU 'might' last running at 100% 24/7? Do you ever shut it down to give them a break? I wonder how much a entire computer can mine as opposed to just a GPU. Does anyone setup to have the processor and ram mine along with the GPU?
  20. Well I guess based on your temps I guess really dont need to worry about my processor and nvme. In your Stats app, should it look like the one your took a screen shot of in your original post.....or just black text? I dont really care how it looks but just mostly want to make sure its running correctly. Awesome apps man! I'm excited to be able to mine. I suppose with one GPU running I cant expect to make hardly anything but its kind of fun to have it doing something. Looks like the extra power will cost me about $12US per month. Any ideas on how much it might make over a month? Should I try out different pools and such? Some pools seem to mine a lot more than others but I suppose there is a balance between how much is mined vs how many miners are involved in the pool. Its been running 25-28MH/s
  21. I know it can run hotter than 70C and be okay, but I'm more concerned with it making the rest of the box hot. Right now, its been at 100% for just over a hour and is staying rock solid at 68C which I suppose it warmer than I'd like due to my processor and nvme drive both being directly above the GPU and have gone up about 8-10C. My hard drives are fine, they have only moved up 1C. processor is Xeon e5 2690v3 with a max operating temp of 89C and its staying steady at 52C (normally at 40C-45C) Samsung nvme has max operating temp of 70C and its staying steady at 48C (normally at 40C) I may lower my target temp a little and see how much louder the fans get....but it does sit in my living room so I try to keep it fairly quiet. Right now its not to bad with the fans at 50-55% I suppose my thought was to set the stop temp just a little higher than the target temp because if its not able to maintain temp then something must be wrong and it needs to stop mining.
  22. My gpu temp is at 68C which is my "target temp" my fan speed is only at around 55%. Does it run the fan just hard enough to maintain the temp right at the "Target Temp"?
  23. Sweet, its working now.....so in the mining container settings it says fan control "only works if privileged mode is enabled"......how do I set up privileged mode? Should I delete my ip from the thread? Maybe that isnt good to publish
  24. In your original post you have a image of your two GPU's with their temp and fan %, is that from your PheonixStats app? I have the app installed however it doesnt look anything like that and isnt pulling in the data when I go to webgui. My Webgui is just text with no data.