WOL only works immediately never as planned or cron task
-
I will look into this when I get home though I make no promises as I have to figure out how its trying to create the tasks. It might be limited as the user it has to create the task is apache.
-
Thanks Tom. Hopefully you are able to find something amiss. If I run ‘lastlog’ I can see that I don’t have an Apache user. If a fix isn’t immediately apparent, I think being able to manually create the cron job with an authoritative user would be an acceptable workaround.
-
From what I could tell looking into this, it’s not using crontab or at to create scheduled jobs, but rather using the scheduletask service to check the database for specifics. I’ll try to look into it this weekend, but no gaurantees.
-
[quote=“Tom Elliott, post: 17959, member: 7271”]From what I could tell looking into this, it’s not using crontab or at to create scheduled jobs, but rather using the scheduletask service to check the database for specifics. I’ll try to look into it this weekend, but no gaurantees.[/quote]
Aka there will probably be a million updates this weekend and this may be one of them
-
I don’t know about that, but I might add a crontab for the root user that basically runs the php file every minute. This way the DB gets checked, assuming this worked at some point in time. That’s my guess at least.
-
I think I found the problem.
The file in /opt/fog/service/FOGTaskScheduler/ is referencing the class files Host.class.php, Task.class.php, etc… as WEB_ROOT . /management/lib/<classfilename> Which is why it’s not finding anything. One of the files, Imageable.interface.php, doesn’t exist and never has, though the file is still referencing it. I may have just found a fix, but will test with a simple inserted job to see that it recognizes and attempts to run the job. Man, maybe this is much easier than I thought it would be.
-
r946 should now have scheduled tasks back. Hopefully this helps, but please test. I don’t know what Imageable.interface.php was supposed to have so I haven’t a clue as to where to begin coding this if it was truly ever needed in the first place.
-
I’ve since, I think, fixed this issue and will post the updates. I’ve also added the tools to start viewing the scheduled jobs as nothing was in place for this. When I have time tomorrow, I’ll try to upload my changes. Hope all is well. First file that needed changing is the one I already uploaded once. It didn’t work through my testing, but I narrowed how to get it sort of working, I think. Again, I have nothing much I can truly test on, but at least I can see the jobs trying to run.
-
r947 was out, please don’t try was testing something and forgot to remove those tests.
r948 is out and should have scheduled tasks back though I don’t really know for sure. Please test.
-
I am adding the caveat to this, as reading a little further, you’re stating that this bug was with 0.32 and I have been updating 0.33. I still don’t know if the jobs are working properly, but can see what’s going on in 0.32. Maybe I’ll have another aha moment when looking into this for you all.
I’m not familiar with scheduled tasks too much beyond crontab specified, so if my results aren’t working fully yet, I’m very sorry.
-
I’m about to release another revision due to Scheduled tasks. Again it’s only for 0.33, but it seems to, finally, be working properly. *'s work just like crontab. There’s a couple other issues in scheduling the task that’s a little off, but that’s validation problems and not scheduling problems.
I’ve only tested using false values for everything and watching log files. Real-world I haven’t a clue, but at least I can say with some assurance it appears to be working as expected. I haven’t figure out the Single Scheduled task entry process yet and haven’t tested it because of this reason. So to be blatant, only cron style tasks seem to be working for now.
Hopefully this helps.
-
I think I actually got it through more rigorous checking with my test system. It actually looks to create the task as active in wait for the job to start.
-
Told ya he’d get it
-
Yep, Not quite a million updates, but a lot of frustrating testing.
Again, I don’t have any thing real to test with, but I can watch the tasks being activated, and verify they’re now activating when they’re expected to. Hopefully this is what’s needed. For the Task Run Time in the log viewer, I have the dates working to display the rfc time based on the timestamp for delayed jobs, and for cron jobs, it just displays the cron as is present on the database. It appears, so far, all is working properly now.
-
How do I get 0.33?
-
You can download from SVN with:
[code]svn co https://svn.code.sf.net/p/freeghost/code/trunk fog_0.33b[/code] then cd to the fog_0.33b folder and perform normal install or you can download a pre-made tarball at latest revision with:
[url]https://mastacontrola.com/fog_0.33b.tar.bz2[/url]Extract the tarball with:
[code]tar -xjf fog_0.33b.tar.bz2[/code]Then cd into the fog_0.33b folder and perform normal install from there.
