report : trigger creation in 3.3.O version

Everything which is related to the installation of phpLogCon.

Google Ads


report : trigger creation in 3.3.O version

Postby plebreton » Fri Nov 18, 2011 2:44 pm

Hello

i installed the new version 3.3.0.
each time i edit my report i have :
The datasource 'Syslog-NG' does not have a TRIGGER installed to automatically generate the message checksum on INSERT. Creating the TRIGGER will speedup the report generation.

Do you want LogAnalyzer to create the TRIGGER now?

But the trigger exist.

Philippe
plebreton
Avarage
 
Posts: 12
Joined: Tue Nov 16, 2010 9:52 am

Urgent Question?

  • Pulling out your Hair?
  • Wasting Time and Money?
  • Deadline Approaching?

Re: report : trigger creation in 3.3.O version

Postby alorbach » Fri Nov 18, 2011 2:57 pm

Which database are you using, mysql, mssql or postgresql? Can you enable debug output in admin preferences?
There should be some useful output at the bottom of the report admin page.

best regards,
Andre Lorbach
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Re: report : trigger creation in 3.3.O version

Postby plebreton » Fri Nov 18, 2011 3:30 pm

I use mysql.

debub output :

UltraDebug
LogStreamDB|VerifyFields: Found Field for 'id'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'datetime'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'host'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'msg_type'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'facility'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'priority'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'program'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'pid'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'msg'
UltraDebug
LogStreamDB|VerifyFields: Found Field for 'checksum'
UltraDebug
LogStreamDB|VerifyIndexes: Found INDEX for 'host'
UltraDebug
LogStreamDB|VerifyIndexes: Found INDEX for 'checksum'
UltraDebug
LogStreamDB|VerifyIndexes: Found INDEX for 'datetime'
UltraDebug
LogStreamDB|VerifyIndexes: Found INDEX for 'priority'
UltraDebug
LogStreamDB|VerifyIndexes: Found INDEX for 'msg_type'
Warning
LogStreamDB|VerifyChecksumTrigger: Missing TRIGGER 'CF_logs_msg' for Table 'logs'
Debug
LogStream|SetFilter: SetFilter combined = 'source:sng syslogtag:sample'.
plebreton
Avarage
 
Posts: 12
Joined: Tue Nov 16, 2010 9:52 am

Re: report : trigger creation in 3.3.O version

Postby alorbach » Fri Nov 18, 2011 3:38 pm

And if you run "SHOW TRIGGERS" command using phpmyadmin sql for example, you see a trigger named: CF_logs_msg ?
It is possible that the automatic trigger creation fails if your database user does not have the SUPER privilege which is required to create triggers in mysql.

best regards,
Andre Lorbach
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Re: report : trigger creation in 3.3.O version

Postby plebreton » Fri Nov 18, 2011 3:54 pm

The trigger is present :


[cfp00@systeme-sng ~]$ mysql -u CF -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2391
Server version: 5.1.30-log MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

(CF@localhost) [(none)]> connect CF
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Connection id: 2392
Current database: CF

(CF@localhost) [CF]> show triggers;
+-------------+--------+-------+----------------------------------------------------------+--------+---------+----------+---------+----------------------+----------------------+--------------------+
| Trigger | Event | Table | Statement | Timing | Created | sql_mode | Definer | character_set_client | collation_connection | Database Collation |
+-------------+--------+-------+----------------------------------------------------------+--------+---------+----------+---------+----------------------+----------------------+--------------------+
| CF_logs_msg | INSERT | logs | BEGIN
SET NEW.checksum = crc32(NEW.msg);
END | BEFORE | NULL | | CF@% | latin1 | latin1_swedish_ci | latin1_swedish_ci |
+-------------+--------+-------+----------------------------------------------------------+--------+---------+----------+---------+----------------------+----------------------+--------------------+
1 row in set (0.00 sec)

(CF@localhost) [CF]>
plebreton
Avarage
 
Posts: 12
Joined: Tue Nov 16, 2010 9:52 am

Re: report : trigger creation in 3.3.O version

Postby alorbach » Fri Nov 18, 2011 6:06 pm

Did you create the trigger manually or did LogAnalayzer create it automatically?
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Re: report : trigger creation in 3.3.O version

Postby plebreton » Mon Nov 21, 2011 9:28 am

Hello,

It's Loganalyzer.

Philippe
plebreton
Avarage
 
Posts: 12
Joined: Tue Nov 16, 2010 9:52 am

Re: report : trigger creation in 3.3.O version

Postby jenns » Wed Jan 11, 2012 4:18 am

Hi,

Is there any solution to this issue? I encounter exactly the same issue. I use rsyslog and mysql database. the trigger is automatically created by the loganalyzer, however it keep prompting a message that it does not exist and ask again if you want to create the trigger. creating the trigger the second time will result in error because the first trigger had actually been successfully created and exist in MySQL database.

I tried to create the trigger manually in MySQL database, but it prompted error that the syntax is wrong.

Can anyone helps?

TIA!
jenns
New
 
Posts: 3
Joined: Wed Jan 11, 2012 4:14 am

Re: report : trigger creation in 3.3.O version

Postby jenns » Wed Jan 11, 2012 7:31 am

Below is the error message shown when i tried to manually create the trigger:
mysql> CREATE TRIGGER SyslogDB_SystemEvents_message BEFORE INSERT ON `SystemEvents`
-> FOR EACH ROW
-> BEGIN
-> SET NEW.checksum = crc32(NEW.message);
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 4
mysql> END
-> ;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'END' at line 1
mysql>
jenns
New
 
Posts: 3
Joined: Wed Jan 11, 2012 4:14 am

Re: report : trigger creation in 3.3.O version

Postby alorbach » Wed Jan 11, 2012 5:54 pm

Code: Select all
CREATE TRIGGER SyslogDB_SystemEvents_message BEFORE INSERT ON `SystemEvents`
FOR EACH ROW
BEGIN
SET NEW.checksum = crc32(NEW.message);
END
;


Should work, if not try to use phpmyadmin to run the full SQL Command.
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Re: report : trigger creation in 3.3.O version

Postby jenns » Thu Jan 12, 2012 7:13 am

Thanks, I finally manage to create the trigger manually in PhpMyAdmin by changing the default delimiter to other than ';'. However, when i go back to the Report Modules in LogAnalyzer, it's still shows the Logstream performance warning and still asking the same question whether we want to create a trigger or not.
jenns
New
 
Posts: 3
Joined: Wed Jan 11, 2012 4:14 am

Re: report : trigger creation in 3.3.O version & 3.4.1

Postby deveng » Sun Jan 22, 2012 1:04 am

Yeah I feel your pain with this and I am trying to use 3.4.1

System Arch: RHEL5,Mysql5,Apache2,PHP5

I am getting the same errors with no results, I have been trying for at least 3 hrs uninstalling and reinstalling multiple times.
I also do not get any buttons displayed on the "Reports" page, so I will revert back to a working version of this software until this is fixed.


Trigger issues:
log1.PNG
Trigger issues???
log1.PNG (32.16 KiB) Viewed 20576 times


No Buttons:
log2.PNG
Where are the buttons????
log2.PNG (26.38 KiB) Viewed 20576 times





Problem Solved:
UPDATE YOUR MYSQL DATABASE !5.0.77



Thanks
Dev
deveng
New
 
Posts: 1
Joined: Sun Jan 22, 2012 12:51 am

Google Ads



Return to Installation

Who is online

Users browsing this forum: No registered users and 0 guests

cron