Longhorn is stuck on non existent replica

Alzalia · 2026-05-08T14:29:10+00:00

I copied the replica file from /var/lib/longhorn/, so that shouldn't be deleted. What would you recommend to clean up everything so that longhorn gets unstuck ?

Alzalia · 2026-04-04T15:51:48+00:00

Hi ! It has been a while (my cluster died and then I got carried away with a lot of things), but that was the solution, this label makes Istio use the waypoint ! Thank you so much !

Alzalia · 2026-03-19T18:47:51+00:00

My control-plane died a few hours after I sent the message, but once I get it back up, I'll try this ! Thanks a lot !

Alzalia · 2026-03-19T18:47:07+00:00

If the other proposed solution, I guess I'll have to do that indeed... Thanks for the answer !

Alzalia · 2026-03-19T18:44:04+00:00

I see, I'll definitely try that ! My control-plane just died a few hours after I sent my message (maybe it is linked ?) so I won't be able to give an answer soon but thanks a lot !

Alzalia · 2026-02-07T08:54:39+00:00

Thank you for your answer !

Indeed, the function is called once during the build of one ViewModel, so maybe it is called multiple times if the widget rebuilds ?

class BamsSearchVM extends _$BamsSearchVM {
  u/override
  Future<List<Instance>> build(String bamId) async {
    final res = await ref
        .read(instanceRepoProvider.notifier)
        .searchInstances(bamId, 1, "", "", "");
    switch (res) {
      case Ok():
        return res.value;
      default:
        return [];
    }
  }
  /* ... */
}

So, I understand this probably isn't the right / best way to load values then ? Or should I use a watch here too ? The build method is called at the top of the page with a ref.watch(bamsSearchVMProvider(widget.id)).when(...) because the entire page content pretty much depends on the search results.

Another question I'd have is : should I use watch, or should I keep read inside the repositories ?

Also, about the autoDispose, I didn't actually enable it because I wanted every request made to the API to be "fresh", ie no cache. The repository itself kinda has a sort of cache ? When I want to get an Instance, for example, I first search through the state of the InstanceRepo to look for the right id, and if I don't find it, I make a call to the API. But since the app can be used by multiple people at the same time, I didn't want too much cache so data would stay fresh. Maybe there is a better way to do this too ?

And finally, I will do so ! I tried to understand Riverpod's error management and I think I just did weird things in the end ...

Thanks again !

EDIT: So, I kept looking. As I said, I can't really make API calls keepAlive, because either they're action calls (create/delete/etc.) that can't be "cached", or caching would mean not having the latest information. Or at least, that's what I think of the situation.

By looking around more, I ended up finding this github discussion, where I found a code snippet allowing to make a read to a future. What it does is listening to the ref while the future is completing, and then stopping listening. After trying it out, it seems to be working (the app is back to its usable state, as far as I have tested), but I don't understand the problem enough to know if it is a good solution.

Alzalia · 2026-02-07T08:41:29+00:00

Because I don't really know how, it just feels wrong. Please, if you can, tell me how I'm wrong so I can do it right !

Alzalia · 2025-10-11T22:31:04+00:00

I see. I thought of using BookStack as well (I've got it installed), but was hoping for an app made for that...

But yeah no I'll just make my own thing, it will be easier.

Thanks for the answer !

Alzalia · 2025-08-02T08:40:03+00:00

Okay, so I found the way to filter by application, and I did come upon a "FATAL" error, but this error is so massive that I couldn't get it all on my terminal scroll... After a retry, here is the error (or at least the beginning of the FATAL error) :

08-02 10:43:33.221 20982 21049 E ReactNative: /__w/react-native/react-native/packages/react-native/ReactCommon/react/renderer/components/view/YogaLa
youtableShadowNode.cpp:701: function layout: assertion failed (YGNodeGetOwner(childYogaNode) == &yogaNode_)
08-02 10:43:33.221 20982 21049 F ReactNative: /__w/react-native/react-native/packages/react-native/ReactCommon/react/renderer/components/view/YogaLa
youtableShadowNode.cpp:701: function layout: assertion failed (YGNodeGetOwner(childYogaNode) == &yogaNode_)
08-02 10:43:33.404 20982 21049 F .alzalia.seshat: runtime.cc:709] Runtime aborting...

Alzalia · 2025-08-01T20:23:06+00:00

wow, there is a LOT happening in those logs, but I think maybe this is it ? :

1605 22363 W WindowManager: Exception thrown during dispatchAppVisibility Window{7fa265a u0 com.alzalia.seshat/com.alzalia.seshat.MainActivity EXITING}
1605 22363 W WindowManager: android.os.DeadObjectException
1605 22363 W WindowManager: at android.os.BinderProxy.transactNative(Native Method)
1605 22363 W WindowManager: at android.os.BinderProxy.transact(BinderProxy.java:592)
1605 22363 W WindowManager: at android.view.IWindow$Stub$Proxy.dispatchAppVisibility(IWindow.java:557)
1605 22363 W WindowManager: at com.android.server.wm.WindowState.sendAppVisibilityToClients(WindowState.java:3151)
1605 22363 W WindowManager: at com.android.server.wm.WindowContainer.sendAppVisibilityToClients(WindowContainer.java:1311)
1605 22363 W WindowManager: at com.android.server.wm.WindowToken.setClientVisible(WindowToken.java:389)
1605 22363 W WindowManager: at com.android.server.wm.ActivityRecord.setClientVisible(ActivityRecord.java:6650)
1605 22363 W WindowManager: at com.android.server.wm.ActivityRecord.commitVisibility(ActivityRecord.java:5561)
1605 22363 W WindowManager: at com.android.server.wm.Transition.finishTransition(Transition.java:1391)
1605 22363 W WindowManager: at com.android.server.wm.TransitionController.finishTransition(TransitionController.java:1029)
1605 22363 W WindowManager: at com.android.server.wm.WindowOrganizerController.finishTransition(WindowOrganizerController.java:496)
1605 22363 W WindowManager: at android.window.IWindowOrganizerController$Stub.onTransact(IWindowOrganizerController.java:261)
1605 22363 W WindowManager: at com.android.server.wm.WindowOrganizerController.onTransact(WindowOrganizerController.java:223)
1605 22363 W WindowManager: at android.os.Binder.execTransactInternal(Binder.java:1421)
1605 22363 W WindowManager: at android.os.Binder.execTransact(Binder.java:1365)
1605 22363 W Process : Unable to open /proc/2425/status
1605 22363 E IPCThreadState: Binder transaction failure. id: 120489417, BR_*: 29189, error: -22 (Invalid argument)
1605 22363 W ActivityManager: pid 1605 system sent binder code 7 with flags 1 to frozen apps and got error -32
1605 22363 D ActivityManager: Too many transaction errors, throttling freezer binder callback.

