I want to dump my sequence files from hdfs to local and i tried with seqdumper.
How to resolve following error?
I am using mahout 0.12.0 version.
I got the same error with clusterdump as well.
The error message "Unexpected -s" tells us that the "-s" flag you're using is not expected by the job. Perhaps you mean to use "-i" for input? The expected options are listed after the error message.
Related
I try to install InfluxDB Enterprise Edition using this documentation: https://docs.influxdata.com/enterprise/v1.2/production_installation/. The Requirements suggest to either use a license-key or license-path, where I do it with the License Key.
In Step 2, after installing, configuring and starting the Data Nodes I try to join the data nodes to the cluster. But executing influxd-ctl add-data enterprise-data-01:8088 gives me the error:
add-data: operation exited with error: open /tmp/influx-enterprise.key.json: no such file or directory
although I configured not to use the license-key json but rather the license-key.
I also have the json file, so I tried it with the license-path but still getting the same error. Has somebody else encountered the same issues?
EDIT
Issue has been resolved, I had to restart the Data nodes after I changed the configuration to use the license-path facepalm. I went into this problem as I previously entered an old license key.
In Team Foundation Server 2015 Build (on-premise), I'm having issues running simple command line commands. All Command Line tasks simply fail with the following error: "File not found: ".
Take for example the following build definition:
This is executed using an on-premise Build Agent and will fail with the following exception in the logs:
BUILD FAILED
2016-01-20T12:04:47.5127709Z ##[warning]Filename doesn't indicate a full path to a executable file.
2016-01-20T12:04:47.5127709Z Executing the following commandline. (workingFolder = D:\_work\2\s)
2016-01-20T12:04:47.5127709Z date
2016-01-20T12:04:47.5127709Z Error message highlight pattern:
2016-01-20T12:04:47.5127709Z Warning message highlight pattern:
2016-01-20T12:04:47.5439748Z ##[error]File not found: date
Of course this is a simplified example where I simply want to output the current date using the date /t command. But the same problem occurs with all general command line commands which I've tried, such as dir, time, path etc. The MSDN does not provide any troubleshooting info on it, other than that the tool executed must reside in the PATH variable.
The issue is not specific to one build definition or repo; it can be reproduced on others as well.
The builds run as the built-in svc_tfsbuild account.
I'm perhaps thinking this is either a simple setting, or - wildly guessing - an issue related to rights, but cannot find any documentation where to look or what to check. Any help would be appreciated.
It appears this is a known issue on MS Connect as well.
In short a MSFT mentions the following:
Commands that are built-in to command prompt don't work. Anything resolvable based on your PATH/PATHEXT will work.
In the comment from 27 Oct, 2015 it is stated that this will be fixed in the next sprint. The mentioned workaround for now is simply executing cmd.exe first and provide the rest as arguments.
Using the example from the original question this would lead to:
Tool: cmd.exe
Arguments: /c "date /t"
And I can indeed confirm this works.
I have jenkins v 1.580 installed on windows.
All my jobs were working fine until afternoon but all of a sudden all the jobs started failing with the following error,(The only error)
FATAL: (class: org/apache/commons/codec/binary/Base64OutputStream, method: signature: (Ljava/io/OutputStream;ZI[B)V) Incompatible argument to function
FATAL: (class: org/apache/commons/codec/binary/Base64OutputStream, method: signature: (Ljava/io/OutputStream;ZI[B)V) Incompatible argument to function
Finished: null
The only thing i found to happen in the afternoon was a windows security update but that also I was able to get uninstalled with the help of IT.
(I have close to 50 jobs running. Is there any limitation on number of jobs)
Can anyone tell me what could be wrong here?
Following the error snippet I can see from jenkins.error,
a user in error attempting to specify a java: URL name in a non-J2EE client or server environment. Throwing
Caused by: com.thoughtworks.xstream.io.StreamException: : only whitespace content allowed before start tag and not \u0
(position: START_DOCUMENT seen \u0... #1:1)
Caused by: org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not \u0 (position:
START_DOCUMENT seen \u0... #1:1)
Should I go for reinstallation of jenkins?
Thanks in advance.
Sakthivel C
Are you using fingerprint plugin? It appears as if fingerprint files were corrupted.
Delete the directory "fingerprints" from JENKINS_HOME and restart your Jenkins to resolve the issue.
If that doesn't work, paste the exact error log here.
I'm installing Dspace in Windows 7 and I got it working fine with me until I got this error message:
I tried doing what the link :build failed .. creation was not successful for an unknown reason has said, but still nothing's change. Does anyone know how to fix it?
Check dspace.install.dir at build.properties, it seems to have a bad value.
Change the value to the location you want to install and use "/" character to the directory. For example C:/Program Files/Dspace.
I am getting this error on azcopy ;the command syntax in incorrect
azcopy error specifying multiple file patterns is not supported
my command azcopy myfile.csv kobosh.blob.core/mycontainer/destkey:key axkey.txt
any one have idea or encountered this error ?
Are you going to upload myfile.csv or axkey.txt?
The tools stopped to support multiple file pattern since 2.5 due to performance considerationg: http://ppe.blogs.msdn.com/b/windowsazurestorage/archive/2014/08/08/azcopy-2-5-release.aspx
Additionally, per the help (run 'AzCopy /?') its input format is:
AzCopy source destination [filepattern] [options]
source and dest are both "containers", in your case it should be local folder. and you need to put the option after the the pattern, as well as your URL should be correct, so it might be :
azcopy <the folder of your file> https://kobosh.blob.core.windows.net/mycontainer <your file name> /destkey:key