when i launch the server without oxide, it launches perfectly fine. after i install oxide, steamcmd verifies the game, says "Success! App '258550' already up to date." and then nothing else happens. everything was working fine yesterday, now all of a sudden its not working.
Server not starting with Oxide installedSolved
- 1
- 2
If you are running SteamCMD after installing Oxide, Oxide wouldn't be installed anymore. I'd suggest checking your output_log from Rust.
Wulf
If you are running SteamCMD after installing Oxide, Oxide wouldn't be installed anymore.
i havent changed the batch file at all, its been working forever until now. i didnt change anything between yesterday and now. even with the verification oxide has always been working
edit: i just now removed the steam verification from the batch file, server still starts without oxide but hangs with it.
As mentioned above, please check your output_log for errors.
There has been nothing changed with how Oxide works, it wouldn't stop working only for a single user with a minor update. If you have further details you can provide such as the logs, I'd be more than willing to take a look at your issue.
There has been nothing changed with how Oxide works, it wouldn't stop working only for a single user with a minor update. If you have further details you can provide such as the logs, I'd be more than willing to take a look at your issue.
As mentioned above, please check your output_log for errors.
There has been nothing changed with how Oxide works, it wouldn't stop working only for a single user with a minor update. If you have further details you can provide such as the logs, I'd be more than willing to take a look at your issue.
there are many log files under the logs and oxide\logs file however there is no output_log in the server directory at all.
oxide log from 7/4/2020 when the server was working: https://pastebin.com/NWuSgTe1
oxide log from 7/5/2020 when the server stopped working: https://pastebin.com/6M7R7cZt
compiler log from 7/5/2020: https://pastebin.com/QyPPhSzv
if theres an output_log file that im just not seeing, if you could point me to where it should be that would be great.
edit: the output_log file from my client install: https://pastebin.com/qVTFcKxY
as stated before there is no output_log anywhere in the server files
The output_log would be something you would have to have set in your startup script.
Ex. -logfile path/to/output_log.txt
That file is created by Rust and Unity (the engine Rust uses) and would show why it isn't starting.
Ex. -logfile path/to/output_log.txt
That file is created by Rust and Unity (the engine Rust uses) and would show why it isn't starting.
The output_log would be something you would have to have set in your startup script.
Ex. -logfile path/to/output_log.txt
That file is created by Rust and Unity (the engine Rust uses) and would show why it isn't starting.
thank you :)
heres the log: https://pastebin.com/KZEcP5hz
Did you stop the server process before looking at that file? I don't see anything that would indicate it not starting, unless the log file is incomplete.
Did you update Rust (with validate option) before updating Oxide?
Also, if you could, start as vanilla and see what version shows by using the version command.
Did you update Rust (with validate option) before updating Oxide?
Also, if you could, start as vanilla and see what version shows by using the version command.
Did you stop the server process before looking at that file? I don't see anything that would indicate it not starting, unless the log file is incomplete.
Did you update Rust (with validate option) before updating Oxide?
Also, if you could, start as vanilla and see what version shows by using the version command.
i guess its possible that the server was starting but the console wasnt showing anything and i couldnt type
also now the server is bugging out vanilla, the info at the bottom such as the players isnt showing. i tried to run server.stop but it says a server isnt running.
Protocol: 2242.196.1
Build Date: 07/04/2020 18:48:24
Unity Version: 2019.3.5f1
Changeset: 52658
Branch: release
- log file too big for pastebin: https://drive.google.com/file/d/1TfTs1tqzY5KWulu-U3djAas9VgrWbu1N/view?usp=sharing
According to that log, multiple servers are running on the same port. Are you hosting with your own machine or with a host using their control panel?
Couldn't create server on port 27015 (Startup Error)
According to that log, multiple servers are running on the same port. Are you hosting with your own machine or with a host using their control panel?Couldn't create server on port 27015 (Startup Error)
im hosting on my own machine however the only server that should be running is rust, currently i cant properly close the server due to the issues im having so the task stays open in the background causing that issue. i could end all the tasks and try again if youd like
edit: before i go to bed ill quickly remake the server and tomorrow ill let you know if anything is different
If you are only running one Rust server, open Task Manager and make sure there are no other RustDedicated processes; kill if so. When stopping the server, make sure to use "quit", as "stop" or "server.stop" doesn't actually sit the server down fully.
After you have done so, run SteamCMD with validate to make sure Rust is updated, then install the latest build of Oxide.
Then start the server and see how it does.
After you have done so, run SteamCMD with validate to make sure Rust is updated, then install the latest build of Oxide.
Then start the server and see how it does.
If you are only running one Rust server, open Task Manager and make sure there are no other RustDedicated processes; kill if so. When stopping the server, make sure to use "quit", as "stop" or "server.stop" doesn't actually sit the server down fully.
After you have done so, run SteamCMD with validate to make sure Rust is updated, then install the latest build of Oxide.
Then start the server and see how it does.
ive done that a few times already and each result is worse. please see my previous edit
If you are only running one Rust server, open Task Manager and make sure there are no other RustDedicated processes; kill if so. When stopping the server, make sure to use "quit", as "stop" or "server.stop" doesn't actually sit the server down fully.
After you have done so, run SteamCMD with validate to make sure Rust is updated, then install the latest build of Oxide.
Then start the server and see how it does.
ill actually go to bed later, i remade the server from scratch and im still getting issues. as before the info at the bottom of the console such as current/maxplayers is not showing.
log: https://pastebin.com/UBtSGSWt
i dont see any reason to test it with oxide if its broken without it. im not sure why its breaking more and more each time i start it
i tried server.stop and it said no server was running - no other processes are running - i then used quit
edit: is it possible my steamcmd is corrupt or something of the sort?
That log is showing the same thing, is that the same log? The server can't start because the port is already in use. The most common case of this is when there is another server process in the background that wasn't stopped.
The whole server startup, networking, etc. is entirely unrelated to Oxide, so it would not be the cause of the issue. In this case, the log indicates it being the port binding, which is handled by Rust.
There is no indication your server install is wrong, just something else using that same port so the server can't actually start.
The whole server startup, networking, etc. is entirely unrelated to Oxide, so it would not be the cause of the issue. In this case, the log indicates it being the port binding, which is handled by Rust.
There is no indication your server install is wrong, just something else using that same port so the server can't actually start.
Locked automatically
- 1
- 2