Createjavavm failed with error 6



Upgrading Jira

we want to upgrade our Jira Core, Jira Software and Jira Service Management.

Our current Version:

Jira Software: 7.10.1

Jira Service Desk: 3.13.1

We want the latest versions of these applications.

We are using Jira Server, is there a documentation that you guys would recommend? I didnt install Jira, I am trying to manage it, so I dont know if i will breake something.

Any help would be appreciated.

2 answers

The short answer though is

  • You can use the installer to do the upgrade in place — the best one for you to use would be Jira Software (that will upgrade Core and Software)
  • Then you can upgrade JSM from Admin -> Manage applications
  • Then upgrade all the apps that are showing «upgrade available» in Admin -> manage apps.

The one most important thing I recommend though is test test test. Set up a copy of your production system (in an isolated place, so it doesn’t try to talk to production systems) and test the upgrade process

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

So, i have downloaded 8.22.2 Jira Software Installer,

I dont need to upgrade Jira core if I directly upgrade Jira Software to 8.22.2?

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Ok, Jira Software is not a standalone application. The installer is Jira Core + Software bundled together. Same as Jira Service Management — Core + JSM bundled. Atlassian don’t do a bundle of all three together.

The Jira Core installer will only upgrade Core, and you’d have to manually upgrade the other two after using it. I’ve recommended using the Jira Software installer because it will upgrade Core + Software in one go.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Ok got it,
I will use Intaller to Install 8.22.2 up upgrade Jira Core and Jira Software

then I will upgrade JSM and other plugins.

We are also moving Application data from C to D. is it better to move the directory before upgrading?

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

I’d tend towards moving before — it’ll be one less step to do while migrating.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

i cant find Jira Update Check, I want to check my Apps before I upgrade Jira.

You know where I can find it?

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

I’m not sure it goes back as far as 7.10

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

so i upgraded JIRA SOFTWARE and now we cant start the service.

in Commons-daemon we have following errors.

[2022-05-20 17:06:41] [error] [ 7772] The name is already in use as either a service name or a service display name.
[2022-05-20 17:06:41] [error] [ 7772] Apache Commons Daemon procrun failed with exit value: 8 (failed to install service).
[2022-05-20 17:06:42] [error] [ 7772] The name is already in use as either a service name or a service display name.
[2022-05-20 17:24:34] [info] [ 9720] Apache Commons Daemon procrun (1.3.0.0 64-bit) started.
[2022-05-20 17:24:34] [info] [ 9720] Running Service ‘JIRASoftware091118084820’.
[2022-05-20 17:24:34] [info] [ 9696] Starting service.
[2022-05-20 17:24:34] [error] [ 9640] CreateJavaVM Failed with error [-6]
[2022-05-20 17:24:34] [error] [ 9640] The system cannot find the file specified.
[2022-05-20 17:24:34] [error] [ 9696] Failed to start Java
[2022-05-20 17:24:34] [error] [ 9696] ServiceStart returned 4.
[2022-05-20 17:24:34] [info] [ 9720] Run service finished.
[2022-05-20 17:24:34] [info] [ 9720] Apache Commons Daemon procrun finished.
[2022-05-20 17:29:22] [info] [ 7012] Apache Commons Daemon procrun (1.3.0.0 64-bit) started.
[2022-05-20 17:29:22] [info] [ 7012] Running Service ‘JIRASoftware091118084820’.
[2022-05-20 17:29:22] [info] [ 3744] Starting service.
[2022-05-20 17:29:22] [error] [13860] CreateJavaVM Failed with error [-6]
[2022-05-20 17:29:22] [error] [13860] The system cannot find the file specified.
[2022-05-20 17:29:22] [error] [ 3744] Failed to start Java
[2022-05-20 17:29:22] [error] [ 3744] ServiceStart returned 4.
[2022-05-20 17:29:22] [info] [ 7012] Run service finished.
[2022-05-20 17:29:22] [info] [ 7012] Apache Commons Daemon procrun finished.
[2022-05-20 17:33:26] [info] [ 4752] Apache Commons Daemon procrun (1.3.0.0 64-bit) started.
[2022-05-20 17:33:26] [info] [ 4752] Running Service ‘JIRASoftware091118084820’.
[2022-05-20 17:33:26] [info] [10992] Starting service.
[2022-05-20 17:33:26] [error] [ 9556] CreateJavaVM Failed with error [-6]
[2022-05-20 17:33:26] [error] [ 9556] The system cannot find the file specified.
[2022-05-20 17:33:26] [error] [10992] Failed to start Java
[2022-05-20 17:33:26] [error] [10992] ServiceStart returned 4.
[2022-05-20 17:33:26] [info] [ 4752] Run service finished.
[2022-05-20 17:33:26] [info] [ 4752] Apache Commons Daemon procrun finished.

