Hi Damian,
I just updated to 3.11.8-014067. I initially ran your update query:
psql -d SIPXCONFIG -U postgres -c "update backup_plan SET backup_type = 'L'
where backup_type = ''"
but this did not solve the issue in my case. I made sipxconfig work
again running:
update backup_plan SET backup_type = 'L' where backup_type IS NULL
Thanks again
Alberto
Damian Krzeminski ha scritto:
Damian Krzeminski wrote:
Alberto wrote:
Details below:
[...]
Mmh not sure. First I had this issue when I upgraded 2 days ago. And
thought it was caused by some work in progress. Today I updated again,
and the problem persisted. I tried to figure out what svn version it was
but unfortunately the build page is limited in time. My last working
build it is one that succeeded in the build system around 4-5 days ago.
Any chance you had a backup of you DB before this upgrade?
Unfortunately no.
I'll look at the code. I am pretty sure that setting the backup type is not
recent patch, but there might be an issue somewhere.
If anybody else see something like that please let me know.
D.
OK people - the bad new it's not just Alberto - it can happen to anyone.
The good news is that Kevin and Kathy helped me to figure out what's wrong.
If your sipXconfig does not start and you see (in sipxconfig.log):
org.hibernate.WrongClassException: Object with id: 1 was not of the
specified subclass: org.sipfoundry.sipxconfig.admin.BackupPlan
(Discriminator: null)
You need to execute the following:
psql -d SIPXCONFIG -U postgres -c "update backup_plan SET backup_type = 'L'
where backup_type = ''"
That should get you up and running again.
Now explanation (mostly for sipXconfig contributors' benefit):
Back when we initially added FTP Backup support to sipXconfig, database
patch added a new column but did not set the value for a newly added
column. sipXconfig code had careful workarounds for the missing value (such
as using HSQL queries to retrieve specific objects instead of loadAll
method). I managed to successfully remove this workarounds yesterday, which
exposed the issue.
I'll opened a new issue:
http://track.sipfoundry.org/browse/XCF-3073
Will have a fix soon.
D.
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
