w^w
-
Posts
43 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by w^w
-
-
On 5/29/2020 at 1:39 AM, CorneliousJD said:
Is your ALLOWED_HOST variable set to *? If not set it back to * and try again, also see known issues about linked recipies as well, it is known to hang currently when trying to link a recipe.
1/2 is supported just fine but ½ (the actual symbol) is not.
e.g. the following are fine
0.5 cup water
1/2 cup water
the following is NOT
½ cup water
The last one will not work becuase it cannot proccess that as a proper quantity.
Hi @CorneliousJD. If you set openeats database collation to "utf8_general_ci" you can use "½ cup water".
-
@ljm42thanks for this detailed info about LAN-LAN config. Based on your work I successfully configured Server-Server feature. Have one question, is it necessary to have two different ports (52001 on unraid1 and 52002 on unraid2) instead one?
-
On 12/19/2019 at 10:48 PM, bonienl said:
Below an example configuration
It is mandatory to define a local endpoint (main server) and a peer endpoint (backup server). These endpoints can be a URL or a (public) IP address of the server.
When the main server is behind a NAT router then port forwarding must be set on the router.
The same is true for a NAT router used at the backup server (peer) side.
@bonienl thanks for this screenshoot but this is only configuration for "main server", could you post screenshoot about "backup server" settings? I'm asking about it because I'm struggling with this for many hours.
I will be very grateful. Thank you.
-
I like constantly expanding unRAID possibilities.
I would like to have nvidia and dvb support in one system.
-
16 hours ago, balsman225 said:
I’ve moved all my containers to a dedicated VLAN (br0.7) similar to what @Hoopster mentioned. Been working great after moving everything over and getting communication working. No trace logs and super solid on 6.7.2
So you don't have any docker on bridge or host iterface?
-
After couple of hours, call trace shows up:
Nov 27 16:46:32 unRAID kernel: WARNING: CPU: 7 PID: 0 at net/netfilter/nf_conntrack_core.c:977 __nf_conntrack_confirm+0x9f/0x5c4 Nov 27 16:46:32 unRAID kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT xt_nat ip6table_mangle ip6table_nat iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_MASQUERADE iptable_filter iptable_nat nf_nat ip_tables xfs md_mod nct6775 hwmon_vid wireguard ip6_udp_tunnel udp_tunnel rsnvme(PO) av201x(O) si2157(O) si2183(O) tbsecp3(O) tas2101(O) input_leds hid_logitech_hidpp led_class i2c_mux x86_pkg_temp_thermal dvb_core(O) intel_powerclamp videobuf2_vmalloc(O) videobuf2_memops(O) coretemp videobuf2_common(O) kvm_intel kvm videodev(O) btusb igb crct10dif_pclmul crc32_pclmul crc32c_intel btrtl mc(O) btbcm btintel i2c_i801 i2c_algo_bit ghash_clmulni_intel bluetooth i2c_core aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate nvme nvme_core intel_uncore hid_logitech_dj intel_rapl_perf ecdh_generic ecc cdc_acm video backlight ahci ie31200_edac libahci thermal button fan Nov 27 16:46:32 unRAID kernel: CPU: 7 PID: 0 Comm: swapper/7 Tainted: P O 5.3.11-Unraid #1 Nov 27 16:46:32 unRAID kernel: Hardware name: ASUSTeK COMPUTER INC. P10S-M WS Series/P10S-M WS Series, BIOS 4401 03/05/2018 Nov 27 16:46:32 unRAID kernel: RIP: 0010:__nf_conntrack_confirm+0x9f/0x5c4 Nov 27 16:46:32 unRAID kernel: Code: 89 ea 89 c6 41 89 c4 49 c1 ef 20 44 89 ff 45 89 fe e8 c8 ee ff ff 48 8b 4c 24 08 84 c0 75 b1 48 8b 85 80 00 00 00 a8 08 74 26 <0f> 0b 44 89 e6 44 89 ff 45 31 ed e8 be e6 ff ff be 00 02 00 00 48 Nov 27 16:46:32 unRAID kernel: RSP: 0018:ffffc90000214948 EFLAGS: 00010202 Nov 27 16:46:32 unRAID kernel: RAX: 0000000000000188 RBX: ffffffff8208ed40 RCX: ffff888bc4151458 Nov 27 16:46:32 unRAID kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffffff82009558 Nov 27 16:46:32 unRAID kernel: RBP: ffff888bc4151400 R08: 00000000e988b712 R09: ffff888fe302f7a0 Nov 27 16:46:32 unRAID kernel: R10: 0000000000000158 R11: ffffffff8208ed40 R12: 000000000000a218 Nov 27 16:46:32 unRAID kernel: R13: 0000000000000000 R14: 00000000000063d6 R15: 00000000000063d6 Nov 27 16:46:32 unRAID kernel: FS: 0000000000000000(0000) GS:ffff88903fbc0000(0000) knlGS:0000000000000000 Nov 27 16:46:32 unRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 27 16:46:32 unRAID kernel: CR2: 000055c525cf1000 CR3: 000000000200a006 CR4: 00000000003606e0 Nov 27 16:46:32 unRAID kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Nov 27 16:46:32 unRAID kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Nov 27 16:46:32 unRAID kernel: Call Trace: Nov 27 16:46:32 unRAID kernel: <IRQ> Nov 27 16:46:32 unRAID kernel: nf_confirm+0xc8/0xd4 Nov 27 16:46:32 unRAID kernel: nf_hook_slow+0x39/0x8e Nov 27 16:46:32 unRAID kernel: ip_local_deliver+0xad/0xdc Nov 27 16:46:32 unRAID kernel: ? ip_protocol_deliver_rcu+0x176/0x176 Nov 27 16:46:32 unRAID kernel: ip_sabotage_in+0x4e/0x58 Nov 27 16:46:32 unRAID kernel: nf_hook_slow+0x39/0x8e Nov 27 16:46:32 unRAID kernel: ip_rcv+0x8e/0xbe Nov 27 16:46:32 unRAID kernel: ? ip_rcv_finish_core.isra.0+0x2fa/0x2fa Nov 27 16:46:32 unRAID kernel: __netif_receive_skb_one_core+0x6f/0x90 Nov 27 16:46:32 unRAID kernel: netif_receive_skb_internal+0x79/0x94 Nov 27 16:46:32 unRAID kernel: br_pass_frame_up+0x125/0x147 Nov 27 16:46:32 unRAID kernel: ? br_port_flags_change+0x29/0x29 Nov 27 16:46:32 unRAID kernel: br_handle_frame_finish+0x350/0x391 Nov 27 16:46:32 unRAID kernel: ? br_pass_frame_up+0x147/0x147 Nov 27 16:46:32 unRAID kernel: br_nf_hook_thresh+0xa3/0xc3 Nov 27 16:46:32 unRAID kernel: ? br_pass_frame_up+0x147/0x147 Nov 27 16:46:32 unRAID kernel: br_nf_pre_routing_finish+0x263/0x28a Nov 27 16:46:32 unRAID kernel: ? br_pass_frame_up+0x147/0x147 Nov 27 16:46:32 unRAID kernel: ? br_handle_local_finish+0xe/0xe Nov 27 16:46:32 unRAID kernel: ? nf_nat_ipv4_in+0x1e/0x49 [nf_nat] Nov 27 16:46:32 unRAID kernel: ? br_handle_local_finish+0xe/0xe Nov 27 16:46:32 unRAID kernel: br_nf_pre_routing+0x3d9/0x400 Nov 27 16:46:32 unRAID kernel: ? br_nf_forward_ip+0x38f/0x38f Nov 27 16:46:32 unRAID kernel: br_handle_frame+0x2a5/0x2ed Nov 27 16:46:32 unRAID kernel: ? br_pass_frame_up+0x147/0x147 Nov 27 16:46:32 unRAID kernel: __netif_receive_skb_core+0x4b1/0x813 Nov 27 16:46:32 unRAID kernel: __netif_receive_skb_one_core+0x38/0x90 Nov 27 16:46:32 unRAID kernel: netif_receive_skb_internal+0x79/0x94 Nov 27 16:46:32 unRAID kernel: napi_gro_receive+0x44/0x7b Nov 27 16:46:32 unRAID kernel: igb_poll+0xb97/0xbbd [igb] Nov 27 16:46:32 unRAID kernel: net_rx_action+0x107/0x26c Nov 27 16:46:32 unRAID kernel: __do_softirq+0xc9/0x1d3 Nov 27 16:46:32 unRAID kernel: irq_exit+0x47/0x86 Nov 27 16:46:32 unRAID kernel: do_IRQ+0xb2/0xc8 Nov 27 16:46:32 unRAID kernel: common_interrupt+0xf/0xf Nov 27 16:46:32 unRAID kernel: </IRQ> Nov 27 16:46:32 unRAID kernel: RIP: 0010:cpuidle_enter_state+0xe8/0x1f0 Nov 27 16:46:32 unRAID kernel: Code: ff 45 84 ff 74 1d 9c 58 0f 1f 44 00 00 0f ba e0 09 73 09 0f 0b fa 66 0f 1f 44 00 00 31 ff e8 2f 25 ba ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 ea 00 00 00 49 63 cc be ff ff ff 7f 48 ba ff ff ff Nov 27 16:46:32 unRAID kernel: RSP: 0018:ffffc900000d7e90 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdc Nov 27 16:46:32 unRAID kernel: RAX: ffff88903fbe0ac0 RBX: ffff88903fbea200 RCX: 000000000000001f Nov 27 16:46:32 unRAID kernel: RDX: 0000000000000000 RSI: 0000000022a1d464 RDI: 0000000000000000 Nov 27 16:46:32 unRAID kernel: RBP: ffffffff820584e0 R08: 00000e4c7de8470e R09: 0000000000605328 Nov 27 16:46:32 unRAID kernel: R10: 071c71c71c71c71c R11: 0000000000000020 R12: 0000000000000004 Nov 27 16:46:32 unRAID kernel: R13: 00000e4c7de00ba9 R14: 00000e4c7de8470e R15: 0000000000000000 Nov 27 16:46:32 unRAID kernel: cpuidle_enter+0x25/0x31 Nov 27 16:46:32 unRAID kernel: do_idle+0x17e/0x1fc Nov 27 16:46:32 unRAID kernel: cpu_startup_entry+0x18/0x1a Nov 27 16:46:32 unRAID kernel: start_secondary+0x154/0x16f Nov 27 16:46:32 unRAID kernel: secondary_startup_64+0xa4/0xb0 Nov 27 16:46:32 unRAID kernel: ---[ end trace e348ab53433168b2 ]---
It's weird because I don't have any docker on br0 interface. I have one on br0.160 so I will disable it and check logs.
-
On 11/3/2019 at 2:21 AM, balsman225 said:
Out of curiosity have you tested this issue on any newer releases (6.8.0)?
Yes. I tested it. The problem still exists in 6.8.0 rc3, 4, 5, 6 and 7. I had a Pi-hole on br0 interface but after reading this topic I stopped it and watching my logs now
Thank you guys for your knowledge and a lot of tests. I'm not the only one with this problem.
-
On 12/27/2018 at 2:32 AM, Jason Harris said:
I have this problem for an onboard Intel GPU. I have no intention of passing it through. It is in its own IOMMU group. Would there be any way to just not use this IOMMU group entirely?
As others have said, this is the top result when looking for this issue so any help would be appreciated.
Hi. I have exacly the same problem but when I put "intel_iommu=igfx_off" in syslinux.cfg file this error never shows up in log. But even if i don't use onboard Intel GPU when I pass my GeForce GT 1030 to any of my VMs unraid just hangs totally.
-
Hi. I have a question. Is there any chance to have this modified Unraid version with DVB support?
-
16 hours ago, piotrasd said:
yes in all packages
because are same like in original one so first update to original 6.6.3 then just replace files from my packages in /boot or /flash and reboot
tested and working
I confirm. It works. Dzięki
-
On 11/2/2018 at 7:57 PM, CorneliousJD said:
ha_key can now be replaced with token -- fore more information on how to create a token see here: https://appdaemon.readthedocs.io/en/latest/CONFIGURE.html
It's a very good information. Thanks
-
Hi piotrasd.
bzroot and bzroot-gui files are missing in your tbs-os package. There are md5 files for them but without bzroot and bzroot-gui files.
-
Hi CHBMB. Is there any chance to have 6.6.3 with DVB support?
-
11 hours ago, CHBMB said:
Got a lot on at the moment, so probably won't be for over a week.
OK. Thanks for info. I will wait for it
-
Hi CHBMB.
Are you planing to release 6.6.2 version?
-
OK. Thanks for info.
-
Hi CorneliousJD.
Since a Home Assistant have user authentication method is it possible to change the Appdaemon authentication from API password to something else (according to HA docs API authentication method will be dropped in next releases)?
-
It's working now. Thanks coppit.
-
Server and clients versions are OK. Clients (on windows computers and iphones) doesn't connect at all to the specified port: 8090.
And I can't connect to the 10090 port via web browser.
I run your docker from scratch and the problem with no connection still exists.
-
Hi coppit.
I updated Xeoma docker to the newest version and after that I can't connect any client to the xeoma server.
Logs are OK. here they are:
Configuration: PASSWORD=<hidden> VERSION=latest 2018-08-16 09:18:00 Determining version of Xeoma to use 2018-08-16 09:18:00 Config version is "latest" 2018-08-16 09:18:00 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version2.xml 2018-08-16 09:18:01 Using Xeoma version 18.7.10 (the latest stable version) 2018-08-16 09:18:01 Downloaded file /config/downloads/xeoma_18.7.10.tgz already exists. Skipping download 2018-08-16 09:18:01 Installing Xeoma from /config/downloads/xeoma_18.7.10.tgz 2018-08-16 09:18:02 Installation complete [Aug 16 09:18:02] Setting the password Password set successfull Started runsvdir, PID is 56. Waiting for processes to start.... [Aug 16 09:18:02] Starting the server in 5 seconds. See the log directory in your config directory for server logs. run: cron: (pid 61) 5s run: xeoma: (pid 60) 5s
My xeoma docker configuration is simple but I pass new port for xeoma web service.
-
Hi. I have some new info after many tests of unraid version 6.4.1 and later.
According to my last post...
When I power up my server with 6.5.0 or later unraid versions without hdmi cable plugged into it everything works perfect. After unraid boots up I need to plug hdmi cable into server and whola I have a LibreELEC VM perfectly working with IGD HD Graphics P630 passthrough BUT can someone tell me why in version 6.4.1 everything works perfect without unplugging and plugging hdmi cable?
When I don't unplug hdmi cable in 6.5.0 or later version I have a
Device or resource busyon VM log and black screen shows up.
Anyone could help me?
-
7 hours ago, Squid said:
What does it do if you select the GUI mode from the boot menu?
In GUI mode system boots up with no errors but when I try to run LibreELEC VM with gpu Intel HD Graphics P630 I have this on log:
2018-03-23T15:42:19.818621Z qemu-system-x86_64: -device vfio-pci,host=00:1f.3,id=hostdev1,bus=pci.4,addr=0x1: vfio error: 0000:00:1f.3: group 9 is not viable6 hours ago, BRiT said:Try using EFI boot selection in bios and ensure directory on flash drive is set as EFI.
When I disable legacy mode in BIOS system boots up perfectly but when I try to run LibreELEC VM with GPU I have this on VM log:
2018-03-23T15:35:42.561504Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region2+0x43ed50, 0x0,4) failed: Device or resource busyIt looks like that in UEFI mode my graphics card is busy and can't be used by VM.
-
I will let you know because the only thing which I tried was safe mode (no GUI) but in this situation the problem still exist.
-
Hi.
I used so far 6.5.0 unRAID version on my machine until today when I update my motherboard BIOS to the newest version. After BIOS update I see only "loading bzimage... ok" and "loading bzroot... ok" and next system is restarting. After restart the same situation repeats. BUT when I switch to 6.4.1 everything works OK.
My motherboard is ASUS P10S-M WS with 4301 BIOS version.
UPDATE:
In 6.5.1rc1 this problem still exist.
Thank you guys for your knowledge and a lot of tests. I'm not the only one with this problem.
because are same like in original one 
[SUPPORT] OpenEats - CorneliousJD Repo
in Docker Containers
Posted
It will be great to have this option