Anybody else having problems with on-line/offline database syncing under 3.7.2?

Since upgrading our office (8 seats) to Daylite 3.7.2 we have been experiencing incredibly long times to both access on-line databases and to sync off-line and on-line databases. We thought the problem might be related to change in the openbase database version (although the installer said no change was required), so we tried deleting the offline databases and then re-creating them. It took about an our and a half to replicate our main database to an offline version. Then, although I had made no changes to the offline version, as a test, I tried to sync the offline version to the online version. It is crawling through the sync process at the same pace as if it was replicating the database for the first time. I've been watching it grind away for over an hour already. Normally, this would take about 2 minutes. Even those in the office who do not have offline versions of the database are complaining about how slow Daylite has become to fully launch and connect with the online database.

Also, forgot to mention, that after installing 3.7.2, OpenBase Manager takes over half an hour to launch and display the resident offline databases now. The window comes up, but no databases are shown. I have stopped and then deleted all offline databases twice now thinking that they were somehow corrupted and that re-creating them would solve the problem.

I checked the OpenBase Manager log and it seems that the application is re-building every index in the database every time, each one taking a minute or more and there are a lot of them! :/

Go to System Preferences -> OpenBase and turn off "Automatic IP Address". Reboot and see if the that helps.

We've gotten 4 or 5 reports of this slow down on 10.5.2 and our current suspect is that switch.

Hi Eric,

In follow up to AJ's post, launch OpenBase Manager (found in Applications - OpenBase).

Now it may take a while to access OpenBase (spinning beach ball) whilst is scans for other OpenBase servers on the network. When access is granted, go to the menu bar and select OpenBaseManager -> Local Preferences -> Local Host Settings...
Ensure that the "Automatic IP Address" box is unchecked. If it isn't, uncheck it, close the window and save changes when prompted.

Automatic IP Address was not turned on and is, in fact, greyed out which normally indicates that the feature is not available.

"Start OpenBase Processes at Computer Sartup" was turned on.

"Enable Network Access" was not turned on.

Have confirmed this morning that launching Daylite and logging into the offline database takes pretty much the normal amount of time. Accessing the on-line database is the problem. Has been 15 minutes so far and the progress bar is about half way and looks like it is stalled, but in fact the program is slowly slogging its way through the sync process.

Not sure what "automatic IP Address" does, but seems to me that once an IP address is obtained, it would "stick" for the duration of the sync and should not inhibit communication between the client and the server?

OOPS! Mat, I did not read your posting carefully enough. The "Automatic IP Address" feature was greyed out in the OpenBase Preference pane of System Preferences. I was not referring to OpenBase Manager, which I had not launched. Good to know that the lengthy delay in launching openbase manager is normal, although it is taking a LOT longer than it used to take to bring up the local databases, which makes me think that it is being affected by the same issue that is causing Daylite to work so slowly.

I am waiting for Openbase Manager to complete its search for databases and will then see if "automatic IP address" is selected in the local preferences>local host settings.

OK. After waiting for about 20 minutes for Openbase manager to fully launch, I was able to select the "local preferences" menu item. Three minutes later, the local preferences pane came up.

Settings seem to be identical to those that I found in the Openbase preferences pane of System Preferences, which is not surprising I guess.

Network Access is not selected.
Automatic IP Address is greyed out.

Must be something else.

I am pleased to announce that I have just successfully shifted from my offline database to my online database after 2 hours and 30 minutes of syncing activity.

This morning, our systems administrator successfully defended her Master's thesis at the University of Ottawa and has now completed her Master's degree in System Science. I was going to acknowledge her achievement by telling her to take the rest of the day off. (Cake and champagne will be done on Monday when all our staff are in the office.) Instead, I think I need her to see if she can get our Daylite system functional again. She's having the same problem of endless waits for shifting back and forth from online to offline databases. No rest for the weary.

Hi Eric,

