Starting up and verifying Kronodoc

$ /home/kronodoc/kd40/httpd/support/start_kronodoc_web_server

You can verify that the installation has been started properly by checking the end of the Web server log file httpd/logs/error_log.

$ tail /home/kronodoc/kd40/httpd/logs/error_log
/home/kronodoc/kd342/httpd/support/start_kronodoc_web_server: Kronodoc has been started
[notice] FastCGI: process manager initialized (pid 32522)
[warn] FastCGI: server "/home/kronodoc/kd40/Kronodoc/KRONO/fcgi/kronoconf" started (pid 32523) 
[warn] FastCGI: server "/home/kronodoc/kd40/Kronodoc/KRONO/fcgi/kronodoc" started (pid 32524)
[warn] FastCGI: server "/home/kronodoc/kd40/Kronodoc/KRONO/fcgi/kronodoc" started (pid 32525)
[warn] FastCGI: server "/home/kronodoc/kd40/Kronodoc/KRONO/fcgi/kronodoc" started (pid 32526)
[notice] Apache/2.0.49 (Unix) mod_fastcgi/2.4.2 OpenSSL/0.9.7d configured -- resuming normal operations
[notice] Accept mutex: sysvsem (Default: sysvsem)
$ 

This output should contain messages about some Kronodoc and kronoconf processes started and then not immediately continue with messages of the same processes dying or other unexpected error messages.

You can now test the complete installation. Start a browser and go to the URL displayed by the installation script. For more information on using Kronodoc 5.0, please consult the Kronodoc 5.0 User Guide.