[1.4.2] ZABBIX-Server crash (PostgreSQL)

[NOB]

Hi,

I added one active item (log watcher) and the server crashed a few
minutes later.

Here is the error message in the zabbix_server.log file:

 88845:20071214:154232 Query::update items set nextcheck=1197643472,prevvalue=la
stvalue,lastvalue='16.10.2007   22:47:20        Deleted         NT AUTHORITY\\NE
TWORK SERVICE   D:\\Program Files (x86)\\Microsoft Forefront Security\\Exchange 
Server\\FSECCRService.exe       D:\\Program Files (x86)\\Microsoft Forefront Sec
urity\\Exchange Server\\Data\\Engines\\x86\\Kaspersky5\\Bin\\dailyc.txt Univ.scr
ipt/99a (Virus)',lastclock=1197643352 where itemid=500000000020292
 88845:20071214:154232 Query failed:PGRES_FATAL_ERROR:ERROR:  value too long for
 type character varying(255)
 88845:20071214:154232 Query::select distinct function,parameter,itemid,lastvalu
e from functions where itemid=500000000020292
 88845:20071214:154232 Query failed:PGRES_FATAL_ERROR:ERROR:  current transactio
n is aborted, commands ignored until end of transaction block

I fixed it by enlarging the lastvalue field in DB table items to varchar (512) and restarting the server prozess.
I am not sure, whether this is the right fix, but it works for me

Waiting for 1.6 to arrive !

Regards

Norbert.

[Aly]

Let me guess, you use pgsql8.3b ?!

[NOB]

Let me guess, you use pgsql8.3b ?!

Sorry to not mention it: 8.2.4 on FreeBSD 6.1

Regards

Norbert.

[mbarthelemy]

Hi all, Hi Alexei,

No, this kind of problem is not specific to PG 8.3.
The fields defined when we create the database schema are too short (255 chars), especially with items like eventlog[] or log[]. Someone suggested on another thread related to the same problem that these fields should even be set to type 'text' for postgres (allows compression, does not put any size limit).
Would it be possible to change the schema creation script (and even provide an update schema) for zabbix 1.4.5?