jpilot@lists.jpilot.org

General support, questions, patches for J-Pilot.

View all threads

slow_sync_application: Unable to open file: DatebookDB

PA
Philippe Auphelle
Tue, Jun 9, 2020 2:47 PM

Hi,

I have recently noticed that jpilot sync is not able to access my
DatebookDB file:
slow_sync_application: Unable to open file: DatebookDB

If I use sync with backup, I get the similar:
fast_sync_application: Unable to open file: DatebookDB

How can I fix that?

Thanks in advance!

PhA

Hi, I have recently noticed that jpilot sync is not able to access my DatebookDB file: slow_sync_application: Unable to open file: DatebookDB If I use sync with backup, I get the similar: fast_sync_application: Unable to open file: DatebookDB How can I fix that? Thanks in advance! PhA
RS
Rich Shepard
Tue, Jun 9, 2020 3:00 PM

On Tue, 9 Jun 2020, Philippe Auphelle wrote:

I have recently noticed that jpilot sync is not able to access my
DatebookDB file: slow_sync_application: Unable to open file: DatebookDB

If I use sync with backup, I get the similar: fast_sync_application:
Unable to open file: DatebookDB

How can I fix that?

PhA,

As Bob Dole responded when asked by a reporter whether he wore briefs or
boxers, "depends."

What's your OS? What's your handheld? What connection channel are you using?
Did it work before? Have you tried pilot-link?

Rich

On Tue, 9 Jun 2020, Philippe Auphelle wrote: > I have recently noticed that jpilot sync is not able to access my > DatebookDB file: slow_sync_application: Unable to open file: DatebookDB > If I use sync with backup, I get the similar: fast_sync_application: > Unable to open file: DatebookDB > How can I fix that? PhA, As Bob Dole responded when asked by a reporter whether he wore briefs or boxers, "depends." What's your OS? What's your handheld? What connection channel are you using? Did it work before? Have you tried pilot-link? Rich
PA
Philippe Auphelle
Tue, Jun 9, 2020 3:29 PM

Hi Rich,

Thanks for your superfast reply.

As Bob Dole responded when asked...

:-)

  • It worked before (for many years, actually). I figured out the problem
    today because an appointment I just made (in the Palm) didn't show up in
    j-pilot after the sync, but it could have started a few days ago without my
    noticing.
  • All others databases do sync properly, it's just Datebook that seems
    to be messed up somehow.
  • Currently running Ubuntu 18.4.4 x64, jpilot 1.8.2 (latest Ubuntu
    installed / updated)
  • Palm Tx, PalmOS 5.49028
  • In j-Pilot Prefs, all Palm files are config'd for "Palm OS < 5.2.1",
    though. I don't think I ever changed those since I installed 18.4 LTS (and
    it worked before).
  • Never used pilot-link directly (and just skimming thru the man pages
    kinda scares me right now!)
  • Connected through an USB port.
  • In case this matters, I have FileZ installed on the Palm. It shows no
    file attrs checked on DatebookDB details, but I have no idea whether this
    is significant as I never checked it up for this file before.
  • Finally, I have had a few Ubuntu crashes lately - not j-pilot related
    in any way, but j-pilot was up when they happened, it always is, config'd
    to autostart at startup time.

Thanks for your help and time!    /PhA.

On Tue, 9 Jun 2020 at 17:01, Rich Shepard rshepard@appl-ecosys.com wrote:

On Tue, 9 Jun 2020, Philippe Auphelle wrote:

I have recently noticed that jpilot sync is not able to access my
DatebookDB file: slow_sync_application: Unable to open file: DatebookDB

If I use sync with backup, I get the similar: fast_sync_application:
Unable to open file: DatebookDB

How can I fix that?

PhA,

As Bob Dole responded when asked by a reporter whether he wore briefs or
boxers, "depends."

What's your OS? What's your handheld? What connection channel are you
using?
Did it work before? Have you tried pilot-link?

Rich


Jpilot mailing list
Jpilot@lists.jpilot.org
http://lists.jpilot.org/mailman/listinfo/jpilot_lists.jpilot.org

