HUDlite not connecting

The same for me, no firewall. I get this error

[root@asterisk1 logs]# /usr/local/fonality/hud/hudlite-server -debug2
could not find ParserDetails.ini in PERL2EXE_STORAGE/XML/SAX
You must provide a password

Any suggestions?

edited: Just installed perl-XML-SAX.noarch and now i get only this error but no connection

You must provide a password

RE-EDITED: after a "chkconfig ircd on" and a reboot I get connected but still the same error

You must provide a password

HHello,

So let's go over the basic checks first.

1. Check that the hudlite server is running with:
ps wax | grep hudlite

and you should see a process with "hudlite-server" to verify it is running.

2. Now it is important that the IRC server is running. HUDlite uses this as a communication platform between the client and the server.

ps wax | grep irc

you should see something in the process list with "ircd" in it.

Do both of those check out? If so, here is an easy way to tell if you can connect to the IRC server running on your trixbox from the machine where the HUDlite client was installed.

Try telnetting to the same server name and server port (which is usually 6600) that you have in your HUDlite advanced connection settings. This will quickly tell you if the machine running the client can connect to the machine running HUD.

If this does not work, then do you have some strange network config setup? Can the machine running the client even see the machine running HUD? If not, then I can't be of much help. I'm not a network guy :(

If you are able to connect with telnet, please let me know and we'll go from there.

Have a great day.

Is this a clean install of trixbox? trixbox should install all the correct deps

Manually starting hudlite-server seems to get things going. I'll report back if I continue to have problems.

by senyo on 2007/1/10 16:45:16

"Manually" ? How was it being started before?

I don't know. I assumed something in the distro starts it during boot ?

HUDlite-server was not showing up in the process list. So I went to /usr/local/fonality/hud/ and ran hudlite-server. After that, the HUD client is working. I have not rebooted the server since so I don't know if hudlite-server will come up on it's own or not. I'll play with that a bit this evening.

This was a fresh install of Trixbox 2.0 but there were a couple false starts with HUD. Installing from the command line as listed in help-trixbox. That didn't work so I then added the admin paackage from the trixbox package menu. When that still didn't get HUD up I removed both packages and reinstalled the admin package as kerryg recently posted. If I have time this evening I'll reinstall trixbox 2.0 from scratch ona fresh hard drive and see how things go.

I installed the latest version of the HUDlite server and Windows client. I checked the server and both processes are running. I used telenet from my client machine and I am able to make a telenet connection. Did the administration and checked the users.xml file. However, I am not able to get the client to make a connection to the server.

:HUDserver NOTICE AUTH :*** Looking up your hostname...
:HUDserver NOTICE AUTH :*** Checking Ident
:HUDserver NOTICE AUTH :*** No Ident response
:HUDserver NOTICE AUTH :*** Found your hostname

Any suggestions on what I might look at next?

Thanks, Stu...

Hello,

When the HUDlite client fails to connect, what kind of message do you receive?

Do you see anything in /usr/local/fonality/hud/logs/error.log that give us a clue on the cause to this?

Hi,

I am getting the same error in my error.log file. My server will stop running after a while as well.
I am afraid that my problem may have been that my machine is not on the network and I had to load the package manually using yum. I copied the RPM file and did a local install.
This did not add the HUD config tab into the Asterisk menu, and I am beginning to wonder if there are a number of config files that did not get built correctly.
Is there a way to add this prompt manually or am I hosed?
Thanks,
David

BTW. this is running on my desktop on a small system as a POC and am not allowed to put it on the production network. Our R&D network is not up as yet. I have my laptop and desktop tied together with a router that supplies DHCP.

Thanks dude... I was looking for these types of commands. I think there should be Heading Post for commands like this within the forum with a text box that explains what they do ;)

So I saw your post... and wham... it worked. This is what I did...

/etc/rc.d/rc3.d/S95hudlite-server stop
/etc/rc.d/rc3.d/S95hudlite-server start

waited till hudlite-server started, then

/etc/init.d/ircd start

AND EVERYTHING WAS GREAT! I could use my HudClient see all ext's, etc.
Sorry for the shout... but thats how easy.. and happy I am... now I have a fix, until a "real" one comes out :)

Thanks again
Voiper

... same problem (using Trixbox 2.2.0rc3) !! but probably solved.

debugging the hudlite-server activity, I found a strange error with reference to this file:
21250620070202-userx.xml

it is an old copy of "users.xml" (generated authomatiically), locate in the same diretory.

hudlite-server was trying to use it but finding a sort of access problem.
Solved keeping away this old file.

then, ... hudlite-server stop and start.

