Created question in FIWARE Q/A platform on 07-10-2015 at 12:10
Please, ANSWER this question AT http://stackoverflow.com/questions/32989596/fiware-can-not-start-cygnus-as-service
Question:
Fiware: can not start cygnus as service
Description:
I installed cygnus using RPMs on fiware image CentOS-7-x64 and I can't start it as a service, Here is my logs:
[centos@cygnus-mongo conf]$ sudo service cygnus start
Starting cygnus (via systemctl): Job for cygnus.service failed. See 'systemctl status cygnus.service' and 'journalctl -xn' for details.
[FAILED]
[centos@cygnus-mongo conf]$ sudo journalctl -xn
– Logs begin at mer. 2015-10-07 07:48:29 UTC, end at mer. 2015-10-07 10:02:35 UTC. –
oct. 07 10:02:20 cygnus-mongo.novalocal su[5700]: pam_unix(su:session): session closed for user cygnus
oct. 07 10:02:22 cygnus-mongo.novalocal cygnus[5695]: cat: /var/run/cygnus/cygnus_mongo.pid: No such file or directory
oct. 07 10:02:22 cygnus-mongo.novalocal cygnus[5695]: [FAILED]
oct. 07 10:02:22 cygnus-mongo.novalocal cygnus[5695]: rm: cannot remove ‘/var/run/cygnus/cygnus_mongo.pid’: No such file or directory
oct. 07 10:02:22 cygnus-mongo.novalocal systemd[1]: cygnus.service: control process exited, code=exited status=1
oct. 07 10:02:22 cygnus-mongo.novalocal systemd[1]: Failed to start SYSV: cygnus.
– Subject: Unit cygnus.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
–
– Unit cygnus.service has failed.
–
– The result is failed.
oct. 07 10:02:22 cygnus-mongo.novalocal systemd[1]: Unit cygnus.service entered failed state.
oct. 07 10:02:34 cygnus-mongo.novalocal dhclient[1064]: DHCPREQUEST on eth0 to 192.168.111.71 port 67 (xid=0x761299ef)
oct. 07 10:02:34 cygnus-mongo.novalocal dhclient[1064]: DHCPACK from 192.168.111.71 (xid=0x761299ef)
oct. 07 10:02:35 cygnus-mongo.novalocal sudo[5774]: centos : TTY=pts/0 ; PWD=/usr/cygnus/conf ; USER=root ; COMMAND=/bin/journalctl -xn
Actually the directory /var/run/cygnus was not created, is it going to be created automatically?
Here is my configuration files:
agent_mongo.conf
cygnusagent.sources = http-source
cygnusagent.sinks = mongo-sink
cygnusagent.channels = mongo-channel
#=============================================
- source configuration
- channel name where to write the notification events
cygnusagent.sources.http-source.channels = mongo-channel
- source class, must not be changed
cygnusagent.sources.http-source.type = org.apache.flume.source.http.HTTPSource
- listening port the Flume source will use for receiving incoming notifications
cygnusagent.sources.http-source.port = 5050
- Flume handler that will parse the notifications, must not be changed
cygnusagent.sources.http-source.handler = com.telefonica.iot.cygnus.handlers.OrionRestHandler
- URL target
cygnusagent.sources.http-source.handler.notification_target = /notify
- Default service (service semantic depends on the persistence sink)
cygnusagent.sources.http-source.handler.default_service = def_serv
- Default service path (service path semantic depends on the persistence sink)
cygnusagent.sources.http-source.handler.default_service_path = def_servpath
- Number of channel re-injection retries before a Flume event is definitely discarded (-1 means infinite retries)
cygnusagent.sources.http-source.handler.events_ttl = 10
- Source interceptors, do not change
cygnusagent.sources.http-source.interceptors = ts gi
- TimestampInterceptor, do not change
cygnusagent.sources.http-source.interceptors.ts.type = timestamp
- GroupinInterceptor, do not change
cygnusagent.sources.http-source.interceptors.gi.type = com.telefonica.iot.cygnus.interceptors.GroupingInterceptor$Builder
- Grouping rules for the GroupingInterceptor, put the right absolute path to the file if necessary
- See the doc/design/interceptors document for more details
cygnusagent.sources.http-source.interceptors.gi.grouping_rules_conf_file = /usr/cygnus/conf/grouping_rules.conf
- ============================================
- OrionMongoSink configuration
- sink class, must not be changed
cygnusagent.sinks.mongo-sink.type = com.telefonica.iot.cygnus.sinks.OrionMongoSink
- channel name from where to read notification events
cygnusagent.sinks.mongo-sink.channel = mongo-channel
- FQDN/IP:port where the MongoDB server runs (standalone case) or comma-separated list of FQDN/IP:port pairs where the MongoDB replica set members run
cygnusagent.sinks.mongo-sink.mongo_hosts = 127.0.0.1:27017
- a valid user in the MongoDB server (or empty if authentication is not enabled in MongoDB)
cygnusagent.sinks.mongo-sink.mongo_username =
- password for the user above (or empty if authentication is not enabled in MongoDB)
cygnusagent.sinks.mongo-sink.mongo_password =
- prefix for the MongoDB databases
cygnusagent.sinks.mongo-sink.db_prefix = kura_
- prefix pro the MongoDB collections
cygnusagent.sinks.mongo-sink.collection_prefix = kura_
- true is collection names are based on a hash, false for human redable collections
cygnusagent.sinks.mongo-sink.should_hash = false
#=============================================
- mongo-channel configuration
- channel type (must not be changed)
cygnusagent.channels.mongo-channel.type = memory
- capacity of the channel
cygnusagent.channels.mongo-channel.capacity = 1000
- amount of bytes that can be sent per transaction
cygnusagent.channels.mongo-channel.transactionCapacity = 100
cygnus_instance_mongo.conf :
- Who to run cygnus as. Note that you may need to use root if you want
- to run cygnus in a privileged port (<1024)
CYGNUS_USER=cygnus
- Where is the config folder
CONFIG_FOLDER=/usr/cygnus/conf
- Which is the config file
CONFIG_FILE=/usr/cygnus/conf/agent_mongo.conf
- Name of the agent. The name of the agent is not trivial, since it is the base for the Flume parameters
- naming conventions, e.g. it appears in .sources.http-source.channels=...
AGENT_NAME=cygnusagent
- Name of the logfile located at /var/log/cygnus. It is important to put the extension '.log' in order to the log rotation works properly
LOGFILE_NAME=cygnus.log
- Administration port. Must be unique per instance
ADMIN_PORT=8081
- Polling interval (seconds) for the configuration reloading
POLLING_INTERVAL=30
2015-10-07 15:05|CREATED monitor | # answers= 0, accepted answer= False