While working on configuring the Shibbolet SP, I had to stop and start the shibd service many times after reconfiguring the shibboleth2.xml file.
first it worked ok, but then I couldn't start it again!
when running this command on cmd C:\>net start shibd_default, I got the following:
The Shibboleth 2 Daemon <Default> service is starting.
The Shibboleth 2 Daemon <Default> service could not be started.
The service did not report an error.
and when attempting to run it from Control Panel > Services > Administrative Tools , I got this error
The Shibboleth 2 Daemon <Default> service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
I've re-installed the Shibboleth SP to overcome this problem, but still getting this error!
Can anyone help me figure this out?
Thanks
Please check your log files at C:\opt\shibboleth-sp\var\log\shibboleth for errors.
IF there is a XML configuration error, the service won't load properly.
I Got an error similar to the one below:
ERROR Shibboleth.Config : error while loading resource (C:/opt/shibboleth-sp/etc/shibboleth/shibboleth2.xml): XML error(s) during parsing, check log for specifics
2013-05-13 10:59:13 FATAL Shibboleth.Config : caught exception while loading configuration: XML error(s) during parsing, check log for specifics
Related
I have been trying to start ApacheDS service on windows for a while, but failed.
I want to connect to LDAP but the ApacheDS service can't start.
I tried to check my wrapper log file and found the error -
Unable to load the Wrapper's native library 'wrapper.dll'.
However, I am running a 64-bits JVM and my computer has 64-bits as well. How can I find the wrapper.dll file of 64-bits, if it is the cause to the error?
I hope if this error gets fixed, I will be able to connect LDAP without error: [LDAP result code 52 - unavailable] Proxy operation retry failed.
Thank you for your assistance.
wrapper log file
Hi I tried the below command to start the dmgr.
~Websphere/Appserver/profiles/CORPDWAS70DepMgr/bin
$ ./startManagaer.sh
I got the below error.
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/CORPDWAS70DepMgr/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the CORPDWAS70DepMgr profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
/opt/IBM/WebSphere/AppServer/profiles/CORPDWAS70DepMgr/logs/dmgr
should contain failure information.
I opened the systemout.log
I am unable to understand the error.
Please help.
I am using wildfly 10.1 in standalone mode and need to use it as a service.
I copied the service files to the bin folder and then installed the service from the command prompt.
This works well, except that it is impossible to stop the service without killing the process using taskkill.
As a fix, I tried replacing
set DESCRIPTION="WildFly Application Server"
with
set DESCRIPTION=WildFly Application Server
in the service.bat file as mentioned here. But this is causing the service not to start. The system log says:
The Wildfly service terminated with the following service-specific
error: Incorrect function.
How can I fix this issue and get the service starting and stoppping normally?
Add System variable JAVA_HOME to System variable and try to start the service. It worked for me.
I created websphere server. I was able to launch my application with it. However after I enable the debugging , the server is not starting. I am getting the following error
"ADMU7704E: Failed while trying to start the Windows Service associated with
server: server1; probable error executing WASService.exe"
On some sites a workaround was to delete server.pid file but I am not seeing any such files in the location.
Please suggest
The first thing to test is to disable the WAS Windows service from Windows Services Panel and then try to start server using command line ie startserver.bat
You run this command from PROFILE_HOME/bin. if this starts fine, you can recreate the service using wasservicecmd
http://www-01.ibm.com/support/docview.wss?uid=swg21397335
If the manual startup fails , please check if any logs created under PROFILE_HOME/logs// Check for any error messages in SystemOut.log, SystemErr.log , native_stderr and native_stdout logs.
PROFILE_HOME is home directory of WAS profile.
VG, opinions are my own and not those of my employer
I downloaded Hudson, and am trying to install it as a service. I followed the steps from this page, but when I try to start the service, it always fails. I'm not really getting any defined error codes either. If I try to run the service from the command line (using net start) I get the following (unhelpful) message:
The hudson service could not be started.
The service did not report an error.
The install process seemed to work fine, as the hudson service is installed, and all the files are in the new directory, but the service won't start. Has anyone else run into this problem?
As documented on that page, they have a note of...
If a restart fails for some reason, check the output from Hudson, which is stored in the installation directory that you specified.
Is there anything to denote further errors?