lukaszzborek opened a new issue, #2720:
URL: https://github.com/apache/iggy/issues/2720
### Bug description
When using iggy server, I get some problem with user login after restart
(graceful shutdown, then start) with error `Failed to parse password hash:
PhcStringField`. I cannot login in .net sdk and in web ui
Sometimes, it proceed to shutdown server, sometimes not.
What funny, I can login to default account (iggy with generated password on
first iggy start). It's only apply to other users.
I tried to repplicated it to write step by step, but I don't know what to
do. I just run server for few hours with 128mb segment, enabled cleaner and
message expiration after 10 minutes.
I create user with web ui or via cli
### Deployment
Pre-built binary / release artifact
### Versions
0.6.3-edge.1
### Hardware / environment
local with nvme
### Sample code
_No response_
### Logs
sample logs from yesterday, but today i have the same problems
```
2026-02-10T22:06:14.322775Z INFO shard-2 server::tcp::tcp_listener: Created
new session: client ID: 2641427913, IP address: 192.168.68.11:>
2026-02-10T22:06:14.324464Z INFO shard-2
server::binary::handlers::users::login_user_handler: Logging in user: otherapp
...
thread 'shard-2' (3569260) panicked at
core/server/src/streaming/utils/crypto.rs:35:40:
Failed to parse password hash: PhcStringField
2026-02-10T22:06:14.324462Z INFO shard-0
trace_login_user{iggy_user_id=4294967295 iggy_client_id=492040921}:
server::binary::handlers::use>
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'shard-0' (3569258) panicked at
core/server/src/streaming/utils/crypto.rs:35:40:
Failed to parse password hash: PhcStringField
2026-02-10T22:06:14.326335Z ERROR shard-0
server::shard::task_registry::registry: Connection handler panicked on shard 0:
Failed to parse p>
thread 'shard-2' (3569260) panicked at
core/server/src/streaming/utils/crypto.rs:35:40:
Failed to parse password hash: PhcStringField
2026-02-10T22:06:14.326393Z ERROR shard-2
server::shard::task_registry::registry: Connection handler panicked on shard 2:
Failed to parse p>
2026-02-10T22:06:14.326419Z INFO shard-2
trace_login_user{iggy_user_id=4294967295 iggy_client_id=2641427913}:
server::binary::handlers::us>
2026-02-10T22:06:14.326456Z INFO shard-0 server::http::http_server: HTTP
API shut down gracefully
2026-02-10T22:06:14.326470Z ERROR shard-2
server::shard::task_registry::registry: Connection handler panicked on shard 2:
Failed to parse p>
2026-02-10T22:06:14.326520Z INFO shard-3 iggy_server: Shard 3 run completed
2026-02-10T22:06:14.326666Z INFO main iggy_server: Shard 3 exited
successfully
2026-02-10T22:06:14.326923Z INFO shard-2 iggy_server: Shard 2 run completed
2026-02-10T22:06:14.326934Z INFO shard-0 iggy_server: Shard 0 run completed
2026-02-10T22:06:14.327084Z INFO main iggy_server: Shard 2 exited
successfully
2026-02-10T22:06:14.327120Z INFO main iggy_server: Shard 0 exited
successfully
2026-02-10T22:06:14.327988Z INFO shard-1 iggy_server: Shard 1 run completed
2026-02-10T22:06:14.328212Z INFO main iggy_server: Shard 1 exited
successfully
2026-02-10T22:06:14.328311Z INFO main iggy_server: All shards have shut
down. Iggy server is exiting.
```
### Iggy server config
[current_config.txt](https://github.com/user-attachments/files/25243689/current_config.txt)
### Reproduction
1. start server
2. create new user (all global permissions)
3. take some time 😅
4. restart server
5. try to login with created user
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
