bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30323: Cygnus is not working in Fiware Tour Guide


From: Krishan Babbar
Subject: bug#30323: Cygnus is not working in Fiware Tour Guide
Date: Fri, 2 Feb 2018 14:43:07 +0000

Hi All,

I am following tour guide given at 
http://fiwaretourguide.readthedocs.io/en/latest/fiware-tour-guide-application-a-tutorial-on-how-to-integrate-the-main-fiware-ges/introduction/
I have Ubuntu 16.04.1 instance on Firware Cloud.

Guide is working fine till "Keyrock", but last two topics are not working i.e. 
"Cygnus - Publishing historical data" and "Running the front-end application"

For Cygnus, I could not see new database in MySQL Docker Container.
For Front-end, I tried http://MyHostIP with port 80 and 3000 from my Windows 
machine but these are not working. (Both ports have been added in Security 
Group of Instance.)

Below are given logs of "tourguide" and "Cygnus".

Tourguide Logs
address@hidden:~$ docker logs tourguide
DEFAULT_MAX_TRIES is undefined. Using default value of '60'
TOURGUIDE_HOSTNAME is undefined. Using default value of 'tourguide'
FIWARE_SERVICE is undefined. Using default value of 'tourguide'
IDAS_HOSTNAME is undefined. Using default value of 'idas'
Orion PEP Proxy authentication has been DISABLED.
Testing if port '8000' is open at host 'keyrock'.
Checking connection to 'keyrock:8000' [try 1/60] ... Retrying.
Checking connection to 'keyrock:8000' [try 2/60] ... OK.
Port '8000' at host 'keyrock' is open.
Testing if port '1026' is open at host 'orion'.
Checking connection to 'orion:1026' [try 1/60] ... OK.
Port '1026' at host 'orion' is open.
Enabling site tourguide-app.
To activate the new configuration, you need to run:
  service apache2 reload
Starting tourguide
* Starting web server apache2
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 172.17.0.9. Set the 'ServerName' directive globally to 
suppress this message
*
==> /var/log/apache2/access.log <==
tail: unrecognized file system type 0x794c7630 for 
'/var/log/apache2/access.log'. please report this to address@hidden reverting 
to polling

==> /var/log/apache2/error.log <==
[ 2018-02-02 11:19:12.1306 61/7f849eff3780 agents/Watchdog/Main.cpp:538 ]: 
Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nogroup', 
'default_python' => 'python', 'default_ruby' => '/usr/bin/ruby', 'default_user' 
=> 'nobody', 'log_level' => '0', 'max_pool_size' => '6', 'passenger_root' => 
'/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini', 
'passenger_version' => '4.0.37', 'pool_idle_time' => '300', 'temp_dir' => 
'/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com', 
'union_station_gateway_port' => '443', 'user_switching' => 'true', 
'web_server_passenger_version' => '4.0.37', 'web_server_pid' => '60', 
'web_server_type' => 'apache', 'web_server_worker_gid' => '33', 
'web_server_worker_uid' => '33' }
[ 2018-02-02 11:19:12.1370 64/7f5fbab1b780 agents/HelperAgent/Main.cpp:643 ]: 
PassengerHelperAgent online, listening at 
unix:/tmp/passenger.1.0.60/generation-0/request
[ 2018-02-02 11:19:12.1545 70/7fd1f5f12780 agents/LoggingAgent/Main.cpp:321 ]: 
PassengerLoggingAgent online, listening at 
unix:/tmp/passenger.1.0.60/generation-0/logging
[ 2018-02-02 11:19:12.1549 61/7f849eff3780 agents/Watchdog/Main.cpp:728 ]: All 
Phusion Passenger agents started!
[ 2018-02-02 11:19:12.1796 84/7f09fdfd0780 agents/Watchdog/Main.cpp:538 ]: 
Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nogroup', 
'default_python' => 'python', 'default_ruby' => '/usr/bin/ruby', 'default_user' 
=> 'nobody', 'log_level' => '0', 'max_pool_size' => '6', 'passenger_root' => 
'/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini', 
'passenger_version' => '4.0.37', 'pool_idle_time' => '300', 'temp_dir' => 
'/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com', 
'union_station_gateway_port' => '443', 'user_switching' => 'true', 
'web_server_passenger_version' => '4.0.37', 'web_server_pid' => '81', 
'web_server_type' => 'apache', 'web_server_worker_gid' => '33', 
'web_server_worker_uid' => '33' }
[ 2018-02-02 11:19:12.1887 87/7f84cb918780 agents/HelperAgent/Main.cpp:643 ]: 
PassengerHelperAgent online, listening at 
unix:/tmp/passenger.1.0.81/generation-0/request
[ 2018-02-02 11:19:12.1978 94/7f9b6f46b780 agents/LoggingAgent/Main.cpp:321 ]: 
PassengerLoggingAgent online, listening at 
unix:/tmp/passenger.1.0.81/generation-0/logging
[ 2018-02-02 11:19:12.1981 84/7f09fdfd0780 agents/Watchdog/Main.cpp:728 ]: All 
Phusion Passenger agents started!
[Fri Feb 02 11:19:12.200152 2018] [mpm_event:notice] [pid 81:tid 
140155835357056] AH00489: Apache/2.4.7 (Ubuntu) Phusion_Passenger/4.0.37 
OpenSSL/1.0.1f configured -- resuming normal operations
[Fri Feb 02 11:19:12.200286 2018] [core:notice] [pid 81:tid 140155835357056] 
AH00094: Command line: '/usr/sbin/apache2'
tail: unrecognized file system type 0x794c7630 for 
'/var/log/apache2/error.log'. please report this to address@hidden reverting to 
polling

