#Dedicated since last update is given loads errors and is not responsive as before

124 messages · Page 1 of 1 (latest)

warm lark
#

can i drop the log file here ?

#

if so , is this the correct directory ? is on documents/Mygames/SimBin/Raceroom dedicated /userdata/logs_dedicated ?

proper dock
#

Our servers look exactly the same, errors everywhere

#

FYI we are also unable to kick or ban members without resetting the server every session. That problem seemed to start after the last Dedi update.

#

We will keep our fingers crossed and hope you can fix it 🤞, thanks for all the hard work you do guys 💪

warm lark
#

y side logd

#

my side logs

cursive prawn
#

Yep we have the same issue but already before the last update(this bug is there for years already). If the admin panel doesn't kick or ban anymore the API also doesn't allow kicks and bans. ✌️

#

We might wanna tag @dire wasp to make sure he's aware of it. s3devHD

dire wasp
#

Thank you @cursive prawn

@proper dock @warm lark
Can you guys start the dedi with --reset and see if it still happens?

cursive prawn
#

@lusty patio ☝️

proper dock
dire wasp
#

thanks

proper dock
# dire wasp thanks

I have the file ready to send but Discord doesn't seem to want to let me send it to you.

dire wasp
#

zip it?

#

that looks like an empty file on gdrive

#

ok weirdly empty as well here

proper dock
#

give me a min 🤣

proper dock
dire wasp
#

ok and you say this happens when you kick and ban players?

#

and you do that from the vanilla interface?

proper dock
#

The yellow and red errors are there as soon as the servers start. they come up every time a session starts.
The kick and ban issue is a more recent problem for us but @cursive prawn said he has had the problem a lot longer
I think we are looking at 2 different unrelated problems unfortunately

#

Vanilla interface?

dire wasp
#

ok and --reset doesn't get rid of the process warnings?

proper dock
#

no they come up as soon as I turn a server on

dire wasp
#

what's the uptime of your server?

#

could it be in need of a reboot?

#

thinking processID / some ghost process

proper dock
#

We have 2 servers at 2 different locations on 2 different PC's

#

same problems

#

@warm lark has the same problem too

cursive prawn
proper dock
#

even after a reboot it is the same

warm lark
#

i will be on pc soon

proper dock
#

What is a Vanilla interface, you are talking to a total beginner here😂 . I just use the dedicated server from Steam

cursive prawn
proper dock
#

We have Justrace on one pc but that still uses the standard admin panel in the background. the other PC is very standard

#

@dire wasp I can give you remote access with Teamviewer to the server PC if that helps

proper dock
#

I don't know if this is relevant or useful, but the one thing all our servers probably have in common are very long banned drivers lists.

cursive prawn
#

Nope shouldn't be relevant, this bug was also present in previous community that cleared the ban list regularly.

warm lark
#

my side log C:\Users[USERNAME]\AppData\Local\Sector3_Studios_AB\logs\ @dire wasp

steel parcel
#

@lament scarab

dire wasp
#

Are the machines using the same provider by any chance?

steel parcel
#

for @proper dock he uses 2 machines, 1 is at is ip the other is away

#

i only use 1 ip 5 servers

cursive prawn
steel parcel
#

i have in UK

#

also @proper dock

#

we have separated computers , not using Nat loop or anything similar

proper dock
#

900 download and 60 upload and the other 70 down and 20 up

proper dock
#

Update: restart session is not working either now ☹️

#

@jolly steeple 👆

cursive prawn
steel parcel
#

I think I found a litle way to avoid errors.... but 1000% i myth be wrong 😉

#

what i did was just create a new server and run it for some time and even with loads drivers and see if i get a error and nothing... all good . so my 1000% felling is the servers after the update need to be deleted and new ones to replace them and no errors

#

also tested kick and works too fast now ahahha

#

🙂

#

try this @proper dock

#

turn all off

#

then make a new one copy paste and run that one and get the team on it

proper dock
#

I will try it 👍

warm lark
#

@cursive prawn @dire wasp since last night , all i did was create new servers to replace the ones i had running and then deleted them . so far so good fingers crossed

cursive prawn
#

@lusty patio if you have some time tonight could you try it?

dire wasp
#

you guys are sure you tried --reset ?

#

watch out there are two -

warm lark
#

