MonitorWare Knowledge Base

Hi,

I'm using rsyslog's default Template to write Syslog data into Postgresql, and configured phpLogCon as follows:

$CFG['Sources']['Source1']['ID'] = 'Source1';
$CFG['Sources']['Source1']['Name'] = 'xxx';
$CFG['Sources']['Source1']['ViewID'] = 'SYSLOG';
$CFG['Sources']['Source1']['SourceType'] = SOURCE_PDO;
$CFG['Sources']['Source1']['DBTableType'] = 'monitorware';
$CFG['Sources']['Source1']['DBType'] = DB_PGSQL;
$CFG['Sources']['Source1']['DBServer'] = 'localhost';
$CFG['Sources']['Source1']['DBName'] = 'Syslog';
$CFG['Sources']['Source1']['DBUser'] = 'phplogcon';
$CFG['Sources']['Source1']['DBPassword'] = 'xxx';
$CFG['Sources']['Source1']['DBTableName'] = 'systemevents';
$CFG['Sources']['Source1']['DBEnableRowCounting'] = false;

Due to the wonders of the ps command, I can tell that phpLogCon is able to log in to the postgresql database correctly. However, the web interface shows me a number of empty rows equal to the number of rows in the database. Any hints would be appreciated...

• Custom phpLogCon configuration?
• Maintenance Contract?
• Installation support?

There seems to be a problem or bug within the new PDO Database Source, I will look into this today and possibly create an updated today or tomorrow.

best regards,
Andre Lorbach

Hi again,

I want to inform you that I have fixed the issue of empty rows in version 2.3.8 available for download here:
http://www.phplogcon.org/downloads

best regards,
Andre Lorbach

Hi,

I am the workmate of mgoetze.

The problem still exists! There are just empty lines to see.

I restartet the postgres database with debugging output and took a look at the statement that
is executed if I request /phplogcon/index.php?sourceid=Source1. The statement is

SELECT ID, DeviceReportedTime, Facility, Priority, FromHost, SysLogTag, InfoUnitID, Message FROM systemevents ORDER BY ID DESC

The statement is correct. If I execute it on the database directly I got a lot of data.

Do you need some debug info?

Cheers,
Jonny

Hrm I guess I need to do some further testing with Postgresql then on a test machine.
I will look into this very soon and let you know when I find something.

One thing just came to my mind! Have you checked if the systemevents table is spelled like this in your database?
"SystemEvents"

phpLogCon uses lowercase "systemevents" by default (also in your case).

I am currently working on an enhanced verification system to find such error's or problems better. This will be most likely available in Version 2.5.2.

best regards,
Andre Lorbach

Thanks for the info, it was a guess. I had a simular issue in MYSQL a few days ago.
So I am going to look into it very soon once I have finished this new feature (Which I wrote about in my previous post).

best regards,
Andre Lorbach

Hi again,

I want to inform you that Version 2.5.2 has been released and is available for download here:
http://www.phplogcon.org/downloads

If possible please try this version, it may outputs an error with more details as I have enhanced the error analysis within the logstream sources. I will do the testings with Postgresql during meantime.

best regards,
Andre Lorbach

Thanks, it runs.