User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
Hi s**3 m
do you have a small example, which you can post or send it
directly to me or Jakob?
Greetings, Harald
Am 13.09.21 um 22:25 schrieb Syed Şah
Sultan:
window 10 and
SUMO latest version i.e. 1.10.0
Regards
S3M
================================
Syed Shah Sultan Mohiuddin
Ph.D.
Candidate
Department
of Industrial Engineering
Yaşar
University
On Mon, 13 Sept 2021 at 23:15,
Harald Schaefer <fechsaer@xxxxxxxxx> wrote:
Hi S3M,
what kind
of system (windows/linux) are you
using?
Which
version of Sumo?
Regards,
Harald
Am 13.09.21 um 22:08 schrieb Syed Şah Sultan:
Thanks
a lot Harald for your reply.
Previously I was getting FatalTraCIError: Could not connect.
That issue has been resolved just by changing the folder. But due to some other reasons I have to change my system. I installed python and SUMO from scratch. Now after every single run I am gettingFatalTraCIError:Connection closed by SUMO.After receiving this error message, I have to restart the Kernel first to run the simulation again. I tried to generate the "log file", but it is also empty. In my code I am using traci.close(), so I don,t think this might be a problem.
Regards
S3M
================================
Syed Shah Sultan Mohiuddin
Ph.D.
Candidate
Department of Industrial Engineering
Yaşar University
On Mon, 13 Sept 2021
at 16:48, Harald Schaefer <fechsaer@xxxxxxxxx>
wrote:
Another idea:
if you run in a loop different instances of sumo
and forgot to close each instance at the end
(traci.close() ), your operating system runs out
of resources and might give at the end the message
could not open connection
/ Harald
Am 13.09.21 um 15:13 schrieb Harald Schaefer:
Hi,
you are reporting two different error messages:
First FatalTraCIError: Could not connect.
and now FatalTraCIError: connection closed by SUMO
This last error is often caused by problems with sumo (sumo crashes)
I have checked
almost everything from my side. I did not
find the reason for this issue. Then I made
a new folder and put the related file there
and tried to run the simulations from there.
It started working. But after almost 100
simulation runs, I am again having the same
FatalTraCIError: connection closed by SUMO.
After continus trying, it starts working but
just for two or three simulations. Jacob,
please could you help me.
generally, in the case of "something
works and then it did not", this will
not be due to a SUMO related issue. It
seems very unlikely that the program has
changed out of the blue.
So, places to start looking for a
resolution could be:
your code: did this change?
your environment: did something
about Python change?
your system: did you install some
update, or some major program? maybe
something with the firewall?
Your issue, as you yourself have also
observed, seems related to that
particular system. So, in order to solve
this you will have review the system and
its setup. Maybe do some rubber
duck debugging? :-) With the
information you have provided below it's
impossible to determine what caused the
error; you'll have to search for this
locally.
Greets,
Menno
On 12/09/2021 14:03, Hervé Diedie
wrote:
Forget aboutit python
it"s too Messy...use TraCI for C++
I was using sumo
version 1.7.0. I tried the
same code on another system
having sumo version 1.8.0,
the code is working
perfectly. But in my system,
till yesterday morning it was working,
but suddenly starts giving me "FatalTraCIError: Could not connect." I reinstalled the latest version of Sumo i.e. 1.10.0 but still receiving the same error message. I have reviewed the previous discussions on the subject of the same error and tried what they suggested. But no improvement.