yes i have done it and andy too yesterday and still was givin errors

#

after some time like 20 minutes or so

#

but since i did last night replaced the servers no more errrors

cursive prawn
warm lark
#

so far so good

#

🙂

#

me and Andy justt tested it

#

to make sure

proper dock
#

Yes 👍, 5 servers have been re-setup manually and no errors so far which suggests that importing any previous server settings is a bad idea.

#

Time consuming but worth the effort if the errors don’t come back 🤞

#

5 more to do now 😅

proper dock
cursive prawn
#

I'm out camping this weekend, so love to hear from you when I'm back if the bug is gone. 💪 👊

cursive prawn
proper dock
#

Update, it worked on one PC but the other is still getting the error messages 🙁

vivid bolt
#

Once I had problems with starting the server, I deleted the whole folder in documents of the server, think it starts with simbin. But make a copy or screenshots of your settings, because it is all gone when you delete that folder.

proper dock
vivid bolt
#

I saw some warnings in our server too, but it is still working

steel parcel
#

for me too. all working properly after we replaced the servers after dedi update. a few random errors but all works now 💪

warm lark
#

back to the same @kip 😦 @dire wasp

proper dock
steel parcel
vital slate
#

Not too sure, but I think you need to manually run the dedi server in CMD with --reset, it's not a steam launch option I think.. Which one did you guys do?

vivid bolt
#

It is a steam launch option

#

Checked our server yesterday, it is working since some weeks now I think. Where are your servers located? Ours is in Frankfurt/Main germany. We use Windows server 2019.

proper dock
steel parcel
#

I have done also with the --reset and after a couple hours same happen again.

steel parcel
proper dock
#

So we are back to square one 🤔
Have you looked at the additional information provided @dire wasp ?
Do you have any suggestions?
Are any updates due for the dedi that could improve things?

vivid bolt
#

How about the rest of the software? Did you try to update .net framework to newest version? Which browser do you use for the the dedi software? We use firefox, but recommended it chrome afaik.

dire wasp
#

are there any crash dmp files from dedi? next thing I think of is your dedi is either intensively banning people in a weird way, either sometimes your dedi exe might crash or not be closed properly

proper dock
# dire wasp are there any crash dmp files from dedi? next thing I think of is your dedi is e...

It has never crashed, it just comes up with errors like @steel parcel servers.
Not as many as before after manually entering all the details again.
The servers seem to be working ok apart from the error messages.
What do the error messages actually mean?

yellow: Warn:DedicatedServerProcess.Process.Start pipe still connecting
and
red: Error DedicatedServerProcess.PushToPipe connect fail
and on occasion this one
red: Error Dediserver.get.ReadServerRequest

steel parcel
#

i can drop more more log files , but there is no crashdumps from dedicated @dire wasp the tool keeps going... with the yellow and red warnings... if the problem is the bans... lets give it a go... I will save data and then... close dedicated, open and remove all bans 😊 then i will close dedicated and clean all folders from past 💪... I will launch again dedicated and even create new server and delete all others... Fresh start 💪 i will keep you updated @dire wasp

steel parcel
#

@proper dock i have cleared all bans and now testing it. Fingers crossed no more errors 😉

vital slate
#

Yeah my bad I should've just tested the --reset myself, didn't read everything and I missed the part where it was clear you did try it out

proper dock
#

So far no errors on one server and the other has:
6x yellow: Warn:DedicatedServerProcess.Process.Start pipe still connecting
and
3x red: Error DedicatedServerProcess.PushToPipe connect fail
@dire wasp What are those errors? Is it a problem connecting to the Raceroom servers?
Forgive my stupidity but I am old and not that techy 🤣

dire wasp
#

Could you guys try without any MOTD - see if you notice an improvement?

neat zealot
proper dock
vital slate
proper dock
#

Yes I tried it only on one of the servers overnight. The MOTD’s are back now.

steel parcel
#

this morning all servers gone 😒 luckily i had done a backup 😊 the dedicated opened without any server

#

motd on or off its the same. errors still same .

cursive prawn
#

@dire wasp it's getting worse.. Normally when you restart server it's fine again. But now after I restarted the server I still can't kick people.

proper dock
#

@dire wasp 0 errors on either server since update 🎉

#

So far 🤞

steel parcel
#

errors back again 😒