Details
- 
        Type:
Monitor
 - 
        Status: Closed
 - 
            Priority:
 Major
                
             - 
            Resolution: Done
 - 
            Affects Version/s: None
 - 
            Fix Version/s: 2021
 - 
            Component/s: FIWARE-TECH-HELP
 - 
            Labels:
 
- 
                        HD-Chapter:Data
 - 
                        HD-Enabler:Cosmos
 
Description
Created question in FIWARE Q/A platform on 16-09-2015 at 13:09
Please, ANSWER this question AT https://stackoverflow.com/questions/32606863/warning-on-cygnus-avoids-data-persistence-on-cosmos
Question:
Warning on Cygnus avoids data persistence on Cosmos
Description:
This is a cygnus agent log:
16 Sep 2015 12:30:19,820 INFO  [521330370@qtp-1739580287-1] (com.telefonica.iot.cygnus.handlers.OrionRestHandler.getEvents:236)  - Received data (<notifyContextRequest><subscriptionId>55f932e6c06c4173451bbe1c</subscriptionId><originator>localhost</originator>...<contextAttribute><name>utctime</name><type>string</type><contextValue>2015-9-16 9:37:52</contextValue></contextAttribute></contextAttributeList></contextElement><statusCode><code>200</code><reasonPhrase>OK</reasonPhrase></statusCode></contextElementResponse></contextResponseList></notifyContextRequest>)
16 Sep 2015 12:30:19,820 INFO  [521330370@qtp-1739580287-1] (com.telefonica.iot.cygnus.handlers.OrionRestHandler.getEvents:258)  - Event put in the channel (id=1145647744, ttl=0)
16 Sep 2015 12:30:19,820 WARN  [SinkRunner-PollingRunner-DefaultSinkProcessor] (com.telefonica.iot.cygnus.sinks.OrionSink.process:184)  - 
16 Sep 2015 12:30:19,820 INFO  [SinkRunner-PollingRunner-DefaultSinkProcessor] (com.telefonica.iot.cygnus.sinks.OrionSink.process:193)  - Finishing transaction (1442395508-572-0000013907)
We conserve the same configuration than this question:
Fiware Cygnus Error. 
Although the Cygnus agent receives data correctly from the Context Broker suscription, Cosmos doesn't receive any data.
Thanks in advance, again ![]()
Activity
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
		    	
  | 
			2h 59m | 1 | Backlog Manager | 25/May/17 6:04 PM | |||||
		    	
  | 
			3h | 1 | Backlog Manager | 25/May/17 9:04 PM | |||||
		    	
  | 
			12h 59m | 1 | Fernando Lopez | 26/May/17 10:03 AM |