Can't run query: Unknown column 'MinPixelThreshold' in 'fiel

Support and queries relating to all previous versions of ZoneMinder
Locked
gessel
Posts: 26
Joined: Sat Jan 24, 2004 12:24 am

Can't run query: Unknown column 'MinPixelThreshold' in 'fiel

Post by gessel »

I recently upgraded to 1.17.2 and started getting this error. The entries in the system log are:
Feb 9 23:09:30 merritt zmc-d0[2312]: INF [Monitor main IBC = 20, WUC = 10, pEC = 10, PEC = 10, FRI = 1000, RBP = 10]
Feb 9 23:09:30 merritt zmc-d0[2312]: ERR [Can't run query: Unknown column 'MinPixelThreshold' in 'field list']

I'm also getting these crashes:
Server starting at 04/02/09 23:09:26
'zmc -d 0' started at 04/02/09 23:09:29
'zmc -d 0' starting at 04/02/09 23:09:29, pid = 2309
'zmc -d 0' crashed at 04/02/09 23:09:30, exit status 30
'zmc -d 0' starting at 04/02/09 23:09:30, pid = 2312
'zmc -d 0' started at 04/02/09 23:09:30
'zmc -d 0' crashed at 04/02/09 23:09:30, exit status 30

But I'm afraid it has something to do with having two ImpactVCB cards in the box. With MoTV I can read /dev/video0 just fine, but running motv --device /dev/video1 creates some odd glitches and then crashes x-windows hard... so there's something else going on, but not surprisingly there's no video capture happinging. Oddly - I'm only looking for /dev/video0, which works in MoTV just fine, but nothing in zm.

I'm running bttv 0.9.12 and 2.4.24 on RH9. I'm posting to the v4l forum on the MoTV crash, but if anyone has some hints, here's the startup log for bttv:

Feb 9 22:47:06 merritt kernel: Linux video capture interface: v1.00
Feb 9 22:47:21 merritt kernel: bttv: driver version 0.9.12 loaded
Feb 9 22:47:21 merritt kernel: bttv: using 8 buffers with 2080k (520 pages) each for capture
Feb 9 22:47:21 merritt kernel: bttv: Host bridge needs ETBF enabled.
Feb 9 22:47:21 merritt kernel: bttv: Bt8xx card found (0).
Feb 9 22:47:21 merritt kernel: PCI: Found IRQ 11 for device 00:0d.0
Feb 9 22:47:21 merritt kernel: PCI: Sharing IRQ 11 with 00:0d.1
Feb 9 22:47:21 merritt kernel: bttv0: Bt878 (rev 2) at 00:0d.0, irq: 11, latency: 66, mmio: 0x42100000
Feb 9 22:47:21 merritt kernel: bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
Feb 9 22:47:21 merritt kernel: bttv0: using: Hauppauge (bt878) [card=10,autodetected]
Feb 9 22:47:21 merritt kernel: bttv0: enabling ETBF (430FX/VP3 compatibilty)
Feb 9 22:47:21 merritt kernel: bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
Feb 9 22:47:21 merritt kernel: i2c-dev.o: Registered 'bt878 #0 [sw]' as minor 0
Feb 9 22:47:21 merritt kernel: i2c-core.o: adapter bt878 #0 [sw] registered as adapter 0.
Feb 9 22:47:21 merritt kernel: bttv0: Hauppauge eeprom: model=64405, tuner=Unspecified (4), radio=no
Feb 9 22:47:21 merritt kernel: bttv0: using tuner=4
Feb 9 22:47:21 merritt kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not found
Feb 9 22:47:21 merritt kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
Feb 9 22:47:21 merritt kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found
Feb 9 22:47:21 merritt kernel: tvaudio: TV audio decoder + audio/video mux driver
Feb 9 22:47:21 merritt kernel: tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951),ta8874z
Feb 9 22:47:21 merritt kernel: i2c-core.o: driver generic i2c audio driver registered.
Feb 9 22:47:21 merritt kernel: i2c-core.o: driver i2c TV tuner driver registered.
Feb 9 22:47:21 merritt kernel: bttv0: registered device video0
Feb 9 22:47:21 merritt kernel: bttv0: registered device vbi0
Feb 9 22:47:21 merritt kernel: bttv0: PLL: 28636363 => 35468950 .. ok
Feb 9 22:47:21 merritt kernel: bttv: Bt8xx card found (1).
Feb 9 22:47:21 merritt kernel: PCI: Found IRQ 11 for device 00:0e.0
Feb 9 22:47:21 merritt kernel: PCI: Sharing IRQ 11 with 00:0e.1
Feb 9 22:47:21 merritt kernel: bttv1: Bt878 (rev 2) at 00:0e.0, irq: 11, latency: 66, mmio: 0x42300000
Feb 9 22:47:21 merritt kernel: bttv1: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
Feb 9 22:47:21 merritt kernel: bttv1: using: Hauppauge (bt878) [card=10,autodetected]
Feb 9 22:47:21 merritt kernel: bttv1: enabling ETBF (430FX/VP3 compatibilty)
Feb 9 22:47:21 merritt kernel: bttv1: Hauppauge/Voodoo msp34xx: reset line init [5]
Feb 9 22:47:21 merritt kernel: i2c-dev.o: Registered 'bt878 #1 [sw]' as minor 1
Feb 9 22:47:21 merritt kernel: i2c-core.o: adapter bt878 #1 [sw] registered as adapter 1.
Feb 9 22:47:21 merritt kernel: bttv1: Hauppauge eeprom: model=64405, tuner=Unspecified (4), radio=no
Feb 9 22:47:21 merritt kernel: bttv1: using tuner=4
Feb 9 22:47:21 merritt kernel: bttv1: i2c: checking for MSP34xx @ 0x80... not found
Feb 9 22:47:21 merritt kernel: bttv1: i2c: checking for TDA9875 @ 0xb0... not found
Feb 9 22:47:21 merritt kernel: bttv1: i2c: checking for TDA7432 @ 0x8a... not found
Feb 9 22:47:21 merritt kernel: bttv1: registered device video1
Feb 9 22:47:21 merritt kernel: bttv1: registered device vbi1
Feb 9 22:47:21 merritt kernel: bttv1: PLL: 28636363 => 35468950 .. ok
User avatar
zoneminder
Site Admin
Posts: 5215
Joined: Wed Jul 09, 2003 2:07 pm
Location: Bristol, UK
Contact:

Re: Can't run query: Unknown column 'MinPixelThreshold' in '

Post by zoneminder »

Hi David,

Did you remember to run zmalter-1.17.1.sql into your DB to update it for 1.17.2? That seems to be your main problem. Once you've done that, if you still have problems, then have a look in /var/log/messages and see if there's anything suspicious in there.

Cheers,

Phil,
gessel
Posts: 26
Joined: Sat Jan 24, 2004 12:24 am

Re: Can't run query: Unknown column 'MinPixelThreshold' in '

Post by gessel »

Phil,

Thanks for your prompt and successful help.

I had to run

#mysql
mysql> \u zm
mysql> \. zmalter-1.17.1.sql

Which worked find to upgrade to the new version. From the install instructions I thought that mysql mysql < zmalter-1.17.1.sql
would work, but it didn't, probably for all the right reasons.

No I get a kernel reboot when I look at /dev/video1 but that's not an installation problem (nor a ZM problem). I'll post some log details in general - there may be a way to trap the errors and shut down the process before it causes a hard crash.

Cheers,

David
Locked