[7.4.2] Where to configure log archiving ?

Home Forums Convertigo Products [7.4.2] Where to configure log archiving ?


This topic contains 4 replies, has 2 voices, and was last updated by  Emmanuel Jamet 1 year, 4 months ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #152490

    Emmanuel Jamet


    I was wondering if there would be a way to configure log archiving in Convertigo Admin Console.

    For 10 files of 10KB, we eventually get :

    -rw-rw-r-- 1 jboss jboss        0 May 29  2015 audit.log
    -rw-rw-r-- 1 jboss jboss 10486036 Jan 27 11:38 engine.iycz2jiv.iyfoebbu.log
    -rw-rw-r-- 1 jboss jboss 10840341 Jan 27 11:39 engine.iyfoebbv.iyfoebbv.log
    -rw-rw-r-- 1 jboss jboss 10903220 Jan 27 11:50 engine.iyfoexrt.iyfoexrt.log
    -rw-rw-r-- 1 jboss jboss 10878895 Jan 27 15:48 engine.iyfotcth.iyfotcth.log
    -rw-rw-r-- 1 jboss jboss 10486348 Jan 30 14:26 engine.iyfxbq24.iyk4pah7.log
    -rw-rw-r-- 1 jboss jboss     8841 Feb  2 14:30 engine.log
    -rw-rw-r-- 1 jboss jboss    10443 Feb  2 14:30 engine.log.1
    -rw-rw-r-- 1 jboss jboss    10608 Feb  2 14:30 engine.log.10
    -rw-rw-r-- 1 jboss jboss    11121 Feb  2 14:30 engine.log.2
    -rw-rw-r-- 1 jboss jboss    11377 Feb  2 14:30 engine.log.3
    -rw-rw-r-- 1 jboss jboss    10446 Feb  2 14:30 engine.log.4
    -rw-rw-r-- 1 jboss jboss    10773 Feb  2 14:30 engine.log.5
    -rw-rw-r-- 1 jboss jboss    11049 Feb  2 14:30 engine.log.6
    -rw-rw-r-- 1 jboss jboss    10679 Feb  2 14:30 engine.log.7
    -rw-rw-r-- 1 jboss jboss    11017 Feb  2 14:30 engine.log.8
    -rw-rw-r-- 1 jboss jboss    12068 Feb  2 14:30 engine.log.9

    We would like to get rid of the first 5 “engine.*.*.log” files, wherereas the Console gives access to standard log4j configuration for the default appender only the 11 last files in the above list.



    Gregory Vorbe

    Howdy, Emmanuel

    “engine.*.*.log” files are generated when you consult logs through the Convertigo Web Administration Console widget.
    These files are renamed files from the standard “engine.log.x” files to fit the widget syntax to parse log files (just “engine.log.x”).
    If you don’t look at logs through Administration Console, you’ll never have those kind of files.
    If you delete them you’ll loose some past logs.
    It seems you changed the “Log4J audit appender max file size” property to 10 (without unit). That will create log files of 10KB size instead of default 10MB, was it intentional ? You may end up with a large amount of 10KB files, depending on logs level.
    More “Logs” configuration are available in the “Config” widget of Administration Console, but can’t setup the way Logs widget is renaming the Log4j files.



    Emmanuel Jamet


    Thank you again for the quick answer.

    I can now understand better what are these files.

    We indeed changed the log config to 10 10KB files, only for test purpose. Production servers still have 100 10MB files configured.

    In my opinion, log retention should only be provided by log4j managed files. These other files aren’t necessary other that to fit the widget syntax, so should be cleaned frequently, otherwise the growth will become a problem in Production environment.

    Is it planned to add such a cleaning within Convertigo soon ?



    Gregory Vorbe

    These files are not duplicates of existing log4j files but only renamed ones, this will not double the occupied disk space as it is not new files.
    I forgot to mention that in “Logs” widget you have a feature to purge logs older than a particular datetime (based on engine.xxx.yyy.log).
    It is possible to call Convertigo Administration API to authenticate to the portal and then call the purge servlet.
    For example:

    curl "http://localhost:18080/convertigo/admin/services/services/engine.Authenticate" -d "authUserName=admin&authPassword=admin&authType=login" -c "D:\tmp\cookies.txt"
    curl "http://localhost:18080/convertigo/admin/services/logs.Purge" -b "D:\tmp\cookies.txt" -d "action=delete_files&date= 2017-02-01 23:59:59,999 "



    Emmanuel Jamet


    I thought these files were duplicates, indeed.

    Whereas this mechanism does not double the occupied disk space, it makes the applictaion more complex to maintain in Production environment, where the rule is to have all log files managed.

    The logging configuration section of the Console thus covers only a part of logging and forces us to create a custom purge script.
    Even if the API can provide a better way to purge a range of files based on a particular datetime, the problem remains the same :

    we need a simple way to configure the log files creation and retention to prevent a unmanaged growth of the disk usage.


Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.