Ad Widget

Collapse

1.0 - 1.1.4 Upgrade Trouble.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • smallclanger
    Junior Member
    • Dec 2006
    • 13

    #1

    1.0 - 1.1.4 Upgrade Trouble.

    HI all,

    I've just finished attempting to upgrade a long-running 1.0 server to 1.1.4. The frontend is in place, all of the patches have been applied in sequence (The last being 1.1beta12_to_1.1) and the server/agents have been compiled and installed. I've created a server config and when I attempt to start the server, I get the following in the logs:
    Code:
    031142:20061206:110718 server #9 started [Poller. SNMP:OFF]
    031134:20061206:110718 Query::select i.itemid,i.key_,h.host,h.port,i.delay,i.description,i.nextcheck,i.type,i.snmp_community,i.snmp_oid,h.useip,h.ip,i.history,i.lastvalue,i.prevvalue,i.hostid,h.status,i.value_type,h.network_errors,i.snmp_port,i.delta,i.prevorgvalue,i.lastclock,i.units,i.multiplier,i.snmpv3_securityname,i.snmpv3_securitylevel,i.snmpv3_authpassphrase,i.snmpv3_privpassphrase,i.formula,h.available from items i,hosts h where i.nextcheck<=1165403238 and i.status=0 and i.type not in (2,7) and ((h.status=0 and h.available!=2) or (h.status=0 and h.available=2 and h.disable_until<=1165403238)) and h.hostid=i.hostid and i.itemid%6=0 and i.key_ not in ('status','icmpping','icmppingsec','zabbix[log]') order by i.nextcheck
    031134:20061206:110718 Query failed:Unknown column 'h.network_errors' in 'field list' [1054]
    There's a few of those, then:
    Code:
    031140:20061206:110718 Query failed:Unknown column 'h.network_errors' in 'field list' [1054]
    031124:20061206:110718 One child process died. Exiting ...
    031124:20061206:110718 Got QUIT or INT or TERM or PIPE signal. Exiting...
    ...until it quits.

    As far as I can make out, the 1.1beta5_to_1.1beta6 mysql patch dropped network_errors from the table and nothing since has reinstated it.

    The zabbix_server binary version, however, is reporting as 1.1beta2. Is this normal? I've compiled it from a fresh download of the 1.1.4 source, but perhaps the server binary hasn't changed since beta2?

    After patching, the hosts table structure is as follows:
    Code:
    mysql> show columns from hosts;
    +---------------+--------------+------+-----+-----------+----------------+
    | Field         | Type         | Null | Key | Default   | Extra          |
    +---------------+--------------+------+-----+-----------+----------------+
    | hostid        | int(4)       |      | PRI | NULL      | auto_increment |
    | host          | varchar(64)  |      | UNI |           |                |
    | useip         | int(1)       |      |     | 1         |                |
    | ip            | varchar(15)  |      |     | 127.0.0.1 |                |
    | port          | int(4)       |      |     | 0         |                |
    | status        | int(4)       |      | MUL | 0         |                |
    | disable_until | int(4)       |      |     | 0         |                |
    | error         | varchar(128) |      |     |           |                |
    | available     | int(4)       |      |     | 0         |                |
    | errors_from   | int(4)       |      |     | 0         |                |
    | templateid    | int(4)       |      |     | 0         |                |
    +---------------+--------------+------+-----+-----------+----------------+
    Versions:
    Code:
    Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.2.3 mod_python/3.1.3 Python/2.3.5 PHP/4.4.0-4
    mysql  Ver 14.7 Distrib 4.1.14, for pc-linux-gnu (i486) using readline 5.0
    Config:
    Code:
    Server=1
    StartPollers=5
    StartTrappers=2
    ListenIP=127.0.0.1
    ListenPort=10051
    HousekeepingFrequency=1
    SenderFrequency=30
    DebugLevel=3
    Timeout=5
    UnreachablePeriod=300
    UnavailableDelay=15
    UnavailableDelay=120
    PidFile=/var/run/zabbix/zabbix_server.pid
    LogFile=/var/log/zabbix/zabbix_server.log
    AlertScriptsPath=/home/zabbix/bin/
    DBHost=localhost
    DBName=zabbix
    DBUser=zabbix
    DBPassword=xxxxxx
    Last edited by smallclanger; 06-12-2006, 14:07.
  • smallclanger
    Junior Member
    • Dec 2006
    • 13

    #2
    Funny how one small coincidence can have you barking up the wrong tree for hours...

    There was a typo in my initial ./configure invocation that meant the server wasn't built at all. The binary that was in /usr/local/bin turned out to be one that had been built by someone else in an earlier abortive attempt at an upgrade and left behind after the clean-up.

    Server is up and running now.

    Comment

    • Calimero
      Senior Member
      • Nov 2006
      • 481

      #3
      That's just 50 minutes of barking which is - I guess - acceptable.

      Comment

      Working...