Hi Rich, Thanks for your superfast reply. > As Bob Dole responded when asked... :-) - It worked before (for many years, actually). I figured out the problem today because an appointment I just made (in the Palm) didn't show up in j-pilot after the sync, but it could have started a few days ago without my noticing. - All others databases do sync properly, it's just Datebook that seems to be messed up somehow. - Currently running Ubuntu 18.4.4 x64, jpilot 1.8.2 (latest Ubuntu installed / updated) - Palm Tx, PalmOS 5.49028 - In j-Pilot Prefs, all Palm files are config'd for "Palm OS < 5.2.1", though. I don't think I ever changed those since I installed 18.4 LTS (and it worked before). - Never used pilot-link directly (and just skimming thru the man pages kinda scares me right now!) - Connected through an USB port. - In case this matters, I have FileZ installed on the Palm. It shows no file attrs checked on DatebookDB details, but I have no idea whether this is significant as I never checked it up for this file before. - Finally, I have had a few Ubuntu crashes lately - not j-pilot related in any way, but j-pilot was up when they happened, it always is, config'd to autostart at startup time. Thanks for your help and time! /PhA. On Tue, 9 Jun 2020 at 17:01, Rich Shepard <rshepard@appl-ecosys.com> wrote: > On Tue, 9 Jun 2020, Philippe Auphelle wrote: > > > I have recently noticed that jpilot sync is not able to access my > > DatebookDB file: slow_sync_application: Unable to open file: DatebookDB > > > If I use sync with backup, I get the similar: fast_sync_application: > > Unable to open file: DatebookDB > > > How can I fix that? > > PhA, > > As Bob Dole responded when asked by a reporter whether he wore briefs or > boxers, "depends." > > What's your OS? What's your handheld? What connection channel are you > using? > Did it work before? Have you tried pilot-link? > > Rich > > _______________________________________________ > Jpilot mailing list > Jpilot@lists.jpilot.org > http://lists.jpilot.org/mailman/listinfo/jpilot_lists.jpilot.org >
PA
Philippe Auphelle
Tue, Jun 9, 2020 3:46 PM

Rich,

PS:

  • In the screen log, I have "slow_sync_application: Unable to open file:
    DatebookDB", but
  • later in the j-pilot screen log, I see "Fetching 'DatebookDB' (Creator
    ID 'date')... OK".

On Tue, 9 Jun 2020 at 17:01, Rich Shepard rshepard@appl-ecosys.com wrote:

On Tue, 9 Jun 2020, Philippe Auphelle wrote:

I have recently noticed that jpilot sync is not able to access my
DatebookDB file: slow_sync_application: Unable to open file: DatebookDB

If I use sync with backup, I get the similar: fast_sync_application:
Unable to open file: DatebookDB

How can I fix that?

PhA,

As Bob Dole responded when asked by a reporter whether he wore briefs or
boxers, "depends."

What's your OS? What's your handheld? What connection channel are you
using?
Did it work before? Have you tried pilot-link?

Rich


Jpilot mailing list
Jpilot@lists.jpilot.org
http://lists.jpilot.org/mailman/listinfo/jpilot_lists.jpilot.org

Rich, PS: - In the screen log, I have "slow_sync_application: Unable to open file: DatebookDB", but - later in the j-pilot screen log, I see "Fetching 'DatebookDB' (Creator ID 'date')... OK". On Tue, 9 Jun 2020 at 17:01, Rich Shepard <rshepard@appl-ecosys.com> wrote: > On Tue, 9 Jun 2020, Philippe Auphelle wrote: > > > I have recently noticed that jpilot sync is not able to access my > > DatebookDB file: slow_sync_application: Unable to open file: DatebookDB > > > If I use sync with backup, I get the similar: fast_sync_application: > > Unable to open file: DatebookDB > > > How can I fix that? > > PhA, > > As Bob Dole responded when asked by a reporter whether he wore briefs or > boxers, "depends." > > What's your OS? What's your handheld? What connection channel are you > using? > Did it work before? Have you tried pilot-link? > > Rich > > _______________________________________________ > Jpilot mailing list > Jpilot@lists.jpilot.org > http://lists.jpilot.org/mailman/listinfo/jpilot_lists.jpilot.org >
RS
Rich Shepard
Tue, Jun 9, 2020 4:07 PM

On Tue, 9 Jun 2020, Philippe Auphelle wrote:

  • All others databases do sync properly, it's just Datebook that seems
    to be messed up somehow.
  • Palm Tx, PalmOS 5.49028
  • In j-Pilot Prefs, all Palm files are config'd for "Palm OS < 5.2.1",
    though. I don't think I ever changed those since I installed 18.4 LTS (and
    it worked before).

Phillippe,

I use a Palm TX and set the databases for PalmOS > 5.2.1 to match the TX.

The PalmOS 5.x should use Calendar rather than Datebook; can't get rid of
the latter, though. Here, CalendarDB-PDat.pdb currently holds 191KB and DatebookDB.pdb
is 360B.

  • Connected through an USB port.

Is this usb: or a tty-specific one?

  • In case this matters, I have FileZ installed on the Palm.

Shouldn't matter.

I recommend doing a soft reset on the TX to reboot it without clearing all
data. Press and release the reset button in the tiny hole. A hard reset is
done by holding down the power button while pressing the reset button. If
worse comes to worse a hard reset followed by restore handheld should do the
trick.

Regards,

Rich

