How do you debug an Azure WebJob that won't start? - azure-webjobs

I have a WebJob that is triggered by an Azure Storage Queue. When I test this locally everything works fine. When I publish the WebJob (as part of an Azure WebSite) and then go to the Azure Management Portal and try to start the WebJob, it throws and error.
I had this running earlier, but it was having problems so I deleted the job in the management portal and tried to republish the web site with the web job.
Any suggestions on how to figure out what's going on?

In the old Azure Management Portal there was no clear way I could find to kill the process (stop the Job if there was one). Using the new portal, I looked at all the processes running on the site and there was the WebJob running 26 threads. After killing the process I was able to start the recent uploaded one.

Related

Issues for launch one-shot task in Cloud Foundry v2

Currently I'm just trying to use the spring cloud task feature in pivotal public cloud with my account, the api version is 2.63. I just copy the only complete sample code from the spring cloud task document, build and package locally and push to the cloud foundry, and specify "no-route: true" and "health-check-type: none" in manifest.yml. But it seems no use, the log shows error info "Process has crashed with type: web" after successfully run the sample and destroy the container. So I wonder why cloud foundry think my applications is a web based application, because judging from the dependency, I only use the spring-cloud-task-core and spring-boot-starter. Why it still perform health check even I've set it to avoid this kinds of check?
The health-check-type property has effects only for worker application to ensure not crash during application start and run in Diego container. But when the application finished and container destroyed, this property can't prevent Diego to take it as a crash issue and restart it. Only Cloud Foundry V3 start to support the feature of Task.

Sharepoint 2013 - Timer job is not running

I have a server farm configuration with 2 web server, 1 app servers and 1 database server.
What i am trying to do from timer job is to loop through all web applications present in the server farm and perform some action against some web-applications.
I have timer job which is provisioned with Central admin web application and locktype as ContentDatabse passed as parameter, and i have scheduled this job to run every 2 minutes. This timer job is provisioned by a feature which has a farm scope.
Central admin site is hosted on web servers but not on app server.
My timer job never runs.
In Central admin, i see job is scheduled to be run from 2 web servers but not from app server.
In SharePoint app server log i see one interesting log which says "Job definition TestJob, id 779b3ccf-df47-4c4d-aaea-7b3ae2f6502a has no online instance for service Microsoft.SharePoint.Administration.SPWebService, id db200214-6eb2-4696-bb3b-53cb12119650, ignoring"
If i stop the SharePoint timer service running in the app servers my timer job runs, after my job has run once, if i start the timer service in app server, my job runs every 2 minutes as expected. From this blog i have came to know that "So, the first thing is that for a particular server to be eligible to run the job, it must be provisioned with the service or web app associated with the job." And my app servers does not host the web applications.
My questions is.
Why is my timer job is trying to run from the app servers?
If i pass a web server while provisioning timer job is that correct? I think timer job becomes tied to particular server and removing/ taking it down may make the timer job not to run.

Azure Web Jobs architecture

I have some code that needs to run as a result of a call to a service bus. This particular code is CPU intensive and it is possible that 100s of these will need to run at the same time. Does Azure Web Jobs use computing resources from one machine, or does it use any available computing resources from several machines?
Web Jobs uses your web app resources, why don't you try the Azure Functions which can be scaled and their pricing is almost zero. They are in Technical preview i have tried using it, Azure functions is very cheap. If your service bus call can be out of process service meaning it does not need a instance results from your application you can try azure functions. Azure functions are mostly used for maintenance and night time running jobs. I have used it to minify my images to thumbnail. It worked perfectly fine
Azure Webjobs is designed to run on as many servers as you've scaled up the website to run on. By default it will run up to 16 tasks from a queue concurrently but this is configurable as shown here.
public class Program
{
static void Main()
{
JobHostConfiguration config = new JobHostConfiguration();
config.Queues.BatchSize= 1;
JobHost host = new JobHost(config);
host.RunAndBlock();
}
}
A web job deployed as part of an Azure WebSite will share the resources with the web application. You have the option to scale the website up to 10 (I think?) instances if you need parallelism.
As I mentioned in the comment to Matthew's post, if you use the Azure WebJobs SDK to have functions triggered by ServiceBus queue messages, we don't parallelize as part of the same host. This means that messages will be processed sequentially as long as you have a single host.

informatica problem

Facing Error: *cannot start the server 'servername' *
when trying to start the workflow, iam getting the above error. I have configured server settings properly and it resolved as well..
all the informatica services are running fine. what could be the problem.
I suspect this as a wrong assignment of Integration service to workflow.
Make sure you assign a running/working Integration service to the workflow.
To assign a Integration service, Close all folders and select the Integration server from the navigation panel and select the workflow which you are trying to run and apply the settings.
Let me know if this works for you.
which version are you running ?? there could be multiple reasons for this error message, but most probably -
your informatica server configuration is not correct, and therefore the attempt to start the server fails. As a result, when a workflow tried to execute, the attempt to connect to a running server instance fails.
I doubt if all the infa services are running fine.. if actually so, then I would reconfigure my client connection and see if you are actually hitting the right domain/service combination.
I feel there can be multiple reason for this issue
Informatica Integration services is not correctly assinged
Informatica services is not running
wrong connection
I believe informatica integration services related issue will be there.

VMware Server 2.0 - The VMware Infrastructure Web Service not responding

After installing VMware Server I get the following error when I try to access the VMware web-based server manager:
The VMware Infrastructure Web Service
at "http://localhost:8222/sdk" is not
responding
Go into the services manager and check that the 'VMware Host Agent' service is running. If not, then start it and then try browsing to the site again.
Vmware Hostd was not working for me either.
However, in trying to start the service it stopped automatically. Typically when this happens it is because there is an error in your config.xml.
C:\ProgramData\VMware\VMware Server\hostd\config.xml
In my case, checking the logs at:
C:\ProgramData\VMware\VMware Server
showed it erroring out after "Trying hostsvc".
Searching the config.xml for hostsvc showed references to several things, the first thing was the datastore. In checking my datastores.xml file:
C:\ProgramData\VMware\VMware Server\hostd\datastores.xml .
I found it full of all sorts of random characters instead of a properly formed XML document.
Renaming datastores.xml to datastorex.xml.bad allowed me to start the service. At which point I had to add back my datastores through the GUI.
Hopefully this will help someone else out. I did not find any other references in Google to this issue.
Try accessing via "http://localhost:8222" without the /sdk. You can also try the secure site via "https://localhost:8333".