Debugging Windows Service Startup

From Observer GigaFlow Support | VIAVI Solutions Inc.
Revision as of 16:02, 11 February 2019 by NMCM (Talk | contribs)

Jump to: navigation, search



Open Windows Task Manager.

  • Check "GigaFlow.exe" is running.
  • If so, select it and then click the "End Task" button.
  • Open up an administrator command prompt.
  • Navigate to the folder where GigaFlow.exe is located (default:c:\GigaFlow\Flow\resources). Run:
GigaFlow.exe -debug
  • The output of this should tell you what the problem is (e.g. Java not installed; no database access or some invalid parameter in the GigaFlow.ini file).

Java Problems

If Java hasn't been found, re-run the Java installer; sometimes attempts to upgrade the JRE end up removing it from the registry.

  • If you ran the full installer, the standalone java installer will be available in the dist folder (default:c:\GigaFlow\Flow\dist\jre-8*).
  • Once this has been installed, rerun the "GigaFlow.exe -debug" command to see if the problem has been resolved. If it has, press ctrl-c to stop the debug mode and then re-start the service from the windows service console.

PostgreSQL Problems

If you have a postgres error, open up the services.msc application to check that the PostgreSQL service is installed (postgresql-x64-xxx).

  • If it is, ensure that it is set to start automatically and is running.
  • If it is not installed, you can reinstall using the file in the dist folder (default:c:\GigaFlow\Flow\dist\postgresql-xxxx*).
  • The only thing you will have to set is the postgres user password, this should be "P0stgr3s_2ME".
  • When installation is complete, you can use the postgres pgAdmin tool to add the myipfix user (with password "myipfx" and superuser permissions) and a myipfix database with the owner of myipfx).
  • Please ensure that the "account disabled" tick box is clear before saving.

Other Problems

If postgres is installed but won't start, check the Windows Event Viewer and also the logs in the postgres "data\pg_logs" folder; normally there is either a bad setting or the disk is full.

When problems are rectified, you can restart the GigaFlow service to resume normal operations.