Riak CS cannot start with log.syslog=on - riak

In /etc/riak-cs/riak-cs.conf I've changed
log.syslog=off
to
log.syslog=on
After that
service riak-cs start
returns
18:33:51.427 [error] Error generating configuration in phase apply_translations
18:33:51.428 [error] Translation for 'lager.handlers' expected to find setting 'log.syslog.ident' but was missing
I've added this option in /etc/riak-cs/riak-cs.conf
log.syslog=on
log.syslog.ident=riakcs
But after that it gives me
18:18:40.800 [error] Error generating configuration in phase transform_datatypes
18:18:40.800 [error] Conf file attempted to set unknown variable: log.syslog.ident
What am I missing?

Depending Riak CS version, but it seems that you encountered the bug [1].
An workaround to use advanced.config is described in the issue comment [2].
It will be fixed in the coming releases Riak CS 2.1.0.
[1] https://github.com/basho/riak_cs/pull/1162
[2] https://github.com/basho/riak_cs/pull/1162#issuecomment-110550814

Related

Artifactory - Failed to update stats with error couldn't find versionIDs for the given paths

My Artifactory logs are showing the following errors with alarming frequency. The metadata service is up and healthy according to Artifactory, and aside from the log spam, it doesn't seem to be causing any problems. Does anyone have any ideas how to fix this?
[jfrt ] [ERROR] [af10ed1c492f4e88] [s.MetadataEventServiceImpl:346] [art-exec-6 ] - Unable to send statistics event to Metadata Server. Caught exception: Failed executing api/v1/stats, with response code: HTTP/1.1 500 Internal Server Error and response message: {"cause":"Internal error while processing request","message":"Failed to update stats with error couldn't find versionIDs for the given paths: couldn't find versionIDs for the given paths"}
Artifactory 7.27.10, running in Kubernetes
Using an external postgres 13 database
Using s3 as the storage backend
This is a known issue (documented internally as META-1180). This has been fixed and is released with Artifactory 7.29. This version of Artifactory is scheduled for release sometime over the next few weeks.

WSO2 APIM 3.2.0 error while updating API definition

We are getting the below error while updating the API definition through publisher on WSO2 3.2.0 APIM. How to fix this issue:
TID: [-1234] [api/am/publisher] [2021-09-13 11:32:18,306] ERROR {org.wso2.carbon.apimgt.rest.api.util.exception.GlobalThrowableMapper} - An unknown exception has been captured by the global exception mapper. org.apache.cxf.interceptor.Fault: Couldn't find MIME boundary: ------WebKitFormBoundaryEsb6bxMwX39fG8Sb
at org.apache.cxf.interceptor.AttachmentInInterceptor.handleMessage(AttachmentInInterceptor.java:60)
at org.apache.cxf.jaxrs.ext.MessageContextImpl.createAttachments(MessageContextImpl.java:284)
at org.apache.cxf.jaxrs.ext.MessageContextImpl.get(MessageContextImpl.java:79)
at org.apache.cxf.jaxrs.impl.tl.ThreadLocalMessageContext.get(ThreadLocalMessageContext.java:42)
at org.apache.cxf.jaxrs.utils.multipart.AttachmentUtils.getMultipartBody(AttachmentUtils.java:143)
at org.apache.cxf.jaxrs.utils.multipart.AttachmentUtils.getAttachments(AttachmentUtils.java:155)
Caused by: java.io.IOException: Couldn't find MIME boundary: ------WebKitFormBoundaryEsb6bxMwX39fG8Sb
at org.apache.cxf.attachment.AttachmentDeserializer.initializeRootMessage(AttachmentDeserializer.java:140)
at org.apache.cxf.attachment.AttachmentDeserializer.initializeAttachments(AttachmentDeserializer.java:110)
at org.apache.cxf.interceptor.AttachmentInInterceptor.handleMessage(AttachmentInInterceptor.java:58)
... 54 more
Is this issue occurring in the vanilla pack? Because this erroneous behavior is due to a known bug in the Tomcat version[1]. This issue has been identified and have fixed in the latest WUM updates.
Or else, you need to use a 9.0.34[2] bundle version and replace the appropriate jars. Also, new jars should be replaced in the bundle.info[3] as appropriate.
[1] https://github.com/wso2/product-apim/issues/8029
[2] https://maven.wso2.org/nexus/content/repositories/releases/org/wso2/orbit/org/apache/tomcat/tomcat-catalina-ha/9.0.34.wso2v1/
[3]
repository/components/default/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info

