I have scheduled few tasks in "Scheduled Tasks", but tasks are being queued instead of executing. When I run the tasks manually tasks being executed correctly. I tried all the possible configuration/properties suggested after Google search. Below are screenshots of the task properties.
This post is a litle bit old, but i had the same issue and a found a funny solution. I don't know if this is your case, but i using a Notebook that was not connected from the power. Well... Just disable the option "Start the task only if the computer is on AC power"
(or just put it on the power) and have fun!
Task Conditions
I had faced the same issue and after making a small setting change it worked! Screenshot is attached. When I selected red tick option from X option, it did the trick.
Initially, I selected "Do not start a new instance" and the job was going in "Queued" state. When I changed it to "Stop the existing instance" it worked for me!
Hope it could help.
Unfortunately I was not able to find the reason for this. I had to delete all tasks and add again to solve the issue.
Too bad I only found this post now, we encountered the same issue.
What solved it for us was to run a sysprep (without generalize), reboot the machine and rejoin it into the domain.
Hope it will help you / someone in the future.
Related
When I try to run a project (Only this project and others work fine), it always stucks at the publishing(copy and paste point). It can work perfectly fine until one time I(not sure) accidentally click incrementally publish and then stop it forcefully. Then this problem persists. I try to clean the server and also try to empty the domain folder but none of them works. It is like very strange bug.
I don't want to try creating a new domain since I have add JAAS configuration and JNDI in this domain. Or can anyone tell me how to import the configuration into a new domain?
If I wait long time for it to finish, random problem occurs:
The problem is other project can be run in debug and this project also can previously. It is all just out of sudden when I forcefully stop some process in eclipse tho I am not sure whether it is because of.
This is so annoying and can anyone give some constructive advice? Thx a lot!
Anyone encountering similar situation and sharing his/her experience here will be appreciated. It does not have to be exactly same and any lead or hint are welcome, please.
Actually, I think it is definitely an eclipse bug.
Creating a new workspace and importing all the related projects and glassfish servers can solve the problems though I don't know the actual reason.
I'm new to Azure DevOps, so please forgive me if my query seems a tad silly.
I'm trying to change our build definition so that it will miss certain steps based on the value of a Pipeline variable. So, if I'm correct, I believe that I first must change the Run this task selection (found under Control Options) to Custom conditions (its current value is Only when all previous tasks have succeeded). However, everytime I try this, the original is reinstated. It's as though I don't have the proper permissions, but I'm certainly able to change and save other properties. I'd be grateful for any suggestions!
Thanks,
David.
Thanks to those who responded. I've just tried again, and got it working. The "trick" involved is to make the selection using the arrow keys, and not the mouse. A colleague has also verified this quite odd behaviour.
The browser we are using is Chrome.
Regards,
David.
I've seen variants of this question around, but I'm looking for a definitive answer if anyone has one...
We are running a Cloud SQL Postgres instance, and are stuck on restarting the DB after having an export crash out with an unspecified error.
For several hours now our DB has been out of action saying it's restarting.
The options to export, restart, all of that good stuff, are greyed out and unavailable.
There doesn't seem to be a way to force a restart either through the console, or via gcloud command.
Most of the replies I've seen to this question seem to end up with the poster being helped out by Google support. Don't get me wrong, I'd very much appreciate that, but I'd also like to know if there's a way of doing this myself?
Any help greatly appreciated.
Currently, the 'force restart' option is not available for 'PostgreSQL' instance.
There may be several reasons behind the 'stuck' stage of an SQL instance. Not every time, 'force restart' option wouldn't resolves the root/actual cause.
However, if you still think this option needs to be included in the 'PostgreSQL' instance, I strongly recommend opening a 'Feature Request' through the issue tracker. While opening the 'Feature Request', try to include a bit more details about your use case scenario(with or without an example) as well.
I'm using JavaHg in order to build a customised GUI interface. I was able to clone via code as follows:
BaseRepository repo = Repository.clone(new File(checkout_folder), url);
However, this being a GUI app, it just stalls until the clone is complete. Is there any way to do this clone command while also allowing the GUI to monitor its progress?
My gut feeling is telling me to take a look at the MercurialEclipse plug-in and see how they do it there, but if anyone can suggest an approach, I'd be glad to hear it.
Regards,
Gurce
EDIT:
Thanks for the info on both perspectives, one for the reality of the present situation, and for the suggestion of a night-rider progress bar.
I recently opted for a dodgey workaround approach, which I seem to be getting away with for now.
Since I'm hosting my mercurial projects on a hgweb server, I tried doing it this way:
A checkout (ok ok, clone! :)) is triggered in my app
My app visits the server via ssh and runs a "du" command on the bare repository for the project intending to be checked out
So then my app uses the returned total-disk-space-used by that bare-repo as an estimate of the total disk-space the final checkout should have on the local working folder
My app then polls the local working folder once a second with the "du" command, to see amount of disk-usage the checkout/clone is currently consuming
I use this du result versus the du result from the server to display my progress bar
It's not 100% accurate, but oh well, it seems to do the job ok...
Currently JavaHg doesn't support showing progress of long running operations
with a work thread you can solve the hanging part. i'll check the monitoring, but i think a night rider, work in progress bar will do just fine. you'll have to start a thread to handle the communication and let the main thread go on and handle the actions on the gui.
there are two options to see if the cloneing is over:
-via a callback method (this is the nice, bigbook style way to do this)
-check upon the work thread periodicaly (not so good, but if you're into while cycles and hate callbacks it'll do the trick)
Greetings all.
I have 2 actions: "Find" and "Run". They can be invoked in 3 ways: Find only; Run only; and Find and Run.
I want to put both actions in Jobs.
For the case of "Find and Run", what is the best way in Eclipse to have the "Run" job wait for the "Find" job to complete. Importantly, the "Run" job depends on the results from the Find job.
As I understand it, I could use a lock, or I could use a rule, though the docs indicate that a single rule is the same thing as a lock.
I know I can accomplish this by adding a post-run event onto the Find job which would then invoke the Run job, but I think the platform provides an preferred mechanism for the behavior I need and I wish to use that... just not sure what that mechanism is.
Thanks for advice
Found this in the Eclipse FAQ.
http://wiki.eclipse.org/FAQ_How_do_I_prevent_two_jobs_from_running_at_the_same_time%3F
I'm assuming since it's the answer given in the FAQ that it is, indeed, the best way to solve this problem