Comment 55 for bug 1727653

>Try this then:

>sh -c "ulimit -v 1000000; ulimit -n 8192; exec /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor"

>It adds the ulimit -n call and may do what you need now that the systemd settings are in place.

I added this and the backup did not start automatically yesterday so I tried to run it manually and am getting the permission error again:

~$ sh -c "ulimit -v 1000000; ulimit -n 8192; exec /usr/lib/x86_64-linux-gnu
/deja-dup/deja-dup-monitor"
sh: 1: exec: /usr/lib/x86_64-linux-gnu: Permission denied

>Try running the command as:

>DEJA_DUP_DEBUG=1 sh -c "ulimit -v 1000000; ulimit -n 8192; exec /usr/lib/x86_64-linux-gnu
/deja-dup/deja-dup-monitor"

>This will create a large debug log in ~/.cache/deja-dup/. Please add that as an attachment to this bug report.

The above command also gives me a permission error:

~$ DEJA_DUP_DEBUG=1 sh -c "ulimit -v 1000000; ulimit -n 8192; exec /usr/lib/x86_64-linux-gnu
/deja-dup/deja-dup-monitor"
sh: 1: exec: /usr/lib/x86_64-linux-gnu: Permission denied

Trying the same command without the 'ulimit -n 8182' also gives me a permission error:

~$ DEJA_DUP_DEBUG=1 sh -c "ulimit -v 1000000; exec /usr/lib/x86_64-linux-gnu
/deja-dup/deja-dup-monitor"
sh: 1: exec: /usr/lib/x86_64-linux-gnu: Permission denied

I'm not sure what's going on now. I was getting permission errors as shown above. I tried the commands using 'su' and that did not help either. Then I tried taking my original command that would auto-start the backup and that did not error but also did not start anything. Then I tried all the commands above with the logging and that did not give the permission but it also did not create a log that I can find.