Hey @dosch,
It appears to have failed on this step:
Where you can see the corresponding failure:
2019-08-05 17:15:08,192: WARNING - Aug 05 17:13:32 mijn.dosch.nl systemd[1]: Starting Fail2Ban Service…
2019-08-05 17:15:08,192: DEBUG - + local exit_code=1
2019-08-05 17:15:08,192: WARNING - Aug 05 17:13:32 mijn.dosch.nl fail2ban-client[21729]: ERROR No file(s) found for glob /var/log/fail2ban.log
2019-08-05 17:15:08,192: DEBUG - + ‘[’ 1 -eq 0 ‘]’
2019-08-05 17:15:08,193: WARNING - Aug 05 17:13:32 mijn.dosch.nl fail2ban-client[21729]: ERROR Failed during configuration: Have not found any log file for recidive jail
2019-08-05 17:15:08,193: DEBUG - + trap ‘’ EXIT
2019-08-05 17:15:08,193: WARNING - Aug 05 17:13:32 mijn.dosch.nl systemd[1]: fail2ban.service: Control process exited, code=exited status=255
2019-08-05 17:15:08,194: DEBUG - + set +eu
2019-08-05 17:15:08,194: WARNING - Aug 05 17:13:32 mijn.dosch.nl systemd[1]: Failed to start Fail2Ban Service.
So you might want to investigate your fail2ban configuration. What does:
$ systemctl status fail2ban
Tell you? Does /var/log/fail2ban.log exist?
You could maybe go ahead and raise this issue on the issue tracker of the nextcloud repository to see if there is something that the upgrade script can do this in this case: Issues · YunoHost-Apps/nextcloud_ynh · GitHub.
But I’m not sure.