I've installed WSO2 and have it running, devices connected (Android) etc.
I can see the device and the information about it, but the operations log is empty and it's not letting me view the installed applications or deploy new ones.
I've probably missed something basic, but I can't for the life of me see what it is, any help welcome!
Thanks
I hope you are running WSO2 IoT server 3.1.0.
Please follow these steps to enable debug logs.
Go to the IOT_HOME/conf/log4j.properties file.
Uncomment the following two
#log4j.logger.org.apache.synapse.transport.http.wire=DEBUG
#log4j.logger.feign=DEBUG
Comment the following one.
log4j.category.org.apache.synapse=WARN
Then restart the IoT server.
This will start printing debug logs in the IoT_HOME/repository/logs/wso2carbon.log file.
Related
Im trying to connect to my Amazon Workspace using the Workspace client on Ubuntu. I keep getting this. I can connect no problem from my windows machine at work, but keep getting Display Error at home on my linux machine. .
I had same trouble but solved the problem. Please try following process.
Uninstalled AWS.
Re-start PC and installed AWS again.
Wait for couple of hours. while you waiting, try to keep pushing Refresh button or re-start AWS again and again untill the windows shows log in screen.Because it may take some time to clear old registration information and refresh it in the host side according my IT dept says.
Anyway, I've sent the log files to the AWS help desk and are waiting for their reply.
good luck!
Here we can not assume that it is not working because of so and so reasons, instead we should exactly get to know the root cause for this error. So in order to get the RCA, check the log files present in this directory:
C:\Users\yourname\AppData\Local\Amazon Web Services\Amazon WorkSpaces\logs
So, for me, it was showing the AWS URL access was forbidden.
I'm learning wso2 and working with this sample: http://wso2.com/library/articles/2011/01/wso2-esb-example-file-processing/
I followed the instructions but when I start the server nothing happens. I don't see references to the FileProxy or sequences on the management console until I move the xml files to the deployment directory. When I do that I'll see the proxy and Sequences install but nothing else happens when I drop the txt file in the "in" directory.
I am not sure what I need to do to trigger the proxy. I'm not getting any error messages or anything. The server just kind of sits there.
What do I need to do to run the sample?
Thank you.
Try this sample https://docs.wso2.com/pages/viewpage.action?pageId=33136056 in WSO2 ESB 4.8.1 to get a basic understanding of VFS Proxy.
I am using BAM 2.2.0. I configured the service statistics toolbox inside the BAM server based on the documentation. And run the example program "service-stats"it is working fine.
But when I configure BAM inside my AS server using service data publisher configuration, and test the BAM server.Connection was established. But when I click the dashboard in BAM it shows an empty page with some msg how to configure AS .
Currently inside the BAM available script I can see "service-stats-271". How can I visualize my AS service status in BAM. Both servers are running in two machines.
Seeing "service-stats-271" is natural after installing the toolbox. But first you should see whether data has arrived to Cassandra from AS. For that you can login to Cassandra Explorer in BAM Management Console and see whether there is your column family existing in the EVENT_KS keyspace. If yes see whether there are any rows relevant to your events. If yes see whether the data has arrived to the H2 datbase during the execution of the Hive query.
If your data is not correctly published to Cassandra, please read [1] again. Sometimes you may not have done the following instruction mentioned there.
Go to <WSO2 Application Server home>/repository/conf/etc and open bam.xml file and enable ServiceDataPublishing as follows:
<BamConfig>
<ServiceDataPublishing>enable</ServiceDataPublishing>
</BamConfig>
[1] http://docs.wso2.org/wiki/display/BAM220/Setting+up+Service+Statistics+Data+Agent
I am writing a small application to get the various diagnostic parameter of Apache Webserver like time of the start of the server, Worker mode or Prefork mode, server version and many more. I have found few API for getting info about these parameter. But I colud not find nay API for the getting start time of the WebServer. Is there any such kind of API?
If there is no API then there are different approaches like getting the start time using "ps" command in linux/unix and go for similar API in windows.There can be other approach that I could see is to have the time of the APache WebServer in any Variable or file.
Please enlighten me with your valuable comments, approaches.
TIA
Anil
Try to have a look at the Apache' the mod_status
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".