 |
Снимок экрана_2020-06-17_10-57-42.png (37,854 bytes) Снимок экрана_2020-06-17_10-57-24.png (47,279 bytes) |
|
|
tagort214: It seems we are receiving malformed JSON from the director here as the decoding throws a syntax error. We should have a look at the JSON result the director provides for the particular directory you are trying to list in webui by using bvfs API commands (https://docs.bareos.org/DeveloperGuide/api.html#bvfs-api) in bconsole. In bconsole please do the following: 1. Get the jobid of the job that causes the described issue, 142 in this example. Replace the jobid from the example below with your specific jobid(s). *.bvfs_get_jobids jobid=142 all 1,55,142 *.bvfs_lsdirs path= jobid=1,55,142 38 0 0 A A A A A A A A A A A A A A . 37 0 0 A A A A A A A A A A A A A A / 2. Navigate to the folder which causes problems by using pathid, pathids will differ at yours. *.bvfs_lsdirs pathid=37 jobid=1,55,142 37 0 0 A A A A A A A A A A A A A A . 38 0 0 A A A A A A A A A A A A A A .. 57 0 0 A A A A A A A A A A A A A A ceph/ * *.bvfs_lsdirs pathid=57 jobid=1,55,142 57 0 0 A A A A A A A A A A A A A A . 37 0 0 A A A A A A A A A A A A A A .. 56 0 0 A A A A A A A A A A A A A A groups/ * *.bvfs_lsdirs pathid=56 jobid=1,55,142 56 0 0 A A A A A A A A A A A A A A . 57 0 0 A A A A A A A A A A A A A A .. 51 11817 142 P0A V9T EHt CcR A A A 8AA BAA L4 BhLhQA BhLhP/ BhLhP/ A A C group_aa/ Let's pretend group_aa (pathid 51) is the folder we can not list properly in webui. 3. Switch to API mode 2 (JSON) now and list the content of folder group_aa (pathid 51) to get the JSON result. *.api 2 { "jsonrpc": "2.0", "id": null, "result": { "api": 2 } }*.bvfs_lsdirs pathid=51 jobid=1,55,142 { "jsonrpc": "2.0", "id": null, "result": { "directories": [ { "type": "D", "pathid": 51, "fileid": 11817, "jobid": 142, "lstat": "P0A V9T EHt CcR A A A 8AA BAA L4 BhLhQA BhLhP/ BhLhP/ A A C", "name": ".", "fullpath": ".", "stat": { "dev": 64768, "ino": 89939, "mode": 16877, "nlink": 10001, "uid": 0, "gid": 0, "user": "root", "group": "root", "rdev": 0, "size": 245760, "atime": 1630409728, "mtime": 1630409727, "ctime": 1630409727 }, "linkfileindex": 0 }, { "type": "D", "pathid": 56, "fileid": 0, "jobid": 0, "lstat": "A A A A A A A A A A A A A A", "name": "..", "fullpath": "..", "stat": { "dev": 0, "ino": 0, "mode": 0, "nlink": 0, "uid": 0, "gid": 0, "user": "root", "group": "root", "rdev": 0, "size": 0, "atime": 0, "mtime": 0, "ctime": 0 }, "linkfileindex": 0 }, { "type": "D", "pathid": 52, "fileid": 1813, "jobid": 142, "lstat": "P0A BAGIj EHt C A A A G BAA A BhLgvm Bg/+Bp Bg/+Bp A A C", "name": "d1/", "fullpath": "/ceph/groups/group_aa/d1/", "stat": { "dev": 64768, "ino": 16802339, "mode": 16877, "nlink": 2, "uid": 0, "gid": 0, "user": "root", "group": "root", "rdev": 0, "size": 6, "atime": 1630407654, "mtime": 1627381865, "ctime": 1627381865 }, "linkfileindex": 0 }, { "type": "D", "pathid": 54, "fileid": 1814, "jobid": 142, "lstat": "P0A CCEkI EHt C A A A G BAA A BhLgvm Bg/+Bp Bg/+Bp A A C", "name": "d2/", "fullpath": "/ceph/groups/group_aa/d2/", "stat": { "dev": 64768, "ino": 34097416, "mode": 16877, "nlink": 2, "uid": 0, "gid": 0, "user": "root", "group": "root", "rdev": 0, "size": 6, "atime": 1630407654, "mtime": 1627381865, "ctime": 1627381865 }, "linkfileindex": 0 } ] } }* Do you get valid JSON at this point as you can see in the example above? Please provide the output you get in your case if possible. Note: You can substitue step 3 with sth. like following if the output is too big: [root@centos7]# cat script .api 2 .bvfs_lsdirs pathid=51 jobid=1,55,142 quit [root@centos7]# cat script | bconsole > out.txt Remove everything except the JSON you received from the .bvfs_lsdirs command from the out.txt file. Validate the JSON output with a tool like https://stedolan.github.io/jq/ or https://jsonlint.com/ for example. |
|
|
Try to increase in configuration.ini: [restore] ; Restore filetree refresh timeout after n milliseconds ; Default: 120000 milliseconds filetree_refresh_timeout=220000 |
|
|
This was reported for an end-of-life (EOL) version of Bareos. If you can reproduce this bug against a currently maintained version of Bareos please feel free to open a new issue against that version at https://github.com/bareos/bareos/issues Thank you for reporting this bug and we are sorry it could not be fixed. |
- Anonymous