I need help quickly, no can one work.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Hope this helps,

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Источник

Tomcat 7 получение CreateJavaVM ошибка

у меня есть сервер Apache tomcat 7.0.5 на сервере Windows R2, и я развернул на нем webApp ( java JSF), все работало нормально, но он внезапно остановился и не будет работать снова. когда я пытаюсь запустить его, он говорит мне: «ошибка 1067: процесс был неожиданно завершен» и в журналах я получаю эти файлы:

поскольку у меня была ошибка памяти «perm gen», я добавил некоторые вещи в свои свойства Apache Tomcat, следуя этой ссылке как обращаться с Пермским генератором

поэтому мои параметры Java выглядят следующим образом:

есть идеи, почему сервер больше не запускается? Спасибо!

4 ответов

после нескольких часов, пытаясь понять это, я, наконец, нашел его. У меня было дополнительное пространство в конце команды VM.

который давал мне непризнанный вариант VM.

Спасибо за чтение, надеюсь, когда вы получаете эту ошибку, вы можете принять дополнительные меры предосторожности для проверки синтаксиса.

для управления памятью вам нужно установить некоторые параметры Xms и Xmx

  • Xms управляет начальным размером кучи
  • Xmx управляет максимальным размером кучи

таким образом, попробуйте добавить:

ошибка находится на опции «HeapDumpOnOutOfMemoryError», которая даже не указана в вашем сообщении. Можете ли вы опубликовать экранную печать вкладки «Java» с экрана сервиса «tomcat» (аналогично ссылке, которую вы предоставили) ? Это расскажет нам фактические параметры, которые вы используете, а также память, которую вы установили.

скопировать файл msvcr71.dll из bin dir вашей установки java в bin dir установки tomcat.

Источник

After upgrading confluence from 7.0 to 7.4 Service fails to start

Recently we have upgraded confluence from 7.0 to 7.4, After the upgrade we are getting below error in confluence while starting the service. if someone can help providing guidance on this.

7.0 was working fine, problem started only after 7.4

[2020-06-10 04:21:15] [info] [ 3136] Starting service.
[2020-06-10 04:21:15] [error] [ 3268] CreateJavaVM Failed with error [-6]
[2020-06-10 04:21:15] [error] [ 3268] The system could not find the environment option that was entered.
[2020-06-10 04:21:15] [error] [ 3136] Failed to start Java
[2020-06-10 04:21:15] [error] [ 3136] ServiceStart returned 4.
[2020-06-10 04:21:15] [info] [ 2644] Run service finished.
[2020-06-10 04:21:15] [info] [ 2644] Apache Commons Daemon procrun finished.

1 answer

1 accepted

This is not strictly a Confluence error.

My best guess is that your server is now using a version of Java that does not accept parameters that Confluence is trying to start with.

