You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been running Spoolman for a few months with no issues until yesterday. Now I can’t access my database. I have tried everything I could think of and even started from scratch but the installation can’t seem to connect to a database even though the logs says that it is. I have tried this on the Pi running my Neptune 4 Pro (original install location) and on docker on a linux machine. Both have the same issue.
I just did another fresh install on the Pi and have the above screenshot and the complete log below. I can’t add anything to this either. Notice that it doesn’t even show the version number it is just a spinning icon.
2024-10-09 14:07:52:INFO:Starting Spoolman v0.20.0 (commit: 4f8d5ab) (built: 2024-09-08 20:43:53+00:00)
2024-10-09 14:07:52:INFO:Using data directory: /home/mks/.local/share/spoolman
2024-10-09 14:07:52:INFO:Using logs directory: /home/mks/.local/share/spoolman
2024-10-09 14:07:52:INFO:Using backups directory: /home/mks/.local/share/spoolman/backups
2024-10-09 14:07:52:INFO:Setting up database...
2024-10-09 14:07:52:INFO:No database type specified, using a default SQLite database located at "/home/mks/.local/share/spoolman/spoolman.db"
2024-10-09 14:07:52:INFO:Performing migrations...
2024-10-09 14:07:57:INFO:Scheduling automatic database backup for midnight.
2024-10-09 14:07:57:INFO:Scheduling external DB sync.
2024-10-09 14:07:57:INFO:Startup complete.
2024-10-09 14:07:57:INFO:Syncing external DB.
2024-10-09 14:07:57:INFO:HTTP Request: GET https://donkie.github.io/SpoolmanDB/filaments.json "HTTP/1.1 200 OK"
2024-10-09 14:07:58:INFO:HTTP Request: GET https://donkie.github.io/SpoolmanDB/materials.json "HTTP/1.1 200 OK"
2024-10-09 14:07:58:INFO:External DB synced. Filaments: 2596, Materials: 23
2024-10-09 14:08:01:INFO:Client 192.168.15.7 is now listening on pool spool
2024-10-09 14:08:10:INFO:Client 192.168.15.99 is now listening on pool
The text was updated successfully, but these errors were encountered:
I have been running Spoolman for a few months with no issues until yesterday. Now I can’t access my database. I have tried everything I could think of and even started from scratch but the installation can’t seem to connect to a database even though the logs says that it is. I have tried this on the Pi running my Neptune 4 Pro (original install location) and on docker on a linux machine. Both have the same issue.
I just did another fresh install on the Pi and have the above screenshot and the complete log below. I can’t add anything to this either. Notice that it doesn’t even show the version number it is just a spinning icon.
2024-10-09 14:07:52:INFO:Starting Spoolman v0.20.0 (commit: 4f8d5ab) (built: 2024-09-08 20:43:53+00:00)
2024-10-09 14:07:52:INFO:Using data directory: /home/mks/.local/share/spoolman
2024-10-09 14:07:52:INFO:Using logs directory: /home/mks/.local/share/spoolman
2024-10-09 14:07:52:INFO:Using backups directory: /home/mks/.local/share/spoolman/backups
2024-10-09 14:07:52:INFO:Setting up database...
2024-10-09 14:07:52:INFO:No database type specified, using a default SQLite database located at "/home/mks/.local/share/spoolman/spoolman.db"
2024-10-09 14:07:52:INFO:Performing migrations...
2024-10-09 14:07:57:INFO:Scheduling automatic database backup for midnight.
2024-10-09 14:07:57:INFO:Scheduling external DB sync.
2024-10-09 14:07:57:INFO:Startup complete.
2024-10-09 14:07:57:INFO:Syncing external DB.
2024-10-09 14:07:57:INFO:HTTP Request: GET https://donkie.github.io/SpoolmanDB/filaments.json "HTTP/1.1 200 OK"
2024-10-09 14:07:58:INFO:HTTP Request: GET https://donkie.github.io/SpoolmanDB/materials.json "HTTP/1.1 200 OK"
2024-10-09 14:07:58:INFO:External DB synced. Filaments: 2596, Materials: 23
2024-10-09 14:08:01:INFO:Client 192.168.15.7 is now listening on pool spool
2024-10-09 14:08:10:INFO:Client 192.168.15.99 is now listening on pool
The text was updated successfully, but these errors were encountered: