That is related to the permissions of Urchin and what user you are when you perform administration routines.

If you install Urchin as one user all files and processes are going to be owned by that user.  If you later run the urchinctl to start the services, they will be owned by the user you are logging in as.  This can sometimes create a problem when you install as root.  When doing so, all files and processes should be owned by "nobody."  But if you later restart the services as another user, the GUI can't always recognize the existance of the services.  This is always the case if the services are owned by root.  It is sometimes the case when random different users own the services.

It's worth it to run a ps-auxwww | grep urchin and see who owns the urchinwebd and urchin scheduler daemon.  If it's root or another user (other than the user who owns the Urchin distribution) it should be changed.

Also, you would be doing yourself a favor to add the urchin4_daemons file to your server's start up routine because it will not automatically start when the server is rebooted.

Instructions follow:

There is a startup script that is created upon installation. It is named urchin4_daemons and is located in the Urchin 4 util directory. Copy this script into the /etc/rc.d/init.d/ directory. Look at the /etc/inittab file and determine the default run level (usually 3). Then change into the /etc/rc.d/rcX.d (where X is the run level). Create symbolic links that point to /etc/rc.d/init.d/urchin4_daemons that are named S95urchin and K05urchin. (IE. ln -s ../init.d/urchin4_daemons S95urchin).

One last note about stability:
Urchin can fail if it cannot alocate enough memory to process data.  By default Urchin is only able to access a paultry 20 megs of RAM.  This can be increased from the Admin control panel.  Go to Configuration; Settings; Process Settings; Memory Usage to increase the RAM.