[Backlogmanager] [FIWARE-JIRA] (HELP-14215) [fiware-stackoverflow] Cygnus does not recognize my service-path

[Joaquín Salvachúa (JIRA)]

     [ https://jira.fiware.org/browse/HELP-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joaquín Salvachúa  reassigned HELP-14215:
-----------------------------------------

    Assignee: Andres Muñoz  (was: Joaquín Salvachúa )

> [fiware-stackoverflow] Cygnus does not recognize my service-path
> ----------------------------------------------------------------
>
>                 Key: HELP-14215
>                 URL: https://jira.fiware.org/browse/HELP-14215
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Andres Muñoz
>              Labels: fiware, fiware-cygnus
>
> Created question in FIWARE Q/A platform on 29-05-2018 at 12:05
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50582014/cygnus-does-not-recognize-my-service-path
> +Question:+
> Cygnus does not recognize my service-path
> +Description:+
> I have moved my Fiware structure to the Amazon EC2 service, the configuration of my agent is as follows:
> cygnus-ngsi.sources = http-source
> cygnus-ngsi.sinks = mongo-sink
> cygnus-ngsi.channels = mongo-channel
> cygnus-ngsi.sources.http-source.channels = mongo-channel
> cygnus-ngsi.sources.http-source.type = org.apache.flume.source.http.HTTPSource
> cygnus-ngsi.sources.http-source.port = 5050
> cygnus-ngsi.sources.http-source.handler = com.telefonica.iot.cygnus.handlers.NGSIRestHandler
> cygnus-ngsi.sources.http-source.handler.notification_target = /notify
> cygnus-ngsi.sources.http-source.handler.default_service = default
> cygnus-ngsi.sources.http-source.handler.default_service_path = /sevilla
> cygnus-ngsi.sources.http-source.handler.events_ttl = 2
> cygnus-ngsi.sources.http-source.interceptors = ts
> cygnus-ngsi.sources.http-source.interceptors.ts.type = timestamp
> cygnus-ngsi.sinks.mongo-sink.type = com.telefonica.iot.cygnus.sinks.NGSIMongoSink
> cygnus-ngsi.sinks.mongo-sink.channel = mongo-channel
> cygnus-ngsi.sinks.mongo-sink.enable_encoding = true
> cygnus-ngsi.sinks.mongo-sink.enable_grouping = false
> cygnus-ngsi.sinks.mongo-sink.enable_name_mappings = false
> cygnus-ngsi.sinks.mongo-sink.enable_lowercase = false
> cygnus-ngsi.sinks.mongo-sink.data_model = dm-by-service-path
> cygnus-ngsi.sinks.mongo-sink.attr_persistence = column
> cygnus-ngsi.sinks.mongo-sink.mongo_hosts = ******com:15959
> cygnus-ngsi.sinks.mongo-sink.mongo_username = ********
> cygnus-ngsi.sinks.mongo-sink.mongo_password = ********
> cygnus-ngsi.sinks.mongo-sink.db_prefix = sth_
> cygnus-ngsi.sinks.mongo-sink.collection_prefix = sth_
> cygnus-ngsi.sinks.mongo-sink.batch_size = 1
> cygnus-ngsi.sinks.mongo-sink.batch_timeout = 120
> cygnus-ngsi.sinks.mongo-sink.batch_ttl = 10
> cygnus-ngsi.sinks.mongo-sink.data_expiration = 0
> cygnus-ngsi.sinks.mongo-sink.collections_size = 0
> cygnus-ngsi.sinks.mongo-sink.max_documents = 0
> cygnus-ngsi.sinks.mongo-sink.ignore_white_spaces = true
> cygnus-ngsi.channels.mongo-channel.type = com.telefonica.iot.cygnus.channels.CygnusMemoryChannel
> cygnus-ngsi.channels.mongo-channel.capacity = 15000
> cygnus-ngsi.channels.mongo-channel.transactionCapacity = 11000
> The problem is that when you send the data to MongoDB, it does not send them to the service-path that is configured in the agent, obtaining this response in cygnus.log
> Database: sth_default, Collection: sth_x002f
>   srv = default | subsrv = /
> What happens so that it does not recognize my service-path?



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)