You sir, solved my problem (that was the infamous message). So thanks 1000 times! :-D

As of yesterday I got this error again.

Do I have to keep killing all the oil rigs scientists now everytime? Thats a huge pain to do and I dont like to interfere with the game

YOU ONLY HAVE TO KILL ONE, the one that spawns on the little part that pokes out. The rest are fine.

Uhm. This is weird because:

1. yes, I have seen the scientist in the spawn spot and I have killed it. Once
2. after that, I didn't had the issue anymore
3. I restarted the server due to a map update
4. I didn't had the issue whatsoever.

I checked the large oil rig to see if everything was right and it was. There was no silly scientist in the bad spaw spot. I use the BotSpawn plugin by Stenaamaroo (just for the record) so I really don't know what's going on there.

I updated the Oxide to the last release and also the server. I highly doubt it is a Facepunch thing (otherwise I should keep having the same issue again and again and I don't, I just checked it on my online server and on my local server and they both are clean).

Too bad I am not enough techie to give a better help or answer. :-(

I am checking it right in this moment and everything is smooth and by the numbers.
Yesterday I killed the funny scientist in the spawn spot, restarted the server and then I didn't touch it.

Now I went to the oil rig to check the situation and everything is going ok. I killed some scientist and nothing weird is happening.

So my educated (but technical ignorant) guess is that MAYBE it is a minor glitch in the oil rig system that can be temporarely fixed by killing that one scientist.

Come on, it's a glitch alright but not that huuuuuge one! :-D

It does not affect the game (as per my rekon) and it takes 5 minutes (to be lazy) to be solved (you don't really need to restart the server, just get rid of that guy). I might be wrong but it's really tolerable, right? ;-)

People are posting that they are having this error. Hell, I AM HAVING THIS ERROR as well and I also have 12 hourly restarts. Telling people to kill that one scientist fixes the error for a time, regardless of whos issue this is.

the thing is I did but a few minutes later it starts again

This is odd because since my last restart I did not had this issue anymore. Check my post to understand the whole thing I did. Very odd.

I was getting this before, but today it's not happening - I do a daily backup/restart so I'm guessing it stopped after last night's restart. Hopefully it's gone for good, fingers crossed.

THIS NEEDS TO BE FIXED BY RUST! This is NOT an oxide issue. Please stop telling people to go out and kill 1 scientist because its not reasonable for server owners who have daily (or even 12hr) restarts.

Just as it's not reasonable to yell to the other members of a modding community about something we can't fix either? 

@Philoludos What @Gbutome actually has posted is a copy/paste of my message... but it is true telling server owners to go out and kill a scientist on a platform on both oil rigs isnt a reasonable "fix". I mean I help run 8 servers with 12hr restarts... this wouldnt work for me and isnt reasonable... Now what I can suggest is if people are using Rust Admin is to set a consol filter to hide "SetDestination" and that will at least remove the spam so you can use console one again.

thank you @Razor14150.

@Philoludos    I repeat because people do not bother to read posts from the beginning to the end. so for the fenientants, a little reminder before there are still other messages of the type: "Why .......?".
And still sorry that you take it so bad, but in no case I raise the tone on the other players, but just a little anger towards those who do not read and do not look at the previous messages ..... I have noticed, and on other posts too, that people ask their questions without having even looked at whether the solution has already been mentioned.

It would be necessary to put the subject in resolution and to close it .....

OMG :P :(