Jump to content

Xaero

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Xaero

  • Rank
    Member
  1. Just a minor cosmetic bug when having loads of CPU cores: As you can see, anything past 18c/36t is a bit loopy.
  2. Xaero

    Samba extra configuration

    Samba configuration is notoriously counterintuitive. You need to ensure that the share is both NOT public and also has valid users listed. [Dropbox] path = /mnt/disks/dropbox comment = browseable = yes public = no valid users = user1 writeable = yes vfs objects = Should have the intended behavior. Note that by having browseable set to yes you will SEE the share with all user accounts, but only be able to explore it when authenticated as user1. Other users, including anonymous (and the smbtree, by proxy) will be able to see the share itself, but not it's contents.
  3. Xaero

    Can't see VM on network

    I'm scratching my head here. I've got an ArchLinux guest OS and have everything setup. I'm trying to setup VNC on the ArchLinux guest OS as the Qemu VNC is still pretty archaic and doesn't support dynamic resolution changes or scaling very well. I've got the following set in my VM's settings: and this is what my routes look like on the network page: If I use the built-in VNC viewer I can see the VM and it connects; but to the QEMU hosted VNC (obviously) However I cannot ping the VM itself, or try to connect to the VM's VNC server. What am I missing? EDIT: if I use ip addr I can retrieve the ip address of the VM and connect successfully to the VNC using the IP. So it's not my network configuration within unraid, I think.,
  4. Xaero

    [Support] binhex - rTorrentVPN

    Had to quit using Flood entirely. Doesn't seem to work at all anymore. Not sure why. I did like flood. Also, as a request - I'd like to see the rpc socket also forwarded so that applications like Electorrent can use the docker. EDIT: Nevermind, ruTorrent isn't working now either. Whelp. And that's after rolling back a version. Gonna try one of the other base rtorrent dockers and a separate flood/rutorrent docker from dockerhub. Not sure what's happening or why at this point.
  5. Xaero

    [Support] GitLab-CE

    This is one memory hungry boi. 32gb of ram and Gitlab wants 27% of it with zero repos. Wow.
  6. Xaero

    [Support] binhex - rTorrentVPN

    I've actually switched to using an SCGI file and still have the same problem. It's driving me up a wall. I need to poke around logs and see if I can figure out what's happening.
  7. I just updated MineOS-Node and have lost basically all functionality. I made a backup of my server files of course, but when it starts the container and I login to the WebUI neither of my servers show up. If I try creating a server it isn't added to the list either. Nothing meaningful in the logs: USER_NAME not provided; defaulting to "mc" Created user: mc (uid: 1000) Generating Self-Signed SSL... 2018-11-05 23:19:20,989 CRIT Supervisor running as root (no user in config file) 2018-11-05 23:19:20,989 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing 2018-11-05 23:19:21,001 INFO RPC interface 'supervisor' initialized 2018-11-05 23:19:21,001 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-11-05 23:19:21,002 INFO supervisord started with pid 1 2018-11-05 23:19:22,004 INFO spawned: 'mineos' with pid 32 2018-11-05 23:19:23,560 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-11-05 23:29:17,515 WARN received SIGTERM indicating exit request 2018-11-05 23:29:17,516 INFO waiting for mineos to die 2018-11-05 23:29:17,529 INFO stopped: mineos (terminated by SIGTERM) USER_NAME not provided; defaulting to "mc" mc already exists. 2018-11-05 23:29:23,087 CRIT Supervisor running as root (no user in config file) 2018-11-05 23:29:23,087 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing 2018-11-05 23:29:23,098 INFO RPC interface 'supervisor' initialized 2018-11-05 23:29:23,098 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-11-05 23:29:23,098 INFO supervisord started with pid 1 2018-11-05 23:29:24,101 INFO spawned: 'mineos' with pid 11 2018-11-05 23:29:25,494 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Note that I initiated a restart of the docker in this log. EDIT: Deleting the server profiles from the servers folder, restarting the docker and then creating instances named for each server followed by copying the files back over and restarting the docker again has resolved this. Pretty ugly upgrade process but at least it works.
  8. Xaero

    [Support] binhex - rTorrentVPN

    I meant in the docker settings And yes, it's perfectly acceptable to just ignore the WebUI reporting 100% CPU usage as long as the Unraid WebUI is not ALSO reporting 100% cpu usage. I'm nitpicky though so I like everything to look perfect lol.
  9. Currently rocking this: The extra NIC is for planned expansion, but may end up scraping and going with a single 10gbe and shifting the network to 10gbe instead. The two CPUs detect that way because they are engineering samples; 12 core, 24 thread Xeon E5-2658v3 CPUs.
  10. Xaero

    [Support] binhex - rTorrentVPN

    Try setting "-t" as an extra parameter in the advanced tab and seeing if you still see the abnormal CPU usage reporting.
  11. Xaero

    [Support] binhex - rTorrentVPN

    Any way you could set tty: true to address the CPU usage bug in rtorrent with curl? The fix was applied in another rtorrent docker and seems to have fixed the 100% core usage from rtorrent. Edit: Switching to the advanced tab, and adding "-t" to the extra parameters addresses this issue as well. No longer is one core stuck at 100% usage. Edit2: I realize you are using TMUX to work around that issue; so the -t or tty: true quirk is unapplicable since tmux *should* appear as a TTY to rtorrent. May I also suggest switching to a socket file instead of the ports based system? It seems more stable to me for Flood at least. I've edited the /home/nobody/rtorrent.sh and /home/nobody/flood.sh to wait for the creation of the rpc.socket file like so: until [ -e /tmp/rpc.socket ]; do sleep 0.1 done And updated the config files as appropriate to use the rpc.socket instead of the network settings.
  12. Xaero

    Dynamix - V6 Plugins

    Should have probably mentioned; I was experiencing the same problem on Stable as well, and decided to update to see if it would fix it. Edit: Updated my post with a workaround for this chipset. Seems like a problem with the way lm_sensors uses chip names for filtering. "chip coretemp-isa-0000" works fine but "chip nct7904-i2c-0-2e" does not. This should probably be filed upstream with lm_sensors devs. For now commenting out the chip filters seems to work okay.
  13. Xaero

    Dynamix - V6 Plugins

    So I have a new build running the latest Unraid 6.6.0 rc-4; and I'm having issues with the temperature plugin. The sensors correctly read inside the plugin like so: However after selecting desired sensors like this: And then hitting "Apply" The sensors all disappear like so: Hitting "Rescan" and done have no effect, and all of the sensors on the dashboard also disappear (fan speeds) Running "sensors" in the terminal gives this output: The content of that file looks like this after hitting Apply: If I delete the file, and then run sensors this is the output I get: If I comment out the lines in the config file "chip nct7904-i2c-0-2e" then it works. Not sure if this is a proper fix but its working for now. Hopefully the developer of this plugin can adopt a solution:
  14. Xaero

    6.6 will include QEMU 2.12?

    That was the point of my post: To show the quoted user where the setting is on the interface. It's easier to show with a screengrab than it is to say "yeah at the bottom of the page on the left side of the footer look for the theme dropdown and click it, you can pick a light theme there."