unstatic

Members
  • Posts

    13
  • Joined

  • Last visited

Posts posted by unstatic

  1. On 1/14/2022 at 3:29 PM, Jaska said:

    Any idea why SteamCMD keeps crash looping every steam game? this didn't happen before latest update.

     

    Redirecting stderr to '/home/amp/Steam/logs/stderr.txt'

    ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt".

    [ 0%] Checking for available update...

    [ 0%] Download Complete.

    [----] Verifying installation...

    [ 0%] Downloading Update...

    [ 0%] Checking for available update...

    [ 0%] Download Complete.

    [----] Extracting package...

    [----] Extracting package...

    17:24:20

    [----] Extracting package...

    17:24:22

    [----] Extracting package...

    [----] Installing update...

    [----] Cleaning up...

    [----] Failed to remove temporary unzip folder, continuing anyway

    [----] Update complete, launching...

     

    i'm having the same problem... any idea what could it be?

  2. On 12/13/2020 at 12:15 PM, ich777 said:

    I have to look this up and try this myself. I will report back, can you try to delete the cronjob and add it again?

    I've updated the container yesterday with a newer rsync version.

    nope, still not working... any idea? is there an alternative way to trigger the cron job? from unraid maybe?

  3. On 11/3/2020 at 8:17 PM, ich777 said:

    Sorry for the late answer...

    Problem now solved and tested... ;)

    Please update the container itself and it should work just fine.

     

    Keep in mind that you have to do the sync manually for the first time, after that the cronjob will work (also there will be no display output - luckySync does it this way, you can only check the logs -> LUCKYBACKUPDIR/.luckBackup/logs/NAMEOFTHEJOB-DATE.log)

    Hi ich777, the cron stop working after a few days, don´t have a clue to what happened. Is there anything i can do, manually works fine but the cron is not working.

  4. On 11/3/2020 at 8:17 PM, ich777 said:

    Sorry for the late answer...

    Problem now solved and tested... ;)

    Please update the container itself and it should work just fine.

     

    Keep in mind that you have to do the sync manually for the first time, after that the cronjob will work (also there will be no display output - luckySync does it this way, you can only check the logs -> LUCKYBACKUPDIR/.luckBackup/logs/NAMEOFTHEJOB-DATE.log)

    Thanks man! it's working great! have a beer, me buying.

    • Like 1