@Samiz seeing some crashes when too many events are coming in
```
07-25 09:28:34.816 25366 25383 D NostrClient: New local event received : ae5d7...5fa08
07-25 09:28:34.838 25366 25398 D NostrClient: New local event received : 17322...0bb7a
07-25 09:28:34.852 25366 25397 D NostrClient: New local event received : 15c79...f757f
07-25 09:28:34.865 25366 25383 D NostrClient: New local event received : cfdbb...6acd3
07-25 09:28:34.874 25366 25397 D NostrClient: New local event received : 873d9...ec6d7
07-25 09:28:34.876 25366 25383 D NostrClient: New local event received : d503b...611f4
07-25 09:28:35.255 25366 25395 I SQLiteConnection: Long db operation: /data/user/0/com.koalasat.samiz/databases/samiz_db_common
--------- switch to crash
07-25 09:28:35.327 25366 25395 E AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-5
07-25 09:28:35.327 25366 25395 E AndroidRuntime: Process: com.koalasat.samiz, PID: 25366
07-25 09:28:35.327 25366 25395 E AndroidRuntime: android.database.sqlite.SQLiteDatabaseLockedException: database is locked (code 5 SQLITE_BUSY)
```
chrizzz
chrizzz@nip-05.com
npub13syp...gns9
iykyk
@FIPS so I have fips running on Android in Termux but I can't connect to the DNS responder:
```
$ ./fips --config $HOME/.config/fips/fips.yaml
2026-07-23T13:20:57.088657Z INFO fips: FIPS 0.5.0-dev (rev fc8ebd5a06) starting
2026-07-23T13:20:57.088747Z INFO fips: Loaded config file path=/data/data/com.termux/files/home/.config/fips/fips.yaml
2026-07-23T13:20:57.090335Z INFO fips: Loaded persistent identity from key file path=/data/data/com.termux/files/home/.config/fips/fips.key
2026-07-23T13:20:57.091160Z INFO fips: Node created:
2026-07-23T13:20:57.091182Z INFO fips: npub: @npub1sg3n...kwx5
2026-07-23T13:20:57.091220Z INFO fips: node_addr: c03d91fe06e24716ee2cc84115eef685
2026-07-23T13:20:57.091240Z INFO fips: address: fdc0:3d91:fe06:e247:16ee:2cc8:4115:eef6
2026-07-23T13:20:57.091245Z INFO fips: state: created
2026-07-23T13:20:57.091248Z INFO fips: leaf_only: false
2026-07-23T13:20:57.091977Z INFO fips::transport::udp: UDP transport started local_addr=0.0.0.0:2121 recv_buf=4194304 send_buf=4194304
2026-07-23T13:20:57.092123Z INFO fips::transport::tcp: TCP transport started local_addr=Some(0.0.0.0:8443) mtu=1400
2026-07-23T13:20:57.092149Z INFO fips::node::lifecycle: Transports initialized count=2
2026-07-23T13:20:57.102270Z INFO fips::node::lifecycle: Spawned FMP-encrypt worker pool workers=8
2026-07-23T13:20:57.223137Z INFO fips::node::lifecycle: Spawned FMP-decrypt worker pool workers=8
2026-07-23T13:20:57.224068Z INFO fips::node::lifecycle: DNS responder started for .fips domain (auto-reload enabled) bind=[::1]:5354 hosts=1 mesh_ifindex=None
2026-07-23T13:20:57.224092Z INFO fips::node::lifecycle: Node started:
2026-07-23T13:20:57.224095Z INFO fips::node::lifecycle: state: running
2026-07-23T13:20:57.224097Z INFO fips::node::lifecycle: transports: 2
2026-07-23T13:20:57.224103Z INFO fips::node::lifecycle: connections: 1
2026-07-23T13:20:57.224107Z INFO fips: FIPS running
2026-07-23T13:20:57.224127Z INFO fips::node::dataplane::rx_loop: RX event loop started
2026-07-23T13:20:57.224455Z INFO fips::control::unix_impl: Control socket listening path=/data/data/com.termux/files/usr/tmp/fips/control.sock
2026-07-23T13:20:57.452694Z INFO fips::node::handlers::handshake: Peer promoted to active peer=gateway
2026-07-23T13:20:57.455020Z INFO fips::node::tree: Parent switched, invalidated downstream coord cache entries, announcing to all peers new_parent=gateway new_seq=2 new_root=00001a8c838e51954fffeb3d795a4743 depth=2
```
```
$ dig @127.0.0.1 -p 5354 @npub1qmc3...el98.fips AAAA
;; communications error to 127.0.0.1#5354: connection refused
;; communications error to 127.0.0.1#5354: connection refused
;; communications error to 127.0.0.1#5354: connection refused
; <<>> DiG 9.20.24 <<>> @127.0.0.1 -p 5354 @npub1qmc3...el98.fips AAAA
; (1 server found)
;; global options: +cmd
;; no servers could be reached
```