sbt lagom template+InvalidRemoteException

I tried to follow the follow tutorial:
https://www.lagomframework.com/documentation/1.4.x/java/GettingStartedSbt.html
For generating the project scaffolding, I want to use the following template:
sbt new lagom/lagom-java.g8
But already receive the following error:
[error] org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin
A bit frustrating at such early stage in the tutorial...
Any idea how to fix this?
Edit: the error is caused by:
[error] Caused by: org.eclipse.jgit.errors.NoRemoteRepositoryException: https//github.com/lagom/lagom-java.g8.git: not found.
Seems there is a :missing after https. How to fix?
Verify you have the prerequisites. Prerequisites documented here https://www.lagomframework.com/documentation/1.4.x/java/JavaPrereqs.html
I just followed the instructions and was unable to reproduce the error from the CLI using sbt version 1.1.1.
What version of sbt are you using?

Appcelerator - include jar in build at compile-time?

Since Appcelerator(/Hyperloop) doesn't use Gradle or Maven to manage dependencies, I need to include them all manually for my project by placing them in the app/platform/android folder. I have done this, however I also need to include google dagger (https://github.com/google/dagger) which requires including dagger-compiler-2.x.jar , which I believe is an annotation processor that generates some type of code during compile-time.
Simply placing this in the app/platform/android folder like any other jar results in this error when the dexer is running during the build:
[ERROR] : Failed to run dexer:
[ERROR] :
[ERROR] : PARSE ERROR:
[ERROR] : MethodHandle not supported
[ERROR] : ...while preparsing cst 016c at offset 00001ceb
[ERROR] : ...while parsing com/google/googlejavaformat/java/JavaInput.class
[ERROR] : 1 error; aborting
I think it has something to do with the part of the dagger instructions which state "you will need to include dagger-compiler-2.x.jar in your build at compile time." Is there somewhere else that I need to place this jar file to get it to be used properly? Or is the use of compile-time annotation processors not something that Appcelerator/Hyperloop supports at this time? Any thoughts or insight would be greatly appreciated.
A good amount has changed since this question was asked. This being said, I believe that currently Hyperloop for Android doesn't handle annotations. And this is how dependency injection systems work, so I believe it's still not currently possible to use that or similar JARs.

Error running Kafka on Cloudera quickstart: assembly-package-dependency not valid

I have downloaded Kafka from apache and extracted it to its own folder. Following the quickstart, I also installed sbt, but at the third line in the sbt commands (I am launching the terminal from INSIDE the kafka folder, I get:
[error] Not a valid command: assembly-package-dependency
[error] Not a valid project ID: assembly-package-dependency
[error] Expected ':' (if selecting a configuration)
[error] Not a valid key: assembly-package-dependency (similar: sbt-dependency)
[error] assembly-package-dependency
[error] ^
I have been looking for all day for an answer, but found none which would start my server. The exception when I try the kafka-server-start.sh is always
unable to find main class Kafka.kafka
I also tried "gradle" the first time, but the problem was the same. I have no chance of upgrading to Cloudera-Express to use the parcel installer: my PC is not good enough to support it.
I am quite desperate: please help me!
I found that sbt update etc didn't quite do the job, so in the end I found another answer suggesting:
In the kafka folder:
./gradlew jar

Resources