-
Posts
180 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JustOverride
-
-
18 hours ago, Jamaica1985 said:
I actually have experienced this in version 6.10.2. It fixed itself by refreshing and/or closing the window and re-opening it, restarting the server. The issue hasn't come back. I'm still on version 6.10.2.
I will update later.Updated to 6.10.3 without issues. -
6 minutes ago, Dschnell89 said:
Is there a guide to migrate from the deprecated Bitwarden_rs to Vaultwarden in unraid docker?
Not that I'm aware of.
However, you could just export your passwords, and import them on VW.
-
2 minutes ago, je82 said:
I am using cloudflare, maybe ill start with 2FA, i just feel like its very bothersome having to 2FA since i've configured my webplugin to time out after 5 minutes, having to 2FA everytime seems a little over the top. I just dont want some script to be able to sit and bruteforce my install for 2 years straight but considering my password is over 30 characters long , small + big + weird characters and its highly unlikely anyone would get through i guess.
You should still change it every year at least.
-
On 6/2/2022 at 12:43 AM, MAM59 said:
the 2nd log (receive errors, syn flooding etc) would tell me to check the cables (and more important the plugs).
Looks like you are having a contact problem on either receive or sending side.
Note that modern RJ45 plugs/outlets are a little bit longer than before. When put into an "old" card/switch port, they dont fit really tightly anymore. The same is true for old cables in new ports, they are somewhat a bit loose.
Try to move it and see if the error shows up.
If it does, find a working position and use a bit of hot glue to keep the cable in place.
(yeah seems to be a very basic and lame advice, but really, its the 99% solution)
Of course these errors also can show up from broken network cards / switches or wrong cables (10Gbe UTP cables are really complicated to buy working ones. The cables are usuall ok, but the plugs are a mess and if the lenght goes over 30m, its just plain luck if they work and if they work stable over the time. Better consider going fiber in this case)
Sadly, you did not tell us, what kind of card and mobo this is.
Thanks for the info, as it is not a persistent issue I may be able to live with it until I upgrade to 10G RJ45. I have a 'HP 530SFP+ 10Gb Dual Port PCIe Ethernet Adapter Card 656244-001 w/ SFP' on a EVGA X79 FTW. -
As of right now, on NextCloud version 24.0.1, it appears that it only uses CPU (mine doesn't have intergraded graphics). I do have a graphics card that I have setup for docker use, and have tried to add the extra parameters and variables as suggested here but for Nextcloud with no success.
It appears that Next cloud is using a plugin for the video playback/streaming.
QuoteVideo player
by Björn Korella MIT-licensed
A responsive video player using a skinned version of Video.js
Based on this app: https://apps.owncloud.com/content/show.php/Video+Js?content=159670 Video.js: http://videojs.com/ Skin: https://github.com/cabin/videojs-sublime-skin
Has anyone setup NC to use a graphics card? Does it work with an iGPU?
Thanks.
-
On 4/22/2020 at 7:16 PM, danioj said:
Worked like a charm. I think this should be noted somewhere as being "best practice" for new people setting the app up.
Agree!
I was looking for this too. Honestly, most people setting this up won't need to have the admin panel public facing. In fact, I would prefer a switch on the docker itself to just disable it all together.
-
I have been getting the errors below. This started after upgrading to 6.10, but I have also started to use Swag along with some other vaultwarden and nextcloud. I happen to caught this once, when it happens the unraid dashboard is unresponsive (dockers appear to continue to work fine). This issue also stops after a while. I appreciate any assistance/feedback. I have removed what I thought was identifiable info, if you need any additional details let me know.
May 29 18:46:24 ServerName kernel: vetha2fb6ef: renamed from eth0 May 29 18:46:24 ServerName avahi-daemon[7235]: Interface vethbb#####.IPv6 no longer relevant for mDNS. May 29 18:46:24 ServerName avahi-daemon[7235]: Leaving mDNS multicast group on interface vethbb#####.IPv6 with address v6IPaddress##. May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethbb#####) entered disabled state May 29 18:46:24 ServerName kernel: device vethbb##### left promiscuous mode May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethbb#####) entered disabled state May 29 18:46:24 ServerName avahi-daemon[7235]: Withdrawing address record for v6IPaddress##1 on vethbb#####. May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered blocking state May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered disabled state May 29 18:46:24 ServerName kernel: device vethe##### entered promiscuous mode May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered blocking state May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered forwarding state May 29 18:46:24 ServerName kernel: eth0: renamed from veth8dcd8d2 May 29 18:46:24 ServerName kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe#####: link becomes ready May 29 18:46:26 ServerName avahi-daemon[7235]: Joining mDNS multicast group on interface vethe#####.IPv6 with address fe80::d8d9:e1ff:fe88:8a3. May 29 18:46:26 ServerName avahi-daemon[7235]: New relevant interface vethe#####.IPv6 for mDNS. May 29 18:46:26 ServerName avahi-daemon[7235]: Registering new address record for fe80::d8d9:e1ff:fe88:8a3 on vethe#####.*. May 29 19:24:31 ServerName kernel: br-(rand###/letters): port 3(veth3####b9) entered disabled state May 29 19:24:31 ServerName kernel: vethbc7f3e1: renamed from eth0 May 29 19:24:31 ServerName avahi-daemon[7235]: Interface veth3####b9.IPv6 no longer relevant for mDNS. May 29 19:24:31 ServerName avahi-daemon[7235]: Leaving mDNS multicast group on interface veth3####b9.IPv6 with address v6IPaddress##2. May 29 19:24:31 ServerName kernel: br-(rand###/letters): port 3(veth3####b9) entered disabled state May 29 19:24:31 ServerName kernel: device veth3####b9 left promiscuous mode May 29 19:24:31 ServerName kernel: br-(rand###/letters): port 3(veth3####b9) entered disabled state May 29 19:24:31 ServerName avahi-daemon[7235]: Withdrawing address record for v6IPaddress##2 on veth3####b9. May 29 19:25:58 ServerName emhttpd: spinning down /dev/sdh May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered blocking state May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:28:11 ServerName kernel: device vethe##### entered promiscuous mode May 29 19:28:11 ServerName kernel: eth0: renamed from veth140669f May 29 19:28:11 ServerName kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe#####: link becomes ready May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered blocking state May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered forwarding state May 29 19:28:13 ServerName avahi-daemon[7235]: Joining mDNS multicast group on interface vethe#####.IPv6 with address fe80::c4ee:cdff:fe96:b1db. May 29 19:28:13 ServerName avahi-daemon[7235]: New relevant interface vethe#####.IPv6 for mDNS. May 29 19:28:13 ServerName avahi-daemon[7235]: Registering new address record for fe80::c4ee:cdff:fe96:b1db on vethe#####.*. May 29 19:33:01 ServerName emhttpd: spinning down /dev/sdi May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:34:01 ServerName kernel: veth140669f: renamed from eth0 May 29 19:34:01 ServerName avahi-daemon[7235]: Interface vethe#####.IPv6 no longer relevant for mDNS. May 29 19:34:01 ServerName avahi-daemon[7235]: Leaving mDNS multicast group on interface vethe#####.IPv6 with address fe80::c4ee:cdff:fe96:b1db. May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:34:01 ServerName kernel: device vethe##### left promiscuous mode May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:34:01 ServerName avahi-daemon[7235]: Withdrawing address record for fe80::c4ee:cdff:fe96:b1db on vethe#####. May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethad56df4) entered blocking state May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethad56df4) entered disabled state
May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 108 May 30 16:33:54 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:54 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 92 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 124 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 200 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 700 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 180 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 596 May 30 16:34:53 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:53 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 340 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 948 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 324 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:19 ServerName kernel: net_ratelimit: 9 callbacks suppressed May 30 16:35:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:19 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 1316 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 124 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 236 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 340 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 348 May 30 16:35:58 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 116 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 372 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 724 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 596 May 30 16:36:42 ServerName kernel: net_ratelimit: 1 callbacks suppressed May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 260 May 30 16:36:47 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:47 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:37:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:37 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:37 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 688 May 30 16:38:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:59 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:59 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 656 May 30 16:39:06 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:06 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 324 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 196 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 372 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 724 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 1496 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 536 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 84 May 30 17:11:11 ServerName kernel: TCP: request_sock_TCP: Possible SYN flooding on port ####. Sending cookies. Check SNMP counters.
[2022-05-30 00:41:13.920][request][INFO] GET /admin/diagnostics [2022-05-30 00:41:14.951][response][INFO] (diagnostics) GET /admin/diagnostics => 200 OK [2022-05-30 00:49:31.496][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:53710. [2022-05-30 00:49:31.518][request][INFO] GET /api/accounts/revision-date [2022-05-30 00:49:31.518][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 00:49:31.566][request][INFO] POST /identity/connect/token [2022-05-30 00:49:31.568][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 00:49:31.617][request][INFO] GET /api/sync [2022-05-30 00:49:31.619][response][INFO] (sync) GET /api/sync?<data..> => 200 OK [2022-05-30 01:05:47.537][request][INFO] POST /identity/connect/token [2022-05-30 01:05:47.539][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 01:05:47.576][request][INFO] GET /api/accounts/revision-date [2022-05-30 01:05:47.576][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 01:05:47.584][request][INFO] GET /api/sync [2022-05-30 01:05:47.586][response][INFO] (sync) GET /api/sync?<data..> => 200 OK [2022-05-30 01:20:21.381][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:42682. [2022-05-30 01:20:21.448][request][INFO] GET /api/accounts/revision-date [2022-05-30 01:20:21.449][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 02:57:14.651][request][INFO] GET /api/accounts/revision-date [2022-05-30 02:57:14.652][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 03:04:52.544][request][INFO] POST /identity/connect/token [2022-05-30 03:04:52.546][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 03:04:52.627][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:47352. [2022-05-30 03:04:52.633][request][INFO] GET /api/accounts/revision-date [2022-05-30 03:04:52.633][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 03:41:44.006][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:45732. [2022-05-30 03:41:44.027][request][INFO] GET /api/accounts/revision-date [2022-05-30 03:41:44.028][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 03:53:29.595][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:48368. [2022-05-30 03:53:29.677][request][INFO] GET /api/accounts/revision-date [2022-05-30 03:53:29.678][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 09:57:05.847][request][INFO] POST /identity/connect/token [2022-05-30 09:57:05.850][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 09:57:05.907][request][INFO] GET /api/accounts/revision-date [2022-05-30 09:57:05.908][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 10:53:24.734][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:38604. [2022-05-30 10:53:24.806][request][INFO] GET /api/accounts/revision-date [2022-05-30 10:53:24.806][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 11:41:44.836][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:53574. [2022-05-30 11:41:44.905][request][INFO] GET /api/accounts/revision-date [2022-05-30 11:41:44.906][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 12:45:37.765][request][INFO] POST /identity/connect/token [2022-05-30 12:45:37.767][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 12:45:37.835][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:43316. [2022-05-30 12:45:37.841][request][INFO] GET /api/accounts/revision-date [2022-05-30 12:45:37.841][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 12:57:28.374][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:35930. [2022-05-30 12:57:28.395][request][INFO] GET /api/accounts/revision-date [2022-05-30 12:57:28.396][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 14:12:21.811][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:46842. [2022-05-30 14:12:21.838][request][INFO] GET /api/accounts/revision-date [2022-05-30 14:12:21.839][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 16:10:44.365][request][INFO] POST /identity/connect/token [2022-05-30 16:10:44.367][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 16:10:44.446][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:50864. [2022-05-30 16:10:44.504][request][INFO] GET /api/accounts/revision-date [2022-05-30 16:10:44.504][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 16:51:18.227][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:54980. [2022-05-30 16:51:18.251][request][INFO] GET /api/accounts/revision-date [2022-05-30 16:51:18.251][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 17:12:43.792][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:42284. [2022-05-30 17:12:43.865][request][INFO] GET /api/accounts/revision-date [2022-05-30 17:12:43.865][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 17:34:14.676][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:40482. [2022-05-30 17:34:14.744][request][INFO] GET /api/accounts/revision-date [2022-05-30 17:34:14.744][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 17:46:57.416][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:55264. [2022-05-30 17:46:57.492][request][INFO] GET /api/accounts/revision-date [2022-05-30 17:46:57.493][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 20:45:11.352][request][INFO] POST /identity/connect/token [2022-05-30 20:45:11.356][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 20:45:11.443][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:33428. [2022-05-30 20:45:13.471][request][INFO] GET /api/accounts/revision-date [2022-05-30 20:45:13.471][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 21:38:03.216][request][INFO] GET /admin [2022-05-30 21:38:03.216][response][INFO] (admin_login) GET /admin/ [2] => 200 OK [2022-05-30 21:38:33.253][request][INFO] POST /admin [2022-05-30 21:38:33.254][response][INFO] (post_admin_login) POST /admin/ => 303 See Other [2022-05-30 21:38:33.309][request][INFO] GET /admin [2022-05-30 21:38:33.310][response][INFO] (admin_page) GET /admin/ => 200 OK
-
This does not appear to be working on unraid 6.10. Can we expect an update ? Or do we just need to update the icons location download?
Thanks for all your videos by the way.
-
12 minutes ago, Zonediver said:
Thanks for the link, but how shall i do this?
I dont know the error - so how shall i describe it?
The Sys doesnt boot - why? I dont know...
I updated my Flash directly over the web-GUI from 6.9.2 to 6.10
Explain what happens after you press the power button, take pictures of everything that comes up on the screen, where it hangs/resets/shuts off. Post it on the link provided above.
-
The amount of brave people without password for the root account is scary.
- 3
- 1
-
9 hours ago, ezhik said:
Upgraded two systems, no issues. To those who are running nvidia cards and the nvidia plugin, it was a smooth sail to upgrade. MUCH better than earlier versions.
Cheers.
Yea, I was running the plugin but it wasn't smooth sailing for me. Needed to remove it, re-install, and then select the version that would be applicable to my card as the latest one doesn't support it. (I will be upgrading the graphics card soon). But once that was sorted everything is going super well for me for me so far. Happy to see I can use WSD again without getting cores stuck to 100%. Now all I'm missing from Unraid is ZFS, VM snapshots/backups, and ARC and/or L2ARC #myUnraidWishlist. -
Upgraded from 6.9.2 to 6.10 no issues, except plex won't start, getting message of 'Execution error, Bad parameter', and receiving a message from the 'Fix common issues' plugging that 'preclear.disk.plg Not Compatible with Unraid version 6.10.0'. Other than that, Unraid is working well and the other dockers and VM's I've tested work fine. I'll look into the plex issue in a moment, and just have to wait for the the preclear plugging to be updated.
-
Anyone here really excited to update, but can't because you need the internet to continue to work from home?
No? Just me then?
Thanks for the update Limetech!
- 2
-
I've got to say that I been playing around with Truenas, and ARC and L2ARC is really awesome. The using spare RAM as cache is really awesome. Hope we get something like this in Unraid.
-
Really? Wow, I don't see where that toggle came from then. Either way, then there is a lot of room for improvement.
-
We currently have 'all' or 'started' VM's and dockers views. Can we add an option for only pinned/favorite VM's/dockers to show? I looked around and wasn't able to find a plugin or something that does this, unless I missed it.
-
I understand that it could be bad to allow a VM to start without the array because the Unraid license model (as some of you pointed out). However, if Unraid sees it has a PRO license active then it should not be a problem. Perhaps, make a new license "PRO+" and then we can simply pay for the additional features we want. A "system pool" can and should be added for VM's and Docker to be able to run independently from the array (a lot of users already run their systems this way). At the end of the day, if it can be done great, if not that's fine. This is merely a feature request. If not I'll just have to run a separate system, but its not something I'm looking to do. So if ultimately the problem has to do with licensing and the possibility of Unraid being 'cheated' out of licensing, then just add a new license that allows for this. Is there something else I'm missing?
-
On 2/25/2022 at 7:56 AM, BVD said:
Reaffirming the home assistant note - I'd not really thought of it a great deal until recently, as we just finished purchasing and moving into our new home about 4 months ago, and have finally gotten it to the stage where we're ready to implement some of our plans for the place (connected garage door, motion detection and temp control, soil monitoring for the garden, etc)...
Say you suffer a double failure - you want to minimize IO during the rebuild to mitigate (as much as one can) the potential for a third failure during reconstruction, so you start the array in maintenance mode. With 16TB drives becoming more commonplace, 20TB drives now available, and 24TB+ drives on the horizon, rebuild times are only going to get longer and longer. If we average 150MB/s across the entirety of reconstruction (whichever then is wildly optimistic), you're looking at ~1.5-2 days downtime.
Not a huge deal for a media server. But for critical needs (like heating and cooling, home security, many others), thatd feel like a lifetime.
I agree. Honestly I don't see why VM's can't run without the array, I really don't. I thought about getting a separate machine, but that would defeat the point of consolidating equipment.
-
+1
All these options should be the default as it would be more secure. Then instead a toggle for anyone having issues or running older hardware.
-
Working on my array at the moment, upgrading/changing disks makes me wish that stopping the array does not mean I will lose internet if the computer isn't being reset. This makes me want to actually have additional hardware to run the internet, but then one of the point of unraid was to consolidate hardware. I really don't see why this haven't been added if the VM (really all I care about is at least pfsense or any other internet-like VM) does not have any dependencies from the array. If the reason money related, or something like that, I wouldn't mind paying for "plus" features and maybe additional features can be added in the future. Just don't make it a subscription and I'll be happy.
+1 -
I believe this is showing you what the size of the cache drive is. Anyone feel free to correct me on this. I do not see anything wrong with your setup, and will work as you expect it to. Note, you will be able to still write to the drive after the 1T, it will simply start to write to the array as the cache would be full.
-
4 minutes ago, kalind said:
hi there .. sorry if below queries are already answered .. but I couldn't find proper answers anywhere..
1) We are going to switch to 10 or 20Gbps network. is unRaid capable for such fast read/write speed.?? As per my knowledge wright speed depends on cache speed and read speed depend on data drive ( hdd or ssd ) speed.. is this information correct ? or there is a way to achieve very fast read/write speed. ??
2) As mover runs, does is copy data or Move data .. if it copy data then it may possible to read the same data from cache .. otherwise it need to access it through data drive.
1) UNRAID is capable of delivery those speeds as long as your setup is configure correctly with the right hardware. UNRAID is not the limiting factor.
2) The Mover, moves data from the cache drives to the array. I'm not sure what you mean by "need to access it through data drive". It will simply move it from the cache drive to the array. -
Great job! Hope it gets baked into UNRAID.
- 1
-
Quote
Other Changes
We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core.
This will be fixed in Unraid v6.10.
- 2
- 1
[Plugin] CA Application Auto Update
in Plugin Support
Posted
Thanks @Squid, exactly what I was looking for. Making my unraid more and more automated so that 'everything just works' and I have less and less to do on it.