On Tue, 9 Jun 2020, Philippe Auphelle wrote: > - All others databases do sync properly, it's just Datebook that seems > to be messed up somehow. > - Palm Tx, PalmOS 5.49028 > - In j-Pilot Prefs, all Palm files are config'd for "Palm OS < 5.2.1", > though. I don't think I ever changed those since I installed 18.4 LTS (and > it worked before). Phillippe, I use a Palm TX and set the databases for PalmOS > 5.2.1 to match the TX. The PalmOS 5.x should use Calendar rather than Datebook; can't get rid of the latter, though. Here, CalendarDB-PDat.pdb currently holds 191KB and DatebookDB.pdb is 360B. > - Connected through an USB port. Is this usb: or a tty-specific one? > - In case this matters, I have FileZ installed on the Palm. Shouldn't matter. I recommend doing a soft reset on the TX to reboot it without clearing all data. Press and release the reset button in the tiny hole. A hard reset is done by holding down the power button while pressing the reset button. If worse comes to worse a hard reset followed by restore handheld should do the trick. Regards, Rich
PA
Philippe Auphelle
Wed, Jun 10, 2020 9:33 AM

Rich,

I recommend doing a soft reset on the TX to reboot it without clearing

all data.

That fixed it!
After I double checked the problem was gone, I followed your other
suggestion and switched all databases to the "> 5.2.1" format.
Yet another sync confirmed all was still fine, so I'm good now.

Thanks for all your help!  /Ph.

On Tue, 9 Jun 2020 at 18:07, Rich Shepard rshepard@appl-ecosys.com wrote:

On Tue, 9 Jun 2020, Philippe Auphelle wrote:

  • All others databases do sync properly, it's just Datebook that seems
    to be messed up somehow.
  • Palm Tx, PalmOS 5.49028
  • In j-Pilot Prefs, all Palm files are config'd for "Palm OS < 5.2.1",
    though. I don't think I ever changed those since I installed 18.4 LTS

(and

it worked before).

Phillippe,

I use a Palm TX and set the databases for PalmOS > 5.2.1 to match the TX.

The PalmOS 5.x should use Calendar rather than Datebook; can't get rid of
the latter, though. Here, CalendarDB-PDat.pdb currently holds 191KB and
DatebookDB.pdb
is 360B.

  • Connected through an USB port.

Is this usb: or a tty-specific one?

  • In case this matters, I have FileZ installed on the Palm.

Shouldn't matter.

I recommend doing a soft reset on the TX to reboot it without clearing all
data. Press and release the reset button in the tiny hole. A hard reset is
done by holding down the power button while pressing the reset button. If
worse comes to worse a hard reset followed by restore handheld should do
the
trick.

Regards,

Rich


Jpilot mailing list
Jpilot@lists.jpilot.org
http://lists.jpilot.org/mailman/listinfo/jpilot_lists.jpilot.org

Rich, > I recommend doing a soft reset on the TX to reboot it without clearing all data. That fixed it! After I double checked the problem was gone, I followed your other suggestion and switched all databases to the "> 5.2.1" format. Yet another sync confirmed all was still fine, so I'm good now. Thanks for all your help! /Ph. On Tue, 9 Jun 2020 at 18:07, Rich Shepard <rshepard@appl-ecosys.com> wrote: > On Tue, 9 Jun 2020, Philippe Auphelle wrote: > > > - All others databases do sync properly, it's just Datebook that seems > > to be messed up somehow. > > - Palm Tx, PalmOS 5.49028 > > - In j-Pilot Prefs, all Palm files are config'd for "Palm OS < 5.2.1", > > though. I don't think I ever changed those since I installed 18.4 LTS > (and > > it worked before). > > Phillippe, > > I use a Palm TX and set the databases for PalmOS > 5.2.1 to match the TX. > > The PalmOS 5.x should use Calendar rather than Datebook; can't get rid of > the latter, though. Here, CalendarDB-PDat.pdb currently holds 191KB and > DatebookDB.pdb > is 360B. > > > - Connected through an USB port. > > Is this usb: or a tty-specific one? > > > - In case this matters, I have FileZ installed on the Palm. > > Shouldn't matter. > > I recommend doing a soft reset on the TX to reboot it without clearing all > data. Press and release the reset button in the tiny hole. A hard reset is > done by holding down the power button while pressing the reset button. If > worse comes to worse a hard reset followed by restore handheld should do > the > trick. > > Regards, > > Rich > > _______________________________________________ > Jpilot mailing list > Jpilot@lists.jpilot.org > http://lists.jpilot.org/mailman/listinfo/jpilot_lists.jpilot.org >
RS
Rich Shepard
Wed, Jun 10, 2020 12:24 PM

On Wed, 10 Jun 2020, Philippe Auphelle wrote:

That fixed it! After I double checked the problem was gone, I followed
your other suggestion and switched all databases to the "> 5.2.1" format.
Yet another sync confirmed all was still fine, so I'm good now.

Thanks for all your help!  /Ph.

Philippe,

I'm glad that I could help you.

Stay well,

Rich

On Wed, 10 Jun 2020, Philippe Auphelle wrote: > That fixed it! After I double checked the problem was gone, I followed > your other suggestion and switched all databases to the "> 5.2.1" format. > Yet another sync confirmed all was still fine, so I'm good now. > > Thanks for all your help! /Ph. Philippe, I'm glad that I could help you. Stay well, Rich