I have no clue about what am I wrong in here.
C:\Program Files\JBOSS\jboss-5.1.0.GA\bin>run.bat
Calling C:\Program Files\JBOSS\jboss-5.1.0.GA\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files\JBOSS\jboss-5.1.0.GA
JAVA: C:\Program Files\Java\jdk1.6.0_34\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun
.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg
.jboss.resolver.warning=true -server
CLASSPATH: C:\Program Files\JBOSS\jboss-5.1.0.GA\bin\run.jar
===============================================================================
log4j:ERROR Failed to create directory structure: C:\Program Files\JBOSS\jboss-5
.1.0.GA\server\default\log
log4j:ERROR setFile(null,false) call failed.
java.io.FileNotFoundException: C:\Program Files\JBOSS\jboss-5.1.0.GA\server\defa
ult\log\boot.log (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:194)
at java.io.FileOutputStream.<init>(FileOutputStream.java:116)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:2
56)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.j
ava:132)
at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.j
ava:96)
at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigura
tor.java:654)
at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigura
tor.java:612)
at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyC
onfigurator.java:509)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:415)
at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:441)
at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionCon
verter.java:470)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
at org.jboss.logging.log4j.Log4jLoggerPlugin.init(Log4jLoggerPlugin.java
:70)
at org.jboss.logging.Logger.getDelegatePlugin(Logger.java:603)
at org.jboss.logging.Logger.<init>(Logger.java:119)
at org.jboss.logging.Logger.getLogger(Logger.java:567)
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java
:204)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:1
73)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:1
43)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
11:42:08,937 INFO [ServerImpl] Starting JBoss (Microcontainer)...
11:42:08,938 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build:
SVNTag=JBoss_5_1_0_GA date=200905221634)
11:42:08,939 INFO [ServerImpl] Bootstrap URL: null
11:42:08,939 INFO [ServerImpl] Home Dir: C:\Program Files\JBOSS\jboss-5.1.0.GA
11:42:08,940 INFO [ServerImpl] Home URL: file:/C:/Program%20Files/JBOSS/jboss-5
.1.0.GA/
11:42:08,940 INFO [ServerImpl] Library URL: file:/C:/Program%20Files/JBOSS/jbos
s-5.1.0.GA/lib/
11:42:08,942 INFO [ServerImpl] Patch URL: null
11:42:08,942 INFO [ServerImpl] Common Base URL: file:/C:/Program%20Files/JBOSS/
jboss-5.1.0.GA/common/
11:42:08,943 INFO [ServerImpl] Common Library URL: file:/C:/Program%20Files/JBO
SS/jboss-5.1.0.GA/common/lib/
11:42:08,944 INFO [ServerImpl] Server Name: default
11:42:08,944 INFO [ServerImpl] Server Base Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server
11:42:08,945 INFO [ServerImpl] Server Base URL: file:/C:/Program%20Files/JBOSS/
jboss-5.1.0.GA/server/
11:42:08,946 INFO [ServerImpl] Server Config URL: file:/C:/Program%20Files/JBOS
S/jboss-5.1.0.GA/server/default/conf/
11:42:08,946 INFO [ServerImpl] Server Home Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default
11:42:08,947 INFO [ServerImpl] Server Home URL: file:/C:/Program%20Files/JBOSS/
jboss-5.1.0.GA/server/default/
11:42:08,947 INFO [ServerImpl] Server Data Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default\data
11:42:08,948 INFO [ServerImpl] Server Library URL: file:/C:/Program%20Files/JBO
SS/jboss-5.1.0.GA/server/default/lib/
11:42:08,949 INFO [ServerImpl] Server Log Dir: C:\Program Files\JBOSS\jboss-5.1
.0.GA\server\default\log
11:42:08,949 INFO [ServerImpl] Server Native Dir: C:\Program Files\JBOSS\jboss-
5.1.0.GA\server\default\tmp\native
11:42:08,950 INFO [ServerImpl] Server Temp Dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default\tmp
11:42:08,951 INFO [ServerImpl] Server Temp Deploy Dir: C:\Program Files\JBOSS\j
boss-5.1.0.GA\server\default\tmp\deploy
11:42:09,548 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/P
rogram%20Files/JBOSS/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
11:42:10,125 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.pl
ugins.cache.CombinedVFSCache]
11:42:10,129 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache
: null]]
11:42:10,409 INFO [CopyMechanism] VFS temp dir: C:\Program Files\JBOSS\jboss-5.
1.0.GA\server\default\tmp
11:42:10,411 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
11:42:10,667 ERROR [AbstractKernelController] Error installing to Create: name=A
spectManager state=Configured
java.io.FileNotFoundException: Failed to create tmpClassesDir: C:\Program Files\
JBOSS\jboss-5.1.0.GA\server\default\tmp\aopdynclasses
at org.jboss.aop.asintegration.core.AspectManagerServiceDelegate.create(
AspectManagerServiceDelegate.java:237)
at org.jboss.aop.deployers.AbstractAspectManager.create(AbstractAspectMa
nager.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(Reflec
tionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(
ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethod
JoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$Joi
npointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(Executio
nWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
patchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInte
rnal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction
(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction
(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.sim
pleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.ins
tall(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install
(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
ctControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
ctController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
actController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
oller.java:540)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean
(AbstractKernelDeployer.java:319)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean
s(AbstractKernelDeployer.java:297)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(Abs
tractKernelDeployer.java:130)
at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicK
ernelDeployer.java:76)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa
sicXMLDeployer.java:91)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBa
sicXMLDeployer.java:161)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
:138)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
450)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
11:42:11,350 INFO [ServerInfo] Java version: 1.6.0_34,Sun Microsystems Inc.
11:42:11,350 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (b
uild 1.6.0_34-b04)
11:42:11,351 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.9-
b04,Sun Microsystems Inc.
11:42:11,352 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
11:42:11,353 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128M -X
mx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dg
c.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.di
rs=C:\Program Files\JBOSS\jboss-5.1.0.GA\lib\endorsed
11:42:11,384 INFO [JMXKernel] Legacy JMX core initialized
Failed to boot JBoss:
java.lang.IllegalStateException: Incompletely deployed:
DEPLOYMENTS IN ERROR:
Deployment "AspectManager" is in error due to: java.io.FileNotFoundException:
Failed to create tmpClassesDir: C:\Program Files\JBOSS\jboss-5.1.0.GA\server\def
ault\tmp\aopdynclasses
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "JMXStartStopAdvice$AspectBinding" is missing the following depende
ncies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "BeansDeploymentAopMetaDataDeployer" is missing the following depen
dencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", bu
t is actually in state "**ERROR**")
Deployment "AOPDeploymentAopMetaDataDeployer" is missing the following depende
ncies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", bu
t is actually in state "**ERROR**")
Deployment "AOPClassLoaderDeployer" is missing the following dependencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "JMXRegistrationAdvice$AspectBinding" is missing the following depe
ndencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "AspectManagerJMXRegistrar" is missing the following dependencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
Deployment "JMXCreateDestroyAdvice$AspectBinding" is missing the following dep
endencies:
Dependency "AspectManager" (should be in state "Installed", but is actually
in state "**ERROR**")
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalVa
lidate(AbstractKernelDeployer.java:278)
at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(A
bstractKernelDeployer.java:174)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java
:142)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:
450)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:662)
11:42:13,576 INFO [ServerImpl] Runtime shutdown hook called, forceHalt: true
11:42:13,582 INFO [ServerImpl] Shutdown complete
Shutdown complete
Halting VM
Press any key to continue . . .
Looks like a bug that occurs with certain specific combinations of JRE and OS versions (see https://jira.jboss.org/jira/browse/JBAS-6981). Basically, the JBoss config is relying on reflection to return constructors in a certain order, and in some cases this order is different, causing the exception. Did you change your JRE version when you reinstalled, say from 1.6.0_17 to _18?
Anyway, the workaround is described in the JIRA issue, and also here. You need to change the content of conf/bootstrap/profile.xml. Look for the definition of the AttachmentStore, and change the constructor line so that it starts:
The original version doesn't have the class="java.io.File" attribute.
Pretty sloppy of the JBoss folks, but there you go.
Hope it helps.
(copied from Error starting jboss server)
Related
I am not able to run nifi in window server 2016 even though I change to java 8
java version "1.8.0_202"
Java(TM) SE Runtime Environment (build 1.8.0_202-b08)
Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)
C:\Users\HelloWorld\Desktop\nifi-1.16.1-bin\nifi-1.16.1\bin>run-nifi.bat
2022-05-11 23:20:58,804 INFO [main] org.apache.nifi.bootstrap.Command Starting Apache NiFi...
2022-05-11 23:20:58,804 INFO [main] org.apache.nifi.bootstrap.Command Working Directory: C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1
2022-05-11 23:20:58,804 INFO [main] org.apache.nifi.bootstrap.Command Command: C:\Program Files\Java\jdk1.8.0_202\bin\java.exe -classpath C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\conf;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\logback-classic-1.2.11.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\logback-core-1.2.11.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-api-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-nar-utils-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-properties-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-property-utils-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-runtime-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-stateless-api-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\nifi-stateless-bootstrap-1.16.1.jar;C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\lib\slf4j-api-1.7.36.jar -Dorg.apache.jasper.compiler.disablejsr199=true -Xmx512m -Xms512m -Dcurator-log-only-first-connection-issue-as-error-level=true -Djavax.security.auth.useSubjectCredsOnly=true -Djava.security.egd=file:/dev/urandom -Dzookeeper.admin.enableServer=false -Dsun.net.http.allowRestrictedHeaders=true -Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -Djava.protocol.handler.pkgs=sun.net.www.protocol -Dnifi.properties.file.path=C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\.\conf\nifi.properties -Dnifi.bootstrap.listen.port=54233 -Dapp=NiFi -Dorg.apache.nifi.bootstrap.config.log.dir=C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\bin\..\\logs org.apache.nifi.NiFi
2022-05-11 23:20:59,078 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read pid file C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\bin\..\run\nifi.pid; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2022-05-11 23:20:59,078 WARN [main] org.apache.nifi.bootstrap.Command Failed to set permissions so that only the owner can read status file C:\Users\HelloWorld\Desktop\NIFI-1~1.1-B\NIFI-1~1.1\bin\..\run\nifi.status; this may allows others to have access to the key needed to communicate with NiFi. Permissions should be changed so that only the owner can read this file
2022-05-11 23:20:59,078 INFO [main] org.apache.nifi.bootstrap.Command Launched Apache NiFi with Process ID 964
I am going to install NetFlow.
Here is a document for it.
My logstash.yml setting is following.
modules:
- name: netflow
var.input.udp.port: 9996
I've run this command.
/usr/share/logstash/bin/logstash --modules netflow -M netflow.var.input.udp.port=9996
I've got following error.
JDK: /usr/share/logstash/jdk
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
WARNING: Could not find logstash.yml which is typically located in $LS_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults
Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console
[INFO ] 2022-02-15 23:44:29.148 [main] runner - Starting Logstash {"logstash.version"=>"7.17.0", "jruby.version"=>"jruby 9.2.20.1 (2.5.8) 2021-11-30 2a2962fbd1 OpenJDK 64-Bit Server VM 11.0.13+8 on 11.0.13+8 +indy +jit [linux-x86_64]"}
[INFO ] 2022-02-15 23:44:29.163 [main] runner - JVM bootstrap flags: [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djruby.compile.invokedynamic=true, -Djruby.jit.threshold=0, -Djruby.regexp.interruptible=true, -XX:+HeapDumpOnOutOfMemoryError, -Djava.security.egd=file:/dev/urandom, -Dlog4j2.isThreadContextMapInheritable=true]
Your settings are invalid. Reason: Path "/usr/share/logstash/data" must be a writable directory. It is not writable.
[FATAL] 2022-02-15 23:44:29.208 [main] Logstash - Logstash stopped processing because of an error: (SystemExit) exit
org.jruby.exceptions.SystemExit: (SystemExit) exit
at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:747) ~[jruby-complete-9.2.20.1.jar:?]
at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:710) ~[jruby-complete-9.2.20.1.jar:?]
at usr.share.logstash.lib.bootstrap.environment.<main>(/usr/share/logstash/lib/bootstrap/environment.rb:94) ~[?:?]
Is there a solution for it?
The error message states the following:
Your settings are invalid. Reason: Path "/usr/share/logstash/data" must be a writable directory. It is not writable.
So you simply need to make the /usr/share/logstash/data folder writable by the logstash user.
If I just run the StartSonar.bat everything works and starts fine.
If I setup a service to run using NSSM using:
Path: ..\blah\wrapper.exe
Startup directory: ..\blah
Arguments: -c ..\blah\conf\wrapper.conf
I get an error in the logs that says:
2019.06.24 16:03:49 INFO web[][o.s.p.ProcessEntryPoint] Starting web
2019.06.24 16:03:50 INFO web[][o.a.t.u.n.NioSelectorPool] Using a shared selector for servlet write/read
2019.06.24 16:03:51 INFO web[][o.e.p.PluginsService] no modules loaded
2019.06.24 16:03:51 INFO web[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.join.ParentJoinPlugin]
2019.06.24 16:03:51 INFO web[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.percolator.PercolatorPlugin]
2019.06.24 16:03:51 INFO web[][o.e.p.PluginsService] loaded plugin [org.elasticsearch.transport.Netty4Plugin]
2019.06.24 16:03:52 INFO web[][o.s.s.e.EsClientProvider] Connected to local Elasticsearch: [127.0.0.1:9001]
2019.06.24 16:03:52 INFO web[][o.s.s.p.LogServerVersion] SonarQube Server / 7.7.0.23042 / 1dcac8b8de36b377a1810cc8f1c4c31744e12729
2019.06.24 16:03:52 INFO web[][o.sonar.db.Database] Create JDBC data source for jdbc:sqlserver://BRKPRCSQUBE1;databaseName=sonar;integratedSecurity=true
2019.06.24 16:03:53 ERROR web[][o.s.s.p.Platform] Web server startup failed
java.lang.IllegalStateException: Can not connect to database. Please check
connectivity and settings (see the properties prefixed by 'sonar.jdbc.').
That leads me to believe there is a problem with setting up the database correctly, but once again.. if I run the StartSonar.bat everything works fine.
The only thing I can think of is that I am setting up the service as a "Local System account," instead of when I run the bat it would be from my own account.
That being said, I cannot use my account and then login and change my password or something every time my AD changes.
I'm trying to setup Teamcity on an EC2 Ubuntu instance.
I've:
Downloaded the package through wget http://download.jetbrains.com/teamcity/TeamCity-9.0.4.tar.gz. Unpackaged it.
Unpackaged it: tar -xvzf TeamCity-9.0.4.tar.gz.
sh Teamcity/bin/teamcity-server.sh start.
I can't access the web-app, and when I check the logs, says:
INFO - jetbrains.buildServer.STARTUP - Server shutdown has been requested
WARN - jetbrains.buildServer.STARTUP - Could not determine the local IP address: ip-172-30-1-83: ip-172-30-1-83: unknown error
INFO - jetbrains.buildServer.STARTUP - Server IP address: -unknown-
INFO - jetbrains.buildServer.STARTUP - Server shutdown complete
Complete log:
INFO - jetbrains.buildServer.STARTUP - Starting TeamCity server
INFO - jetbrains.buildServer.STARTUP - Server shutdown has been requested
INFO - jetbrains.buildServer.STARTUP - TeamCity version: 9.0.4 (build 32407), data format version 709
INFO - jetbrains.buildServer.STARTUP - OS: Linux, User: ubuntu, JRE: 1.8.0_45-b14 Java HotSpot(TM) 64-Bit Server VM
INFO - jetbrains.buildServer.STARTUP - JVM parameters: -Djava.util.logging.config.file=/home/ubuntu/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/home/ubuntu/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djsse.enableSNIExtension=false -Djava.awt.headless=true -Djava.endorsed.dirs=/home/ubuntu/TeamCity/endorsed -Dcatalina.base=/home/ubuntu/TeamCity -Dcatalina.home=/home/ubuntu/TeamCity -Djava.io.tmpdir=/home/ubuntu/TeamCity/temp
INFO - jetbrains.buildServer.STARTUP - Garbage collection: Copy, MarkSweepCompact
WARN - jetbrains.buildServer.STARTUP - Could not determine the local IP address: ip-172-30-1-83: ip-172-30-1-83: unknown error
INFO - jetbrains.buildServer.STARTUP - Web server version: Apache Tomcat/7.0.59
INFO - jetbrains.buildServer.STARTUP - Server IP address: -unknown-
INFO - jetbrains.buildServer.STARTUP - Servlet real path: /home/ubuntu/TeamCity/webapps/ROOT/
INFO - jetbrains.buildServer.STARTUP - Current stage: TeamCity server is shutting down
INFO - jetbrains.buildServer.STARTUP - Stopping the main application
INFO - jetbrains.buildServer.STARTUP - The main servlet is not initialized, nothing to shut down.
INFO - jetbrains.buildServer.STARTUP - Server shutdown complete
Any hints on how to solve it?
I have Teamcity's web-app working on my local machine (also Ubuntu, and the same Teamcity package).
Read the shell script TeamCity/bin/teamcity-server.sh, it is written with limitation, the script can't run out of the application folder.
export CATALINA_OPTS
CATALINA_HOME=./..
CATALINA_BASE=./..
So you should cd to the bin folder and run :
cd Teamcity/bin
sh teamcity-server.sh start
Let me know if it fixs your issue or not.
I wanted to deploy a simple jsp application: I created and copied the myApp.war file to the $JBOSS_HOME/standalone/deployment folder.
Instead of deploying the war file , JBoss created *.war.failed ,
So I thought maybe it's a good idea to restart the jboss to see if it affects the deployment.
In some forums it was suggested to restart the JBoss through : $JBOSS_HOME/bin/jboss-cli.sh
But there was no shutdown or restart command.
While I was trying to restart , I ran the following command :
/usr/local/jboss7/bin/jboss-cli.sh -c ":shutdown(restart=true)"
JBoss stopped working , but it didn't start again.
Now , I want to start it again by :
$JBOSS_HOME/bin/standalone.sh
But it gives me the following exception :
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /usr/local/jboss7
JAVA: /Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
17:29:43,399 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:29:43,536 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:29:43,567 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
17:29:43,876 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '*' (code 42) (expected a name start character)
at [row,col {unknown-source}]: [190,160]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639)
at com.ctc.wstx.sr.StreamScanner.parseLocalName(StreamScanner.java:1798)
at com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:2975)
at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2926)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2802)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1050)
at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1125)
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.nextTag(XMLExtendedStreamReaderImpl.java:152) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.as.server.deployment.scanner.DeploymentScannerParser_1_1.readElement(DeploymentScannerParser_1_1.java:85)
at org.jboss.as.server.deployment.scanner.DeploymentScannerParser_1_1.readElement(DeploymentScannerParser_1_1.java:28)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:894) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:330) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
... 3 more
17:29:43,882 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:29:43,889 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final "Brontes" stopped in 4ms
I searched for the cause of the problem , and I found that probably there's a problem with standalone.xml file.
In /usr/local/jboss7/standalone/configuration/standalone_xml_history I have the following files , but not the standalone.xml
2014xxxx-xxxxxxxx
snapshot
standalone.initial.xml
current
standalone.boot.xml
standalone.last.xml
I'd like to know if I have to rename any of these files to standalone.xml ? (actually I tried renaming standalone.boot.xml to standalone.xml but it didn't work either !) or download a new one ? may I remove these xml files after having the new standalone.xml ?
If JBoss-7 is installed in $JBOSSHOME, the default standalone configuration file is $JBOSS_HOME/standalone/configuration/standalone.xml; $JBOSSHOME/standalone/configuration is the default value of the jboss.server.config.dir property; and running $JBOSSHOME/bin/standalone.sh with no options will start JBoss in standalone mode on Linux/Unix systems.
In order to use a different standalone configuration file it can be renamed to standalone.xml, put in jboss.server.config.dir if it is not already there and standalone.sh run with no options; or its file name can be given to standalone.sh as an argument to its -c option after it is put in jboss.server.config.dir, for example:
$JBoss_home/bin/standalone.sh -c standalone-full.xml
RedHat documentation for this is at https://docs.jboss.org/author/display/AS71/Command+line+parameters
I have had the best success with standalone/configuration/standalone-full.xml since it has the full configuration. It is shipped with JBoss-7. If you don't have it you could download a fresh copy of the distro to get it. What I always do is archive a zip of the distro for recovery in case something gets corrupted or lost in the working copy.