Rudder

reports keep piling up in /var/rudder/reports/ready

the debug logs are

DEBUG relayd::input::watch: inotify: "/var/rudder/reports/incoming" 
DEBUG relayd::input::watch: inotify: "/var/rudder/reports/incoming" 
DEBUG tokio_reactor::registration: scheduling Read for: 1    
DEBUG relayd::processing::reporting: skipping "/var/rudder/reports/incoming/.davfs.tmp0a8131" as it does not have a known report extension
DEBUG report{queue_id=A93F69A7282ECF15906FFEA7CD61C785}: relayd::data::runinfo: Parsed run info RunInfo {
    node_id: "08b4fff3-de3e-40a2-add9-eeafce9ab6fe",
    timestamp: 2019-08-13T16:18:32+00:00
}
DEBUG report{queue_id=A93F69A7282ECF15906FFEA7CD61C785}:node{node_id=08b4fff3-de3e-40a2-add9-eeafce9ab6fe}: relayd::processing::reporting: received: "/var/rudder/reports/incoming/2019-08-13T16:18:32+00:00@08b4fff3-de3e-40a2-add9-eeafce9ab6fe.log.gz" 
DEBUG hyper::client::connect::dns: resolving host="server"    
DEBUG hyper::client::connect::http: connecting to 192.168.43.2:443    
DEBUG tokio_reactor: adding I/O source: 8388610    
DEBUG tokio_reactor::registration: scheduling Write for: 2    
DEBUG hyper::client::connect::http: connected to Some(V4(192.168.43.2:443))    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG hyper::proto::h1::io: flushed 168 bytes    
DEBUG hyper::proto::h1::io: flushed 2194 bytes    
DEBUG hyper::proto::h1::io: read 251 bytes    
DEBUG hyper::proto::h1::io: parsed 5 headers    
DEBUG hyper::proto::h1::conn: incoming body is content-length (228 bytes)    
DEBUG hyper::proto::h1::io: read 228 bytes    
DEBUG hyper::proto::h1::conn: incoming body completed    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG hyper::client::pool: pooling idle connection for "https://server"    
DEBUG reqwest::async_impl::response: Response: '405 Method Not Allowed' for https://server/report/    
DEBUG relayd::output::upstream: Server response: Response {
    url: "https://server/report/",
    status: 405,
    headers: {
        "date": "Tue, 13 Aug 2019 16:18:33 GMT",
        "server": "Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips mod_wsgi/3.4 Python/2.7.5",
        "allow": "POST,OPTIONS,GET,HEAD,TRACE",
        "content-length": "228",
        "content-type": "text/html; charset=iso-8859-1" 
    }
}
DEBUG relayd::processing: deleted: "/var/rudder/reports/incoming/2019-08-13T16:18:32+00:00@08b4fff3-de3e-40a2-add9-eeafce9ab6fe.log.gz" 
DEBUG tokio_reactor::registration: scheduling Read for: 2    
DEBUG relayd::input::watch: listing "/var/rudder/reports/incoming" 
DEBUG hyper::proto::h1::io: read 0 bytes    
DEBUG tokio_reactor: dropping I/O source: 2    
DEBUG relayd::input::watch: listing "/var/rudder/reports/incoming"