LogAnalyzer v3.2.1 (v3-stable) released

Hi all,

We have just released LogAnalyzer 3.2.1. The new stable release has the following changes:

  • Fixed timezone parsing in GetEventTime function. This caused problems reading date/time strings with negative timezone offsets.
  • Added option to disable context links in LogAnalyzer.

Download:

http://loganalyzer.adiscon.com/downloads/loganalyzer-v3-2-1

As always, feedback is appreciated.

Best regards,
Florian Riedl

Tags: , , ,

3 Responses to “LogAnalyzer v3.2.1 (v3-stable) released”

  1. Dominique says:

    Hi,

    it is a great programm, but they are two Bugs:

    A change by "Select Language " get:
    Notice: Undefined index: gen_lang in /var/www/LogAnalyzer/3.2.1/src/include/functions_themes.php on line 51 Notice: Undefined index: gen_lang in /var/www/LogAnalyzer/3.2.1/src/include/functions_themes.php on line 51 Notice: Undefined index: gen_lang in /var/www/LogAnalyzer/3.2.1/src/include/functions_themes.php on line 51 Notice: Undefined index: gen_lang in /var/www/LogAnalyzer/3.2.1/src/include/functions_themes.php on line 51

    And sometine the Search ist on the Default Source, not on the defined Source, i think the Session timed out or is not corretct defined, when the User too fast change the Source.

    Greetings
    Dominique

  2. Arthur Duarte says:

    A way to get around this error message would be adding a "@" in front of the lines containing the "gen_lang" in the functions_theme.php file:

    // — gen_lang
    $content[‘LANGUAGES’][$i][‘langcode’] = $alldirectories[$i];
    if (@$content[‘gen_lang’] == $alldirectories[$i] )
    @$content[‘LANGUAGES’][$i][‘selected’] = "selected";
    else
    @$content[‘LANGUAGES’][$i][‘selected’] = "";
    // —

    This would hide the PHP "Notice" messages.

    Thank You.

  3. Harry says:

    Hi,
    I’m really newbie using Linux (Debian), for the fun I have installed and configured rsyslog, MySQL, PostGreSQL and LogAnalyser. At first, I have installed version 3.0.4 (works great, no problem !) and after version 3.2.1 (both working a the same time with separate installations). In version 3.2.1, when I choose "Syslog Fields", LogAnalyser doesn’t work with PostGreSQL database. LogAnalyser say’s "No syslog records found". However, it works with "Eventlog Fields" and "Webserver Fields".
    Hope this help.
    Regards,
    Harry

Leave a Reply