Ad Widget

Collapse

insert errors on auditlog after mysql to psql conversion

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • acalvo
    Member
    • Oct 2010
    • 30

    #1

    insert errors on auditlog after mysql to psql conversion

    Hi,
    We've moved from MySQL to PostgreSQL.
    We get an insert error everytime we do a change to zabbix.

    Code:
    pg_query(): Query failed: ERROR: null value in column "resourcename" violates not-null constraint[/var/www/localhost/htdocs/zabbix/include/db.inc.php:491]
    Error in query [INSERT INTO auditlog (auditid,userid,clock,action,resourcetype,details,ip) VALUES (18382,3,1292254801,1,2,'Working time [1-5,09:00-19:00;]','192.168.0.82')] [ERROR: null value in column "resourcename" violates not-null constraint]
    We've dropped those tables and recreated them, but still failing.

    Edit:
    Another one more detailed:
    Code:
    [update escalations set status=2,esc_step=0,nextcheck=0 where escalationid=2 and status=0]
     20699:20101213:170248.333 [Z3005] Query failed: [0] PGRES_FATAL_ERROR:ERROR:  null value in column "error" violates not-null constraint
     [insert into alerts (alertid,actionid,eventid,userid,clock,mediatypeid,sendto,subject,message,status,alerttype,esc_step) values (162,4,318311,3,1292256168,1,'[email protected]','[PROBLEM] Sshd is not running on machine: OK','Sshd is not running on dre021: OK',0,0,0)]
     20699:20101213:170248.333 [Z3005] Query failed: [0] PGRES_FATAL_ERROR:ERROR:  current transaction is aborted, commands ignored until end of transaction block
    Edit2: we ended up recreating all the schemas
    Last edited by acalvo; 14-12-2010, 19:01.
Working...