martinjuhasz

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

martinjuhasz's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. cool, ok thats easier. will give that a try first than having to create new firewall rules for a new VLAN and remapping everything -.- Is there some guide or information already on IPVLAN on unraid? Improvements/Drawbacks on using it and how to use it? // edit: running RC1 now with IPVLAN as docker network type. fingers crossed
  2. Well here i am, also fighting this issue it seems. First i had issues with BTRFS, so i switched to XFS and a single cache drive (bummer). But now i get these stacktraces with nf_conntrack_core macvlan. Oct 2 10:55:55 Winston kernel: ------------[ cut here ]------------ Oct 2 10:55:55 Winston kernel: WARNING: CPU: 10 PID: 19944 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 Oct 2 10:55:55 Winston kernel: Modules linked in: tun veth macvlan xt_nat xt_MASQUERADE iptable_nat nf_nat xfs ecb crypto_simd cryptd glue_helper xts dm_crypt dm_mod dax md_mod ipmi_devintf ip6table_filter ip6_tables iptable_filter ip_tables bonding igb i2c_algo_bit intel_powerclamp coretemp kvm_intel kvm i2c_i801 i2c_smbus crc32c_intel i2c_core input_leds intel_cstate led_class i5500_temp intel_uncore ipmi_si cdc_acm ata_piix i7core_edac button acpi_cpufreq [last unloaded: i2c_algo_bit] Oct 2 10:55:55 Winston kernel: CPU: 10 PID: 19944 Comm: kworker/10:0 Not tainted 5.10.21-Unraid #1 Oct 2 10:55:55 Winston kernel: Hardware name: Supermicro X8DT3/X8DT3, BIOS 2.2 07/09/2018 Oct 2 10:55:55 Winston kernel: Workqueue: events macvlan_process_broadcast [macvlan] Oct 2 10:55:55 Winston kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 Oct 2 10:55:55 Winston kernel: Code: e8 64 f9 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 d5 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 5d f3 ff ff e8 30 f6 ff ff e9 22 01 Oct 2 10:55:55 Winston kernel: RSP: 0000:ffffc90003414dd8 EFLAGS: 00010202 Oct 2 10:55:55 Winston kernel: RAX: 0000000000000188 RBX: 000000000000453f RCX: 0000000090f81b21 Oct 2 10:55:55 Winston kernel: RDX: 0000000000000000 RSI: 000000000000026b RDI: ffffffff8200a1ec Oct 2 10:55:55 Winston kernel: RBP: ffff88825c527cc0 R08: 00000000ea80c49f R09: ffff88834286f8e0 Oct 2 10:55:55 Winston kernel: R10: 0000000000000000 R11: ffff8883f69c9600 R12: 000000000000fe6b Oct 2 10:55:55 Winston kernel: R13: ffffffff8210db40 R14: 000000000000453f R15: 0000000000000000 Oct 2 10:55:55 Winston kernel: FS: 0000000000000000(0000) GS:ffff888633b00000(0000) knlGS:0000000000000000 Oct 2 10:55:55 Winston kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 2 10:55:55 Winston kernel: CR2: 0000151fb09ec000 CR3: 00000003af620003 CR4: 00000000000206e0 Oct 2 10:55:55 Winston kernel: Call Trace: Oct 2 10:55:55 Winston kernel: <IRQ> Oct 2 10:55:55 Winston kernel: nf_conntrack_confirm+0x2f/0x36 Oct 2 10:55:55 Winston kernel: nf_hook_slow+0x39/0x8e Oct 2 10:55:55 Winston kernel: nf_hook.constprop.0+0xb1/0xd8 Oct 2 10:55:55 Winston kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe Oct 2 10:55:55 Winston kernel: ip_local_deliver+0x49/0x75 Oct 2 10:55:55 Winston kernel: __netif_receive_skb_one_core+0x74/0x95 Oct 2 10:55:55 Winston kernel: process_backlog+0xa3/0x13b Oct 2 10:55:55 Winston kernel: net_rx_action+0xf4/0x29d Oct 2 10:55:55 Winston kernel: __do_softirq+0xc4/0x1c2 Oct 2 10:55:55 Winston kernel: asm_call_irq_on_stack+0x12/0x20 Oct 2 10:55:55 Winston kernel: </IRQ> Oct 2 10:55:55 Winston kernel: do_softirq_own_stack+0x2c/0x39 Oct 2 10:55:55 Winston kernel: do_softirq+0x3a/0x44 Oct 2 10:55:55 Winston kernel: netif_rx_ni+0x1c/0x22 Oct 2 10:55:55 Winston kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Oct 2 10:55:55 Winston kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Oct 2 10:55:55 Winston kernel: process_one_work+0x13c/0x1d5 Oct 2 10:55:55 Winston kernel: worker_thread+0x18b/0x22f Oct 2 10:55:55 Winston kernel: ? process_scheduled_works+0x27/0x27 Oct 2 10:55:55 Winston kernel: kthread+0xe5/0xea Oct 2 10:55:55 Winston kernel: ? __kthread_bind_mask+0x57/0x57 Oct 2 10:55:55 Winston kernel: ret_from_fork+0x22/0x30 Oct 2 10:55:55 Winston kernel: ---[ end trace 39e64ba254a07726 ]--- Will now try to seperate my dockers into a seperate VLAN.
  3. Do you have some more information on that @aptalca? I have a subdomain set up using proxy_domain and swag, but am not able to find anything online about sub-subdomain configuration.
  4. my bad. the server was spun up using "localhost", not "0.0.0.0.", so it wasn't exposed to its LAN. Now it shows up on its localip:8000. I'm still struggling to configure swag to forward this. // Edit: nevermind: it shows up now, just took some minutes So if anybody has a more elegant idea of doing this, let me know. I would love to be independent from ports as i might also have multiple instances running, that are connected just with "localhost". some tunneling would be awesome. but i guess that might not be achievable or even practical. in that case a VNC would make more sense.
  5. Is there some way to expose a locally running webserver that i started on the code-server terminal for development. I have code-server running using swag for reverse proxy, everything is fine. I have a command to spin up a local web-server for web-dev needs (like hot-reloading etc). The command runs fine and starts a server on some port (lets say 8000). I'm unable to access that website of course. Is there some recommended way to do this on code-server? I was looking for some plugins that would run a headless-chrome or something inside vs-code but they all seem to connect on the client side between browser and server. I also thought about exposing a specific port on the docker and on the proxy, but without luck. Even tho a web-server on port 8000 is runnin in the code-server terminal, i don't seem to be able to access it locally (without swag) even tho the port is exposed in the docker config.
  6. I never managed to get "Single" mode running, so i'm also using JOBD mode. Getting the same errors as you do. According to this post on serverfault, the error of the raid controller can safely be ignored, as it seems to be only related with not supported/forwarded status commands. I receive the following two errors: Oct 17 07:24:34 Winston kernel: 3w-sas: scsi1: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x85. Oct 17 07:24:34 Winston emhttpd: error: mdcmd, 2640: Invalid argument (22): write What i did is to suppress those messages from getting written into the log. To suppress those you need to write filters for rsyslogd into files in rsyslogs config dir, which are normally located under `/etc/rsyslog.d`. I used the following two filters to get rid of this errors: :msg,contains,"error: mdcmd, 2640: Invalid argument (22): write" stop :msg,contains,"ERROR: (0x03:0x0101)" stop So, whenever a message contains on of those contents, it will not get written into log. You can f.e. edit the file `/etc/rsyslog.d/01-blocklist.conf` and add those lines. Then run `/etc/rc.d/rc.rsyslogd restart` to restart the service and check if that worked for you. If you want to make that persistent you need to write those changes on each unraid start. For this edit `/boot/config/go` and add the following lines to it: echo ":msg,contains,\"error: mdcmd, 2640: Invalid argument (22): write\" stop" >> /etc/rsyslog.d/01-blocklist.conf echo ":msg,contains,\"ERROR: (0x03:0x0101)\" stop" >> /etc/rsyslog.d/01-blocklist.conf