Skip to content

Script don't start before long delay when a DNS server is in line but don't send responses #332

Open
@father-mande

Description

@father-mande

Hi,
During some test ... suddenly when I select a script ... I have to wait for a long long time with some messages in the top of the left screen ... I don't remember all of them (except some humorous (I presume) like ... 42 ... and after some time and multiples messages the script start but all seems long.
I am on a local LAN with fixed I.P. ... no proxy ... but at the same time I have problem with the DNS of my Internet provider (present but not responding) and when I read the server.log at the time of the problem ... it seems that the delay is linked to a line :
[script_server.audit_utils.WARNING] Could not get hostname for 192.168.10.101 ... my box don't have a local DNS and DHCP propose only the Provider DNS servers.
when DNS works again ... (so with immediate response (unknown) on hostname request) ALL go back normal.

So clearly it's a VERY RARE case but is it possible (when we use script-server only in a local LAN) to prevent audit (or others) to request hostname to the DNS and keep only the I.P. ?

Or do you think it's another problem ? because script-server require Internet or others services to run as well ?

As I said first, it's not a common situation, so I can understand that it's absolutely not a priority ....
And for now, I don't have any idea on how reproduce this problem ...

Philippe.
N.B. to introduce me, I am a NAS package integrator (open source) and use script bash to configure applications, I have start to write a webui but it's a lot of works and so specific to each package and your tool (script-server) seem to be a very good and very easy solution (after my first try).

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions