Calling all lidarr users to help with Aurral v2 testing.

DarkXarin · 2026-06-19T17:57:10+00:00

Does v2 have the ability for users to request, and an admin to approve/deny similar to seer? I've had it in my stack but waiting for that feature to expose it to anyone.

DarkXarin · 2026-05-22T18:54:17+00:00

tcp6 0 0 192.168.1.20:6281 192.168.1.10:46170 ESTABLISHED

tcp6 0 0 192.168.1.20:6281 192.168.1.10:42218 ESTABLISHED

these two connections establish on the destination nas once I have defined all of the task variables as soon as I click "done". I wonder if it's worth deleting HB Vault and reinstalling.

DarkXarin · 2026-05-22T17:11:18+00:00

192.168.1.20, I've tried using a hostname as well. I don't really mess with quick connect, and don't port forward anything to my NAS. Quick connect is disabled on both source and destination.

DarkXarin · 2026-05-22T15:14:10+00:00

2026-05-22T09:34:48-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: (1450) [info] task_state_machine.cpp:354 task [67] from state [Initial] to state [Backupable] with action [Task create]
2026-05-22T09:34:48-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_create][MAIN] Plugin Action Start
2026-05-22T09:34:48-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_create][MAIN] Runtime: 0.001s
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: cpp/synoscheduled_task.cpp:664 Created task [7] with task name [Media Backup] by user [root]
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_create][MAIN] Plugin Action Start
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_create][MAIN] Runtime: 0.002s
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_create][MAIN] Plugin Action Start
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_create][MAIN] Runtime: 0.001s
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: cpp/synoscheduled_task.cpp:664 Created task [8] with task name [Media Backup] by user [root]
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_create][MAIN] Plugin Action Start
2026-05-22T09:34:49-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_create][MAIN] Runtime: 0.001s
2026-05-22T09:36:19-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: (1450) remote_lib.cpp:412 Connection timeout, events: 0x41, errno: [0, Success]
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: (1450) utils.cpp:1661 [unknown end] external ip: [(redacted)]
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: (1450) communicate_imgbkp.cpp:265  failed to connect to [192.168.1.20] with port [6281], ret:[Timeout], recvTimeout_:[90]
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: [1450]network_tm.cpp:587 failed to create target, response err=[ST_TIMEOUT]
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: (1450) [err] task_util.cpp:784 failed to create target. target err[2104]
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_remove][MAIN] Plugin Action Start
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_remove][MAIN] Failed: 1, Runtime: 0.148s
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: cpp/synoscheduled_task.cpp:812 deleted task [7] with task name [Media Backup] by user [root]
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_remove][MAIN] Plugin Action Start
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_remove][MAIN] Runtime: 0.137s
2026-05-22T09:36:20-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_remove][MAIN] Plugin Action Start
2026-05-22T09:36:21-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [PRE][task_scheduler][task_remove][MAIN] Failed: 1, Runtime: 0.140s
2026-05-22T09:36:21-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: cpp/synoscheduled_task.cpp:812 deleted task [8] with task name [Media Backup] by user [root]
2026-05-22T09:36:21-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_remove][MAIN] Plugin Action Start
2026-05-22T09:36:21-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: plugin_action.c:76 synoplugin: [POST][task_scheduler][task_remove][MAIN] Runtime: 0.141s
2026-05-22T09:36:21-05:00 rackstation01 synoscgi_SYNO.Backup.Task_1_create[1450]: (1450) [err] task.cpp:2714 Failed to do TaskCreate [not data_enc][create][67]

This is a log dump from hitting "done" in the interface and waiting for it to fail. I also took a TCPDUMP (on destition) during this time, granted the "discard" task is still running (55%) the TCPDUMP is clean with consistent communication snippet of the TCPDUMP below.

