iServer Help

4 replies [Last post]
leighton.olds
Offline
Joined: 10 Nov 2012

Last week for some unknown reason iServer suddenly stopped working on my HAH.

It's been working fine and out of the blue just stopped.

 

Restarting it manually gets the following...

#  iServer -i br0 -d 9

 

iServer for xAP v12

Copyright (C) DBzoo 2010

[inf][init.c:98:discoverBroadcastNetwork] 2 interfaces found

[inf][init.c:102:discoverBroadcastNetwork] 1) interface: lo

[inf][init.c:102:discoverBroadcastNetwork] 2) interface: br0

[inf][init.c:109:discoverBroadcastNetwork] address: 192.168.2.100

[inf][init.c:121:discoverBroadcastNetwork] broadcast: 192.168.2.255

[ntc][init.c:55:discoverHub] Broadcast socket port 3639 in use

[inf][init.c:56:discoverHub] Assuming a hub is active

[ntc][init.c:65:discoverHub] Socket port 3640 in use

[ntc][init.c:65:discoverHub] Socket port 3641 in use

[ntc][init.c:65:discoverHub] Socket port 3642 in use

[ntc][init.c:65:discoverHub] Socket port 3643 in use

[ntc][init.c:65:discoverHub] Socket port 3644 in use

[ntc][init.c:65:discoverHub] Socket port 3645 in use

[inf][init.c:67:discoverHub] Discovered port 3646

[dbg][timeout.c:18:xapAddTimeoutAction] Add timeout. interval=60

[dbg][init.c:237:xapAddSocketListener] socket=4

Segmentation fault

 

Has anyone else come accross this or know of a fix?

leighton.olds
Offline
Joined: 10 Nov 2012
Problem Now Solved

I noticed client authentication was accidently enabled and no password was set.

Setting this to disable cured the issue.

brett
Offline
Providence, United States
Joined: 9 Jan 2010
Strange as there is logic in

Strange as there is logic in the system to detect this situation.

The iServer will die and report an error message.
https://github.com/dbzoo/hah/blob/master/userapps/hah/iServer/main.c#L777

Can you describe what you change to correct this and how your iserver.ini file looked to cause it?

Brett

leighton.olds
Offline
Joined: 10 Nov 2012
Hi Brett,My iserver.ini

Hi Brett,

My iserver.ini contained the following

[iserver]
enable=1
authmode=1
port=9996
pacing=20

The only error reported back on the web UI was

Connection Refused: check iServer is running.

Simply switching off client authentication mode cured the problem and now all is running happy again.

No clues were given when I launched iserver manually only the segmentation error I posted earlier.

 

Regards

 

Leighton

 

AttachmentSize
hah.jpg 13.45 KB
brett
Offline
Providence, United States
Joined: 9 Jan 2010
Yep my bad, I've checked in a

Yep my bad, I've checked in a commit to fix the segv.  Thx.
https://github.com/dbzoo/hah/commit/eaac7c692b3fd37928fa3697bf71d430a7f2...

Hardware Info