Bug 396434 - Uncontrolled log messages oversize log file up to run out of disk space
Summary: Uncontrolled log messages oversize log file up to run out of disk space
Status: RESOLVED UPSTREAM
Alias: None
Product: digikam
Classification: Applications
Component: Albums-Engine (show other bugs)
Version: 5.9.0
Platform: openSUSE Linux
: NOR critical
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-12 10:55 UTC by Rafael Linux User
Modified: 2018-07-15 08:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Linux User 2018-07-12 10:55:13 UTC
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
Comment 1 caulier.gilles 2018-07-12 20:05:10 UTC
yes digiKam is very verbose if debug trace are enabled.

But digiKam do not write something in Linux log file. All is done in the console only.

So this is typically a OpenSuse customization which re-route the debug trace to a log file. This can be done easily with a Qt customization in settings.

This do not be done for desktop application. Never. This must be possible to customize one by one by end user if necessary. Desktop application are not service in fact.

So the problem must be reported to OpenSuse as well and fixed quickly.

Best

Gilles Caulier
Comment 2 Maik Qualmann 2018-07-12 20:36:13 UTC
What kind of openSUSE version do you use? I've been using openSUSE for 20 years now and have never seen log/messages written by desktop programs. In addition, openSUSE has been using Systemd-journal for quite some time, so a log/messages does not exist at all.

Maik
Comment 3 Rafael Linux User 2018-07-12 21:49:53 UTC
Latest. OpenSUSE 15. In fact, I can't communicate with OpenSUSE forum cause, despite I'm registered, several months ago each time I enter in their forum, any web browers show me "too many redirections" and doesn't not show the forum after being loged. It's happening to more people too.
Comment 4 Maik Qualmann 2018-07-13 11:40:46 UTC
On my service laptop here in the company I also have openSUSE Leap 15. A log/messages does not exist but in the Systemd Journal are actually entries from digiKam, but only after the update to Leap 15 early July. Also other KF5 programs. From my side, it is a bug of openSUSE Leap 15, such logging should not be the standard. A test of openSUSE Tumbleweed is pending.

Maik
Comment 5 Maik Qualmann 2018-07-15 08:08:08 UTC
On openSUSE Tumbleweed there was a short period of a few days, where also messages from desktop programs (also digiKam) appear in the log. Currently this is no longer the case. Try reporting the bug to openSUSE Leap 15. I close the bug now.

Maik