HFS stop responding when update dialogbox is shown on the server

[pieropingi]

All beta versions till build 253

Maybe that is not a real bug, but ...

I activate the 'Update-Auto check every day' option.
When a new build is available, a dialog box is shown asking me if I want to update, then the server stop responding.
This is not suitable for unattended servers.
Shall I uncheck the autocheckupdate option?
No way to be advised and to have HFS still responding?

[SilentPliz]

Hi !

Indeed this message block the server..

But if your server is often unattended, it might be more appropriate for you to disable checking daily updates ... and do it manually whenever you can. (a beta version might have a bug that renders your server instable)

Edit :

If you check the automatic update, there is no message ... the update is ... Automatic.



 

[SilentPliz]

Edit above

[rejetto]

SP, are you confirming this problem?
i ask because in my tests hfs is not stopping when the dialog is displayed.

[SilentPliz]

HFS is OK

There is no bug ... pieropingi had not checked the correct options probably.

[rejetto]

i asked you because you said "Indeed this message block the server.."
from which i understand you are confirming the problem.
let me know.

[pieropingi]

Thanks for the answer, the support, and for HFS, of course.

I'm using the beta version because of his management of users access, that is much easyer as the last stable version. Moreover, my server is often unattended, but for a restricted non-professional use: the kids of a skatebord-team download his video-clips.

SP, can you tell me the right options to have the message and the server work toghether? Or you are telling me to stop the auto-check message, as in your preceding post (or to do auto-updates)?

Thanks, anyway.

[SilentPliz]

@rejetto

Sorry, shame on me... I did not check, I thought the message halted server activity.

I correct:
The server continues to function when the message is displayed.


@pieropingi

For me, the server continues to function when the message is displayed.

Try to check these 3 options:

- Auto check every day
- Keep old version
- Update from official to beta versions

Keep us informed.

[rejetto]

@pieropingi
please double check it: your problem may only seems related to that dialog.
indeed, both me and SP checked ourselves, and HFS continues serving while the dialog is on screen.

[pieropingi]

I'll double check.
Every time the server was not responding to a request from the WAN, I'm gone to the server and found the Available update messagem, but it can be that the problem is not the message itself.
I activate the auto check again and keep you informed (see you on the next update).

I forgot: i enabled the DynDNS wizard. Perhaps the problem is there? Next time I see the problem, I'll check the local accessibility, too.

[pieropingi]

I confirm the problem.

Explanations:
I saw the Available update dialog on the HFS-server.

Working yesterday on the pc that hosts hfs server:
- I tryed addressing his browser to the dyndns litteral address: the server was responding. The dialog doesn't stop the server!
- I left the dialog open to try later, and from another pc.

Working today on another pc (WAN access):
- the server is unreachable!
- the VNC server on the same LAN is unreachable!!
It seems that the dialog stops the dyndns ip-number update (dyndns wizard). In fact I use the HFS-dyndns wizard to update the ip-number for the VNC server, too.

Later I'll go back to the server and test it again.

[rejetto]

from the information you reported i may even suppose your server machine was switched off

to assert that the dialog stops the dyndns updater you should at least check if the IP pointed by the dns differs from the one that should be.

[pieropingi]

Two pc switched off? mmmhhhh... (HFS and VNC are on two separate machines).

I'm back to the server!

I confirm.

The IP reported in the dyndns settings page is different from the actual IP showed in the router page.
Clearly, the server don't responds with the literal name, but it responds with 127.0.0.1 (dialog still visible, waiting for an answer).

The dialog don't stop the server, but dyndns IP isn't updated.
I will install a dyndns updater on my VNC server, but I hope my discovery will be useful for your excellent work.
Thanks again for HFS!

PS: I saw the change on bad dates in the folder. Now bad dates are shown, and it is possible to enter in folders with corrupted dates. Thanks.

[SilentPliz]

Clearly, the server don't responds with the literal name, but it responds with 127.0.0.1 (dialog still visible, waiting for an answer).

Maybe you use Stunnel with HFS, and a "ban" \127.0.0.1;192.168 .*.*
In this case, it's not a bug.

With Stunnel, HFS accepts only local connections.
- External connections go first by Stunnel that redistribute at HFS --

Maybe I'm wrong, but I think that's your trouble.

[rejetto]

The dialog don't stop the server, but dyndns IP isn't updated.
I will install a dyndns updater on my VNC server, but I hope my discovery will be useful for your excellent work.

ok. bug reproduced finally, and noted.
i'll let you know when it's fixed.
you can click "notify" on this topic if you wish.

PS: I saw the change on bad dates in the folder. Now bad dates are shown, and it is possible to enter in folders with corrupted dates. Thanks.

i needed a feedback about it. thank you.