1. Hello.

    I have a very quick question that I would like answered if anyone has the time.

    I noticed that there is a LOT of Rust Oxide updates recently, the only issue is that whenever an update occurs the older version of Oxide completely breaks and stops working. I'm on Linux - Ubuntu 14.04. Meaning I have to manually redownload Oxide and grant executable permissions to the CSharpCompilers for Oxide to be able to run again.

    Is there a fix for the fact that an update completely breaks older versions or do I need to constantly keep reloading the change log page to see when an update is pushed and manually download it and grant it permissions?
     
  2. Wulf

    Wulf Community Admin

    That isn't Oxide breaking, that's permissions needing to be set by you that Linux requires. if there is an actual breakage, we'd need to know about it, but without any details provided by you there isn't much to go on. There has also been few Rust updates with Oxide lately, so I'm not sure what you're thinking about. Oxide snapshots are built for every game for every commit made, so perhaps you're thinking about that.
     
  3. In all honesty I'm not too sure what is going on either, other than the times when Oxide stops working are around the times when a change log release note is added. It has only started recently. I'm aware that I need to keep setting permissions but if I just go back and set them it doesn't work unless I download a completely fresh copy of Oxide and reset the perms again.
     
  4. Wulf

    Wulf Community Admin

    Oxide wouldn't just stop working, that would generally be an indication that it isn't installed. The CSharpCompiler permissions are set by us each build, so if it's losing those, that can be a sign that it was uploaded from a Windows machine. Nothing has changed with the compiler in many months though.
     
  5. I understand. You are correct indeed that it gets uploaded from a Windows machine, I'll attempt to download it from the actual machine.
     
  6. Wulf

    Wulf Community Admin

    I did make a commit the other day to set the permissions on startup though, but it hasn't been tested yet. So that may solve some headaches. ;)
     
  7. Ah. Ok! I'll test that too. :) Thank you for your help Wulf! I'll let you know if I have any further issues.
     
  8. The issue seems to be happening again. I am downloading it directly on the linux machine from the GitHub link.
     
  9. Wulf

    Wulf Community Admin

    I'd need details, logs, errors, etc. Literally nothing has changed with the compiler in months.
     
  10. I don't believe it is the compiler, it just doesnt load after a while.
     
  11. Wulf

    Wulf Community Admin

    Well, this thread is about the compiler. I'd need to see logs either way.
     
  12. Log files attached.
     

    Attached Files:

  13. updating your plugins would be a good start
     
  14. The plugins have been updated now, but still the core Oxide breaks/loses perms so doesnt run on the next restart.
     
  15. Wulf

    Wulf Community Admin

    I don't see any issues in your logs that are related to Oxide itself, only outdated plugins. Your compiler log shows you using a VERY OLD version of the compiler though.
     
  16. Hello. Sorry for re-opening this ticket, seeing as it is the same issue I won't make a new ticket unless you wish me to do so.

    Have you made any alterations to the default permissions of the files as this issue has started again? After 24 hours, and a restart the file stop being loaded. I have attempted to force the permissions to the user running the server, along with setting executable. However, it still stops. I have been doing the same as I have been since this issue started, but it suddenly stopped working again last week, any ideas?
     
  17. Wulf

    Wulf Community Admin

    No, the compiler has no changed in many months.
     
  18. What else has changed recently, I'm not sure it is to do with the compiler anymore, nothing to do with Oxide starts up.
     
  19. Wulf

    Wulf Community Admin

    Nothing that would prevent plugins from being compiled. The way the compiler loads and compiles hasn't been touched in probably over a year.