while running an Wf through Autosys i am not able to open the session log in monitor were as if i run the same wf in workflow manger i am able to open the session log
can some1 pls help with this issue.
thanks
Related
I keep receiving an "Internal Server Error" redirect when I click the "Open Airflow UI" link in the Amazon MWAA console; it's just a blank white screen with "Internal Server Error" in big black text. I was being successfully redirected to the Airflow UI when I set up the environment, but it appeared to break overnight. It then started working again yesterday, then broke again today overnight.
Please let me know if I can provide further details--thank you!
I have tried and confirmed the following:
Region is correct with us-west-2
Logging in and back out as root user with access to everything
VPC setup and permissions are the same as when the Open Airflow UI was successfully redirecting me
VPC setup is with the standard AWS Cloudformation template that is provided during MWAA setup
A token is provided after the login = true portion of the URL redirect
Maintenance window is set as 7 AM UTC, Sunday, so it shouldn't be occurring now
I expect to be redirected to the Airflow UI successfully.
This is a bug that I expect to be fixed fairly quickly. As a workaround you can delete your browser's cookie whose name corresponds to your Airflow UI link, refresh, and you're good to go.
It is a known issue of MWAA. I am unsure what is the root cause of it, but I've seen this issue for a while. I am using MWAA Airflow 2.4.3. It happened when I tried to access MWAA Airflow UI the day after I deployed it.
You have to delete the cookie. I'll use Chrome to demonstrate it.
Open the Chrome Developer Tools and click Application then Cookie:
Click session and delete the value.
Now go back to AWS console MWAA environment page and click the Open Airflow UI button again, you should be able to access Airflow UI.
Hope this helps.
I have a tomcat server in Azure(Linux RedHat8.1) and DB server in GCP(Centos Linux). I connected tomcat to the DB server, And I successfully opened the URL in a browser and I logged into the website. For the first time successfully login and I give break for 10 to 15min and try to login again, this time it can't be logged in.
I don't know what is the root cause of this issue.
After some time when I refresh the page, it automatically logged in, or after 20 to 30min it can be logged in. (or) after 6 to 12hrs it's logged in or in case restart the
tomcat it's logged in.
But the issue does not come from GCP(Tomcat) connecting to GCP(DB) or AWS(Tomcat) connecting to GCP(DB)
Please anyone help me regarding this issue?
Thanks in advance.
I have couple of dataservices to be run on wso2 esb. I have created a tenant instance and placed these dataservices in repository/tenants/[tenant_id]/dataservices. when I login into wso2 management console with tenant user and try to run any of the dataservice- I’m getting an error saying
the input stream of an incoming message is null
On the other hand the dataservices placed for the master user under folder repository/deployment/server/dataserivice is getting executed and fetching desired results when ran through admin master user. can I get some help to resolve this issue with tenant.
I just downloaded and installed WSO2 API Manager to a Linux server. As per the installation guide, I have not made any changes.
The only wrinkle I had was that the wso2server.sh script did not have execute permission so I set that manually. I did not check or modify any other permissions.
After startup, I am able to access each of the Admin, Publisher and Store apps.
In the Admin app, the first screen shows the message: "No tasks assigned to the login user or no connectivity with BPS engine."
When I dig into the logs, I see this entry in wso2carbon.log
TID: [-1234] [] [2017-03-02 10:26:12,049] WARN {JAGGERY.site.blocks.user.login.ajax.login:jag} - Not Retrieving Pending Tasks. Check BPS Connectivity. java.lang.IllegalArgumentException: Illegal character in authority at index 8: https://<BPSHost>:<BPSPort>/services/AuthenticationAdmin {JAGGERY.site.blocks.user.login.ajax.login:jag}
the wso2-apigw-errors.log has a largely identical error
2017-03-02 10:26:12,049 [-] [http-nio-9443-exec-17] WARN login:jag Not Retrieving Pending Tasks. Check BPS Connectivity. java.lang.IllegalArgumentException: Illegal character in authority at index 8: https://<BPSHost>:<BPSPort>/services/AuthenticationAdmin
This may or may not be relevant, I am also seeing warnings about being unable to flush and lock system prefs, even though its successfully creating the directory earlier.
TID: [-1234] [] [2017-03-02 09:28:30,285] INFO {java.util.prefs.FileSystemPreferences$1} - Created user preferences directory. {java.util.prefs.FileSystemPreferences$1}
TID: [-1] [] [2017-03-02 11:11:19,058] WARN {java.util.prefs.FileSystemPreferences} - Could not lock System prefs. Unix error code 32645. {java.util.prefs.FileSystemPreferences}
TID: [-1] [] [2017-03-02 11:11:19,058] WARN {java.util.prefs.FileSystemPreferences} - Couldn't flush system prefs: java.util.prefs.BackingStoreException: Couldn't get file lock. {java.util.prefs.FileSystemPreferences}
I am assuming I need to configure or download something else to get this work. Please advise!
I am not sure what your use case is. You can integrate a BPS engine with WSO2 API Manager for the following tasks.
User Signup Workflow
Application Creation Workflow
Application Registration Workflow
API Subscription Workflow
This blog explains how you can integrate WSO2 Business Process Server with WSO2 API Manager. You can check the official documentation which explains the avaiable workflow extensions.
You are getting this warning message when you are logging to admin portal as it checks if there are any pending approval tasks. You can ignore this warning if you are not using any BPS integrations. Based on your use case you can add a BPS engine for workflows.
I've gotten WSO2 working on the server. I can login through the management console and EMM, publisher, and store are all working. I can create a new user through the EMM dashboard, and the email is sent correctly. So everything is fine while using the website.
I'm using the sample APK that comes with WSO2 to do some development, but every time I try to register the app pops up "Authentication Failed - Cannot proceed the authentication. Please contact an administrator." And there is no output in the console when this happens.
If I put in the incorrect credentials I get a separate error, "Authentication Failed - Incorrect login information. Please try again." So I know my credentials are correct.
What does this mean? Is there another place to find more detailed logs?
Have you tried debugging the Android-agent ? If so you might be able to provide more information regarding this issue by looking at agent debug logs.
BTW did you tried enrolling as the admin user?