Atuin stopped working on local XFS storage

Help
1

I have been using Atuin and loving it on my home laptop, and was successfully using it for several months on my Linux server at work. Then one day, it suddenly stopped working. I was originally hosting my database in a directory on my local XFS disk that has been NFS exported - this worked wonderfully for maintaining command history across any machine in our compute cluster. Then one day, I got the dreaded “Error: pool timed out while waiting for an open connection”.

I know that there are sometime issues with NFS, so I have changed my config.toml to point to a path that is not NFS shared. Even after moving my old database out of the way, this is what I see:

mamartin@pegasus: ~
[] (nfs) 
$> eval "$(atuin init bash)"
mamartin@pegasus: ~
[] (nfs) 
$> aError: pool timed out while waiting for an open connection
-- INSERT --
Location:
    /home/runner/work/atuin/atuin/crates/atuin-client/src/record/sqlite_store.rs:48:20
atuError: pool timed out while waiting for an open connection

Location:
    /home/runner/work/atuin/atuin/crates/atuin-client/src/record/sqlite_store.rs:48:20
atuin doctor
Error: pool timed out while waiting for an open connection

Location:
    /home/runner/work/atuin/atuin/crates/atuin-client/src/record/sqlite_store.rs:48:20
Error: pool timed out while waiting for an open connection

Location:
    /home/runner/work/atuin/atuin/crates/atuin-client/src/record/sqlite_store.rs:48:20
[ble: exit 1]
mamartin@pegasus: ~
[] (nfs) 
$>

As such, Atuin has become completely unusable for me, and I am finding myself crippled at work. So, I have a couple questions:

  1. Has anyone else experienced any issues with XFS? I have found issues with ZFS and NFS, but neither of those seem applicable.
  2. Is this possibly some sort of corporate firewall/anti-virus/anti-malware issue, where a needed port for the SQLITE database is being blocked? If so, how can I diagnose this?

I just updated to 18.4.0, and confirm the same behavior. I’m not sure how to provide any diagnostic info, since atuin doctor won’t even run. Thanks so much!

Matt

2

I’m not yet aware of any issues with XFS - it definitely won’t be a corporate firewall type issue though, as SQLite doesn’t use any network ports/etc.

Does running sqlite3 ~/.local/share/atuin/history.db work ok? You may need to install the database client

3

Yes, running sqlite3 seems to work just fine

mamartin@pegasus: /data/users/mamartin/atuin
[]
$> sqlite3 history.db
SQLite version 3.26.0 2018-12-01 12:34:55
Enter ".help" for usage hints.
sqlite> .tables
_sqlx_migrations  history         
sqlite>
4

The different path is due to the fact that my home directory is actually NFS mounted to be accessible from every machine I might log into. That used to work, until I got hammered by antivirus software running on the filer that hosts the home directories. I moved to my local machine and that worked great for a couple months, and now it is completely non functional :frowning:

Here is my config.toml

mamartin@pegasus: ~/.config/atuin
[] (nfs) 
$> cat config.toml | sed '/^#/d;/^$/d'
db_path = "/data/users/mamartin/atuin/history.db"
auto_sync = false
filter_mode_shell_up_key_binding = "session"
enter_accept = true
keymap_mode = "auto"
local_timeout = 1
[stats]
[keys]
[sync]
records = true
[preview]
[daemon]
mamartin@pegasus: ~/.config/atuin
[] (nfs) 
$>