I tried running 2 with different ports, different session_store_path but the same install_path
After opening 2 server managers I always get "Internal Server Error" when I open Cars & Setups page and any race editing page of one of the server manager (seems to be the one opened later), while other pages all seem to be working properly and 2 lobbies can be started at the same time with no issue.
btw the console says
Any tips on running multiple serversCode:Panic: runtime error: invalid memory address or nil pointer dereference
V14.0 was working perfectly.
Switched to v14.2 and keep getting message: "the server seems to be unavailable"
after AC opens to car.
Tried fresh install of v14.0 and 14.2 same results.
Any ideas?
Thanks
A) Great app!
B) What do I need to do to get the "legal tyres" to show up? It the boxes are always empty, regardless of whatever car / mod I pick.
C) What do we need to do to be able to pick a fixed setup? It seems it's always locked to "No fixed setup", but I saw that under CONTENT it says "cars & setups" but then the whole description only mentions cars, so not exactly sure how to proceed here.
Thanks
This is the error message:
error msg="Could not send websocket message" error="write tcp 127.0.0.1:8772->127.0.0.1:54985: wsasend: An established connection was aborted by the software in your host machine."
I seem to remember some mod cars simply not working with the legal tyres thing. Does it work with official Kunos cars?Yeah the mod cars work otherwise just fine. But is not a big deal with the tires.
Hm, that's an interesting one. What's your hardware/software setup like? Are you using a dedicated server or hosting on a local machine? This could be caused by a firewall overstepping and blocking the port.
Thanks
Same LAN setup I have always used. Same firewall settings, same ports open.
I had to go back to v1.3.4 to get a working connection. Something in Content Manager possibly?
v 1.3.4 doesn't seem to rely on CM like updated versions
A small issuewhen the lobby restarts/jumps the session (automatically loops or use /restart_session, etc) the live timing stops working, it shows nothing but the session time count-down.
I remembered version 1.3.x did not have this issue
Thanks for the reply.Hi Jach,
Does it fix on page refresh or do you need to restart the server to get the live timing back?
We'll do some more extensive testing soon but I'm pretty sure we're not seeing this issue at all, which will make the problem difficult to track down. Using /restart_session can cause some oddities, but this shouldn't be happening when the server moves to the next session.
Thanks
time="2019-09-17T13:08:47+08:00" level=error msg="Unable to handle event: 53" error="racecontrol: could not find DriverGUID for CarID: 0"
Thanks for the reply.
I do need to stop and start the server again to get the live timing back. Refreshing the page we'll see an empty track (before refreshing we can see drivers on the map but are just static)
We get error messages on the server manager console:
(BTW these messages appear 4 times a second when "refresh_interval_ms" is set to 250ms)Code:time="2019-09-17T13:08:47+08:00" level=error msg="Unable to handle event: 53" error="racecontrol: could not find DriverGUID for CarID: 0"
After further tests I see this happens when a race ends and starts the weekend again (both automatically or /next_session. If a race has two rounds, it happens after the last round ends.
If a server only has practice, /restart_session or /next_session won't cause the problem/. Using /next_session in a qualifying to skip to rac, or /restart_session during the race won't cause it either.
i have strange error integrating stracker, my config is (linux SO):
#######
# each executable specified is run from the directory it is inside, for example,
# the command: ../stracker/stracker_linux_x86/stracker --stracker_ini stracker-default.ini
# now actually performs the following two commands:
#
# 1. cd ./stracker/stracker_linux_x86
# 2. ./stracker --stracker_ini stracker-default.ini
run_on_start: ./stracker_linux_x86/stracker --stracker_ini stracker-default.ini
# uncomment the line below for stracker on Linux
# uncomment the line below for stracker on Windows
# - ./stracker/stracker.exe --stracker_ini stracker.ini
######
but i have the following error:
!!! An Error Occurred !!!
-------------------------
Failed to initialise server manager.
Your configuration file is probably incorrect, or you haven't followed the instructions in the README properly.
Please carefully check that your options are set correctly.
Error Details
-------------------------
The error occurred attempting to: Read configuration file (config.yml)
The error more specifically is: yaml: unmarshal errors:
line 221: cannot unmarshal !!str `./strac...` into []string
-------------------------
thanks
Hi!
Looks to me like you removed part of the run on start command that needs to be there, and formatted it wrong. It should look like this:
run_on_start:
- ./stracker/stracker_linux_x86/stracker --stracker_ini stracker.ini
The preceding - is required, and the command should be on the next line with two spaces before it. .yml files are quite particular about formatting.
Thanks, hope that fixes it for you!
I am getting the following error when trying to upload a few cars:
time="2019-09-24T19:55:08-04:00" level=error msg="could not decode Car file data" error="illegal base64 data at input byte 4"
time="2019-09-24T19:55:08-04:00" level=error msg="couldn't upload file" error="illegal base64 data at input byte 4"
Can anyone help with this issue?