Running G2 on Linux systems you encounter the following or a similar error with a default SQLite configuration:
Exporting to g2report.g2v ...
Traceback (most recent call last):
File "G2Report.py", line 1043, in <module>
exportToCsv()
File "G2Report.py", line 715, in exportToCsv
cursor = odsDbo.sqlExec('select * from DBREPORT_DETAIL_VIEW order by ENTITY_CATEGORY1,
ENTITY_CATEGORY2, REPORT_CATEGORY, AUDIT_NAME, AUDIT_KEY, RECORD_SEQ')
File "/opt/senzing/g2/python/G2Database.py", line 107, in sqlExec
raise self.TranslateException(err)
File "/opt/senzing/g2/python/G2Database.py", line 313, in TranslateException
raise G2Exception.G2DBUnknownException(errMessage)
G2Exception.G2DBUnknownException: database or disk is full
Note: This example is from the G2Report utility, the main focus is G2Exception.G2DBUnknownException: database or disk is full
First, check that any filesystems haven't filled up, use the df command to check the usage and available space:
- df -h
If you determine you have ample storage space on the filesystems and can't account for such an error it is likely the temp space utilised by SQLite and will need re-configuring - Temporary Files Used By SQLite
A one liner to capture the disk usage to a file during a long running process when you're not sure what might be filling up:
- while true; do df -h | tee -a df.out; echo >> df.out; sleep 2; done
To watch the disk usage in real time as a process is running, changes will be highlighted as they occur:
- watch -d 'df -h'
Comments
0 comments
Please sign in to leave a comment.