# DevNet validator won’t start after 0.7.5 → 0.9.3

**URL:** <https://forum.canton.network/t/devnet-validator-won-t-start-after-0-7-5-0-9-3/9366>\
**Category:** App Development\
**Created:** [October 23, 2026, 1:41pm UTC](https://forum.canton.network/t/devnet-validator-won-t-start-after-0-7-5-0-9-3/9366 "2026-10-23T13:41:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![fzavalia](https://avatars.discourse-cdn.com/v4/letter/f/9d8465/32.png) [@fzavalia](https://forum.canton.network/u/fzavalia)\
**Post date:** [October 23, 2026, 1:41pm UTC](https://forum.canton.network/t/devnet-validator-won-t-start-after-0-7-5-0-9-3/9366/1 "2026-10-23T13:41:19Z")

</div>

We upgraded our DevNet validator (docker-compose, migration id 1) from Splice 0.7.5 to 0.9.3 on Oct 21 and it hasn’t started since. The upgrade landed in the topology freeze ahead of the LSU to serial 6 / PV 36, and at first the validator looped on `check_establish_topology_mapping` with `FAILED_PRECONDITION: Condition is not yet observed`, so we waited.

Two days later, init now fails at **Vet packages** and the app exits:

```haskell
ABORTED: TOPOLOGY_TOO_MANY_PENDING_TOPOLOGY_TRANSACTIONS(2,77fbb546):
Too many pending topology transactions on this node.

```

The `/info` endpoint still shows `current.serial_id: 5` with `successor.serial_id: 6`, so the LSU doesn’t seem to have completed yet (scheduled for Oct 21 13:00 UTC). Our guess is the participant’s topology outbox filled up with vetting transactions queued across restarts during the freeze.

Questions:

1. Is the DevNet LSU to serial 6 delayed? Where can we track its status?
2. Once it completes, will the outbox drain and vetting succeed on its own, or do we need a recovery step?
3. Anything we should do in the meantime? We haven’t touched topology state or rolled back.

Happy to share fuller logs. Thanks!