Final update:
Okay - I think I fixed everything. It appears that the zmupdate script was not adding a row into the Config table; specifically - this row:
Code: Select all
insert into Config set Id = 42, Name = 'ZM_FFMPEG_OPEN_TIMEOUT', Value = '10', Type = 'integer', DefaultValue = '10', Hint = 'integer', Pattern = '(?^:^(\d+)$)', Format = ' $1 ', Prompt = 'Timeout in seconds when opening a stream.', Help = 'When Ffmpeg is opening a stream, it can take a long time before failing; certain circumstances even seem to be able to lock indefinitely. This option allows you to set a maximum time in seconds to pass before closing the stream and trying to reopen it again.', Category = 'images', Readonly = '0', Requires = 'ZM_OPT_FFMPEG=1'
I fixed it by moving everything starting with id 42 down by one:
Code: Select all
update Config set id = id+1 where id > 41 order by id asc;
And then inserting the missing row:
Code: Select all
insert into Config set Id = 42, Name = 'ZM_FFMPEG_OPEN_TIMEOUT', Value = '10', Type = 'integer', DefaultValue = '10', Hint = 'integer', Pattern = '(?^:^(\d+)$)', Format = ' $1 ', Prompt = 'Timeout in seconds when opening a stream.', Help = 'When Ffmpeg is opening a stream, it can take a long time before failing; certain circumstances even seem to be able to lock indefinitely. This option allows you to set a maximum time in seconds to pass before closing the stream and trying to reopen it again.', Category = 'images', Readonly = '0', Requires = 'ZM_OPT_FFMPEG=1';
After that, I started the ZM process and things seems to be chugging along smoothly. If you have experienced similar problems, you can try the above approach but
BE AWARE THAT THIS IS RISKY AND CAN HOSE YOUR DATABASE!. If you, like me, are running ZoneMinder on a VM, take a snapshot!
So now the question is - why did it not update my DB and why didnt the refresh config command work?