19:36:27 #startmeeting 19:36:27 Meeting started Wed Jan 2 19:36:27 2019 UTC. The chair is sumpfralle1. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:36:27 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:36:41 It is time for our first meeting in this year! 19:37:02 #chair TheSnide h01ger bcg chteuchteu kenyon be0rn 19:37:02 Current chairs: TheSnide bcg be0rn chteuchteu h01ger kenyon sumpfralle1 19:37:06 Who is around? 19:40:25 Hi sumpfralle1, it's literally a .lock file at that location, I assume it's because it's trying to gather data. 19:40:48 and the update log keeps saying that it cant find any old data for the workstation, which doesnt make sense if it's a new entry 19:41:03 munin-node has been stopped and reset every time a change was made 19:42:24 themadmule: did your try "nc WORKSTATION munin" from the master? 19:43:47 as a command? nc isn't recognized 19:43:59 "telnet" would do the same 19:44:12 otherwise "netcat" (nc) is a good tool - maybe install it? 19:44:23 I'll check it out 19:44:33 but yes telnet is confirming a connection to the workstation 19:45:46 ok - sounds good 19:46:04 can you share your master configuration (the part containing your node descriptions) somewhere? (in a pastebin or a pad?) 19:48:58 sure: https://pastebin.com/RJj7AgLH 19:49:12 the troubled one, sys363, currently has different settings than the other two for testing 19:49:45 but even when it mirrors sys8 or sys50's config, it won't work 19:50:13 (I'm basically trying to get hundreds of workstations to report to a munin server, if such a scale is possible) 19:53:10 hundreds of nodes is possible with a good IO (due to lots of RRD files being written every five minutes) 19:53:54 The configuration looks ok. Could you also share the part of the munin-update.log, that refers to that host? 19:54:02 (or the full log) 19:58:58 regarding today's meeting: it seems like the start of the year will be a bit slow :) 19:59:01 #endmeeting