Error with the Lan Manager service

Configuration
21

Perfect, I voted for it

22

Yes, the scan timeout — the error I’m getting comes from the timeout, and I have the impression that the nmap command takes longer to execute from the Gladys plugin than when run directly on the container.
All the more so because before adding this timeout I could find my devices on the network.

So I think that for cases like mine, making it configurable (leaving 30s as the default) could help, at least to rule out this possibility.

23

Otherwise we can just increase the timeout to 45 seconds; I don’t see any problem with that.

24

Well, I ended up bringing up a fresh Gladys instance on another server, same problem.
So this time it’s clear: it’s indeed the timeout that’s breaking the plugin for me.

What should I do to get the timeout increased in a future release?
If possible, 1 minute rather than 30 or 45 seconds, please

25

If you’re comfortable with GitHub, you can make a Pull Request to change the variables here: Gladys/server/services/lan-manager/lib/lan-manager.constants.js at master · GladysAssistant/Gladys · GitHub

26

I created a PR here :

It was really a change that took me a second :smiley:

27

It’s merged, it will be included in the next version of Gladys!

28

Thank you very much!
No, I’m not at all comfortable with GitHub unfortunately, I’d really like to 


1 Like
29

@pierre-gilles I just tested on version 4.40, everything is OK!
Thank you very much

2 Likes
30

Great, glad to see that 4.40 fixed your issue!

I’m closing this thread :slight_smile:

1 Like