Error ([Errno 111] Connection refused)

193 views
Skip to first unread message

Gaurav Jotwani

unread,
Feb 4, 2015, 1:04:32 AM2/4/15
to omn...@googlegroups.com
Hello,

I am trying to run veins sample example(plexe-veins/examples/sinPlatoon). I get the following error:
I have installed plexe-veins 1.1
and SUM0 0.19
Omnet 4.6



Logging to /tmp/sumo-launchd.log
Listening on port 9999
Connection from 127.0.0.1 on port 58396
Handling connection from 127.0.0.1 on port 58396
Got TraCI message of length 2
Got TraCI command of length 1
Got TraCI command 0x0
Got CMD_GETVERSION
Got TraCI message of length 234
Got TraCI command of length 233
Got TraCI command 0x75
Got CMD_FILE_SEND for "sumo-launchd.launch.xml"
Got CMD_FILE_SEND with data "<launch>
  <basedir path="examples/sinPlatoon/sumocfg"/>
  <copy file="freeway.net.xml"/>
  <copy file="freeway.rou.xml"/>
  <copy file="freeway.sumo.cfg" type="config"/>
  <seed value="0"/>
</launch>
"
Creating temporary directory...
Temporary dir is /tmp/sumo-launchd-tmp-VyaMqA
Base dir is examples/sinPlatoon/sumocfg
Seed is 0
Finding free port number...
Claiming lock on port
...found port 60485
Starting SUMO (sumo-gui -c freeway.sumo.cfg) on port 60485, seed 0
Connecting to SUMO (sumo-gui -c freeway.sumo.cfg) on port 60485 (try 1)
Error ([Errno 111] Connection refused)
Connecting to SUMO (sumo-gui -c freeway.sumo.cfg) on port 60485 (try 2)
Error ([Errno 111] Connection refused)
Connecting to SUMO (sumo-gui -c freeway.sumo.cfg) on port 60485 (try 3)
Error ([Errno 111] Connection refused)
Connecting to SUMO (sumo-gui -c freeway.sumo.cfg) on port 60485 (try 4)
Releasing lock on port
Starting proxy mode

Michele Segata

unread,
Feb 4, 2015, 2:52:36 AM2/4/15
to omn...@googlegroups.com
Dear Gaurav,

there is no error. If you read the veins documentation
(http://veins.car2x.org/documentation/sumo-launchd/) you find

"The SUMO Traffic Control Interface (TraCI) modules for OMNeT++ come
with a small daemon to make running coupled simulations easier:
This daemon, sumo-launchd, is designed to run in the background,
listening for incoming requests. On each incoming connection, it
receives the simulation setup in XML format, then launches a separate
instance of SUMO and proxies requests between OMNeT++ and SUMO."

The daemon starts sumo and tries to connect to it. Until sumo is not
started, the daemon is not able to connect to it, clearly. So what the
launchd does is continuously trying to connect until it succeeds. In
your case the daemon succeeded at the fourth attempt (you got 3
connection refused). Your simulation should be running fine.

Best
Michele
> --
> You received this message because you are subscribed to the Google
> Groups "omnetpp" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to omnetpp+u...@googlegroups.com
> <mailto:omnetpp+u...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

--
Michele Segata, MSc

Department of Information Engineering and Computer Science
University of Trento, Italy

Institute of Computer Science
University of Innsbruck, Austria

http://ccs-labs.org/~segata/

Mkaefakdf

unread,
Nov 22, 2016, 4:59:29 AM11/22/16
to OMNeT++ Users
So if it not a problem, why the simulation crashes?
I have the same issue
BR

Amr Abughazala

unread,
Nov 22, 2016, 8:07:36 AM11/22/16
to OMNeT++ Users
Reply all
Reply to author
Forward
0 new messages