2012

> Can you stop webdna and find the db file to fix while not
> running?

I cannot do anything of consequence on the server. =A0I cannot
stop it, I cannot download the Triggers.db, and of course I
cannot open the Triggers.db in a text editor to confirm
whether or not it is formatted properly.

But I do not suspect a problem with the db file anyways.
Instead I suspect WebDNA itself because there have been
other problems on this server lately which required a reboot
to eliminate. =A0For example:

I have two different scripts that generate email files on the
server. =A0Both work properly by creating only one file per
recipient and placing it into the EmailFolder. =A0But some of
these emails are sent multiple time ...

The host "thinks" that WebDNA is creating multiple emails
(from each individual email file) in its Emailer Queue and
then sending those multiple emails to the mail server for
delivery. =A0The reason he believes this is because the mail
server is on a different box, yet after he rebooted the
WebDNA server the duplicate email problem went away.

---------------------------

Has anyone ever had the "next execute" field fail to update
when the trigger is run?

I suggested to the host that perhaps he gave the Triggers.db
the wrong permissions when he created the sandbox. =A0My
thought was that even though I can edit the Triggers.db via
WebDNA Admin, perhaps somehow the WebDNA software itself
cannot edit the db because it doesn't have enough
permission.

The host sent me this in response to my suggestion:

> Here are the permission levels on the triggers.db file in
> their sandbox.
>
> -rw-rw-r-- =A0 =A01 apache =A0 apache =A0 =A0 =A0 =A0233 Jan 28 06:40<=br>> Triggers.db

Is this the correct permissions on the Triggers.db file?

I really do not think it is possible for WebDNA Admin to be
able to edit a db while the WebDNA software itself cannot,
because they are "one an the same" aren't they?

Other than this possibility I'm at a loss as to what might
cause the Triggers.db to fail to update after the trigger is
run ... except in the case of a bug of course, or possibly a
corrupted database.

But after I deleted all triggers then recreated a new one
the problem persisted, which makes me think it is not a
corrupt db. =A0So this brings me back to the thought that the
WebDNA software may be corrupted.

All other thoughts welcome.

Sincerely,
Kenneth Grome
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us&g=t;.
To unsubscribe, E-mail to: <talk=-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us