When are we looking at the logs (/var/opt/jfrog/artifactory/log/console.log
), we can see next picture in many place:
2021-10-07T11:58:37.772Z 35[jfob ] [INFO ] [06640885d968439e] [shipping_service.go:79 ] [main ] - Validating if shipping need to be enabled or not... [shipping_service]
2021-10-07T11:58:37.775Z 35[jfob ] [WARN ] [06640885d968439e] [shipping_service.go:86 ] [main ] - Shipping is not enabled in Platform Configuration [shipping_service]
We viewed https://www.jfrog.com/confluence/display/JFROG/Logging and didn't see any Level with "jfob" name.
We viewed /opt/jfrog/artifactory/var/etc/system.full-template.yaml and didn't see any config key with "shipping" name.
Please tell me how to get rid of these notifications in the log file?
#vsgonchar Hi, The messages you have shared here are related to Insight service. Please be informed that these warnings/informational messages would not have an impact on the Artifactory's performance and it can be safely ignored. In future versions, these messages are discussed to be amended as a part of DEBUG mode enablement.
Related
I am using botium box and configured a Google Assistant Connector.
When I run a test case, I encounter the following botium core error :
Empty response, configuration, or start utterance Parler avec test app name invalid :
{
micOpen: true,
textToSpeech: [],
displayText: [],
ssml:
[ "<speak><s>In order to purchase a product, please contact our support.</s><s>Can I do anything else for you ?</s></speak>" ],
suggestions: []
}
However, as you can see, the response is not empty as it contains my actions' answer in the ssml array and since my actions answers correctly the start utterance seems correct.
Any idea on why botium core considers this answer to be an error ?
Thanks !
The Botium Google Assistant Connector currently only supports the "textToSpeech" element. There are some amendments planned for december release, the SSML support will be one of them.
Trying to find a solution for opening RabbitMQ to the internet is not exactly easy. The documentation is sparse and the configuration I can find is in multiple formats. How can I configure RabbitMQ to allow external access?
There are 3 ways to configure RabbitMQ: command line and two styles of configuration file. Here is how to configure RabbitMQ using one of the configuration styles.
First you'll need to find the rabbitmq.config. It is found in the RabbitMQ installation directory. I found mine here:
C:\Users\[User]\AppData\Roaming\RabbitMQ\rabbitmq.config
The config file follows a very particular syntax. You'll need to take care. After a configuration change you will need to restart RabbitMQ for the configuration to take affect. If RabbitMQ stops immediately there is a problem with your configuration.
If RabbitMQ runs this only means that the configuration didn't kill the process. It does not mean that it was applied correctly. It will certainly apply if you get the syntax correctly, but every wrong configuration does not guarantee the service crashes.
Follows are a few example configurations (notice the trailing ".") :
Base of the RabbitMQ configuration style we will be using (should only appear once in the configuration file):
[{rabbit, []}].
Configuration that allows the RabbitMQ management plugin to be accessed from the internet:
[{rabbit,
[
{rabbitmq_management, [{listener, [{port, 15672}]}]},
{rabbitmq_management, [{cors_allow_origins, ["*"]}]}
]
}].
Configuration that allows the RabbitMQ api to be accessed from the internet:
[{rabbit,
[
{tcp_listeners, [5672]}
]
}].
Configuration that allows guest user to access the management plugin from the internet:
[{rabbit,
[
{loopback_users, []},
{rabbitmq_management, [{listener, [{port, 15672}]}]},
{rabbitmq_management, [{cors_allow_origins, ["*"]}]}
]
}].
Configuration that does all of the above:
[{rabbit,
[
{tcp_listeners, [5672]},
{loopback_users, []},
{rabbitmq_management, [{listener, [{port, 15672}]}]},
{rabbitmq_management, [{cors_allow_origins, ["*"]}]}
]
}].
Leaving a trailing comma in an array in your configuration will cause RabbitMQ to stop.
If you are still having issues check that you've permitted the ports through any firewalls.
Considerations This leaves your RabbitMQ server wide open. You will want to certainly restrict the access. A search of tcp_listeners will reveal other options to restrict access to particular ip. It is also not a good idea to expose the default guest user to the internet in any production environment.
I'm facing a serious problem with my elasticsearch server.
I'm using ES 1.7 on a symfony2 project with fosElasticaBundle.
The ES index has been deleted two times today, and I can't figure out why.
Here are the log I can read in my cluster.log:
[cluster.metadata] [server] [index] deleting index
[cluster.metadata] [server] [warning] deleting index
[cluster.metadata] [server] [please_read] creating index, cause [api], templates [], shards [5]/[1], mappings []
[cluster.metadata] [server] [please_read] update_mapping [info] (dynamic)
The thing is that my ES never faced such kind of issue in the past monthes while the website was on pre-prod.
Do you think this can comes from an attack ? Or an configuration error ?
This is very likely coming from an attack. if you do a <Endpoint>/please_read/_search you will probably see a note like
{
"_index": "please_read",
"_type": "info",
"_id": "AVmZfnjEAQ_HIp2JODbw",
"_score": 1.0,
"_source": {
"Info": "Your DB is Backed up at our servers, to restore send 0.5 BTC to the Bitcoin Address then send an email with your server ip",
"Bitcoin Address": "12JNfaS2Gzic2vqzGMvDEo38MQSX1kDQrx",
"Email": "elasticsearch#mail2tor.com"
}
You should try to make your elasticsearch cluster installation more secure to avoid such downfalls.
There have also been reports of attacks on open to internet databases like mongo/elasticsearch eg. http://www.zdnet.com/article/first-came-mass-mongodb-ransacking-now-copycat-ransoms-hit-elasticsearch/
I concur with #dejavu013, this is most likely database ransomware, I would advise securing your elasticsearch with the free and opensource https://github.com/floragunncom/search-guard, or premium solutions like Elastic's Shield, now part of the Elastic X-Pack or Compose's Hosted Elasticsearch.
many elasticsearch clusters was attacked in the last week:
http://www.zdnet.com/article/first-came-mass-mongodb-ransacking-now-copycat-ransoms-hit-elasticsearch/
this is how you can secure it:
http://code972.com/blog/2017/01/107-dont-be-ransacked-securing-your-elasticsearch-cluster-properly
This was indeed an attack as #dejavu013 said.
I started to secure my datas by allowing only localhost to access to my elasticseach datas.
To do so, I've edited my config file elasticseach.yml and added those two lines :
networt.host: 127.0.0.1
http.port: 9200
So only localhost can access to the datas and make requests.
I have installed the API Mgr 1.7.0 in Win 7 64. I have been through the Quick Start guide and all appeared to work as described. However, when I get to the point of trying the subscribed-to cdyne api, the 'moving dots' graphic stays there forever. I can't find a way to stop it, other than a browser refresh. I can't see an entry in the API Mgr system logs.
I have removed the parameters and the auth info, which is supposed to return a 401, but it doesn't and the moving dots continue. I'm using Firefox 31, with AdBlock+ and Noscript. There are no blocked scripts as far as I can see.
[edit 1] I get the same problem with the first sample (YouTube). I wonder if the problem is caused by port values? As I have the ESB installed, I increased all the ports for API Mgr by 1. Maybe I missed one, or there is one that hasn't been documented.[/edit 1]
[edit 2] I have reinstalled the API Mgr. I stopped the ESB and left the APIM ports as default. I have recreated the Phone Verify service and I still have same problem with 'Try it now'. I set the global log level to DEBUG, but there is too much detail to be of use. I don't know what package names to set for this problem.
There was an entry in the Application Logs as follows, which might be relevant. The first few lines are shown:
System Error Occurred
Exception occurred while trying to invoke service method getApplicationNames
The following error details are available. Please refer logs for more details.
org.apache.axis2.AxisFault: Exception occurred while trying to invoke service method getApplicationNames
at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:370)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:445)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at org.wso2.carbon.logging.view.stub.LogViewerStub.getApplicationNames(LogViewerStub.java:3700)
at org.wso2.carbon.logging.view.ui.LogViewerClient.getApplicationNames(LogViewerClient.java:165)
[/edit 2]
Regards, John
You may not have configured CORS. CORS is cross-origin resource sharing [1] and it is used by the try-it feature in the store.
The CORS configuration is stored in [API Manager Home]/reposotiry/conf/api-manager.xml . The header must include the Host name used by the CORS request. The host name being used by the try-it service is shown in gray at the bottom-left hand corner of the API-Console / try-it screen. It should show up as 'base url'. For example: [ base url: http://10.212.0.846.:8281 , api version: 1.0 ]
You may also be having trouble with the default APIs - please make sure that the APIs in [API Manager Home]/repository/deployment/server/synapse-configs/default/api/ are updated with your port offset. This may be preventing basic authentication. It is documented here [2]
Hope that helps.
-Colin
[1] http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
[2] https://docs.wso2.com/display/AM170/Changing+the+Default+Ports+with+Offset
This question may have been asked before. I have searched for answers, but I haven't found what I was looking for.
In Symfony 2.3, is there a way to disable the logger for specific requests? I mean, I am using a SOAP service for my project. When I send a request to login, the username and password are dumped straight as plain text into the log file. Is there a way to stop logging this kind of specific requests?
For example, when I send a request for login, the logger should be disabled, but for all other request it works again. Is this possible?
depending if your are in Prod or Dev environement but everything is in config.yml or config_dev.yml :
to disable logging just remove monolog configuration like this :
monolog:
handlers:
main:
type: stream
path: "%kernel.logs_dir%/%kernel.environment%.log"
level: debug
console:
type: console
bubble: false
# uncomment to get logging in your browser
# you may have to allow bigger header sizes in your Web server configuration
#firephp:
# type: firephp
# level: info
#chromephp:
# type: chromephp
# level: info
but in my opinion , you shouln't do this because logging allows you to improve significantly your code !
Logging except for a specific service :
You need to create a specific log channel for your service as described there :
http://symfony.com/doc/current/cookbook/logging/channels_handlers.html
and there :
http://symfony.com/doc/current/reference/dic_tags.html#dic-tags-monolog
you ll be able to separate your soap log from others and eventually send it to null