Skip Navigation

Demigodrick

@ Demigodrick @lemmy.zip

Posts

321
Comments

719
Joined

3 yr. ago

Lemmy.zip owner & adminContact me via `hello@lemmy.zip`
Elsewhere: me.lemmy.zip - See my accounts across the internet

Moderating

Starfield lemmy.zip

PlayStation lemmy.zip

Gaming lemmy.zip

bot_community lemmy.zip

Home lemmy.zip

Starfield Mods lemmy.zip

Class Action Park lemmy.zip

Test community plz ignore lemmy.zip

Announcements lemmy.zip

Lies of P lemmy.zip

The Button lemmy.zip

2d ago

Lemmy.zip & Piefed.zip Server Update April 2026
Jump
1

Demigodrick @lemmy.zip 2d ago
Hey, sorry I didnt reply sooner - hopefully that's settled down the past couple of days? There was a bug causing the server to crash. No restrictions on vpn traffic in place :)

2d ago

Welcome to Lemmy.zip - READ ME FIRST!

Jump

Demigodrick @lemmy.zip 2d ago

Hey welcome along 😊

7d ago

[Lemmy] Lemmy Release v0.19.18

Jump

Demigodrick @lemmy.zip 7d ago

Good timing, I've literally just updated to 0.19.18 which should have the fix in!

1w ago

Hexbear has been temporarily defederated - UPDATED now federated

Jump

Demigodrick @lemmy.zip 1w ago

No, no meaningful cpu spikes I could make out anywhere, although admittedly I was focusing on the lemmy server container mostly

1w ago

Hexbear has been temporarily defederated - UPDATED now federated

Jump

Demigodrick @lemmy.zip 1w ago

I noticed in the logs before every timeout there were lots of "verify" words appearing, and in each iteration of that statement there were more and more verify words. Honestly had no idea what it meant at the point, only that I didn't recognise it from looking at lemmy logs previously, it always appeared before a crash, and it felt suspicious.

Here's an example from some logs before a crash:

    
2026-03-15T21:47:22.670586Z  INFO HTTP request{http.method=POST http.scheme="https" http.host=lemmy.zip http.target=/inbox otel.kind="server" request_id=2cc6dc65-571d-4a69-9733-5e80e455c00b}:receive:community:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:verify:
verify:verify:verify:verify: activitypub_federation::fetch: 
Fetching remote object https://hexbear.net/comment/7004776

thread 'actix-server worker 18' has overflowed its stack

fatal runtime error: stack overflow

I pinged some logs over to Nutomic on matrix, who thought it might have been related to nested comments, and then I noticed Dessalines had made the linked thread, which matched pretty much with what I was seeing behaviour and logs-wise.

Usefully the logs link the object it's fetching, and 9 times out of 10 its a deeply nested hexbear thread! Or someone from another instance commenting on a nested hexbear thread. Nutomic confirmed the behaviour based on the logs in the issue, and I'm pulling the logs when I get chance to see what other threads are causing it to crash, although hopefully the fix will make it's way into 0.19.18 beta 3 so I can stop worrying about it!

1w ago

Announcing: The Button Season 3 - Starts May 4th (be with you...)

Jump

Demigodrick @lemmy.zip 1w ago

It won't be possible this time, it will pop up on game start like it did for S2, but I'm considering ways to do this while preventing unbalancing the teams too much