#1375 new defect

global_timeout not used from config

Reported by: hongell Owned by: nobody
Priority: normal Milestone:
Component: node Version: 2.0.17
Severity: normal Keywords: global_timeout
Cc:

Description

Setting global_timeout variable in config does not work, it still defaults to 15min.

Adding global_timeout in Munin/Node/Config?.pm seems to make it work.

my %config_variables = map { $_ => 1 } qw(

ignore_file
paranoia
timeout
global_timeout
tls
tls_ca_certificate
tls_certificate
tls_private_key
tls_verify_certificate
tls_verify_depth
tls_match

);

[root@xx]# date ; telnet localhost 4949 ; date
Thu Aug 29 12:26:05 EEST 2013
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is ']'.
# munin node at xx
moro
# Unknown command. Try cap, list, nodes, config, fetch, version or quit
Connection closed by foreign host.
Thu Aug 29 12:41:05 EEST 2013
[root@xx]#

2013/08/29-12:26:05 CONNECT TCP Peer: "127.0.0.1:39502" Local: "127.0.0.1:4949"
2013/08/29-12:41:05 [28832] Node side timeout while processing: '<waiting for input from master, previous was 'moroM'> testprint global_timeout variable is 900'

after config.pm change:

2013/08/29-12:48:12 CONNECT TCP Peer: "127.0.0.1:39504" Local: "127.0.0.1:4949"
2013/08/29-12:48:22 [29454] Node side timeout while processing: '<waiting for input from master, previous was 'moroM'> testprint global_timeout variable is 10'

Change History (0)

Note: See TracTickets for help on using tickets.