Hi Werner, see my comments in-line.
Regards,
F.

Il 06/02/2015 09:50, dj-wasabi ha scritto:
Hi Fabio,

Thanks for your answer.

I've put the following loggers on "ALL":
connid + org.apache.syncope.core.rest + org.apache.syncope.core.sync +
org.apache.syncope.core.quartz
Use DEBUG level. Change org.identityconnectors to DEBUG.
If you cannot see enough, please move ROOT logger to DEBUG as well.

Check into the following logs.

* core.log
* core-rest.log
* core-connid.log

But I won't see anything in the logfiles. The synchronisation is configured
to run every 10 minutes in the tab you mentioned. It is configured like
this:
* 0/10 * * * ?
Please change it to
0 0/10 * * * ?

Please note that your first '*' if not correct.
If you schedule at 8:34 (your example below), the job will be executed at 8:40, 8:50, 9:00, 9:10, .... and so on (please note, no job will be executed at 8:34).

The strange thing:
When I try to run it manually (I have to click on the execute button twice)
and it run like how it should run, and it will schedule the job and it will
run for 2 times. After that, it stopped.
Please click once. Each click schedule (now) a job.
You have to wait for the next quartz job executor cycle.


Both Last Execution and Next Execution aren't updated. I manually ran the
sync this morning at 08:34. At 08:40 and 08:50 it runs like the cron
configuration. When I open the "Synchronisation" tab on the "Task" page, it
will show me the "Last run": 2/6/15 9:00 AM and "Next run": 2/6/15 9:10 AM.
'last execution' and 'next execution' are about the last execution: you cannot find info about previous executions.
But when I "edit" this task and open the "executions" tab, it only shows me
the last run was at 08:50.
This is really strange: maybe 8:34 and 8:40 executions haven't been really scheduled.
Are you sure about the goodness of your steps.
Please, try again with the following:
1. loggin out if looged in
2. log in again
3. unschedule the task and save
4. check next execution column with no values
5. execute again manually three times, one every 5 minutes.
6. check executions an let me know

Kind regards,
Werner


--
View this message in context: 
http://syncope-user.1051894.n5.nabble.com/cron-openldap-Synchronisation-not-executed-tp5707897p5707899.html
Sent from the syncope-user mailing list archive at Nabble.com.


--
Fabio Martelli

Tirasa - Open Source Excellence
http://www.tirasa.net/

Apache Syncope PMC
http://people.apache.org/~fmartelli/

Reply via email to