My honk host is currently an old Moto G4 running Termux, which was extremely stable for months but lately implodes about every five or six days. Upcoming landing pad:
OS: Void Linux armv7l Host: Raspberry Pi 2 Model B Rev 1.1 Kernel: 5.15.72_1 Uptime: 22 mins Packages: 131 (xbps-query) Shell: sh Terminal: /dev/pts/0 CPU: BCM2835 (4) @ 900MHz Memory: 37MiB / 923MiB
#TeamTinyHonkers
Migration complete! Let's see how long this little honker runs.
@knapjack The Pi should be pretty stable. Honk on!

@petersanchez @dirk Ran into an interesting issue with the Pi. The backend is failing about once a day. Exactly once a day, I asked myself? Yes, it appears so.

When I migrated over, I thought what the heck, let's log to syslog. I installed socklog, left the defaults, voila.

It looks like when the daily log rotation kicks in, the backend crashes. If I try a simple restart of honk the backend doesn't like the socket. A full reboot does the trick.

So, in experimentation mode, now logging to file again. Start the clock.

@knapjack @dirk Interesting. I think @tedu should know about this bug.
@petersanchez @dirk @tedu I would not bet my paycheck that it's a honk bug, but if it is at least it's replicable.