dnLL
-
Posts
219 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dnLL
-
-
I have a E3-1245 V6 from Intel. I don't see /dev/dri in unRAID. I'm using the onboard GPU with no monitor attached. Already made sure it was set to iGPU in the BIOS as primary. My motherboard is the E3C236D2I from AsRock. I'm running unRAID v6.6.5.
Without /dev/dri there is no point in setting the extra parameter in the Linuxserver.io's Plex docker as far as I know so I didn't do that part (yet). Any ideas?
-
On 12/7/2018 at 6:09 AM, jbrodriguez said:
As for auto, Unraid creates an SSL certificate and redirects http -> https transparently for the user, I'll check if that's still the case.
Or perhaps, new installs work a bit differently from older installs (fresh 6.6.x install vs upgrading to 6.6.x).
I started with unRAID 6.4 iirc and the default behavior was not to create a certificate while set to auto. https would be fully enabled only if you generated a certificate by yourself with the webui. After upgrading to 6.6 that was still the case but maybe a fresh installation is different. Either way, it's working perfectly, I can now easily shut down a VM if I need to.
-
19 hours ago, jbrodriguez said:
Hi, it's written in the FAQ, from a user standpoint (what should I do as an app user), instead of from plugin's view (auto means ssl).
The last version of the app always connects to the plugin via ssl, regardless of the Unraid setting, so it shouldn't be a problem
You already solved it by doing ssl=yes, but I'm not sure what issue you were having.
Were you unable to add the server ?
Were you unable to access the additional features the plugin provides ?
I was unable to add the server (the app by default was proposing an IPv6 server which is weird since IPv6 is disabled on my router and everywhere else, but even with entering my IPv4 it wouldn't see the server). SSL was disabled in unRAID (as it was by default on previous versions, not sure about now). I never enabled it until I had issues after downloading ControlR. By default SSL is set to Auto with no promoted certificate (so SSL is disabled with the Auto option).
Also, the FAQ says the following:
Quoteauto->add server via ip/hostname, https port (default is 443), secure switch on
Doesn't work if SSL isn't actually enabled (if you didn't promote a certificate, SSL won't work, the auto switch just sets it to No basically).
-
On 5/7/2018 at 5:58 AM, jbrodriguez said:
Oh ok, if you have SSL set to 'auto', the plugin interprets that ssl is on.
This needs to be pinned somewhere, I was so confused. By default unRAID has it set to Auto with no SSL certificate generated, so basically with default options your app doesn't work. I figured it out by actually creating a certificate and really going with https/ssl. I eventually changed it from Auto to Yes since I don't see disadvantage of using SSL anyway.
-
So I installed virt-viewer on my Windows desktop and edited my VM's XML configuration file overwriting the VNC graphics with spice:
<graphics type='spice' port='3001' autoport='no'> <listen type='address'/> </graphics>
I also installed spice-vdagent on the VM, not sure if it was a necessary step or not but I did anyway:
[vm-manjaro ~]# systemctl status spice-vdagentd ● spice-vdagentd.service - Agent daemon for Spice guests Loaded: loaded (/usr/lib/systemd/system/spice-vdagentd.service; indirect; vendor preset: disabled) Active: active (running) since Sat 2018-12-01 17:24:12 EST; 3s ago Process: 1619 ExecStart=/usr/bin/spice-vdagentd $SPICE_VDAGENTD_EXTRA_ARGS (code=exited, status=0/SUCCESS) Main PID: 1620 (spice-vdagentd) Tasks: 1 (limit: 2372) Memory: 360.0K CGroup: /system.slice/spice-vdagentd.service └─1620 /usr/bin/spice-vdagentd Dec 01 17:24:12 vm-manjaro systemd[1]: Starting Agent daemon for Spice guests... Dec 01 17:24:12 vm-manjaro systemd[1]: Started Agent daemon for Spice guests.
Finally, I made sure iptables was disabled. Trying to connect from my Windows desktop, I get the following:
C:\Program Files\VirtViewer v6.0-256\bin>remote-viewer.exe spice://192.168.1.246:3001/ --debug C:\Program Files\VirtViewer v6.0-256\bin> (remote-viewer.exe:17924): Gtk-WARNING **: Could not find signal handler 'virt_viewer_window_menu_change_cd_activate'. Did you compile with -rdynamic? (remote-viewer.exe:17924): virt-viewer-DEBUG: Opening display to spice://192.168.1.246:3001/ (remote-viewer.exe:17924): virt-viewer-DEBUG: Guest (NULL) has a spice display (remote-viewer.exe:17924): virt-viewer-DEBUG: After open connection callback fd=-1 (remote-viewer.exe:17924): virt-viewer-DEBUG: Opening connection to display at spice://192.168.1.246:3001/ (remote-viewer.exe:17924): virt-viewer-DEBUG: New spice channel 000000000443F830 SpiceMainChannel 0 (remote-viewer.exe:17924): virt-viewer-DEBUG: notebook show status 000000000433FE60 (remote-viewer.exe:17924): virt-viewer-DEBUG: main channel: failed to connect Could not connect to 192.168.1.246: No connection could be made because the target machine actively refused it. (remote-viewer.exe:17924): virt-viewer-DEBUG: Destroy SPICE channel SpiceMainChannel 0 (remote-viewer.exe:17924): virt-viewer-DEBUG: zap main channel
Same with the GUI, it says the target machine actively refuses the connection. I get the same error if I try a different port.
What am I doing wrong?
-
So I know this is an old thread but I was wondering if you still got it working on 6.6 or if there is anything new implemented that would make this even easier?
-
3 hours ago, John_M said:
But does it actually matter? If your server otherwise works normally you could just call it a strange quirk and live with it.
Actually it matters for my Check_MK server since it can't ping anything local outside the server currently (well it can apparently ping the chromecast which isn't exactly very interesting).
I'll try to reset the settings a little bit later and if that doesn't work... I will find a workaround I guess. I'm still quite intrigued since it was working when I added my ipmi to check_mk and I even added my desktop for testing purposes and it can't ping it anymore which is weird.
-
It doesn't work after a reboot either... ?
-
38 minutes ago, John_M said:
@dnLL Would you mind trying something for me, please? Go to Settings -> Network Settings in the GUI, and under the heading Interface eth0 set Enable bonding to Yes. You'll need to stop the Docker and VM services first to be able to do this - probably the easiest way is simply to stop the array. Leave the bonding mode set to active-backup and leave eth0 as the sole member of bond0, like this:
Now click the Apply button, then restart the array. Now do your ping test again and report back.
I notice your motherboard has two main NICs (plus the IPMI one). At the moment you're only using eth0 (the one using the i210 chip), and eth1 is unplugged. Have you decided how you want to use this second port?
EDIT:
I should add that my reason for suggesting that you enable bonding is because that appears to be the default unRAID setting, even if only a single NIC is present. One of my servers has only one NIC and has bridging enabled, but it also has bonding enabled (per the screenshot) and I have no problem pinging.
I remember playing with these settings so that might be the issue. I changed it and restarted the array but I noticed my SSH connection to the server wasn't interrupted or anything and it's still not working. I'm wondering if I need to reboot completely (I'm rebooting it right now, I'll check again once I'm back home later today).
The other NIC isn't used right now and I'm not sure I'm getting any benefit from using it... I have an ASRock Rack E3C236D2I motherboard. I get I could get 2 Gbit ethernet instead of 1 but... I'm limited by the speed of my HDDs at around 110 MB/s anyway (until I add SSD cache) and even if 2 different HDDs are being used, I rarely (I'd say never but I guess there are some very corner case scenarios) transfer files at full gigabit speed multiple times simultaneously.
-
On 5/26/2018 at 6:50 AM, John_M said:
Post your diagnostics zip.
On 5/26/2018 at 6:54 AM, bonienl said:Check if any firewall on these devices is interfering.
It's a simple IPMI port, I highly doubt there are any firewall and I'm not sure why the firewall would accept pings from all devices but the server and its VMs. But I'll do some more testing for sure.
-
5 hours ago, Tybio said:
Interesting, if you fire up a console, do you see any arp entries after you try to pinging outbound?
There we go.
root@server:~# arp -a DD-WRT (192.168.1.1) at 14:91:82:c4:6a:eb [ether] on br0 Chromecast (192.168.1.230) at 88:3d:24:22:13:54 [ether] on br0 ipmi (192.168.1.100) at d0:50:99:e1:db:ea [ether] on br0 root@server:~# ping 192.168.1.100 PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data. --- 192.168.1.100 ping statistics --- 9 packets transmitted, 0 received, 100% packet loss, time 8188ms root@server:~# ping 192.168.1.230 PING 192.168.1.230 (192.168.1.230) 56(84) bytes of data. 64 bytes from 192.168.1.230: icmp_seq=1 ttl=64 time=3.76 ms 64 bytes from 192.168.1.230: icmp_seq=2 ttl=64 time=5.03 ms 64 bytes from 192.168.1.230: icmp_seq=3 ttl=64 time=5.38 ms 64 bytes from 192.168.1.230: icmp_seq=4 ttl=64 time=4.54 ms --- 192.168.1.230 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 3.762/4.682/5.387/0.613 msThis is weird to be honest. From my desktop, no problem...
And it used to work from the Linux servers before. I didn't update the IPMI interface on my ASRock mobo (and don't see how that would be relevant anyway). Even the HTTP (ipmi) webgui used to be accessible from the server and its VMs, now it's not anymore...
-
I have a very small issue and have no idea what I changed to create the issue (it used to work properly).
I have multiple computers including my server on the same network hooked up to the same router. They all get a DHCP address from the router. From any computer on the network, I can do a local ping to any other computer or to the server. I can also ping the VMs, no issues. However, from the server and from the VM, same result: I can NOT ping any of the other computer on the network (I can ping the server/VMs from the server/VMs just fine however). I could understand the difficulties coming from the VMs but from the server itself I don't get it, plus it used to work in the past.
I'm not sure what that means but here are my network settings:
As for my router, I flashed the FW to factory default recently and it didn't change anything... now, it has a DHCP reservation for my server but that's about it.
Why can't my server ping the other devices on the network?
It you think it's unrelated completely to my unRAID configuration, let me know... but I have no issue with any other device on the network.
(SOLVED) iGPU transcoding: i915 driver present but /dev/dri not available
in General Support
Posted · Edited by dnLL
The board doesn't post when I put it onto onboard VGA rather than PCI Express as default.
I just updated to latest BIOS with any success. I can't enable the VGA or set the onboard as the default option over PCIE. I'm forced to clear the CMOS every time I try it. And if I put PCI-Express first with IGFX enabled, I just don't see /dev/dri.