Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore Freshrss on a clean server break fail2ban #172

Open
gwen-lg opened this issue Nov 25, 2023 · 1 comment
Open

Restore Freshrss on a clean server break fail2ban #172

gwen-lg opened this issue Nov 25, 2023 · 1 comment

Comments

@gwen-lg
Copy link

gwen-lg commented Nov 25, 2023

Describe the bug

After restoring a full backup of yunohost with freshrss app installed, fail2ban don't start.

Context

  • Hardware: dedicated server
  • YunoHost version: 11.2.5
  • I have access to my server: Through SSH | through the webadmin
  • Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • Using, or trying to install package version/branch:1.22.1~ynh1

Steps to reproduce

  • On a yunohost with freshrss, create a full backup
    sudo yunohost backup create
  • On a clean server (other server), restore the backup instead of post install
    sudo yunohost backup restore <name of backup>
  • after the backup is restored, fail2ban failed to run with error :
    • fail2ban [6382]: ERROR Failed during configuration: Have not found any log file for freshrss jail
    • fail2ban [6382]: ERROR Async configuration of server failed

Fix the problem

To fix the problem, the file /var/log/${domaine}-access.log should be re-created (or restored)

Expected behavior

The freshrss app shouldn't break the fail2ban service.
The file /var/log/${domaine}-access.log should be available

What is the best solution ?

  • add the file/var/log/${domaine}-access.log in backup ?
  • create the file if missing during restore ?
@gwen-lg gwen-lg mentioned this issue Nov 25, 2023
2 tasks
@croulibri
Copy link

croulibri commented Dec 20, 2023

Hello,
In my case, the logfile exists but FreshRSS indicate the wrong location.
In the restore script, log file is indicated at /var/log/ but the real location of the logfile is at /var/log/nginx/
A SymLink corrects this situation temporarily but a restore script correction would be better 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants