I have 2 fresh installs of TB 2.0 experiencing the exact same startup problem with Hudlite as it appears that it starts before Asterisk, and then fails. I have all updates in both machines. At the end of the day, I have to SSH into the root and start HUDlite manually with the following command:/etc/init.d/hudlite-server startAfter starting HUDlite it is operational and works fairly well; with PC clients having the access I was looking for. However, on a reboot, I will have the same problem. Not being a Linux guru as these board members, can some please advise me how to edit a statement at the end of the boot processes to start the HUDLite server.MUCH appreciated in advance!!!!!!Tx,Jack
HELPPP for /etc/init.d/hudlite-server start
this is a known problem. install the latest version of freePBX this has an updated script that somtimes resolves this problem. We are working on a version of HUD with a fix.
After installing freepbx 2.2.1 the HUD server is running and I manage to activate the client. However, I can't view the other extensions until I restart hudlite-server.
/etc/init.d/hudlite-server restart
Only than I can view the other extensions.
FYI
You can start asterisk and hudlite-server manually like so:
from a console enter the following commands:
chkconfig asterisk off
chkconfig ircd off
chkconfig hudlite-server off
This stops the init from starting these services when it goes to runlevel 3.
Edit the file
/etc/rc.local
and add the following lines:
amportal start
service ircd start
service hudlite-server start
This will start the services in the correct order I believe. hudlite-server needs to be able to talk to asterisk and the ircd processes to pass messages between them. I guess if they are not fully available in the correct order at startup then there might be some issues.
Rehan
Well it did the trick except that amportal start was already there..
Thx
Michael
Just received a new Fonality TrixboxCE (2.6.2.2) this week and after activating the Hudlite had about the same problem - the HUD server showed itself as started in the webgui but after most reboots it almost never allowed the PC clients to connect unless I manually did a restart of the service (/etc/init.d/hudlite-server restart)
Happy to find a working fix here relatively quickly but kind of disappointing to see this same issue has been around for 2.5+ years.
Member Since:
2006-10-24