MonitorWare Knowledge Base

[paladin1974]

Hi all,
I need to store a timestamp with date/time (including milliseconds) to postgreSql and managed to do it, even so as string and not as Date or timestamp type.
Now, I wanted to create a view which shows this high_precision_timestamp together with three or four other SYSLOG information items which are stored in the DB.

First I add the high_precision_timestamp to Fields tab in the Admin Center. Then I added an DBMapping entry. So far so good, but when I want to add a view, LogAnalyser responds with an "Critical Error occured" message. An internal error seems to have occured. (see attachment)

Unfortunatly, I haven't found any documentation about the functionality/dependencies of View/Field/DBMapping settings . Is there documentation on these topics available?

Any help is welcome!
By the way, I am running LogAnalyzer 3.0.0.

[paladin1974]

Servus,
I have to make an addition. Sorry, I have just now enabled the debug output. Created user and group and assigned a newly created view to the goup, but the error still exist and LogAnalyzer logs following ErrorMessage to (r)SysLog:

LogAnalyzer[15446]: DB_PrintError: Database error: Invalid SQL: INSERT INTO logcon_views (DisplayName, Columns, userid, groupid) #012#011#011#011#011#011#011#011VALUES ('test', #012#011#011#011#011#011#011#011'devicereportedtime, msg, logtime_high_precision, FROMHOST',#012#011#011#011#011#011#011#011null, #012#011#011#011#011#011#011#0111 #012#011#011#011#011#011#011#011) <br>mysql error:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version ....

Well, I am a bit puzzled about the #012#011... pattern which I never seen before, should I?

Guess, this should be something like an container?

[alorbach]

Hi,

very odd. Is this really a clean installation or have you modified the codefiles?
Because to be honest I have no idea from where this #011 strings come, and how they end up in the middle of the SQL Statement.

best regards,
Andre Lorbach

[rgerhards]

not sure if that helps anything, but 011 is 9, thus US ASCII tab if encoded in octal. #octal is something that rsyslog does by default for control characters, but I don't see how this could be related here...

[manikutty]

I too have the similar problem. I have 3.0.1 version of LogAnalyzer and PHP 5.0.4 running on Fedora 4.
Please help.

Thanks
MK

[manikutty]

I too have the similar problem. I have 3.0.1 version of LogAnalyzer and PHP 5.0.4 running on Fedora 4.
Please help.

Thanks
MK

Also I do not see any error messages or strange chars on syslog or web server logs.

[Burn]

I too have the similar problem. I have 3.0.1 version of LogAnalyzer and PHP 5.0.4 running on Fedora 4.
Please help.

Thanks
MK

Also I do not see any error messages or strange chars on syslog or web server logs.

I think you can start with updating your software

[manikutty]

I too have the similar problem. I have 3.0.1 version of LogAnalyzer and PHP 5.0.4 running on Fedora 4.
Please help.

Thanks
MK

Also I do not see any error messages or strange chars on syslog or web server logs.

I think you can start with updating your software

I found the problem. This was happening due to a code bug in views.php. The logcon_views table has a column with name as
'Columns' which I think is a reserved word in mysql. The query in the code was
$sqlquery = "INSERT INTO " . DB_VIEWS. " (DisplayName, Columns, userid, groupid) . I added backticks to the word
Columns and it worked !.
Here is the modified query :
$sqlquery = "INSERT INTO " . DB_VIEWS. " (DisplayName, `Columns`, userid, groupid)

-mk