Now, it's perfectly working like in older installation !!! thanks :-P

I am also getting the unable to connect to your hud server due to this error in my error log: "Failed to check configuration files. Reason: Can't call method "reloadUsers" on an undefined value at PERL2EXE_STORAGE/F/Relay.pm line 326."
I not using Trixbox but am running Asterisk on a Fedora Core 3 OS. I am running HudLite-server v2.0 and the Hudlite client v1.1.160. Ircd and Hudlite-server are both running and so is Asterisk but I cannot get it to connect. I feel like my config files are setup correctly. Any help would be appreciated. Hope I didn't leave anything out. Thanks in advance for your help.

I installed new 2.0 set up. Initially, HUD worked perfectly. Then it didn't. I'm gettting the "Relay:2007-02-21 01:54:17> Failed to check configuration files. Reason: Can't call method "reloadUsers" on an undefined value at PERL2EXE_STORAGE/F/Relay.pm line 326." error too.

The only changes I remember doing between the time it was working and the time it wasn't are:
1. rebooting * box
2. plugged in new Polycom phone. Though extension had already been set up in TB. This polycom has 2 different extensions assigned to it.

Hello,

This error is usually caused by Asterisk not running at the time the HUD server first starts up. I know you said that asterisk is running, but have you tried restarting the HUD server after asterisk was already up?

Please let me know.

This issue usually comes because Asterisk is not fully started at the time the HUD server starts up. If Asterisk is running, try restarting the HUD server and see if that helps.

Please let me know.

I ran the command:
/usr/local/fonality/hud/hudlite-server stop
then,
/usr/local/fonality/hud/hudlite-server start
then,
[root@asterisk1 /]# ps wax | grep hudlite
4797 ? SNs 0:13 /usr/local/fonality/hud/hudlite-server stop
4930 pts/0 S+ 0:00 grep hudlite
then,
[root@asterisk1 /]# ps wax | grep irc
2363 ? Ss 0:00 ircd
4933 pts/0 S+ 0:00 grep irc
then,
[root@asterisk1 /]# service hudlite-server status
hudlite-server (pid 4797) is running...

Still getting the following error from error.log,
Relay:2007-03-04 23:43:00> Failed to check configuration files. Reason: Can't call method "reloadUsers" on an undefined value at PERL2EXE_STORAGE/F/Relay.pm line 326.

From server.log:
2007-03-04 23:23:04: RELAY STARTED
2007-03-04 23:23:04: relayStart> IRC connect: nick(Relay) pass(password) user(irc2asterisk_relay) ircname(IRC to Asterisk command bot) address(localhost) port(6600)
2007-03-04 23:23:04: relayStart> Asterisk connect: address(localhost) port(5038)

I have a new install of Trixbox with HUD-lite Server running.

I cannot connect my client PCs running HUD-lite
- Windows XP
- Turned off firewall just in case
- Can Telnet to HUD-Server port 6600 and see messages back from server
- Tried multiple extensions and password combos (sip###/password)
- Seemingly no errors outputted on the client

On the server
- ps awf | grep shows both the hudlite-server and the ircd processes running
- I stopped and restarted the HUD-lite Server as requested just in case ... no change
- There is no error log in /usr/local/fonality/logs, just a server.log file with no apparent errors EXCEPT it occasionally spits out a "doLink> possible failure to recognize outbound call details from extension (###) since the caller id number is missing. Channel (SIP/PSTN##_########)

As a note,
- I have downloaded the latest HUDlite client and server versions as of the time of this post.
- There are no firewalls currently between client and server (local system firewalls currently disabled to troubleshoot this problem)
- Clients and Server are connected to the same switch and are running on the same subnet.

That is about all I can say other than ... Please Help :-D

My hudlite server was only sporadically working from one reboot to another; moreoften not working than working.

It seems that it is a major problem for the hud server to start before the asterisk server; which seems to be the case more often than not. I have spent hours yesterday testing this changing only one variable at a time and determined the following which mostly was stated in separate parts above:

There was one file in /etc/asterisk/hud/ which somehow mysteriously changed its name to user.xml but should correctly be users.xml

once this was corrected, i deleted the tons of archive (04281220071216-user.xml.back) files and then was able to manually stop and restart the server successfully (as mentioned above). After that stage, i have applied the fix indicated above by indyphone:"add the following lines to the end of my /etc/rc.local file:"

/etc/init.d/hudlite-server stop
/etc/init.d/hudlite-server start

which assigns this operation after asterisk loads. After this point, the .back files begin appearing as they should do and has been no need to delete the new correct .back files further and everything has worked perfectly after approximately 20 reboots.

Hope this is useful.