Reboot empeg before sync

Posted by: pache

Reboot empeg before sync - 13/08/2002 14:50

I reboot my empeg before i start synchronizing. Now emplode can't connect to the player (Could not connect socket error).
The point is i don't want to restart emplode (it's still open on my PC) , since i maid a lot of change in the playlists. Is it possible to resolve that easily (if it's to difficult i just restart emplode) that will save me a lot of time.
Posted by: tfabris

Re: Reboot empeg before sync - 13/08/2002 14:58

No. If you rebooted the player after Emplode grabbed its databse, you cannot synch without exiting emplode and losing your changes.

Don't do that.
Posted by: wfaulk

Re: Reboot empeg before sync - 13/08/2002 15:01

Since the entirety of the state information is held in emplode until the sync occurs, I can't conceive of a reason that there couldn't be a reconnect option added to emplode. It might want to check to make sure that it's the same empeg, or warn the use that reconnecting to a different empeg might cause data loss, but there shouldn't be any reason that it's undoable.
Posted by: tfabris

Re: Reboot empeg before sync - 13/08/2002 15:04

I think you could seriously damage the database if certain things happened in the wrong order. Early on, before they added the failsafe into the software to prevent this problem, I seriously hosed my database once doing something like this.
Posted by: pache

Re: Reboot empeg before sync - 14/08/2002 04:55

Well, thank you any way.

I'll sort it over again.
Posted by: tms13

Re: Reboot empeg before sync - 14/08/2002 08:24

JEmplode manages reconnection no problem. I often synchronise my changes a day later, having gone home and back (and used the player there as well as in the car both ways) in between.
Posted by: Roger

Re: Reboot empeg before sync - 14/08/2002 08:53

Why not? Did I break something? The only reason that I can think of that would break it is if the DHCP server gave you the wrong IP address, or the USB path changed, or whatever.

We protect against database corruption by keeping a generation id (sequence_id) so that we can tell if you changed the database on another PC.