- Problem: Logs are not traced
- Problem: The API does not work
- Problem: The GUI does not work
- Other problems
First, check the folder
/var/log/cygnus has been created:
$ ls -la /var/log/cygnus total 117712 drwxr-xr-x 3 frb staff 102 19 feb 09:02 . drwxr-xr-x 61 root wheel 2074 6 may 07:32 .. -rw-r--r-- 1 frb staff 60265711 19 feb 09:00 cygnus.log
Second, check the ownership of the above folder. If the owner is not
cygnus and the group is not
cygnus, you must change the ownership:
$ chown cygnus:cygnus /var/log/cygnus
Third, check the permissions of the log folder. If the permissions does not contain write permissions, add them:
$ chmod a+w /var/log/cygnus
Check the log4j configuration is using a file-related appender.
First of all, check you have a valid
lo4j.properties file (not a template) in
Then, verify you have these lines configured:
Another possibility is you are changing the above configuration from the command line, by using the following arguments:
Check the apender value is
Check the port you are using in the request is the one configued in Cygnus. By default, it is
8081, but can be modified by Cygnus administrator.
The API port may be properly configured but not opened in the firewall (if such a firewall is running) protecting your machine.
The specific solution depends on the specific firewall. Here,
iptables-based firewalling is shown. Please, check the port is open (default
8081 is used in the examples):
$ (sudo) iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp dpt:8081 Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
If not, open it:
$ (sudo) iptables -I INPUT -p tcp --dport 8081 -j ACCEPT
Please look for
fiware-cygnus tag in stackoverflow.com.