baseline_update.sh job is failing with logserver issue.
Logserver log has following message
"LogServer started in non-SSL mode"
I tried restarting PlatformServices
Related
I am trying to install Forticlient EMS onto Windows server. The apache service has been running fine however when running the application it loads with the following error:
Failed to load URL https://localhost/ with error ERR_CONNECTION_REFUSED (-102).
There is not much online to work with regarding this error. I changed the ports in the .conf file to 82 instead of 80 as it was clashing but stuck as to why this error is being produced. Has anyone come across this? This is not running in Chrome rather i am launching Forticlient EMS application for this error to show on the application.
I am trying to run fusion but I keep getting this error: error starting api: api service (pid 8156) failed
zookeeper and solr are started but when it comes to the api i get this error. Any insights are appreaciated.
Run cmd as admin and then try to run the command if that doesn't still work then go to conf/conf.properties and search for port number and change it to some free port on your machine.
Please start the fusion.cmd as Administrator. I faced the same issue and got resolved when I tried as administrator.
I just put my PC on this morning and I get the following error when starting Apache2.4 from Services:
Windows could not start the Apache2.4 service on Local Computer. Error
1067: The process terminated unexpectedly.
I went on Event Viewer to check the logs as most people were suggesting this online and that was no help either, see below screenshot of the error log:
This doesn't really point to the problem or say what the actual problem is, so my question is how can I find the actual cause of Apache not working?
After installing Java EE6 SDK, I installed tutorial with update tool etc. As per Oracle documentation, I started glassfish using
asadmin start-domain --verbose
There was no error in logs but there was no success message too and the command did not end execution, control did not return to dos prompt. Last line in logs was
[#|2012-05-28T19:48:31.213+0530|INFO|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=40;_ThreadName=Thread-2;|JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://WIN-PZ021TGFDU4:8686/jndi/rmi://WIN-PZ021TGFDU4:8686/jmxrmi|#]
Any idea what may have gone wrong? Am able to access server and admin console on 8080 and 4848 resp.
This is normal behavior. The Glassfish verbose mode prints server log messages to System.out (in addition to the log file) and you can see it in the console window. If you don't get an error message everything is ok.
Ctrl-C will stop the server running in verbose mode and you get back to your command prompt.
If you want to see the success message, just start the server without the verbose option.
I'm using rails 3.1.1 and I've been trying to run command as console and rake but I faced with an Error like
Running console attached to terminal...
/Users/ender/.rvm/gems/ruby-1.9.2-p290/gems/
heroku-2.17.0/lib/heroku/client/
rendezvous.rb:33:in `initialize':
Operation timed out - connect(2) (Errno::ETIMEDOUT)
What's the problem? Anyone knows?
There's a few troubleshooting points at http://devcenter.heroku.com/articles/oneoff-admin-ps#troubleshooting - typically it's a problem connecting on port 5000 if you're behind a firewall.