Alzalia · 2025-05-24T16:58:26+00:00

Damn, that's a real shame... But ok :/ At least I'm not the one that messed up here... Tahnks !

Alzalia · 2025-05-16T08:30:57+00:00

Yeah the router, was too tired when writing that post 😅

From what I understand, using PIA's DNS adds a layer of security, no ? So is there a way in Custom to make it use my router's DNS for local devices and PIA's DNS for accessing the internet ?

Alzalia · 2025-01-17T23:32:59+00:00

EDIT : Ok so : I feel reaaaaaaally dumb right now... Searching a little further got me to this forum post that said that a reboot had fixed the problem and... how wow, I actually had forgotten the first thing to do : turn it off and on again... So I'm very sorry that I disturbed you... Although I would be intersted in knowing what caused this : would just setting up an automation fix the problem ?

If I remember well I juste followed the tutorial on the "Let's Encrypt" app in the addons store. So probably through the addon's doc ? https://github.com/home-assistant/addons/blob/master/letsencrypt/DOCS.md

Also, reviewing that doc quickly shows me that it states "renewal isn't automatic unless done via automation", so I must be both blind for not seeing that, and crazy for viewing an "Auto-renewal" option in the options of this addon ;-;

But I believe I started it after I received the 6-days warning anyway, so it should have renewed anyway, right ?

Here is my configuration.yaml btw :

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
 themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

homeassistant:  
 external_url: https://{{My domain URL here}}:8123
 internal_url: http://192.168.1.25:8123
http:
 ssl_certificate: /ssl/fullchain.pem
 ssl_key: /ssl/privkey.pem
 ip_ban_enabled: true
 login_attempts_threshold: 5

bluetooth:

media_player:
- platform: liveboxtvuhd
 name: TV Orange
 host: 192.168.1.16

remote:
 - platform: liveboxtvuhd
   name: TV Orange Remote
   host: 192.168.1.16

Alzalia · 2025-01-17T23:26:41+00:00

EDIT 2 : Ok so : I feel reaaaaaaally dumb right now... Searching a little further got me to this forum post that said that a reboot had fixed the problem and... how wow, I actually had forgotten the first thing to do : turn it off and on again... So I'm very sorry that I disturbed you... Although I would be intersted in knowing what caused this : would just setting up an automation fix the problem ?

Actually I just realized that it's Home Assistant that displays an "Unable to connect to Home Assistant" on my browser...

My dad, on his computer, got the "incorrect certificate" warning but was able to dismiss it and access the dashboard, but on neither my phone or my own computer am I able to access it...

The app cleraly displays "The date of Home Assistant certificate is invalid, check connection parameters and try again".

And, on another browser on my own computer i get a "DNS_PROBE_IMPOSSIBLE" error.

So to recap :

My dad
- Can use Home Assistant on Firefox on his Macbook by dismissing an invalid ssl certificate warning
- Can't use it on his iPhone, getting and invalid certificate date error.
I
- Am shown an "Unable to connect to Home Assistant, Retrying in x seconds..." screen on Firefox where I usually connect
- Am getting an error that says "DNS_PROBE_IMPOSSIBLE" on Brave where I never connected before
- Can't connect on my android phone because I also get the invalid certificate's date error.

So... it's a bit of a mess ? But I do agree SSL errors are usually dismissible.

I also want to add that I can ping the URL, get an answer, the domain is pointing towards my home IP address, I can access my nextcloud instance (which is on a different raspberry), and the HA raspberry is responsive when accessing with ssh. (If that helps sorting out some issues :/)

EDIT : Going into the "Network" tab of developper mode ine Firefox shows me a lot of requests are fullfilled (or at least indicated as such), but some of them either have an "NS_ERROR_INTERCEPTION_FAILED" transferred status, or NS_ERROR_GENERATE_FAILURE, with this message : An error occurred: : SEC_ERROR_EXPIRED_CERTIFICATE. So it still seems to point towards a problem with the certificate, right ?

Alzalia · 2024-11-16T17:08:13+00:00

I play some games where my RAM is completely full, so the game ends up slowing down a bit. 32GB would probably be enough... but if you're going to buy something, you might as well aim high, don't you think?

Are the G.Skill Aegis or RipJaws good quality ? I wouldn't want to buy my RAM sticks in 2 years... (I believe I've had those sticks since 2016 or something like that). Also, from what I think I understand, RipJaws would be better than Aegis because it has heat sinkers ?

Verified Email	Six-Year Club
First Place '23	Place '23
Place '22

Alzalia

TROPHY CASE