Roland, I got rid of all 3 Jobs and just added one for PPolicy and one for Shadow, for a total of 2 jobs.
I am still getting integrity constraint errors. Is there a way to re-initialize the sqlite database? I can always re-enter the jobs. Jose On 3/30/16, 2:11 PM, "Roland Gruber" <[email protected]> wrote: >Hi Jose, > >till 5.4 is released you need to move one PPolicy job to a different >server profile. The shadow one is ok and can stay. > >With 5.4 you can move the second PPolicy job back. >There is one drawback with moving the job. Emails will be sent a second >time. > >An alternative would be to use just one PPolicy job (and one Shadow) for >the meantime. > > >Best regards > >Roland > > >On 30.03.2016 21:03, Gomez-Rubio, J L. wrote: >> Yes, https://localhost.localdomain/lam/templates/config/jobs.php, there are >> actually 3 jobs. Two for PPolicy and one for Shadow. >> >> I can only have one job? >> >> >> >> >> On 3/30/16, 1:47 PM, "Roland Gruber" <[email protected]> wrote: >> >>> Hi Jose, >>> >>> did you configure two jobs in your server profile? I think I found an >>> issue when two jobs finish within one second. >>> >>> Will fix this for 5.4. In the meantime you can create a second server >>> profile just for the second job. >>> >>> >>> Best regards >>> >>> Roland >>> >>> >>> On 29.03.2016 21:56, Gomez-Rubio, J L. wrote: >>>> Roland, >>>> >>>> I am having this Integrity constraint violation issue with >>>> /usr/share/ldap-account-manager/lib/cron.sh lam 180334964969. I did >>>> upgrade to LAM Pro 5.3 but it still exists just like it did with 5.2. Here >>>> is the error message sent to root’s e-mail: >>>> >>>> Error in job PPolicyPasswordNotifyJob: SQLSTATE[23000]: Integrity >>>> constraint violation: 19 columns name, time are not unique >>>> PHP Fatal error: Uncaught exception 'PDOException' with message >>>> 'SQLSTATE[23000]: Integrity constraint violation: 19 columns name, time >>>> are not unique' in /usr/share/ldap-account-manager/lib/database.inc:471 >>>> Stack trace: >>>> #0 /usr/share/ldap-account-manager/lib/database.inc(471): >>>> PDOStatement->execute(Array) >>>> #1 /usr/share/ldap-account-manager/lib/cron.inc(128): >>>> LAM\DB\saveJobRun(Object(PDO), 'PPolicyPassword...', '1007522302852', 1, >>>> 'SQLSTATE[23000]...') >>>> #2 {main} >>>> thrown in /usr/share/ldap-account-manager/lib/database.inc on line 471 >>>> >>>> LAM Pro is configured to use sqlite for Database type and the Test >>>> Settings button says: >>>> >>>> Database connection ok. >>>> LDAP connection ok. >>>> >>>> Thanks for the help in this matter. >>>> >>>> Jose >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Transform Data into Opportunity. >>>> Accelerate data analysis in your applications with >>>> Intel Data Analytics Acceleration Library. >>>> Click to learn more. >>>> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 >>>> >>>> >>>> >>>> _______________________________________________ >>>> Lam-public mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/lam-public >>>> >>> >> ------------------------------------------------------------------------------ >> Transform Data into Opportunity. >> Accelerate data analysis in your applications with >> Intel Data Analytics Acceleration Library. >> Click to learn more. >> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 >> _______________________________________________ >> Lam-public mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/lam-public >> > ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