Can you please send us your Daylite log files to review. You can do this by selecting Help -> Email Log Files from the Daylite menu bar.
(in the email subject field, please add the following number mi_20080328131701

Could you also try disconnecting the computer from the internet (Ethernet and Airport if applicable).
When you have done this, please let us know if you notice any increased speed when accessing OpenBase Manager and accessing your database in Daylite.

I wonder if the following might be part of the problem. I checked on the database status using the Database Administration panel in Daylite Preferences. I wanted to verify that all our computers were using the same version of Openbase.

I noticed that Openbase saw my computer as having THREE IP addresses. I then checked to see if our other computers were showing multiple IP addresses and it appears that none of them are.

Checked the network settings in System Preferences and, sure enough, I have three IP addresses showing up: One for the Mac (IP number is consistent with our DHCP server range), one for Parallels NAT (number not within our DHCP server range), and one for Parallels Host-Guest (number not within DHCP server range).

Am not actually running Parallels Desktop application. Checked another Mac that IS actively running the application and it seems that Openbase shows only one IP address for it.

I wonder if Openbase/Daylite is getting confused because, after upgrading to 3.7.2, it is trying to work with three IP addresses instead of just one?

Mat: Will send Daylite log files, as requested, but thought that the multiple IP address info might be relevant and might not show up in the Daylite logs.

quote:

Checked the network settings in System Preferences and, sure enough, I have three IP addresses showing up: One for the Mac (IP number is consistent with our DHCP server range), one for Parallels NAT (number not within our DHCP server range), and one for Parallels Host-Guest (number not within DHCP server range).

I'm guessing this is on the database host, correct? Try to disable every other interface that is not being actively used on that system; this can be done in the Network pane in System Preferences, by selecting the interface from the list on the left, then clicking the gear icon at the bottom of the list and selecting 'Make Service Inactive'.

This should leave you with just the interface you're actually using, and hopefully speed things up (please let us know). You may need to reboot that machine first, but try without rebooting.

quote:

Am not actually running Parallels Desktop application. Checked another Mac that IS actively running the application and it seems that Openbase shows only one IP address for it.

That will depend on how Parallels is configured to share the networking on that computer.

quote:

Mat: Will send Daylite log files, as requested, but thought that the multiple IP address info might be relevant and might not show up in the Daylite logs.

Make sure you are sending it from the computer that is affected (in this case, the database host computer)

Making progress. Part of the problem at least is clearly linked to the multiple IP addresses. Both our systems administrator and I set up our copies of Parallels with independent IP addresses for the virtual machine. The person in our office who is actively running Parallels, but did not show multiple IP addresses apparently did not choose this setup option when he installed Parallels, which explains why Openbase manager sees only one IP address for his Mac.

I uninstalled Parallels completely, re-started, and that brought me back to only one IP address showing in both System Preferences and in the Daylite Database administration panel.

Then, launched Openbase Manager. It launched fully with local databases showing and accessible within 5 minutes. That's compared with over 30 minutes previously.

Then, launched Daylite and logged in directly to on-line database. Got full access in 4 minutes! Database is about 70+ megs.

Then tried to go to offline database. It got bogged down again half way through the progress bar, so I force quit the application. I have now deleted the local database and will see if re-creating it solves the problem.

This message has been edited. Last edited by: Eric Milligan,

Problem continues.

After having deleted the incompletely synced offline database this morning, I logged in to the online database, which came up within 4 minutes or so. Then, I went offline. Daylite said it had to create a new offline database, not having found an existing one. Replication of the database (96 megs approx) took about 4 hours.

I then quit Daylite, then re-started and logged in to the online database again. Then, went offline. This should have taken a couple of minutes, since there was no difference between the online database and the just-created offline database. It has been 2.5 hours and the syncing process is still ongoing. It seems to be no faster than it was before.

This might be an issue related to Leopard in which it takes about 30 seconds to resolve a host name, which can occur several times during a sync; I've checked the logs you sent in previously, and it appears that's the case.

Unfortunately since this is an Apple issue, there's not really much we can do from our end. There's a thread on Apple's forums that discusses this issue.

One possible solution can be found here.

We've been using Leopard since it first was released, and never had this problem before. It started right after upgrading to 3.7.2. Have passed your post on to our systems administrator in any case. We are now pursuing with Marketcircle tech support, so I think I'll not post further here until we find the cause and can report on it to the forum.