[GH-ISSUE #5] Error: no such column: invite_email #4

Closed
opened 2026-03-04 00:59:35 +03:00 by kerem · 4 comments
Owner

Originally created by @AzatGo on GitHub (Mar 3, 2024).
Original GitHub issue: https://github.com/sirtoobii/vaultwarden_ldap_sync/issues/5

hi аirst of all, I wanted to say thank you for LDAP connector. I am getting an error, maybe you could help me out?
Database used sqlite
ERROR [sync.py] Something went wrong. Error: no such column: invite_email

Originally created by @AzatGo on GitHub (Mar 3, 2024). Original GitHub issue: https://github.com/sirtoobii/vaultwarden_ldap_sync/issues/5 hi аirst of all, I wanted to say thank you for LDAP connector. I am getting an error, maybe you could help me out? Database used sqlite `ERROR [sync.py] Something went wrong. Error: no such column: invite_email`
kerem 2026-03-04 00:59:35 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@sirtoobii commented on GitHub (Mar 3, 2024):

There is most likely something wrong with you sqlite database file, specifically, the init_db() has not been called or something when wrong during the creation of the initial schema (check for other error message during startup).
Are you using the dockerized version? If yes, it might help to delete the /data/ldap_sync.sqlite file.

<!-- gh-comment-id:1975280875 --> @sirtoobii commented on GitHub (Mar 3, 2024): There is most likely something wrong with you sqlite database file, specifically, the [init_db() ](https://github.com/sirtoobii/vaultwarden_ldap_sync/blob/316c4a0f812c648b3a04e578ddf5a2a6a348f03d/vaultwarden_ldap_sync/LocalStorage.py#L16)has not been called or something when wrong during the creation of the initial schema (check for other error message during startup). Are you using the dockerized version? If yes, it might help to delete the `/data/ldap_sync.sqlite` file.
Author
Owner

@AzatGo commented on GitHub (Mar 4, 2024):

Yes, I run in the docker.
Removal /data/ldap_sync.sqlite helped.

SMTP is configured correctly and test messages are being sent. However, the invites from the LDAP connector are not coming through.

2024-03-04:11:25:46 DEBUG [connectionpool.py] Starting new HTTPS connection (1): ****:443
2024-03-04:11:25:46 DEBUG [connectionpool.py] https://****:443 "GET /admin/users HTTP/1.1" 200 3324
2024-03-04:11:25:46 DEBUG [sync.py] Found 0 vanished user(s)
2024-03-04:11:25:46 DEBUG [sync.py] Found 0 deleted user(s)
2024-03-04:11:25:46 DEBUG [sync.py] Found 0 disabled user(s)
2024-03-04:11:25:46 DEBUG [sync.py] Found 0 enabled user(s)
2024-03-04:11:25:46 DEBUG [sync.py] Found 0 user(s) with changed emails
2024-03-04:11:25:46 DEBUG [VaultwardenConnector.py] Cookie store found, loading
2024-03-04:11:25:46 DEBUG [connectionpool.py] https://****:443 "GET /admin/users HTTP/1.1" 200 3324
2024-03-04:11:25:46 DEBUG [sync.py] Found 4 user(s) to invite
2024-03-04:11:25:46 DEBUG [sync.py] Found 0 user(s) to disable
2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com
2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com
2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com
2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com

<!-- gh-comment-id:1975911288 --> @AzatGo commented on GitHub (Mar 4, 2024): Yes, I run in the docker. Removal /data/ldap_sync.sqlite helped. SMTP is configured correctly and test messages are being sent. However, the invites from the LDAP connector are not coming through. `2024-03-04:11:25:46 DEBUG [connectionpool.py] Starting new HTTPS connection (1): ****:443` `2024-03-04:11:25:46 DEBUG [connectionpool.py] https://****:443 "GET /admin/users HTTP/1.1" 200 3324` `2024-03-04:11:25:46 DEBUG [sync.py] Found 0 vanished user(s)` `2024-03-04:11:25:46 DEBUG [sync.py] Found 0 deleted user(s)` `2024-03-04:11:25:46 DEBUG [sync.py] Found 0 disabled user(s)` `2024-03-04:11:25:46 DEBUG [sync.py] Found 0 enabled user(s)` `2024-03-04:11:25:46 DEBUG [sync.py] Found 0 user(s) with changed emails` `2024-03-04:11:25:46 DEBUG [VaultwardenConnector.py] Cookie store found, loading` `2024-03-04:11:25:46 DEBUG [connectionpool.py] https://****:443 "GET /admin/users HTTP/1.1" 200 3324` `2024-03-04:11:25:46 DEBUG [sync.py] Found 4 user(s) to invite` `2024-03-04:11:25:46 DEBUG [sync.py] Found 0 user(s) to disable` `2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com` `2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com` `2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com` `2024-03-04:11:25:46 INFO [sync.py] Invite user ***@gmail.com`
Author
Owner

@sirtoobii commented on GitHub (Mar 10, 2024):

Could it be that DRYRUN mode is still active?

<!-- gh-comment-id:1987297261 --> @sirtoobii commented on GitHub (Mar 10, 2024): Could it be that [DRYRUN](https://github.com/sirtoobii/vaultwarden_ldap_sync/blob/316c4a0f812c648b3a04e578ddf5a2a6a348f03d/.env.dist#L41) mode is still active?
Author
Owner

@AzatGo commented on GitHub (Mar 19, 2024):

I'm sorry for answering so late. Thank you for your advice DRYRUN. It was very helpful!

<!-- gh-comment-id:2007643649 --> @AzatGo commented on GitHub (Mar 19, 2024): I'm sorry for answering so late. Thank you for your advice DRYRUN. It was very helpful!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden_ldap_sync#4
No description provided.