Skip to main content

Troubleshooting

Verify and troubleshoot Forward Collector on Linux​

You can use the following command to verify and troubleshoot Forward Collectors running on Linux:

sudo service fwd-daemon {start|stop|status|restart}

Logs are at <installation_dir>/logs/ and <installation_dir>/.install4j/installation.log. Default installation_dir depends on the OS type and version. Some locations are as follows:

/opt/fwd/
/usr/local/fwd/

Collector crashing​

If you are seeing the Forward Collector crashing, one of the reasons could be that it's going out of memory during collection. If so, you can navigate to the SaaS Deployment Model page to get more details on how to verify the memory requirements or how to modify the memory allocation for the collector.

Collector not connected after reboot​

To automatically start the Forward Collector upon OS startup, it must be installed as a service. For more info, please see the Forward Collector Install and the Update Legacy Linux Collectors pages.