Re: SQL Error in ActiveSQL

Michael J Rubinsky <[email protected]>
Newsgroups gmane.comp.horde.sync
Message-ID <20130522094021.Horde.V1YHMsq3aITAFA7abrwyhw2@h4.theupstairsroom.com>
Quoting Torben Dannhauer <[email protected]>:

> Hi,
>
>
>
> Yesterday I had a configuration error and my server was filled with error
> messages up to the last bit of HDD space. Finally, the database crashed due
> to missing disk space.
>
> Now I get the SQL error below.
>
>
>
> How can I fix that without crashing ActiveSycnß

This can happen normally when the server sends changes to the device  
but for some reason the device doesn't receive/accept them. The device  
then repeats the last SYNC request, with the last synckey, which leads  
to the primary key violation. Under these conditions this is normal  
and the code *should* spit out a log entry in the synclog that it is  
has happened, will delete the existing entry and try again. If this is  
not happening, I'd need some backtrace to figure out why. Otherwise,  
you could just remove the state from Horde and/or recreate the account  
on the device.


> Thanks,
>
> Torben
>
>
>
> HORDE: [horde] SQL QUERY FAILED: SQLSTATE[23505]: Unique violation: 7
> FEHLER:  doppelter Schlüsselwert verletzt Unique-Constraint
> »horde_activesync_state_pkey«#012DETAIL:  Schlüssel
> »(sync_key)=({518ff75a-1e4c-48f3-9152-1dda4e2ee3d4}152)« existiert bereits.
> #012#011INSERT INTO horde_activesync_state (sync_key, sync_data,
> sync_devid,#012#011  sync_time, sync_folderid, sync_user, sync_pending)
> VALUES#012#011  ('{518ff75a-1e4c-48f3-9152-1dda4e2ee3d4}152',#012#011
> E'\\x433a32383a22486f7264655f41637469766553796e635f466f6c6465725f496d6#012#0
> 11
> 170223a313032313a7b613a353a7b733a313a2273223b613a333a7b733a373a2275696#012#0
> 11
> 46e657874223b733a353a223431303533223b733a31313a2275696476616c696469747#012#0
> 11
> 9223b733a31303a2231313239363531313331223b733a31333a22686967686573746d6#012#0
> 11
> f64736571223b693a303b7d733a313a226d223b613a31383a7b693a32393137353b613#012#0
> 11
> a323a7b733a343a2272656164223b693a313b733a373a22666c6167676564223b693a3#012#0
> 11
> 13b7d693a33313438353b613a323a7b733a343a2272656164223b693a313b733a373a2#012#0
> 11
> 2666c6167676564223b693a303b7d693a33353032383b613a323a7b733a343a2272656#012#0
> 11
> 164223b693a313b733a373a22666c6167676564223b693a303b7d693a33353433303b6#012#0
> 11
> 13a323a7b733a343a2272656164223b693a313b733a373a22666c6167676564223b693#012#0
> 11
> a303b7d693a33353433313b613a323a7b733a343a2272656164223b693a313b733a373#012#0
> 11
> a22666c6167676564223b693a303b7d693a33363137373b613a323a7b733a343a22726#012#0
> 11
> 56164223b693a313b733a373a22666c6167676564223b693a303b7d693a33363336313#012#0
> 11
> b613a323a7b733a343a2272656164223b693a313b733a373a22666c6167676564223b6#012#0
> 11
> 93a303b7d693a33393638323b613a323a7b733a343a2272656164223b693a313b733a3#012#0
> 11
> 73a22666c6167676564223b693a313b7d693a34303537333b613a323a7b733a343a227#012#0
> 11
> 2656164223b693a313b733a373a22666c6167676564223b693a303b7d693a343035373#012#0
> 11
> 53b613a323a7b733a343a2272656164223b693a313b733a373a22666c6167676564223#012#0
> 11
> b693a303b7d693a34303934373b613a323a7b733a343a2272656164223b693a313b733#012#0
> 11  a373a22666c6167676564223b693a303b7d
>
> --
> sync mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: [email protected]


-- 
mike

The Horde Project (www.horde.org)
[email protected]

-- 
sync mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
(unnamed) (application/pgp-keys, 2.1 KB) - not displayed
smime.p7s (application/pkcs7-signature, 5.9 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.