==> /var/log/apache2/other_vhosts_access.log <==
tail: unrecognized file system type 0x794c7630 for 
'/var/log/apache2/other_vhosts_access.log'. please report this to 
address@hidden reverting to polling

==> /var/log/apache2/tourguide-app-access.log <==
tail: unrecognized file system type 0x794c7630 for 
'/var/log/apache2/tourguide-app-access.log'. please report this to 
address@hidden reverting to polling

==> /var/log/apache2/tourguide-app-error.log <==
tail: unrecognized file system type 0x794c7630 for 
'/var/log/apache2/tourguide-app-error.log'. please report this to 
address@hidden reverting to polling

==> /var/log/apache2/error.log <==


Cygnus Logs
address@hidden:~$ docker logs cygnus
+ exec /usr/lib/jvm/java-1.6.0/bin/java -Xmx20m 
-Dflume.root.logger=INFO,console -Duser.timezone=UTC -cp 
'/opt/apache-flume/conf:/opt/apache-flume/lib/*:/opt/apache-flume/plugins.d/cygnus/lib/*:/opt/apache-flume/plugins.d/cygnus/libext/*'
 -Djava.library.path= com.telefonica.iot.cygnus.nodes.CygnusApplication -f 
/opt/apache-flume/conf/agent.conf -n cygnus-ngsi -p 8081
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/opt/apache-flume/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/opt/apache-flume/plugins.d/cygnus/lib/cygnus-ngsi-1.2.0_SNAPSHOT-jar-with-dependencies.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/opt/apache-flume/plugins.d/cygnus/libext/cygnus-common-1.2.0_SNAPSHOT-jar-with-dependencies.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
time=2018-02-02T11:19:11.267Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp= | op=main | msg=com.telefonica.iot.cygnus.nodes.CygnusApplication[166] : 
Starting Cygnus, version 1.2.0_SNAPSHOT.8d92dce6853e119e5ecebafca315ab609204bb49
time=2018-02-02T11:19:11.470Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=main | 
msg=com.telefonica.iot.cygnus.nodes.CygnusApplication[279] : Waiting for valid 
Flume components references...
time=2018-02-02T11:19:11.471Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=start | 
msg=org.apache.flume.node.PollingPropertiesFileConfigurationProvider[61] : 
Configuration provider starting
time=2018-02-02T11:19:11.480Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=run | 
msg=org.apache.flume.node.PollingPropertiesFileConfigurationProvider$FileWatcherRunnable[133]
 : Reloading configuration file:/opt/apache-flume/conf/agent.conf
