https://bugs.kde.org/show_bug.cgi?id=396434
Bug ID: 396434
Summary: Uncontrolled log messages oversize log file up to run
out of disk space
Product: digikam
Version: 5.9.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: NOR
Component: Albums-Engine
Assignee: digikam-bugs-n...@kde.org
Reporter: rafael.linux.u...@gmail.com
Target Milestone: ---
Creating the database for a shared folder with 370K photos, all was fine,
apparently. However, while Digikam was working, after a lot of hours, OpenSUSE
gave me an error telling he can't write to disk. It was something extrange,
cause the mysql database should not be greater than 5GiB. However, after some
time looking for the problem, I discovered that the /var/log/messages file had
been grow to 62GB (yes, 62) while Digikam was working, making OpenSUSE run out
of space in system folder.
Here is an extract of messages:
2018-07-12T00:00:18.272846+02:00 DB24469-L digikam[19803]: digikam.database:
Adding new item "/hidden_path/_MG_3156.JPG"
2018-07-12T00:00:18.274130+02:00 DB24469-L digikam[19803]: digikam.metaengine:
DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2016-02-27 15:06:50.000
CET Qt::TimeSpec(LocalTime))
2018-07-12T00:00:18.274569+02:00 DB24469-L digikam[19803]: digikam.metaengine:
DateTime (Exif digitalized): sáb. feb. 27 15:06:50 2016
2018-07-12T00:00:18.274911+02:00 DB24469-L digikam[19803]: digikam.metaengine:
Orientation => Exif.Image.Orientation => 1
2018-07-12T00:00:18.278648+02:00 DB24469-L digikam[19803]: digikam.database:
Scanning took 122 ms
2018-07-12T00:00:18.279756+02:00 DB24469-L digikam[19803]: digikam.database:
Finishing took 1 ms
2018-07-12T00:00:18.378067+02:00 DB24469-L digikam[19803]: digikam.dimg:
"/hidden_path/_MG_3157.JPG" : JPEG file identified
2018-07-12T00:00:18.410899+02:00 DB24469-L digikam[19803]: digikam.database:
Adding new item "/hidden_path/_MG_3157.JPG"
2018-07-12T00:00:18.412194+02:00 DB24469-L digikam[19803]: digikam.metaengine:
DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2016-02-27 15:07:03.000
CET Qt::TimeSpec(LocalTime))
2018-07-12T00:00:18.412562+02:00 DB24469-L digikam[19803]: digikam.metaengine:
DateTime (Exif digitalized): sáb. feb. 27 15:07:03 2016
2018-07-12T00:00:18.412908+02:00 DB24469-L digikam[19803]: digikam.metaengine:
Orientation => Exif.Image.Orientation => 1
2018-07-12T00:00:18.416642+02:00 DB24469-L digikam[19803]: digikam.database:
Scanning took 136 ms
2018-07-12T00:00:18.417804+02:00 DB24469-L digikam[19803]: digikam.database:
Finishing took 1 ms
2018-07-12T00:00:18.516686+02:00 DB24469-L digikam[19803]: digikam.dimg:
"/hidden_path/_MG_3158.JPG" : JPEG file identified
2018-07-12T00:00:18.538561+02:00 DB24469-L digikam[19803]: digikam.database:
Adding new item "/hidden_path/_MG_3158.JPG"
2018-07-12T00:00:18.539797+02:00 DB24469-L digikam[19803]: digikam.metaengine:
DateTime => Exif.Photo.DateTimeOriginal => QDateTime(2016-02-27 15:07:10.000
CET Qt::TimeSpec(LocalTime))
2018-07-12T00:00:18.540158+02:00 DB24469-L digikam[19803]: digikam.metaengine:
DateTime (Exif digitalized): sáb. feb. 27 15:07:10 2016
2018-07-12T00:00:18.540541+02:00 DB24469-L digikam[19803]: digikam.metaengine:
Orientation => Exif.Image.Orientation => 1
2018-07-12T00:00:18.544250+02:00 DB24469-L digikam[19803]: digikam.database:
Scanning took 126 ms
2018-07-12T00:00:18.698213+02:00 DB24469-L digikam[19803]: digikam.database:
Finishing took 154 ms
So, as this occurs in a short time, typical desktop linux systems are not
prepared to control this huge grow of the log file.
So, my question now is: Is there some way to tell Digikam not to be so verbose
with normal (not warning or errors) messages?
Thank you
--
You are receiving this mail because:
You are watching all bug changes.
