REllU

Members
  • Content Count

    46
  • Joined

  • Last visited

Community Reputation

11 Good

About REllU

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Oh, I thought you found out a way to get around it somehow, and pinged me because of that. If that's the case, this really doesn't fix anything for me, since the user-scripts were already doing the same thing, kind of 😅
  2. I remember reading about having to run the job when you launch the GUI, so that the cron jobs work, so I've been doing that (y) I force updated now, and so far, it doesn't seem to be working. Might need to nuke the whole thing, and re-install the docker. I should be able to backup the profile file somewhere though, and restore it after the re-install? Setting up the profiles would be a pain in the ass to do >.< EDIT! Waaaaait! I just checked the log files from the AppData folder. It looks like the cron-jobs are working _just_ like the external script was
  3. I currently have two sets of each schedule-job, one with the console mode, and one without. Neither of them is working. I updated the container two days ago, that's the update where I got the new GUI. (Just in case, checked if there was any more updates left, and no, I'm currently at the latest version) With the latest version, I was finally able to create the cron-jobs, as previously they weren't even created succesfully. Only option left would be to start everything all over again I guess.
  4. Right so, I tried this a few times, and with a few different setups, and so far, I haven't been able to get it to run with cron It seems to me that the cron job is not even started. I've tried multiple times to add a cron job like two minutes from the current time, and I've also had one schedule at 00.05 at night, which hasn't seem to ran either. I'm having a remote server that runs UnRaid as well, and the two servers are connected with WireGuard VPN, and SSH connection within the LuckyBackup. Let me know if you got anything else to try.
  5. Just updated the container, and woop! We got ourselves a new GUI! After the update, the cron-it! button started working. I set it to run this night, so I'll report tomorrow if it worked or not. But so far, looks promising! (I also did check the "console" button in there) Thanks for keeping me in loop!
  6. Hey again, sorry for such a slow response! Been a bit busy on my end. Anyhow, here's the link to the forum post where the developer is: https://sourceforge.net/p/luckybackup/discussion/873564/thread/5eba74ae4d/ Maybe I'll see you there?
  7. I've now been in talks with the developer, and his initial thought is that there might be an issue with the file that has the info for the snapshots for GUI. He's saying that it might be possible that since the GUI is open, said file is reserved for the GUI, and cannot be edited by UnRaid running the script. Is there a way to close the GUI, while keeping the docker image running? Or is that just done by closing the remote access window? Thanks in advance!
  8. Hey again! I've reached out the developer of LuckyBackup on this, and we're trying to figure out what's happening. It looks like the snapshots of the backups are created correctly, since they do appear in their correct folders. The issue seems to be the GUI itself, as it's not seeing the snapshots (or something is not informing the GUI about the snapshots) If we find the cause for this, I'll let you know!
  9. I suppose it'd have something to do with permission issues (atleast that's what I was able to gather from a quick googling) Either way, thank you for the amazing support! I'll be doing my daily check-ins here to see when the issue gets fixed within the GUI
  10. Log: " /tmp/user.scripts/tmpScripts/AutoBackup/script: line 2: luckybackup/.luckyBackup/logs/default-LastCronLog.log: No such file or directory "
  11. Aces! That seemed to fix it, and the script seemed to run just fine! And I'm getting a log from it, which is is good for me. Only one issue I'm having now, is that it doesn't seem to mark the last backup within the "task" -> "Manage backups" So in a case of restoring a backup, it doesn't show up in the menu 🤔
  12. The log says: " Script location: /tmp/user.scripts/tmpScripts/AutoBackup/script Note that closing this window will abort the execution of this script the input device is not a TTY "
  13. Yeah, I figured the "silent" part within the script would do that, but still, I should be getting some sort of a log somewhere about this, right? Also, I tried to see within the LuckyBackup, if those backups had been made or not (from the "task" -> "manage backup" options on top, you can see the latest versions of the backups)
  14. Massive thank you for the script! I feel like I might be missing something here though, should the scrip work through "User Scripts" plugin for UnRaid? I tried to manually run the script, and it doesn't seem to be doing anything as far as I can tell 🤔 I didn't change anything from your script, as my current task within LuckyBackup is named "default" and I haven't changed the container name either.
  15. Hey, I've been checking this on daily basis. Could you explain what you meant with "cron from the host"? Is there a way to make a cron within UnRaid to run the task's within LuckyBackup, or..?