Bug #251
Exception when running the client through cron.
| Status: | Closed | Start date: | 04/09/2010 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 04/09/2010 | |
| Assignee: | % Done: | 100% | ||
| Category: | Backends | Estimated time: | 1.00 hour | |
| Target version: | 0.1.5 |
Description
2010-04-09 04:16:42 INFO Processing backend: network
Traceback (most recent call last):
File "/usr/bin/tinyids", line 34, in ?
main()
File "/usr/lib/python2.4/site-packages/TinyIDS/main.py", line 78, in main
client.run()
File "/usr/lib/python2.4/site-packages/TinyIDS/client.py", line 305, in run
self._run_backends()
File "/usr/lib/python2.4/site-packages/TinyIDS/client.py", line 147, in _run_backends
for data in b.collect():
File "/usr/lib/python2.4/site-packages/TinyIDS/backends/network.py", line 40, in collect
stdout = self.external_command(args)
File "/usr/lib/python2.4/site-packages/TinyIDS/collector.py", line 147, in external_command
p = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/usr/lib/python2.4/subprocess.py", line 550, in __init__
errread, errwrite)
File "/usr/lib/python2.4/subprocess.py", line 993, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Probably one of the commands (netstat, iptables) is not in the PATH. Use the backend configuration files by default and make it possible for the admin to ediut the paths of the commands.
Related issues
History
#1
Updated by George Notaras about 3 years ago
- Due date set to 04/09/2010
- Category set to Backends
- Status changed from New to Assigned
- Assignee set to George Notaras
- Target version set to 0.1.5
- Estimated time set to 1.00
#2
Updated by George Notaras about 3 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Should not happen again with the improved backend API.
#3
Updated by George Notaras about 3 years ago
- Status changed from Resolved to Closed
