Thanks Dave, Ben, We don't intend to continue with remoteformentry in any clinic, Jeremy had given a
suggestion that we test that too. The problem was that somebody had removed sync from the interface hence resulting to the error I attached. We intend to convert three of the servers running on windows by next week one the we get drives that we can use to swap with those of remote sites. Dave, we don't have a cell phone service currently at our remote sites. Thanks. Miencha Agustine Informatics Ampath ________________________________ From: Ben Wolfe <[email protected]> To: [email protected] Sent: Friday, August 12, 2011 2:10 PM Subject: Re: [OPENMRS-DEV] Sync Sprint? Sync should replace entirely the need for remoteformentry. Or are you going to continue a few remote clinics without full sync machines for a while? Sync is a mandatory module because if sync is not running when even 1 commit happens to the database then all other servers and sync'ing could fail. I'm not sure why sync is able to start from that error message. You need to look into the tomcat log file for the true error. It should be the first error printed after starting up. You should use this opportunity to convert all the servers to linux! :-) Copying the tables by filesystem should work within the same OS. So you could do a db dump from the linux central server and run it on just one of the remote window servers. You could then do a filesystem copy from that one server to the other windows servers. FYI: 280MB db is not very big. Did you mean 280 GB? Or 2800 MB ? Ben On Fri, Aug 12, 2011 at 10:24 AM, Dave Thomas <[email protected]> wrote: Hi. To answer your questions: > >1) we're on the latest sync build from svn. there has been a lot of activity >recently on fixing small bugs. > >2) i just do a mysqldump, which doesn't take too long to dump, although the >import takes a large number of hours. Here's the syntax that i use: > >mysqldump --host="localhost" --port="3306" --user="XXX" --password="XXX" >openmrs --add_drop_table -q -e --single-transaction --result "openmrs.sql" > >when you import this, you have to set your max_packet_size to something big in >my.ini -- just google this. > >3) we don't use remoteformentry, so i don't know... it strikes me that this >should be compatible though. It strikes me as wrong that sync should be >marked as a 'mandatory' module, and that you have to overwrite this global >property manually at startup everytime -- you can file a ticket about this. > >Also, at the sites where you use remote form entry, is there cell phone >service? We were recently able to expand our number of servers by setting up >an APN within the MTN network in Rwanda. > >4) And, the version of formentry that you should use is the one that's best >for whatever version of openmrs you're on. there are no specific >compatibility issues that i know of between formentry and sync. We had >terrible problems, however, with Form objects propagating to other servers >that were still mapped to the original server so there were instances when we >found that infopath form submissions were going to the parent server instead >of the local server. You should test this, and potentially block >org.openmrs.Form form syncing. > >d > > > >On Fri, Aug 12, 2011 at 9:01 AM, augustine12th thomas ><[email protected]> wrote: > > >>________________________________ >> >>That is great Dave. Now I need a few clarifications from you please on a few >>issues below: >> >> * Which version of sync a you using? >> * If you implement sync in windows, how best do you dump data from the >> parent to the child, faster enough to reduce downtimes? Given that the >> databases of parent and child have to be the same initially? When I tried to >> dump data to a windows machine, it took four days to finish. Our database is >> big, it is over 280Mb >> >> * A you able to use both remoteformentry and sync together? I have >> tried this, but whenever I restart the server, an error I have attached >> above appears and I'm forced to make sync.mandatory false in the database >> for amrs to start. This problem will be difficult to handle by data >> assistants we use in the remote sides, given that servers will always go >> down. >> >> * Which version of form entry is compatible with sync 0.972?Thanks. >> >>Miencha Agustine >>Informatics >>Ampath. >> >> >> >> >>: Dave Thomas <[email protected]> >>To: [email protected] >>Sent: Friday, August 12, 2011 9:10 AM >> >>Subject: Re: [OPENMRS-DEV] Sync Sprint? >> >> >> >>Hi. I'm the one you need to talk to.... I administer 25 synced servers. >>On Aug 12, 2011 7:57 AM, "augustine12th thomas" <[email protected]> >>wrote: >>> Hi Dave, >>> >>> We're upgrading our remote sites beginning this weekend using sync module. >>> We have decided to use sync v. 0.972 I will be testing this module >>> >>> this afternoon. Please could you link me to somebody in Rwanda. I was told >>> they use sync module. >>> >>> Thanks. >>> >>> Miencha Agustine >>> >>> Informatics >>> ampath. >>> >>> >>> >>> >>> >>> >>> ________________________________ >>> From: Dave Thomas <[email protected]> >>> To: [email protected] >>> Sent: Thursday, August 11, 2011 7:06 PM >>> Subject: Re: [OPENMRS-DEV] Sync Sprint? >>> >>> Yes, still in Rwanda. Count me in at about 95%. >>> >>> d >>> >>> On 8/11/11, Ben Wolfe <[email protected]> wrote: >>>> We've scheduled the Sync Sprint to start Sept 5th to maximize available >>>> developers. >>>> >>>> https://wiki.openmrs.org/display/RES/Sprint+Schedule >>>> >>>> Dave, are you still in Rwanda? If so, you'll be on the same timezone as >>>> half of the openmrs devs: Me in Kenya, Daniel in Uganda, and Rafal in >>>> Poland. Its that Darius character in Seattle that has to worry about >>>> matching up times with. :-) >>>> >>>> Ben >>>> >>>> On Fri, Aug 5, 2011 at 3:16 PM, Dave Thomas <[email protected]> wrote: >>>> >>>>> I'm tenatively in, whenever it happens, although the time difference isn't >>>>> great for real-time collaboration for me. >>>>> >>>>> d >>>>> >>>>> >>>>> On Fri, Aug 5, 2011 at 9:19 AM, Ben Wolfe <[email protected]> wrote: >>>>> >>>>>> The first we could schedule it is Aug 29th. Would there be anything >>>>>> at that time to preclude any pih or ampath devs from contributing? >>>>>> Its always nice to have as many hands on deck as possible during a >>>>>> sprint...and providing coding time a great way for implementations to >>>>>> "give back" to openmrs. ;-) >>>>>> >>>>>> The other option is to have a "catch-up" week the 29th->9th and then >>>>>> do sync starting Sept 5th. >>>>>> >>>>>> Ben >>>>>> >>>>>> On Fri, Aug 5, 2011 at 8:50 AM, Jonah S. Mwogi <[email protected]> >>>>>> wrote: >>>>>> > Darius, >>>>>> > >>>>>> > It think it would be good to have it towards end of August as Ampath >>>>>> intends >>>>>> > to take up Sync in its remote sites immediately. >>>>>> > >>>>>> > Thanks >>>>>> > >>>>>> > On Fri, Aug 5, 2011 at 2:33 AM, Michael Seaton <[email protected]> wrote: >>>>>> >> >>>>>> >> For PIH, the best time for us to contribute would be in early to mid >>>>>> >> September. Maybe the middle 2 weeks, aiming to release a 1.0 prior to >>>>>> the >>>>>> >> October meetings... >>>>>> >> >>>>>> >> On Aug 4, 2011, at 6:40 PM, "Darius Jazayeri" <[email protected] >>>>>> > >>>>>> >> wrote: >>>>>> >> >>>>>> >> Generally speaking, we would like to have the Sync sprint around the >>>>>> time >>>>>> >> that AMPATH is installing the sync module, and before PIH-Rwanda does >>>>>> its >>>>>> >> 1.8 upgrade (in the presence of Sync). >>>>>> >> Are there any particular time we could schedule the sprint when AMPATH >>>>>> or >>>>>> >> PIH devs would be able to contribute? >>>>>> >> >>>>>> >> -Darius >>>>>> >> >>>>>> >> On Thu, Aug 4, 2011 at 4:36 AM, Ben Wolfe <[email protected]> wrote: >>>>>> >>> >>>>>> >>> We're currently behind on the scheduling of sprints, so I can't say >>>>>> >>> right now when this will be. >>>>>> >>> >>>>>> >>> Watch https://wiki.openmrs.org/display/RES/Sprint+Schedule for >>>>>> updates. >>>>>> >>> >>>>>> >>> Ben >>>>>> >>> >>>>>> >>> On Wed, Aug 3, 2011 at 4:25 PM, Jeremy Keiper <[email protected]> >>>>>> wrote: >>>>>> >>> > Hopefully soon ... we >>>>>> >>> > need https://tickets.openmrs.org/browse/SYNC-179 resolved >>>>>> immediately >>>>>> >>> > to >>>>>> >>> > continue testing with 1.8.2. >>>>>> >>> > >>>>>> >>> > Jeremy Keiper >>>>>> >>> > OpenMRS Core Developer >>>>>> >>> > AMPATH / IU-Kenya Support >>>>>> >>> > >>>>>> >>> > >>>>>> >>> > On Tue, Aug 2, 2011 at 5:39 PM, Mark Goodrich <[email protected]> >>>>>> >>> > wrote: >>>>>> >>> >> >>>>>> >>> >> Hey Ben-- >>>>>> >>> >> >>>>>> >>> >> Any update on when the sync sprint might happen? >>>>>> >>> >> >>>>>> >>> >> Mark >>>>>> >>> >> >>>>>> >>> >> _________________________________________ >>>>>> >>> >> >>>>>> >>> >> To unsubscribe from OpenMRS Developers' mailing list, send an >>>>>> e-mail >>>>>> >>> >> to >>>>>> >>> >> [email protected] with "SIGNOFF openmrs-devel-l" in the >>>>>> >>> >> body (not >>>>>> >>> >> the subject) of your e-mail. >>>>>> >>> >> >>>>>> >>> >> [mailto:[email protected] >>>>>> ?body=SIGNOFF%20openmrs-devel-l] >>>>>> >>> > >>>>>> >>> > ________________________________ >>>>>> >>> > Click here to unsubscribe from OpenMRS Developers' mailing list >>>>>> >>> >>>>>> >>> _________________________________________ >>>>>> >>> >>>>>> >>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail >>>>>> to >>>>>> >>> [email protected] with "SIGNOFF openmrs-devel-l" in the >>>>>> body (not >>>>>> >>> the subject) of your e-mail. >>>>>> >>> >>>>>> >>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >>>>>> >> >>>>>> >> ________________________________ >>>>>> >> Click here to unsubscribe from OpenMRS Developers' mailing list >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Jonah S. Mwogi >>>>>> > System Engineer >>>>>> > Ampath Centre - Eldoret Kenya >>>>>> > >>>>>> > ________________________________ >>>>>> > Click here to unsubscribe from OpenMRS Developers' mailing list >>>>>> >>>>>> _________________________________________ >>>>>> >>>>>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to >>>>>> [email protected] with "SIGNOFF openmrs-devel-l" in the body >>>>>> (not the subject) of your e-mail. >>>>>> >>>>>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >>>>>> >>>>> >>>>> ------------------------------ >>>>> Click here to >>>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>>>> OpenMRS Developers' mailing list >>>>> >>>> >>>> _________________________________________ >>>> >>>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to >>>> [email protected] with "SIGNOFF openmrs-devel-l" in the body >>>> (not >>>> the subject) of your e-mail. >>>> >>>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >>>> >>> >>> _________________________________________ >>> >>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to >>> [email protected] with "SIGNOFF openmrs-devel-l" in the body >>> (not the subject) of your e-mail. >>> >>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >>> >>> _________________________________________ >>> >>> To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to >>> [email protected] with "SIGNOFF openmrs-devel-l" in the body >>> (not the subject) of your e-mail. >>> >>> [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l] >> >>________________________________ >> Click here to unsubscribe from OpenMRS Developers' mailing list >> >> >> >>________________________________ >> Click here to unsubscribe from OpenMRS Developers' mailing list >>________________________________ > Click here to unsubscribe from OpenMRS Developers' mailing list ________________________________ Click here to unsubscribe from OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
