| 1 | 1 | simandl | |
| 2 | | | |
| 3 | | | If something goes wrong, it's basically a good idea to take a look at the |
| 4 | | | logfiles. Though there's currently a minor problem concerning the logrotation |
| 5 | | | technique which will probably result in some module logs to be lost after the |
| 6 | | | logs are rotated. We'll be working at a better approach after all serious bugs |
| 7 | | | are fixed. You should try to start HotSaNIC "manually" by calling rrdtimer in |
| 8 | | | non-detached debug mode. To do so, change into the HotSaNIC installation |
| 9 | | | directory, stop any running instance of HotSaNIC ( ./rrdgraph stop) and call: |
| 10 | | | "./rdtimer Dd5". |
| 11 | | | |
| 12 | | | This starts HotSaNIC in debug-mode, outputting everything it does (not every |
| 13 | | | single bit though, but the output is quite verbose ;) ) directly to the |
| 14 | | | console. |
| 15 | | | |
| 16 | | | You can see how it initializes the modules, how they are signaled and when the |
| 17 | | | diagrams will be built. Hovever, the diagram ountput will be found in the |
| 18 | | | diagram logfile under "./var/log". |
| 19 | | | |
| 20 | | | |
