Yes, github clone, just installed another copy yesterday, same result. Previous install is couple of months old (pulled on 16th of April).
Both ACS nodes are running clean install of Debian Buster. Older install is running with nodejs 12.16.2, mongodb 4.0.18, the newest install is using nodejs 12.18.2, mongodb 4.2.8.
Just uploaded a firmware file, supplied all meta data, but it was not stored into database.
This is stored in db, regarding just uploaded firmware:
use genieacs;
switched to db genieacs
db.fs.files.find();
{ “_id” : “geneos-lunar-3.13.1-R.img”, “length” : 9959172, “chunkSize” : 261120, “uploadDate” : ISODate(“2020-07-07T09:57:16.993Z”), “filename” : “geneos-lunar-3.13.1-R.img”, “md5” : “0c01d80f0ef7b992f6ffc40bba7e6a97”, “metadata” : { “fileType” : “”, “oui” : “”, “productClass” : “”, “version” : “” } }
{ “_id” : “geneos-polar-3.13.1-R.img”, “length” : 7755148, “chunkSize” : 261120, “uploadDate” : ISODate(“2020-07-07T10:25:19.638Z”), “filename” : “geneos-polar-3.13.1-R.img”, “md5” : “b1c71ba52d9e5d524b33122612f9aaeb”, “metadata” : { “fileType” : “”, “oui” : “”, “productClass” : “”, “version” : “” } }
Browser is sending all meta data in the header:
PUT /api/files/geneos-polar-3.13.1-R.img HTTP/2
Content-Type: application/octet-stream
metadata.fileType: 1 Firmware Upgrade Image
metadata.oui: 000F94
metadata.productClass: Polar
metadata.version: geneos-polar-3.13.1-R
Content-Length: 7755148
Origin: https://demobox.acs.local:443
Connection: keep-alive
Cookie: genieacs-ui-jwt=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Pragma: no-cache
Cache-Control: no-cache
TE: Trailers
How can I check how headers are handled in detail “on the other side”? What debug to enable and look into?
genieacs-ui log file only holds this, and HERE, metadata info is missing:
2020-07-07T10:05:41.044Z [INFO] admin@127.0.0.1: Upload files; id=“geneos-polar-3.13.1-R.img” metadata={“fileType”:“”,“oui”:“”,“productClass”:“”,“version”:“”}