New install does not load logs or perform backups

mauzilla

@danp it's the exact same

mauzilla

root@XO:/# node -v
v14.16.1

Danp

@mauzilla said in New install does not load logs or perform backups:

it's the exact same

Not always. For example, this is what I get with my install --

danpollak@ubuntuxo:~$ node -v
v14.16.0
danpollak@ubuntuxo:~$ nodejs -v
v10.19.0

mauzilla

@danp sorry, I did not mean the binaries are the exact same, I meant the 2 versions are the exact same

olivierlambert

@mauzilla Have you clicked on "Update" in XOA view?

mauzilla

@olivierlambert, update sorted it, 2 things I noticed was that logs worked out of the box, and I was able to start the backup. For reference, it's the exact same NFS config as on the sources version

olivierlambert

Okay good, so it could be your install/configuration in your VM

mauzilla

@olivierlambert said in New install does not load logs or perform backups:

your

I guess it can only be that. The 2nd VM is a clean Debian 10.9 build, nothing else installed or configured and steps taken exactly from the sources documentation. I can reproduce this on the 1st install as well, doing the exact same result. If something else needs to be configured we would have no insight on that. Are there logs I can look at to try and decipher what could be causing this?

olivierlambert

Hmm in theory a fresh install following the doc should work. I would start simple with everything started as root to be sure it's not a permission issue. Also can you create users in the UI? (to rule out a redis issue)

mauzilla

@olivierlambert said in New install does not load logs or perform backups:

is issue)

You are right, this seems to be a permission issue. I have started the application as root and am now able to see the logs and can also start the backup service.

I have both the XOA and this appliance open and looking at network in console to see if I can pick up which service is failing. From what I can gather (on the backups overview page), on the XOA appliance I am getting a 200 result for the service that returns the below data, however, on the sources version this output / AJAX call returns the internal 500. The backup service however is "created", I can see it in the dashboard, but as there is an internal 500 this in return causes a Javascript error in console which then stops any further Javascript from working (so the backup service "might" work but by the time I click backup the error has already occurred and I take it the backup service don't run as the event cannot complete.

{"data":{"mode":"delta","reportWhen":"failure"},"id":"1619027558357","jobId":"0d38484d-8e9b-4cbf-922b-7b616a073b94","jobName":"TestBackup","message":"backup","scheduleId":"ed9330bd-e4d3-466b-9bf5-110e9e7f57bf","start":1619027558357,"status":"success","infos":[{"data":{"vms":["12f93d7b-8d9a-a72b-6217-f8026d2d7128"]},"message":"vms"}],"tasks":[{"data":{"type":"VM","id":"12f93d7b-8d9a-a72b-6217-f8026d2d7128"},"id":"1619027558781","message":"backup VM","start":1619027558781,"status":"success","tasks":[{"id":"1619027558794","message":"snapshot","start":1619027558794,"status":"success","end":1619027568034,"result":"53cd86e5-7e16-0de8-3997-2a1e255a25d6"},{"data":{"id":"0d201925-80e5-4be5-8f3e-9d66b8589957","isFull":true,"type":"remote"},"id":"1619027570228","message":"export","start":1619027570228,"status":"success","tasks":[{"id":"1619027570230","message":"transfer","start":1619027570230,"status":"success","end":1619027860051,"result":{"size":6848896000}},{"id":"1619027860058","message":"merge","start":1619027860058,"status":"success","end":1619027860058,"result":{"size":0}}],"end":1619027860058}],"end":1619027860083}],"end":1619027860084}

For reference, the Javascript error in console following the internal 500:

index.js:238 SyntaxError: Unexpected token u in JSON at position 0
    at JSON.parse (<anonymous>)
    at r.default (_parseNdJson.js:14)
    at index.js:1998
    at Generator.next (<anonymous>)
    at le (index.js:2856)
    at i (index.js:2856)

olivierlambert

I don't know about this error, maybe @badrAZ will.

mauzilla

@olivierlambert said in New install does not load logs or perform backups:

now abo

I assume the error itself refers to the fact that the JSON parser could not decode "Internal error" as valid JSON, which then in return leads to the rest of the following Javascript calls to not be made. As it's permission related (we now know that), I am not sure what would cause some of the AJAX calls to work, and others return an internal 500, but it has to do with user permissions. I'll wait for feedback but glad we're getting somewhere, thank you for the help so far.

badrAZ

Hi,

This error can be triggered on parsing a non-JSON data by using JSON.parse() or JSON.parse('u').

Please install xo-cli and give me the resulted file of the bellow command.

xo-cli backupNg.getAllLogs ndjson=json:true @=<outputFilePath>

mauzilla

@badraz I installed the module but got an error about the self-signed certificate. I then opted to undo the ssl (editing the toml config file) but after that the application did not want to run at all anymore, it seems to time-out. I did a restart but no luck, it seems to only start as root now. I'm going to reconfigure the forever service to just run the application as root. Although I would prefer to run it within a user ring, I also understand that we're using the application from sources.

Given the potential of permission issues, Im going to reconfigure the application to just run as root. We're using XO from sources now due to our planned migration to XCP-NG (which we intend on getting pro support for) so in the meantime we need to test XO and ensure all features are working.

olivierlambert

You can rely on XOA for now, we can extend the trial as long you need