.
.
.
time=2018-02-02T11:19:11.657Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=getConfiguration | 
msg=org.apache.flume.node.AbstractConfigurationProvider[119] : Channel 
sth-channel connected to [http-source, sth-sink]
time=2018-02-02T11:19:11.657Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=getConfiguration | 
msg=org.apache.flume.node.AbstractConfigurationProvider[119] : Channel 
mongo-channel connected to [http-source, mongo-sink]
time=2018-02-02T11:19:11.657Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=getConfiguration | 
msg=org.apache.flume.node.AbstractConfigurationProvider[119] : Channel 
mysql-channel connected to [http-source, mysql-sink]
time=2018-02-02T11:19:11.663Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=startAllComponents | 
msg=org.apache.flume.node.Application[138] : Starting new configuration:{ 
sourceRunners:{http-source=EventDrivenSourceRunner: { 
source:org.apache.flume.source.http.HTTPSource{name:http-source,state:IDLE} }} 
sinkRunners:{mongo-sink=SinkRunner: { policy:address@hidden counterGroup:{ 
name:null counters:{} } }, mysql-sink=SinkRunner: { policy:address@hidden 
counterGroup:{ name:null counters:{} } }, sth-sink=SinkRunner: { 
policy:address@hidden counterGroup:{ name:null counters:{} } }} 
channels:{sth-channel=com.telefonica.iot.cygnus.channels.CygnusMemoryChannel{name:
 sth-channel}, 
mysql-channel=com.telefonica.iot.cygnus.channels.CygnusMemoryChannel{name: 
mysql-channel}, 
mongo-channel=com.telefonica.iot.cygnus.channels.CygnusMemoryChannel{name: 
mongo-channel}} }
time=2018-02-02T11:19:11.663Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=startAllComponents | 
msg=org.apache.flume.node.Application[145] : Starting Channel sth-channel

.
.
time=2018-02-02T11:19:11.779Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=start | msg=com.telefonica.iot.cygnus.sinks.NGSISink[261] 
: [mongo-sink] Startup completed
time=2018-02-02T11:19:11.780Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=start | msg=com.telefonica.iot.cygnus.sinks.NGSISink[261] 
: [sth-sink] Startup completed
time=2018-02-02T11:19:11.781Z | lvl=WARN | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=<init> | 
msg=com.telefonica.iot.cygnus.interceptors.CygnusGroupingRules[61] : Grouping 
rules syntax has errors. Details: null
time=2018-02-02T11:19:11.807Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=<init> | 
msg=com.telefonica.iot.cygnus.interceptors.CygnusGroupingRules[53] : Grouping 
rules read:
time=2018-02-02T11:19:11.807Z | lvl=WARN | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=<init> | 
msg=com.telefonica.iot.cygnus.interceptors.CygnusGroupingRules[61] : Grouping 
rules syntax has errors. Details: null
time=2018-02-02T11:19:11.982Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=register | 
msg=org.apache.flume.instrumentation.MonitoredCounterGroup[110] : Monitoried 
counter group for type: SOURCE, name: http-source, registered successfully.
time=2018-02-02T11:19:11.983Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=start | 
msg=org.apache.flume.instrumentation.MonitoredCounterGroup[94] : Component 
type: SOURCE, name: http-source started
time=2018-02-02T11:19:12.470Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=main | 
msg=com.telefonica.iot.cygnus.nodes.CygnusApplication[288] : Starting a Jetty 
server listening on port 8081 (Management Interface)
time=2018-02-02T11:19:20.793Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=processNewBatches | 
msg=com.telefonica.iot.cygnus.sinks.NGSISink[363] : Batch accumulation time 
reached, the batch will be processed as it is
time=2018-02-02T11:19:20.795Z | lvl=INFO | corr= | trans= | srv= | subsrv= | 
comp=cygnus-ngsi | op=processNewBatches | 
msg=com.telefonica.iot.cygnus.sinks.NGSISink[421] : Finishing internal 
transaction ()


Do let me know if you need further information.

Kindly guide what am I doing wrong?

Thanks & Regards,
Krishan Babbar
Technical Architect
Manufacturing | Tech Mahindra
Rajiv Gandhi Chandigarh Technology Park, Plot No. 23, Phase 2, Kishangarh, 
Chandigarh 160101, INDIA
* Office: +91 172 666 8400 Ext. 8352 | Mobile: +91 946 303 0996




============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html externally 
http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
===========================================================================================================================

============================================================================================================================

Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
<http://www.techmahindra.com/Disclaimer.html> externally 
http://tim.techmahindra.com/tim/disclaimer.html 
<http://tim.techmahindra.com/tim/disclaimer.html> internally within 
TechMahindra.

============================================================================================================================


reply via email to

[Prev in Thread] Current Thread [Next in Thread]