XO from source: webui lockout recover-account not working



  • hi,

    built my self a xo from source, playing around a bit.

    i am not locked out from the webUI, but i tried to ./xo-server-recover-account admin@admin.net just to see if it works, this is what happens:

    localadmin@xoa:/opt/xen-orchestra/packages/xo-server/bin$ sudo ./xo-server-recover-account admin@admin.net
    Password (leave empty for random): ********
    ✖ Cannot read property 'listingDebounce' of undefined
    TypeError: Cannot read property 'listingDebounce' of undefined
        at new metadataBackup (/opt/xen-orchestra/packages/xo-server/dist/xo-mixins/metadata-backups.js:104:62)
        at new Xo (/opt/xen-orchestra/@xen-orchestra/mixin/dist/index.js:90:29)
        at /opt/xen-orchestra/packages/xo-server/dist/recover-account-cli.js:43:16
        at Generator.next (<anonymous>)
        at asyncGeneratorStep (/opt/xen-orchestra/packages/xo-server/dist/recover-account-cli.js:18:103)
        at _next (/opt/xen-orchestra/packages/xo-server/dist/recover-account-cli.js:20:194)
        at <anonymous>
    
    

    am i doing it wrong? doing it as root gives the same message. I can change the password in the WebUI just fine.

    syslog and messages do not give me anything interesting regarding this, orchestra.log gives me this:

    2020-03-09T08:45:04.176Z app-conf /opt/xen-orchestra/packages/xo-server/config.toml
    2020-03-09T08:45:04.177Z app-conf /opt/xen-orchestra/packages/xo-server/.xo-server.toml
    2020-03-09T08:45:04.192Z xo:main INFO Configuration loaded.
    2020-03-09T08:45:04.201Z xo:main INFO Web server listening on http://[::]:1024
    2020-03-09T08:45:04.320Z xo:xo-mixins:hooks DEBUG start start…
    2020-03-09T08:45:04.372Z xo:xo-mixins:hooks WARN hook start failure: { error: 
       { Error: spawn losetup ENOENT
        at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
        at onErrorNT (internal/child_process.js:362:16)
        at _combinedTickCallback (internal/process/next_tick.js:139:11)
        at process._tickCallback (internal/process/next_tick.js:181:9)
         errno: 'ENOENT',
         code: 'ENOENT',
         syscall: 'spawn losetup',
         path: 'losetup',
         spawnargs: [ '-D' ],
         stdout: '',
         stderr: '',
         failed: true,
         signal: null,
         cmd: 'losetup -D',
         timedOut: false,
         killed: false,
         [Symbol(originalCallSite)]: [ CallSite {}, CallSite {}, CallSite {}, CallSite {} ],
         [Symbol(mutatedCallSite)]: [ CallSite {}, CallSite {}, CallSite {}, CallSite {} ] } }
    2020-03-09T08:45:04.416Z xo:xo-mixins:hooks DEBUG start finished
    
    

  • XCP-ng Team

    Hi!

    How did you install it?



  • I used this, unchanged, non root and port to 1024
    https://xen-orchestra.com/docs/from_the_sources.html
    no auto upgrades on debian

    edit:

    localadmin@xoa:/var/log$  cat /etc/debian_version
    9.11
    localadmin@xoa:/var/log$ node -v
    v8.16.1
    
    

  • XCP-ng Team

    Out of curiosity, can you post the output of node -v ? I realized the node install docs we link to only has instructions on installing node 10 and above now



  • node is still 8

    localadmin@xoa:/var/log$ node -v
    v8.16.1


  • XCP-ng Team

    Ping @julien-f


  • XO Team

    @goorooj Please, try to run xo-server-recover-account with the same user as xo-server and keep me posted.



  • Hi Julien, i already did that. localadmin is the user i also use for the xo-server. did not elaborate that further on a test system.


Log in to reply
 

XCP-ng Pro Support