hi,

i installed myself a xo community edition, great tool.
worth mentioning:
when trying to make a remote for the backup, it fails with

EACCES: permission denied, mkdir '/run/xo-server'

in the webgui.

su root
mkdir /run/xo-server
chown /run/xo-server yourusernamehere:yourusernamehere

changes the error message in the gui to

Command failed: mount -t nfs 192.168.30.60:/mnt/Brutus/Remote /run/xo-server/mounts/bb4532ab-12a7-4103-9420-7847da8ca9ff -o vers=3
mount: only root can use "--options" option

when nfs-common is installed ( which should ) then i can mount the remote as root in the terminal with the command from the message.

works then, but when restarting the xo-vm the mount is gone.

i did a dirty workaround and scripting that when starting the vm.
is there a "clean" solution?

@olivierlambert
yes it was the juniper, had to search a while... and then create xoa-dl as application with tcp 8888 and add it to the zone policy of that VLAN. Juniper cli is a bitch.
works now. thank you.

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.

node is still 8

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

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

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

oh thank you, did not see that

Hi,

been playing a bit with the Backup NG, i kind of miss the possibility of doing different jobs on weekdays than on the weekend...

like for example, i want to backup a fileserver each weekday with a retention value 2 but on saturday, sunday stop that to have the network and remote storage ready for the regular backup jobs.

This is for emergency scenario, the backups on the local storage are done with snapshots.

i miss the day-of-week ( dow ) setting that i have in cron, can i make the job wth a schedule and then change the schedule in crontab?

ok, logged into linux, su root, and tried the command on the console

 mount -t nfs 192.168.30.60:/mnt/Brutus/Remote /run/xo-server/mounts/86109d77-9600-48c6-b131-0ca475cd1ad4 -o vers=3
mount.nfs: requested NFS version or transport protocol is not supported  

tried without -o vers=3 and it worked.

Hello Forum,

community edition, test system.
i was rearranging my Nas, so i disconnected the Remote i used for Backups, made a Raid10 instead of Raid5 ( speed ) and recreated the shares.
the backups were not important, was just a test.
now when i tried to reconnect the remote ( same share name, same server ) it said

remote.test
{
 "id": "bb4532ab-12a7-4103-9420-7847da8ca9ff"
}
{
 "errno": -17,
 "code": "EEXIST",
 "syscall": "mkdir",
 "path": "/run/xo-server/mounts/bb4532ab-12a7-4103-9420-7847da8ca9ff",
 "message": "EEXIST: file already exists, mkdir '/run/xo-server/mounts/bb4532ab-12a7-4103-9420-7847da8ca9ff'",
 "name": "Error",
 "stack": "Error: EEXIST: file already exists, mkdir '/run/xo-server/mounts/bb4532ab-12a7-4103-9420-7847da8ca9ff'"
} 

i destroyed the remote now and made it new, only to see

remote.test
{
  "id": "86109d77-9600-48c6-b131-0ca475cd1ad4"
}
{
  "code": 1,
  "stdout": "",
  "stderr": "mount: only root can use \"--options\" option
",
  "failed": true,
  "signal": null,
  "cmd": "mount -t nfs 192.168.30.60:/mnt/Brutus/Remote /run/xo-server/mounts/86109d77-9600-48c6-b131-0ca475cd1ad4 -o vers=3",
  "timedOut": false,
  "killed": false,
  "message": "Command failed: mount -t nfs 192.168.30.60:/mnt/Brutus/Remote /run/xo-server/mounts/86109d77-9600-48c6-b131-0ca475cd1ad4 -o vers=3
mount: only root can use \"--options\" option

",
  "name": "Error",
  "stack": "Error: Command failed: mount -t nfs 192.168.30.60:/mnt/Brutus/Remote /run/xo-server/mounts/86109d77-9600-48c6-b131-0ca475cd1ad4 -o vers=3
mount: only root can use \"--options\" option

is this expected behaviour, does the xo vm need a reboot between this operations?

@olivierlambert
yes it was the juniper, had to search a while... and then create xoa-dl as application with tcp 8888 and add it to the zone policy of that VLAN. Juniper cli is a bitch.
works now. thank you.

@olivierlambert oh so there IS something wrong on my side, thanks.
i will check with the firewall