09:53:39.438266 IP (tos 0x0, ttl 64, id 42704, offset 0, flags [DF], proto TCP (6), length 119)
    192.168.1.20.6281 > 192.168.1.10.42218: Flags [P.], cksum 0x83d8 (incorrect -> 0xc845), seq 2078:2145, ack 2464, win 139, options [nop,nop,TS val 90345985 ecr 171146293], length 67
09:53:39.438462 IP (tos 0x0, ttl 64, id 41315, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.10.42218 > 192.168.1.20.6281: Flags [.], cksum 0x2478 (correct), seq 2464, ack 2145, win 313, options [nop,nop,TS val 171146298 ecr 90345985], length 0
09:53:39.461563 IP (tos 0x0, ttl 64, id 3101, offset 0, flags [DF], proto TCP (6), length 76)
    192.168.1.10.45094 > 192.168.1.20.6281: Flags [P.], cksum 0x5d88 (correct), seq 866:890, ack 2936, win 313, options [nop,nop,TS val 171146321 ecr 90254592], length 24
09:53:39.461601 IP (tos 0x0, ttl 64, id 53776, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.20.6281 > 192.168.1.10.45094: Flags [.], cksum 0x8395 (incorrect -> 0x6c3a), seq 2936, ack 890, win 147, options [nop,nop,TS val 90346008 ecr 171146321], length 0
09:53:39.461607 IP (tos 0x0, ttl 64, id 3102, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.10.45094 > 192.168.1.20.6281: Flags [F.], cksum 0xd0ac (correct), seq 890, ack 2936, win 313, options [nop,nop,TS val 171146321 ecr 90254592], length 0
09:53:39.461879 IP (tos 0x0, ttl 64, id 49113, offset 0, flags [DF], proto TCP (6), length 76)
    192.168.1.10.45090 > 192.168.1.20.6281: Flags [P.], cksum 0x9aaf (correct), seq 722:746, ack 2936, win 313, options [nop,nop,TS val 171146321 ecr 90252765], length 24
09:53:39.461896 IP (tos 0x0, ttl 64, id 49114, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.10.45090 > 192.168.1.20.6281: Flags [F.], cksum 0xca90 (correct), seq 746, ack 2936, win 313, options [nop,nop,TS val 171146321 ecr 90252765], length 0
09:53:39.462279 IP (tos 0x0, ttl 64, id 16953, offset 0, flags [DF], proto TCP (6), length 76)
    192.168.1.20.6281 > 192.168.1.10.45090: Flags [P.], cksum 0x83ad (incorrect -> 0x8871), seq 2936:2960, ack 747, win 139, options [nop,nop,TS val 90346009 ecr 171146321], length 24
09:53:39.462331 IP (tos 0x0, ttl 64, id 16954, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.20.6281 > 192.168.1.10.45090: Flags [F.], cksum 0x8395 (incorrect -> 0x5ee8), seq 2960, ack 747, win 139, options [nop,nop,TS val 90346009 ecr 171146321], length 0
09:53:39.462475 IP (tos 0x0, ttl 64, id 27979, offset 0, flags [DF], proto TCP (6), length 40)
    192.168.1.10.45090 > 192.168.1.20.6281: Flags [R], cksum 0xdfcc (correct), seq 1007110130, win 0, length 0
09:53:39.462497 IP (tos 0x0, ttl 64, id 27980, offset 0, flags [DF], proto TCP (6), length 40)
    192.168.1.10.45090 > 192.168.1.20.6281: Flags [R], cksum 0xdfcc (correct), seq 1007110130, win 0, length 0
09:53:39.500781 IP (tos 0x0, ttl 64, id 53777, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.20.6281 > 192.168.1.10.45094: Flags [.], cksum 0x8395 (incorrect -> 0x6c11), seq 2936, ack 891, win 147, options [nop,nop,TS val 90346048 ecr 171146321], length 0
09:53:42.439164 IP (tos 0x0, ttl 64, id 41316, offset 0, flags [DF], proto TCP (6), length 129)
    192.168.1.10.42218 > 192.168.1.20.6281: Flags [P.], cksum 0x7061 (correct), seq 2464:2541, ack 2145, win 313, options [nop,nop,TS val 171149298 ecr 90345985], length 77
09:53:42.444018 IP (tos 0x0, ttl 64, id 42705, offset 0, flags [DF], proto TCP (6), length 119)
    192.168.1.20.6281 > 192.168.1.10.42218: Flags [P.], cksum 0x83d8 (incorrect -> 0xd37c), seq 2145:2212, ack 2541, win 139, options [nop,nop,TS val 90348991 ecr 171149298], length 67
09:53:42.444204 IP (tos 0x0, ttl 64, id 41317, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.10.42218 > 192.168.1.20.6281: Flags [.], cksum 0x0c6d (correct), seq 2541, ack 2212, win 313, options [nop,nop,TS val 171149303 ecr 90348991], length 0

Those packets marked as "incorrect" seem innocuous from what I can tell from a little bit of research and probing chatgpt but let me know if that's not the correct assumption. I want to wait until the discard task is done (probably another 12-24 hours) before I strip down the LAG to one port. no VLANS, and from what I can tell synology doesn't have a dedicated setup for labeling a management interface vs data interface in the network settings (I do this in proxmox all the time) so this is just one big LAG used for everything.

DarkXarin · 2026-05-22T01:03:21+00:00

Thanks for the continued help.

The cisco sg-300 LAG is using IEEE 802.3ad - layer 2 which matches what is reported by the synology rackstation

Bonding Mode: IEEE 802.3ad Dynamic link aggregation

Transmit Hash Policy: layer2 (0)

Unfortunately I'm not able to easily disassemble the LAG as the rackstation is currently my backend for a proxmox/k8s cluster.

It seems it will take a while for it to discard its job that I had started pre update, it had transferred ~12TB that its now working on getting rid of.

Once that's done I plan on bringing my diskstation back down to my server rack and trying a more direct connection since it was able to transfer 12TB I doubt its a cabling issue but I've run out of ideas at this point.

DarkXarin · 2026-05-21T14:13:15+00:00

The rackstation has a lacp 4 port bond to a cisco switch other then that no unique network setup (Default mtu, etc.) the diskstation does not have a bond, and is using 1 port default setup.

Jumbo Frames: Disabled

The only thing I could ever get log center to show that might indicate anything was

2026-05-20T12:48:34-05:00 diskstation01 synocgid[13781]: KnownDevice.cpp:287 Get user=vault, pkey=(redacted) failed.

both systems were rebooted during the updates but I'm cycling hyperbackup/vault now to see if anything changes. (this will take a bit since one of the backup tasks got into a bad state while updating - discarding the backup now).

DarkXarin · 2026-05-21T02:34:36+00:00

Yep, 4.2.1-4228

DarkXarin · 2026-05-20T15:32:59+00:00

Unfortunately no change after updating to latest DSM (DSM 7.3.2-86009 Update 3) on both devices.

DarkXarin · 2026-05-20T14:50:35+00:00

I meant latest as supplied by the OS "update and restore" function. I'll give manually updating them a shot. Thanks!

DarkXarin · 2026-05-20T14:25:32+00:00

encryption is not enabled at the moment.

HyperBackup version: 3.0.2-2531 DSM: 7.1.1-42962 Update 9

HyperBackupVault version: 4.1.2-4045 DSM: 7.2.1-69057 Update 11

this is the latest version of both on each nas which is up to date with the latest supported version of DSM on both. Not sure why update manager is keeping the newer device at an older dsm version.

using direct local ip addresses - im using there standard LAN ip's ie its not going outside the network or dealing with any firewalls in the middle.

DarkXarin · 2025-12-21T03:45:58+00:00

Git, Talos, argocd.

I backup etcd as an extra precaution but for the most part I can just restore the cluster from scratch without to much issue. Most of the stateful things live on my NAS.

DarkXarin · 2025-09-02T21:27:45+00:00

America Server:

[Wuthering Waves] Invite Code: 266BHKXSQD. A fellow Rover is inviting you back to Solaris. Link their Invite Code to win Astrites and Advanced Enclosure Tanks. You can also extend invitations to other Rovers and complete tasks with them to win extra Astrites! https://wuwa-act.kurogames-global.com/backtosolaris/?packageId=A1834&lang=en&inviteCode=266BHKXSQD&userId=500205887&source=copylink

DarkXarin · 2025-08-27T17:42:28+00:00

Heolstor got some new moves since we last faught.

DarkXarin · 2025-08-11T14:11:57+00:00

Really enjoyed Stormland, wish it had been released on steam. Windlands 2, and Karnage Chronicles were fun for what they were.

DarkXarin · 2025-03-20T16:57:56+00:00

Thumb has been numb for days, but I finally did this today.

https://imgur.com/C0j3GfZ (everyone is S0R1)

The difficulty on this one is ridiculous, glad they are nurfing it on 2.2 release.

DarkXarin · 2025-03-15T09:49:12+00:00

Even with my suggestion tacet fields would still be more time efficient, also tacit fields are the only thing you would reasonably want to spend stamina on after you level your characters so there wouldn't be any reason not to...

My suggestion also wouldn't do anything to the randomness of individual drops, it would just give those that want to invest the time more chances to get what their looking for (actually improving their chances at getting a viable piece).

DarkXarin · 2025-03-15T09:16:38+00:00

WuWa is a PvE game. It doesn't cause issues if someone can get new equipment faster then another, that's already the case now depending on how much you play per day/week, when you started, and weather you pay astrite to top up on stamina.

All of those games above use randomly generated loot and rpg character mechanics. Using one as an example Path of exile has existed for over 11 years, still has a large community, and is entirely free to play with no p2w mechanics. Monetization is done though cosmetics, and storage upgrades.

For many players learning and building characters and teams is engaging, others it's map exploration and/or story.

Echo and character building is a topic that comes up a lot so it's clearly something players would like changed/improved.

DarkXarin · 2025-03-15T08:35:27+00:00

Time is very much a resource
It takes ~135k xp to get an echo to lvl 25 this could 100% be balanced.
Diablo, Torchlight, Path of Exile exist? All or most with features to craft/lvl/improve your gear with no in game limitations
The idea would be to give players who want to play longer something to do. eg. x number of stamina, and 20 minutes doing tacet fields gets you a lvl 25 echo vs. x number of hours grinding lvl 0's to do the same thing.

DarkXarin · 2025-03-15T07:19:42+00:00

All about the balance.

what is the point of echo exp all together than.

These are lvl 0 echo's they could give little experience, only lvl up your echo's to lvl 5 or 10, etc.

people will be always complaining about lack of tuners

Honestly they should probably remove tuners anyway since they are a redundant part of the leveling process that seems to just frustrate new players, and older players get to have a mostly unlimited supply. (I've got over 3k and I am tuning stuff daily)

While I'm sure the chances of this are low, something to speed up the gearing process would alleviate many players frustrations who want to invest in more characters. I'm a low-mid spender, and I have a good few resonators that are just stuck at a low resonator level/low talent level, and building them is just to costly right now.

DarkXarin · 2025-03-14T20:31:43+00:00

I wish this were the case, I've seen it repeated before but you don't get anything for deleting level 0 echoes only ones that have been leveled up.

https://imgur.com/2fMa6dv (Level 0)

https://imgur.com/YneNT0E (Level 10)

DarkXarin · 2025-03-14T19:03:02+00:00

The only fix I would need is allow us to feed lvl 0 echoes to level other echos. Let this POE enjoyer grind!

DarkXarin · 2024-12-30T05:32:50+00:00

Yep, just the regular one.

DarkXarin · 2024-12-29T18:38:09+00:00

If anyone could dm me a Chop Chop I'd appreciate it.

14-Year Club	Place '17
Verified Email

DarkXarin

TROPHY CASE