I am on Centos 7. 2.19.2 There is indeed a difference in Cron (indeed as root) vs rdlogmanager (as rduser)
So I took a clock (nr 100) from the old (converted) database, save as (nr 101), and changed 1 event (halfway this clock event nr10) If I run the graphical rdlogmanager, everything is scheduled just fine (user: rduser) if I run it in commandline (either root or rd), only for clock 101, the first 2 events are scheduled, and the 3rd event (Voicetrack1) is not scheduled, It skips through to next hour/clock. *Other clocks* are scheduled just fine. I left 101 out of the grid at the moment. I sure hope it didn't mess up my database. I checked the group 'voicetrack' it is in the production group, Also checked the even voicetrack. Everything looks pretty normal, as it used to be defined in the old database. Regards 2018-08-22 1:11 GMT+02:00 Peter Claes <pcl...@cls-bvba.com>: > I am on Centos 7. 2.19.2 > > There is indeed a difference in Cron (indeed as root) vs rdlogmanager > (as rduser) > > So I took a clock (nr 100) from the old (converted) database, save as > (nr 101), and changed 1 event (halfway this clock event nr10) > If I run the graphical rdlogmanager, everything is scheduled just fine > (user: rduser) > > if I run it in commandline (either root or rd), only for clock 101, > the first 2 events are scheduled, and the 3rd event (Voicetrack1) is > not scheduled, It skips through to next hour/clock. > > *Other clocks* are scheduled just fine. > I left 101 out of the grid at the moment. I sure hope it didn't mess > up my database. > I checked the group 'voicetrack' it is in the production group, Also > checked the even voicetrack. Everything looks pretty normal, as it > used to be defined in the old database. > > Regards > Peter > > > > 2018-08-21 23:26 GMT+02:00 Robert Jeffares <jeffares.rob...@gmail.com>: >> Look at the EVENT immediately after the first VTRAX and check Services >> [button mid lower]. >> >> You may find your new service is in there twice.. >> >> Given different performance for cron [as root?] vs rdlogmanager [ as rduser] >> you may have to amend permissions on the Rivendell mysql database. >> >> Are you on CentOS or some other? >> >> R >> >> On 21/08/18 07:46, Peter Claes wrote: >>> >>> I have a strange problem. >>> >>> I imported our database a while a go, onto a new machine. >>> Everything is tested, and runs perfectly. >>> >>> Until I made a new clock under the new database structure. >>> >>> In the new clock (copy and paste from another one) it stops at the 1st >>> voicetrack, and starts a new clock. >>> >>> I generate the logs via a cron job, only then this occurs. >>> >>> If generate a log via Rdllogmanager, this is not happening. >>> >>> Could this be user related ? >>> >>> Regards >>> Peter >>> _______________________________________________ >>> Rivendell-dev mailing list >>> Rivendell-dev@lists.rivendellaudio.org >>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> >> >> _______________________________________________ >> Rivendell-dev mailing list >> Rivendell-dev@lists.rivendellaudio.org >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
