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".
Related
I am trying to install Oracle Client 19c when i starts the installation its freezes at stage 1, checked logs it hangs on "INFO: Checking whether the IP address of the localhost could be determined...", i refer some article to skip stage mentioned step but it also stuck on stage 7.
My System is in Domain
I tried the installation on recently formatted System and it worked with antivirus.
also tried to disable the Antivirus from my system but faced the same freezing issues. if unjoin the Domain and try it works.
I suspect the issue with any Domain Policy but dont understand the which policy is creating the problem, please suggest the solution.
If you are seeing "Reading from the pipe" message in ...\Inventory\logs OUT files then, login Windows with an admin account and run the services called "Server" and "Workstation".
I'm seeing errors in StackDriver logging for my Compute instance. The logs are showing repeated issues every hour, creating a lot of noise. I have a Spring Boot API deployed in a container to a VM in Compute Engine using latest stable version of Container OS.
I'm relatively new to GCP and don't understand what is causing this issue, searches have come up empty so far.
Failed to call method: org.chromium.SessionManagerInterface.RetrieveActiveSessions: object_path= /org/chromium/SessionManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.SessionManager was not provided by any .service files
CallMethodAndBlockWithTimeout(...): Domain=dbus, Code=org.freedesktop.DBus.Error.ServiceUnknown, Message=The name org.chromium.SessionManager was not provided by any .service file
Error calling D-Bus proxy call to interface '/org/chromium/SessionManager': The name org.chromium.SessionManager was not provided by any .service files
The same 3 lines are repeating every hour. Anyone aware of what might be causing this or how to fix/suppress these?
I looked into this error, and as per my findings:
The error message that you have been receiving is a manifestation of Chrome to reliably exit shortly after starting up.
The UI’s job (which encompasses Chrome, the session_manager and the window manager) gets shut down by upstart because of it's thrashing, and when the test tries to restart the session_manager, the session_manager cannot communicate it over to the D-Bus.
The crash collection software in Container OS was originally for Chromebooks (The laptop using Chrome browser). So the code typically expects Chrome and some other related software on the system.
However, Container OS is a server OS, and does not have Chrome. So if Chrome is missing, the software will report some errors. They are actually not real failures, just some verbose error messages.
Overall, It is safe to ignore these logs and continue using your VM Instances.
Hope this helps.
I have installed hyperledger composer locally. But on localhost it gives error :
Error : Error trying to ping.
Error: No business network has been
specified for this connection.
I am not able to add model and script file as well.
This is the errors showing in terminal
error: [Hyperledger-Composer] undefined:HLFConnection :ping() Error: Error trying to ping. Error: No business network has been specified for this connection
at _checkRuntimeVersions.then.catch (/usr/local/lib/node_modules/composer-playground/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:787:34)
at <anonymous>
at runMicrotasksCallback (internal/process/next_tick.js:121:5)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9) error: [Hyperledger-Composer] undefined:ConnectorServer :Error: Error trying to pi
I think I solved this problem.
About the error
The error reason is No business network has been specified for this connection., this does not happen when you first time to run composer-playground, because that time, you truly do not have a network and you either do not have card too, so there is a modal pop up Let's blockchain.
This only happened when you stop/delete your business network net, or there is no business network running but you also have the business card linked to the network.
Solution
Follow the tutorial to create a new business network locally
restart your farbric tool by stopFabric.sh and startFabric.sh, (* this is not to start your business network but your fabric)
run your playground again composer-playground
probably you will also see the error again (error trying to ping), but no worry
find a button at top right corner which is folded My Business Networks
delete the card without connection or deploy a new network
This worked for me, hope it will work for you too. This kind of process design limitation, the card is still there even you delete your network or your are trying to start your playground even you did not start your network. This is why this error happened I think.
Addition, More about playground
Hyperledger Composer Playground (Playground from now on) uses your
browser's local storage to simulate the blockchain network's state
storage, which means you don't need to run a real validating peer
network to use Playground.
Using browser-only mode, you can model and test the business network
using a mock blockchain ledger that resides in your browser's local
storage.
How to delete cache in browser Chrome
This probably can solve many errors.
In Chrome, for example, under Settings > Advanced > Content Settings >
Cookies > All cookies and site data > localhost, click the trashcan
icon to remove local storage. If you're using a different browser,
follow the instructions specific to that browser, and delete all local
storage.
References
A very good IBM blockchain/ composer tutorial, just old, need to be pay attention to that some commands not working in the same way on new version of composer
I got the same issue here. I'm not sure what's wrong(maybe because I fail to create a business network last time). But since the playground store the data with browser local storage. I simply clear the local storage and fix it.
I had the same issue and it got fixed.
Clear the cache of your browser and refresh the page!
Noticed composer wasnt running in the terminal.
Runcomposer-playgroundin the terminal and retry.
I have followed all the steps as per the instructions. All the key services are running like zookeeper, mongodb. I have verified mutliple times.
However when it comes to start kaa-node, then service always fails with exit code.
I have verified several items including IP address etc on the Digital Ocean VPS. Validated the firewall setup.
That might be caused by lack of necessary resources like memory or disk space. Please check the minimal requirements on the Getting started documentation page.
If that is not an issue, please provide more details on the error and logs you get from the kaa-node startup.
I am using Coldfusion MX8 server and one of the scheduled task was running from 2 years but now suddenly from 01/12/2014 scheduled tasks are not running. When i browsed the file in browser then the file is running successfully without error.
I am not sure is there any updatation or license expiration problem. I am aware that mid of this year Adobe closed the support for coldfusion 8.
The first most common problem of this problem is external to the server. When you say you browsed to the file and it worked in a browser, it is very important to know if that test was performed on the server desktop. Knowing that you can browse to the file from your desktop or laptop is of small value.
The most common source of issues like this is a change in the DNS or network stack that is interfereing with resolution. For example, if the internal DNS serving your DMZ suddenly starts serving the "external" address - suddenly your server can't browse to your domain. Or if the IP served by the server for the domain in question goes from being 127.0.0.1 to some other IP that the server can't acces correctly due to reverse proxy or LB or some other rule. Finally, sometimes the Apache or IIS is altered so that an IP that previously was serviced (127.0.0.1 being the most common example) now does not respond.
If it is something intrinsic to the scheduler service then Frank's advice is pretty good - especially look for "proxy schduler" entries in the log - they can give you good clues. I would also log results of a scheduled task to a file. Then check the file. If it exists then your scheduled tasks ARE running - they are just not succeeding. Good luck!
I've seen the cf scheduling service crash in CF8. The rest of CF is unaffected.
Have you tried restarting the server?
Here are your concerns:
Your File (works since you tested it manually).
Your Scheduled Task (failed).
Your Coldfusion Application (Service) (any changes here)?
Your Server (what about here).
To test your problem create a duplicate task and schedule it. Leave the other one in place (maybe set your new one to run earlier). Use the same file too. See if it completes.
If it doesn't then you have a larger problem. Since the Coldfusion Server sits atop of the JVM there could be something happening there. Things just don't stop working unless something got corrupted or you got compromised. If you hardened your server by rearranging/renaming the file structure to make it more secure...It would break your task.
So going back: if your test schedule works then determine what is different between the two. Note you have logging capabilities. Logging abilities for CF8
If you are not directly incharge of maintaining this server, then I would recommend asking around and see if there was recent maintenance, if so, what was done to the server?