Three simple commands to check this (I’ve assumed a Unix like system)

  • grep -H E «JAVA|JVM» /bin/*
  • java -version
  • which java

The first one means «find what JAVA and JVM settings you are starting Confluence with», which should tell us what Java Confluence is trying to run. The second one should tell us what the system default java is, and the third which actual java executable the system is going for.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Thank you Nic_Brough_Adaptavist_ for your feedback

We are currently using it on Windows machine here are the information retrieved based on commands.

java version «1.8.0_144»
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

Источник

Jira wont start after upgrade

I upgraded our dev instance of Jira Server from 8.8.0 to 8.19.0. I didn’t receive any errors during the upgrade. The service will not start, not from the bat files or from the pre-existing service. The event viewer says «The Atlassian Jira service terminated with the following service-specific error: The system cannot open the file.» But it doesn’t specify the file. We are running on a Windows server with a MS SQL Server database.

1 answer

1 accepted

Does the application or server logs have errors showing an attempt to start that then fails?

Check /logs/atlassian-jira.log and then /logs/catalina.out

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

The last entry in atlassian-jira.log is

2021-09-20 09:39:40,595-0400 localhost-startStop-2 INFO [c.a.jira.startup.DefaultJiraLauncher] JIRA launchers stopped in 27706ms

The only entry in catalina.log is

20-Sep-2021 10:55:28.582 SEVERE [main] org.apache.catalina.startup.Catalina.stopServer Could not contact [localhost:8006]. Tomcat may not be running.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

although it is not related to JIRA but it is same error for same environment.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Ok, forget catalina.out then, read back up through atlassian-jira.log to see what caused it to shut down.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

The last few entries seem like they are for the shutdown associated with the upgrade. The logs don’t have any entries after the upgrade. When I try to restart the Windows service, there is only an error in the Event Viewer. No new entries are added to the atlassian-jira.log file.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Unfortunately the solution in the article didn’t work.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Ok, if there’s nothing being written to the logs, then the process isn’t getting that far.

I’m afraid you’ll need to debug the service settings — work out exactly what the service is running when it tries to start, and actually try the commands on the command line. I would expect the call to spit out a large pile of errors before it stops (and returns a fail code back to the service handler)

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Forgive the basic question, but how do I do that? The documentation says I can’t start Jira manually if I have it installed as a service.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

I’m having the same issue when upgrading to 8.19.1.

The Atlassian JIRA service terminated with the following service-specific error:
The system cannot open the file.

[2021-09-21 08:36:07] [info] [ 4688] Apache Commons Daemon procrun (1.2.4.0 64-bit) started.
[2021-09-21 08:36:08] [info] [ 4688] Running Service ‘JIRASoftware150318103047’.
[2021-09-21 08:36:08] [info] [ 3668] Starting service.
[2021-09-21 08:36:08] [error] [ 4064] CreateJavaVM Failed with error [-6]
[2021-09-21 08:36:08] [error] [ 4064] The system cannot find the file specified.
[2021-09-21 08:36:08] [error] [ 3668] Failed to start Java
[2021-09-21 08:36:08] [error] [ 3668] ServiceStart returned 4.
[2021-09-21 08:36:08] [info] [ 4688] Run service finished.
[2021-09-21 08:36:08] [info] [ 4688] Apache Commons Daemon procrun finished.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Are new entries added to the atlassian-jira.log after the upgrade?

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

There were not for my upgrade.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

There’s not a lot more we can do without debugging what the service is actually trying to run.

«The system cannot open the file» might be referring to a batch file (script), part of the install, temporary/cache/log files, or even the Java install that is being used to run the service.

The «create java vm failed» suggests it is the java in use, rather than the install, but we can’t be sure from just that one message.

The docs don’t quite say «you can’t start Jira manually if you have it as a service», they say «it’s not the way you want to run it»

I would want to know what, exactly, the service is configured to try to run (at a guess, it will say /bin/start-jira.bat or something similar), and try running that on a command line to see what errors jump out of that. I’d expect the «cannot find file» to be replicated, maybe not with the same wording, but with a lot more detail.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

I was finally able to get the upgrade to work by first stopping the Jira service and performing the steps in this article to change the display name of the service:

I then ran the upgrade and the service installed and started.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Here is the output from running the start.bat

Using CATALINA_BASE: «E:\Program Files\Atlassian\JIRA2»
Using CATALINA_HOME: «E:\Program Files\Atlassian\JIRA2»
Using CATALINA_TMPDIR: «E:\Program Files\Atlassian\JIRA2\temp»
Using JRE_HOME: «E:\Program Files\Atlassian\JIRA2\jre\»
Using CLASSPATH: «E:\Program Files\Atlassian\JIRA2\bin\bootstrap.jar;E:\Program Files\Atlassian\JIRA2\bin\tomcat-juli.jar»
Using CATALINA_OPTS: «»
NOTE: Picked up JDK_JAVA_OPTIONS: —add-opens=java.base/java.lang=ALL-UNNAMED —add-opens=java.base/java.io=ALL-UNNAMED —add-opens=java.base/java.util=ALL-UNNAMED —add-opens=java.base/java.util.concurrent=ALL-UNNAMED —add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
[0.013s][error][logging] Missing terminating quote in -Xlog option ‘file=»E:\Program’
Invalid -Xlog option ‘-Xlog:gc*:file=»E:\Program’, see error log for details.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.

Источник

Читайте также:  Email server certificate error
Оцените статью
toolgir.ru
Adblock
detector