search

cptcornflakes / smartcoin

Automatically exported from code.google.com/p/smartcoin
0 stars 0 forks source link

Error: no such column: failover_order #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
HERE CAUSE the Bitcoin Forum seems to be down!

Hi,

i updated from 345 and get following error:

----

Your current version is r345.
Are you sure that you wish to perform an update?
y
Bring update script up to current...
U    /home/mono/smartcoin/smartcoin_update.sh
Aktualisiert zu Revision 349.

Preparing to do an Update...
Preparing safe update from r345 to r349
Konflikt in »/home/mono/smartcoin/smartcoin.db« entdeckt.
Auswahl: (p) zurückstellen,
         (mf) volle eigene Datei, (tf) volle fremde Datei,
        (s) alle Optionen anzeigen: tf
G    /home/mono/smartcoin/smartcoin.db
U    /home/mono/smartcoin/smartcoin_control.sh
U    /home/mono/smartcoin/smartcoin_ops.sh
U    /home/mono/smartcoin/smartcoin_status.sh
U    /home/mono/smartcoin/smartcoin_install.sh
 U   /home/mono/smartcoin
Aktualisiert zu Revision 349.

Applying post update patches...
Applying r346 patch...
Error: near "Q": syntax error
Error: near "Q": syntax error
Error: near "Q": syntax error
Update task complete.

Update is now complete!  You should now restart smartcoin. Please hit any key 
to continue.

--

After restart SmartCoin and configure the profile, i get following error when i 
got to (12) Set Failover Order:

--
1) localhostPlease select the machine from the list above that you wish to edit 
Failover order on
1
Error: no such column: failover_order

The current profile failover order is listed above.
Do you want to change the failover order, (y)es or (n)o?
--

Seems the database was not updated.

Update to r350: Same error in (12) Set Failover Order

Original issue reported on code.google.com by mark.bre...@gmail.com on 7 Jul 2011 at 3:40

GoogleCodeExporter commented 9 years ago 
This is now fixed.  The first problem was missing a '$' character in the query 
variables. The other problem was with sqlite3 not playing well with multiple 
scripts accessing it.  It has also been fixed recently with locking 
restrictions.

Original comment by jondecke...@gmail.com on 8 Jul 2011 at 8:50