Error while running Veins demo scenario example

[Md Mahbubur Rasheed]

Hello everyone,

I am newbie in omnetpp and sumo. While I am trying to follow the tutorial at http://veins.car2x.org/tutorial/ , all the steps work except the final step (veins demo scenario). 

FYI, my setup is-

Mac OS X 10.8.3 , omnetpp 4.2.2, sumo 0.16, mixim 2.3, veins 2.0, python 2.7.3 

The message at omnetpp terminal is -

OMNeT++ Discrete Event Simulation  (C) 1992-2011 Andras Varga, OpenSim Ltd.
Version: 4.2.2, build: 120327-7947143, edition: Academic Public License -- NOT FOR COMMERCIAL USE
See the license for distribution terms and warranty disclaimer
Setting up Tkenv...
Loading NED files from ../../src/base: 17
Loading NED files from ../../src/modules: 73
Loading NED files from ..: 36
Loading NED files from /Users/fireball/omnetpp-4.2.2/manet/mixim/src/base: 17
Loading NED files from /Users/fireball/omnetpp-4.2.2/manet/mixim/src/modules: 73
Loading NED files from /Users/fireball/omnetpp-4.2.2/manet/mixim/examples: 36
Loading images from /Users/fireball/omnetpp-4.2.2/manet/mixim/examples/veins/bitmaps: *: 0  
Loading images from ./bitmaps: *: 0  
Loading images from ./images: *: 0  
Loading images from /Users/fireball/omnetpp-4.2.2/images: *: 0  abstract/*: 90  background/*: 4  block/*: 320  device/*: 195  maps/*: 9  misc/*: 70  msg/*: 55  old/*: 111  status/*: 28  
Plugin path: ./plugins
RUNTIME ERROR. A cRuntimeError exception is about to be thrown, and you
requested (by setting debug-on-errors=true in the ini file) that errors
abort execution and break into the debugger.
You should now probably be running the simulation under gdb or another
debugger. The simulation kernel will now raise a SIGABRT signal which will
get you into the debugger. If you are not running under a debugger, you can
still use the core dump for post-mortem debugging. Once in the debugger,
view the call stack (in gdb: "bt" command) to see the context of the
runtime error.
<!> Error in module (TraCIScenarioManagerLaunchd) scenario.manager (id=6) at event #1, t=0: Model error: TraCI server "SUMO 0.16.0" reports API version 5. This server is unsupported..
TRAPPING on the exception above, due to a debug-on-errors=true configuration option. Is your debugger ready?
./run: line 2:  2221 Abort trap: 6           opp_run -l../../src/base/miximbase -l../../src/modules/miximmodules -n"../../src/base;../../src/modules;.." "$@"

And the message at sumo-launchd.py ternimal is-

 fireball$ python sumo-launchd.py -vv -c sumo

Listening on port 9999

Connection from 127.0.0.1 on port 64732
Handling connection from 127.0.0.1 on port 64732
Got TraCI message of length 2
Got TraCI command of length 1
Got TraCI command 0x0
Got CMD_GETVERSION
Got TraCI message of length 316
Got TraCI command of length 311
Got TraCI command 0x75
Got CMD_FILE_SEND for "sumo-launchd.launch.xml"
Got CMD_FILE_SEND with data "<launch>
  <copy file="erlangen.net.xml"/>
  <copy file="erlangen.rou.xml"/>
  <copy file="erlangen.poly.xml"/>
  <copy file="erlangen.sumo.cfg" type="config"/>
  <basedir path="/Users/fireball/omnetpp-4.2.2/manet/mixim/examples/veins/"/>
  <seed value="0"/>
</launch>
"
Creating temporary directory...
Temporary dir is /var/folders/v3/lvjvq7tj2nd067lm_yyfpmfr0000gn/T/sumo-launchd-tmp-i6eUKi
Base dir is /Users/fireball/omnetpp-4.2.2/manet/mixim/examples/veins/
Seed is 0
Finding free port number...
Claiming lock on port
...found port 64733
Starting SUMO (sumo -c erlangen.sumo.cfg) on port 64733, seed 0
Connecting to SUMO (sumo -c erlangen.sumo.cfg) on port 64733 (try 1)
Error ([Errno 61] Connection refused)
Connecting to SUMO (sumo -c erlangen.sumo.cfg) on port 64733 (try 2)
Error ([Errno 61] Connection refused)
Connecting to SUMO (sumo -c erlangen.sumo.cfg) on port 64733 (try 3)
Error ([Errno 61] Connection refused)
Connecting to SUMO (sumo -c erlangen.sumo.cfg) on port 64733 (try 4)
Releasing lock on port
Starting proxy mode
Done with proxy mode
Done with proxy mode, killing SUMO
Done running SUMO
Cleaning up
Result: "<?xml version="1.0"?>
<status>
<exit-code>1</exit-code>
<start>1364094887</start>
<end>1364094891</end>
<status>Exited with error code 1</status>
<stdout><![CDATA[Loading configuration... done.
Step #0.00]]></stdout>
<stderr><![CDATA[Error: tcpip::Socket::recvAndCheck @ recv: peer shutdown
Quitting (on error).
Leaked object at 0x7fa4f3872ac0 (size 296, TraCIServer.cpp:223)
Leaked object at 0x7fa4f38fb820 (size 64, 0x10fa0a49a)
Leaked object at 0x7fa4f38af9c0 (size 64, 0x10fa0a49a)
Leaked object at 0x7fa4f386bcf0 (size 64, 0x10fa0a49a)
Leaked object at 0x7fa4f386d7d0 (size 64, 0x10fa0a49a)
Leaked object at 0x7fa4f386ecc0 (size 64, 0x10fa0a49a)
Leaked object at 0x7fa4f3878710 (size 64, 0x10fa0a49a)
Leaked object at 0x7fa4f38699e0 (size 48, 0x10fa0a63b)
Leaked object at 0x7fa4f386a510 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386b200 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386ba00 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386c420 (size 48, 0x10fa0aa7c)
Leaked object at 0x7fa4f386c110 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386cce0 (size 48, 0x10fa0aa7c)
Leaked object at 0x7fa4f386cb20 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386d4e0 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f386df40 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386dbf0 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f386e8c0 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386e360 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f386f160 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f386fb20 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f386f320 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f3870500 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f3870150 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f3870f50 (size 48, 0x10fa0a967)
Leaked object at 0x7fa4f3870950 (size 48, 0x10fa0aa3c)
Leaked object at 0x7fa4f3871910 (size 24, TraCIServer.cpp:154)
Leaked object at 0x7fa4f4015080 (size 2, 0x10fa6164f)
Leaked object at 0x7fa4f3491650 (size 28, 0x10fa611a7)
*** 30 leaks found
*** WARNING:  GCC 3 or later is detected, please make sure the
    environment variable GLIBCPP_FORCE_NEW (GCC 3.2 and 3.3) or
    GLIBCXX_FORCE_NEW (GCC 3.4 and later) is defined.  Check the
    README file for details.
]]></stderr>
</status>
"
Closing connection from 127.0.0.1 on port 64732

What might go wrong?

[Christoph Sommer]

Md Mahbubur Rasheed wrote:
> While I am trying to follow the
> tutorial at http://veins.car2x.org/tutorial/ , all the steps work except
> the final step (veins demo scenario).
>

> FYI, my setup is Mac OS X 10.8.3 , omnetpp 4.2.2, sumo 0.16, mixim 2.3, veins 2.0, python 2.7.3
>
> The message at omnetpp terminal is [...]

>
> TraCI server "SUMO 0.16.0" reports API version 5. This server is unsupported..

You are using SUMO 0.16.0. This server is not supported. Please check
the tutorial at <http://veins.car2x.org/tutorial/> to see which version
to use.


Best,

Christoph

--
Dr.-Ing. Christoph Sommer
Institute of Computer Science
University of Innsbruck, Austria
Phone: +43 512 507-53285 / Fax: -53079
http://ccs.uibk.ac.at/~sommer/

[Md Mahbubur Rasheed]

Dear Dr. Sommer,

I very much appreciate your kind help and all your work.

I thought the sumo version was >=0.15. Now, it works with the sumo-0.15.0. However I find another issue while running the scenario.  The scenario doesn't look as pretty as it is in the screenshot at http://veins.car2x.org/tutorial/. Please check the following screenshots for reference-

In default mode- http://imgur.com/cfGV8wS

In debug mode- http://imgur.com/8RMoHFf

How to get the view exactly like the screenshot? Is this mac related issue?

Moreover, the view flickers, if I run other examples in sumo-gui of sumo-0.15.0. It's not the issue in sumo-0.16.0. What is wrong?

Best regards,

Md Mahbubur Rasheed

[Md Mahbubur Rasheed]

Hi,

FYI, I have just found the solution to the screen flickering (flashing) issue in sumo-gui of sumo-0.15.0 running in mac os x. The solution can be found at  http://sourceforge.net/apps/trac/sumo/ticket/688 - 

I solved this issue on SUMO 0.13.1, 0.14.0 and 0.15.0 by disabling the stereo mode in src/utils/gui/windows/GUIMainWindow.cpp, i.e., changing
myGLVisual(new FXGLVisual(a, VISUAL_DOUBLEBUFFER | VISUAL_STEREO))
in
myGLVisual(new FXGLVisual(a, VISUAL_DOUBLEBUFFER))

Please help me with the scenario related issue stated in my previous reply to this post. FYI, while running the veins demo scenario, the scenario doesn't look as pretty as it is in the screenshot at http://veins.car2x.org/tutorial/. Please check the following screenshots for reference-

In default mode- http://imgur.com/cfGV8wS

In debug mode- http://imgur.com/8RMoHFf

How to get the view exactly like the screenshot?

I very much appreciate your kind help.

Best regards,

Md Mahbubur Rasheed  

[Christoph Sommer]

Md Mahbubur Rasheed wrote:
> The scenario doesn't look as pretty as it is in the screenshot

> at http://veins.car2x.org/tutorial/ <http://veins.car2x.org/tutorial/>.

> Please check the following screenshots for reference-
>
> In default mode- http://imgur.com/cfGV8wS
> In debug mode- http://imgur.com/8RMoHFf
>
> How to get the view exactly like the screenshot?

How to get the view like in the screenshot is explained in the text
above the screenshot ("In this configuration, it is best...")


Regards,

[Md Mahbubur Rasheed]

Dear Dr.Sommer,

Thank you very much once again :) 

Best regards,

Md Mahbubur Rasheed

[Avinash Tarale]

Hello Md Mahbubur,

I am using all same configuration for omnet++, sumo and veins as mentioned in the Veins Tutorial but still I am  getting below error. Could you please help me on this.

<!> Error in module (TraCIScenarioManager) scenario.manager (id=3) at event #1, t=0: Model error: TraCI server "SUMO 0.21.0" reports API version 8. This server is unsupported

Thank you very much for your help.

Avinash

[Md Mahbubur Rasheed]

Hi Avinash,

The solution to this problem is to closely follow the versions mentions at http://veins.car2x.org/download/ ... I would recommend you to uninstall non- recommended versions and start over with the latest veins along with the prerequisite version of SUMO. I can see Veins 4 requires SUMO 0.22.0 while Veins 3 requires SUMO 0.21.0. Hopefully that would solve your problem.

Regards,

Md Mahbubur Rasheed

[Avinash Tarale]

Hello Md Mahbubur,

I am using Sumo 0.21 and Veins 3.0 as mentioned in the veins tutorials. Still getting the error.

Regards,

Avinash Tarale

--
You received this message because you are subscribed to a topic in the Google Groups "OMNeT++ Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/omnetpp/BFYLOrTbLkQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to omnetpp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Amr Abughazala]

I had several problems but what they are saying is true, trying deleting sumo-0.21.0 and for veins try to follow the steps inside the install file as well it is longer and use sudo if some of them gave errors. Just start downloading from scratch it should work

I am using Ubuntu 14.04
Omnet++4.6
Inet 2.6
Mixim 2.3
Sumo-0.21.0
Veins 3.0

Hope it will work for you

[Md Mahbubur Rasheed]

Hi,

I understand that many of you face issues while installing network and Vehicle simulators, specially in Mac OS X and Linux. I am here to assist you installing and running the example codes in your system remotely. It will save a whole lot of your time and you can focus on your simulation code instead of installation related dilemmas. Check out-

 

https://www.fiverr.com/fireball003/install-network-and-vehicle-simulators-sumo-veins-ns2

P.S. if this shameless plug is against the policy of this group, please let me know in advance.

[Odilbek Urmonov]

Did you guys tried to install new version 4.4 on omnet++ 5.0 version.

Actually, I am having this problem -> screenshot !!!

I'd be appreciated if you guys help me to sort this thing out. 

thanks, Odil