I'm trying to create and start the service instance. But it doesn't start.
Here is the command I ran:
virtuoso-t +service start +instance MyService
Here my output:
The Virtuoso_MyService service is being started
But the localhost:8890 cannot be loaded.
Details:
Opened CMD as administrator.
Ran the same commands 3 days back and the services were running fine till I restarted the system.
Commands followed.
C:\Users\username\Desktop\foldername\MyWork\virtuoso-opensource\bin>virtuoso-t +service create +instance MyService +configfile ..\database\virtuoso.ini
[Using virtuoso.ini in C:\Users\username\Desktop\foldername\MyWork\virtuoso-opensource\database]
The Virtuoso_MyService service has been registered
and is associated with the executable
C:\Users\username\Desktop\foldername\MyWork\virtuoso-opensource\bin\virtuoso-t.exe
C:\Users\username\Desktop\foldername\MyWork\virtuoso-opensource\bin>virtuoso-t +service start +instance MyService
The Virtuoso_MyService service is being started
C:\Users\username\Desktop\foldername\MyWork\virtuoso-opensource\bin>virtuoso-t +service list +instance MyService
MyService Stopped
As suggested by #TallTed, I have added the log:
Wed Mar 01 2017
16:27:37 { Loading plugin 1: Type `plain', file `wikiv' in `../hosting'
16:27:37 WikiV version 0.6 from OpenLink Software
16:27:37 Support functions for WikiV collaboration tool
16:27:37 SUCCESS plugin 1: loaded from ..\hosting\wikiv.dll }
16:27:37 { Loading plugin 2: Type `plain', file `mediawiki' in `../hosting'
16:27:37 MediaWiki version 0.1 from OpenLink Software
16:27:37 Support functions for MediaWiki collaboration tool
16:27:37 SUCCESS plugin 2: loaded from ..\hosting\mediawiki.dll }
16:27:37 { Loading plugin 3: Type `plain', file `creolewiki' in `../hosting'
16:27:37 CreoleWiki version 0.1 from OpenLink Software
16:27:37 Support functions for CreoleWiki collaboration tool
16:27:37 SUCCESS plugin 3: loaded from ..\hosting\creolewiki.dll }
16:27:37 { Loading plugin 4: Type `plain', file `im' in `../hosting'
16:27:37 IM version 0.6 from OpenLink Software
16:27:37 Support functions for Image Magick 6.6.7
16:27:37 SUCCESS plugin 4: loaded from ..\hosting\im.dll }
16:27:37 { Loading plugin 5: Type `plain', file `wbxml2' in `../hosting'
16:27:37 WBXML2 version 0.9 from OpenLink Software
16:27:37 Support functions for WBXML2 0.10.7 Library
16:27:37 SUCCESS plugin 5: loaded from ..\hosting\wbxml2.dll }
16:27:37 Unable to create file virtuoso.lck (File exists).
16:27:37 This probably means you either do not have permission to start
16:27:37 this server, or that virtuoso-t is already running.
16:27:37 If you are absolutely sure that this is not the case, please try
16:27:37 to remove the file virtuoso.lck and start again.
The answer is in the Virtuoso log file --
16:27:37 Unable to create file virtuoso.lck (File exists).
16:27:37 This probably means you either do not have permission to start
16:27:37 this server, or that virtuoso-t is already running.
16:27:37 If you are absolutely sure that this is not the case, please try
16:27:37 to remove the file virtuoso.lck and start again.
Removing the virtuoso.lck as advised there should resolve the issue.
In a normal shutdown, Virtuoso will clean up this file. If power is cycled, or the Virtuoso process is otherwise uncleanly terminated, this file may linger, as in this case, and so need to be manually removed.
The Virtuoso website has a vast amount of information, including the official Virtuoso manual and the evolving docs, covering Open Source in more detail.
ObDisclaimer: OpenLink Software produces Virtuoso, and employs me.
I was having the same issues on windows 10. I fixed by going to my
C:\Program Files\OpenLink Software\Virtuoso OpenSource 7.2\database
and manually delete virtuoso.lck file
The restart my server and everything now started working fine!
Related
I have build a very simple project of hello world in
Payara 5 (5.181)
JSF 2.3
JDK 1.8
CDI 2.0
Maven
and encountered a problem
Unable to start server due following issues: Launch process failed with exit code 1
in console it throws an error of :
Error: Could not find or load main class server\payara5\glassfish.lib.grizzly-npn-bootstrap.jar
[PIC] Payara 5 Error
It seems that the Payara Tools for Eclipse suffer by several bugs that may cause this. In my case, the following workarounds helped:
The Payara installation path should not contain spaces (e.g. Program Files\Payara)
It seems that only Java 8 is supported at the time
Open the domain.xml configuration file for the domain you are trying to start (typically payara_install_path/glassfish/domains/domain1/config/domain1.xml) and search for "Xbootclasspath". You should find a couple of lines like
<jvm-options>[1.8.0|1.8.0u120]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.6.jar</jvm-options>
<jvm-options>[1.8.0u121|1.8.0u160]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.7.jar</jvm-options>
<jvm-options>[1.8.0u161|1.8.0u190]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.8.jar</jvm-options>
<jvm-options>[1.8.0u191|1.8.0u500]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.8.1.jar</jvm-options>
Depending of your installed Java version (try running java --version) and choose the appropriate line (most likely the last one). Remove the remaining lines and remove the [...] part at the beginning of the chosen line so you will get something like
<jvm-options>-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.8.1.jar</jvm-options>
After this, the tools seem to start normally.
The Problem is with Java version. The grizzly-npn-bootstrap-1.8.1.jar Jar is placed in bootclasspath, thats why it requires proper java version to start payara server. So remove unnecessary bootstrap jar from domain.xml.
In Windows:
1) Go To ---C:\Users\xxxx\payara5\glassfish\domains\domain1\config\domain.xml
2) According to my java verson(java version "1.8.0_191") I deleted the following lines from domain.xml. So delete according to your java version.
<jvm-options>[1.8.0|1.8.0u120]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.6.jar</jvm-options>
<jvm-options>[1.8.0u121|1.8.0u160]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.7.jar</jvm-options>
<jvm-options>[1.8.0u161|1.8.0u190]-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.8.jar</jvm-options>
3) Remove this [1.8.0u191|1.8.0u500] part from jvm-options & Edit the line in your domain.xml(w.r.t java -version) as shown below
<jvm-options>-Xbootclasspath/p:${com.sun.aas.installRoot}/lib/grizzly-npn-bootstrap-1.8.1.jar</jvm-options>
4) restart your server.
As Radkovo said, "The Payara installation path should not contain spaces (e.g. Program Files\Payara)", so I moved the Payara to the Documents folder.
Problem solved!
I am using open-source Pentaho distribution from github.com (version 6.1-SNAPSHOT).
In Spoon there are some step missing (e.g. There is no Mongodb input/output step listed) and I cant add dataservice to step (There are no errors, this option just isn't on the list).
I have reinstalled everything (removed .kettle and .pentaho directories as well as whole source and distribution) but it didn't help.
This is what I get at spoon startup:
16:05:50,304 INFO [KarafInstance]
* Karaf Instance Number: 1 at ~/pentaho-kettle/d
ist/./system/karaf//data1
Karaf Port:8801
OSGI Service Port:9050 *
Dec 23, 2015 4:05:51 PM org.apache.karaf.main.Main$KarafLockCallback
lockAquired
INFO: Lock acquired. Setting startlevel to 100
2015/12/23 16:05:53 - cfgbuilder - Warning: The configuration
parameter [org] is not supported by the default configuration builder
for scheme: sftp
Dec 23, 2015 4:05:58 PM
org.pentaho.caching.impl.PentahoCacheManagerFactory$RegistrationHandler$1
onSuccess INFO: New Caching Service registered
16:06:04,009 ERROR [KarafLifecycleListener] The Kettle Karaf Lifycycle
Listener failed to execute properly. Releasing lifecycle hold, but
some services may be unavailable.
I suspect that
ERROR [KarafLifecycleListener] The Kettle Karaf Lifycycle Listener
failed to execute properly. Releasing lifecycle hold, but some
services may be unavailable.
has something to do with it as missing plugins reside somewhere under karaf/ directory.
It was working just fine week ago.
I am using Ubuntu 15.04.
I will be grateful for any hints.
Greetings.
you are using a non stable release. this is the place where you can download the latest stable release http://sourceforge.net/projects/pentaho/
Agreed with jipipayo, For Pentaho CE version, download it from http://community.pentaho.com/ official instead of github. It is highly possible that the codes in github might be in unstable condition.
Also in case you have a missing plugin, try using the Pentaho Marketplace and download the required plugins.
Hope this helps :)
I have installed PostgreSQL 9.4 (x86), PG Admin 1.20 and Slony-I 2.2.3 through Stack Builder on a windows platform.
When trying to create a new Slony cluster in pgAdmin, I get the
"Slony-I creation scripts not available" error message.
1) I have setup options Slony-I path to
-->:C:\Program Files (x86)\PostgreSQL\9.4\share
where all the slony1_*.sql scripts are located but I still get the same error.
2) Using procmon I see that PGAdmin tries to access "slony1_funcs.sql" and "slony1_funcs.2.2.0.sql" none of which exist in my \share directory
the installed funcs scripts are "slony1_funcs.2.2.3.sql", "slony1_funcs.v83.2.2.3.sql", slony1_funcs.v84.2.2.3.sql
and the base scripts are "slony1_base.2.2.3.sql", "slony1_base.v83.2.2.3.sql", slony1_base.v84.2.2.3.sql
3) I have tried to rename "slony1_funcs.2.2.3.sql" to "slony1_funcs.2.2.0.sql" and "slony1_funcs.sql" and I now get a new error "Couldn't test for the Slony version. Assuming 1.2.0" and again the
"Slony-I creation scripts not available" error message
Does anyone have an idea how to get this working?
I’m having an issue with ftp.SyncLocalDir when I have an open file on the local directory.
I’m using the example from http://www.example-code.com/vbnet/ftp_syncLocalTree.asp with a few minor changes. It has been working fine for a few days and then has stopped working.
I’ve found that one of the files is open on the local directory. Looking through the http://chilkatforum.com/ forum I see that one of the answers stated that
“Chilkat will detect errors that are likely permission/access errors and will continue with the remainder of the download.”
This is not happening for me. Looking at the last error text it states that the file is used by another process. Not other files get synchronized.
Is the something else I need to add to the code to force it to continue after the error?
Below is the last error text.
Thanks,
Steve
ChilkatLog:
SyncLocalDir:
DllDate: Dec 5 2014
ChilkatVersion: 9.5.0.46
UnlockPrefix: *********
Username: *********
Architecture: Little Endian; 32-bit
Language: .NET 4.0
VerboseLogging: 0
commandCharset: ansi
dirListingCharset: ansi
localDirPath: Q:\TEST
mode: 2
ProgressMonitoring:
enabled: yes
heartbeatMs: 0
sendBufferSize: 65536
--ProgressMonitoring
downloadDir:
getFile2:
localFilename: Q:\TEST/LINE_6 _13.csv
Replacing existing local file
openForReadWriteWin32:
Failed to open file (2)
localFilePath: Q:\TEST\LINE_6 _13.csv
currentWorkingDirectory: H:\Code In Progress\LLS\Gen 3 Test And Crimp
w-network\VB Code\trunk\FTP Syncronize\bin\Debug
osErrorInfo: The process cannot access the file because it is being us
ed by another process.
localWindowsFilePath: Q:\TEST\Line 6\LINE_6 _13.csv
--openForReadWriteWin32
--getFile2
Failed to download file
failedFilename: /LINE_6 _13.csv
--downloadDir
Failed.
--SyncLocalDir
--ChilkatLog
Please try this new build for the .NET 4.0 Framework:
32-bit Download: http://www.chilkatsoft.com/download/preRelease/ChilkatDotNet4-9.5.0-win32.zip
64-bit Download: http://www.chilkatsoft.com/download/preRelease/ChilkatDotNet4-9.5.0-x64.zip
The feature for continuing past permission/access issues had to do with issues on the remote server as opposed to the local filesystem. This new build should now also do the same for local permission errors. It will be noted in the release notes for Chilkat version 9.5.0.47 when released (soon).
If you have trouble, please post the LastErrorText using this new build.
I am using Marmalade to build a PlayBook app, but I think my question applies to PlayBook apps in general. I have successfully created a debugtoken.bar file and have installed it on my device. When I go to try to install a built application.bar file on the device, I get:
[execute] "blackberry-deploy.bat -device 192.168.1.114 -password ******* -installApp -package deployments\default\playbook\release\Quote Unquote.bar"
Info: Sending request: Install
Info: Action: Install
Info: File size: 6400334
Info: Installing ...
Info: Processing 6400334 bytes
actual_dname::
actual_id::
actual_version::
result::failure 881 required signatures missing (RDK, AUTHOR)
ERROR: error running blackberry-deploy
***ERROR***
Note that this is the Marmalade deploy tool running the standard PlayBook installer.
What I don't understand is: I thought the point of using a debugtoken.bar file was that you could install unsigned apps. I have in fact successfully deployed these unsigned apps using the Marmalade deploy tool just like this. But I was having problems signing the app for distribution, so I went back and did everything from scratch, requested new code signing keys from RIM, made a new debugtoken.bar file and installed it, etc. And now I'm worse off than I was before because I can't even install to the device now.
So again: My understanding is that the point of debugtoken.bar was to be able to deploy to the device before actually signing the application.bar for distribution. So what does this error message even mean?
To answer my own question:
For deploying a "debug" build to a device, it's critical to have
Application-Development-Mode: true
in the MANIFEST.MF within the .bar file.
A stupid mistake, but I'll leave this up in case it helps anyone...
Taking a look to the QNX deployment plugin "C:\Marmalade\6.1\s3e\deploy\plugins\qnx\qnx.py" I found that 'FOR DEVELOPMENT' option is false if the 'playbook_keystore' is given so I just cleared the signing section on the Marmalade System Deployment Tool and it is not longer trying to sign it