On Jul 16, 5:03 pm, AchipA <
attila.cs...@gmail.com> wrote:
> Depending on the cron mode, you likely won't see the logging.warn as
> it is executed in a different process when called from cron. When
> called from the script, the warn is executed in the 'main' process and
> hence you can see it. So that in itself does not mean anything.
Right yes, sorry - I reduced the call to that simple function when my
1st attempts failed.
The real call is an email send using mail.send()
This works fine, as a Hard Cron, if I'm running the Widget & using the
wrapper script to call it.
> When
> debugging cron functions, first make sure it works by calling it via -
> S app/contr/func as debug output will be hard to obtain straight from
> subprocesses.
The function itself works fine from the Web UI, via the CLI called
like this & via the wrapper script called by Cron.
It fails when trying to call from Cron direct.
Another cron issue I have is that even the wrapper script file isn't
working when running as a Windows Service (
http://mdp.cti.depaul.edu/
AlterEgo/default/show/77).
- even if I keep accessing the server, so it's not just rveerting to
Soft mode.
Any further tips on debugging either of these issues would be
welcome :)
F