Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors Faced while trying to install ms-van3t under 'chroot jail' #3

Open
igs3000 opened this issue Nov 1, 2021 · 0 comments
Open

Comments

@igs3000
Copy link

igs3000 commented Nov 1, 2021

Dear Mr. Marco Malinverno,

First of all, I have to thank you and your team for providing such a quality ns-3 VANET extensions (ms-van3t ) for the ns-3 community.

I installed it and got excited with the quality of outputs of your "ns-3 - TraCI - SUMO" integrated simulations.

Excellent work. Keep up the good work.

I hope that your team will provide a Complete DSRC/WAVE/VANET Stack for ns-3.


The Issues that I faced during installing ms-van3t under chroot jail:

Of course, the actual installation procedure given by you is a good one for most of the normal installations. In fact, it is the “git” way of doing things in an elegant way. But I feel that procedure as a difficult one (even though it will do the installation automatically by your installation build script).

Anyway, I tried your ms-van3t extension and want to point out some installation issues on 32bit systems and 'chroot jail' based virtualization.

Issue 1:

The very first failure was due to the peculiar way in which the original installation is done. The standard way of installing “ms-van3t” is done through your installation script “sandbox_builder.sh“. But that script will not run under “root” privilege. (under 'chroot jail', the user normally will have root privilege only)

if [ “$EUID” -eq 0 ]; then
echo “Please do NOT run this script as root.”
exit 1
fi

Even if we disable this by commenting the above lines of the installation script, it will again fail at lines where “sudo” is called(since chroot jail will not have sudo). The installation failed even if we remove all “sudo” strings from the commands. I didn’t experiment with it further; because I decided to install it in a “plain old” and “easy” manual way.

Issue 2:
In fact, in my earlier attempt of installing it on 32 bit OS, there was a problem even after a “successful install” of ms-van3t in a 32 bit Debian 10 (Buster) host under “chroot jail”. After successful install, if we try to run a simulation with ns-3-SUMO interaction feature, then the simulation successfully start to run with opening SUMO GUI ……. But, immediately, the simulation will get terminated with the following error:

    /waf --run "v2i-areaSpeedAdvisor-lte"
    ...
    'build' finished successfully (1.334s)
    Sumo: wait for socket: 1s
    Loading configuration ... done.
    ns3.33-v2i-areaSpeedAdvisor-lte-optimized: ../src/automotive/model/ASN1/asn1-v2/per_support.c:238: 
    per_long_range_rebase: 
    
    Assertion `lb <= ub' failed.
    Command ['/home/ms-van3t/build/src/automotive/examples/ns3.33-v2i-areaSpeedAdvisor-lte-optimized'] terminated with 
    signal SIGIOT. Run it under a debugger to get more information (./waf --run <program> --gdb").

The final solution for installing ms-van3t under 64bit chroot jail.

So, I just copied all the files and folders of ms-van3t directory to ns-3.33 directory (by overwriting the src folder). Now I successfully compiled ns-3.33 along with ms-van3t. And everything is working good.

I have posted my installation procedure of ms-van3t under chroot jail at the following link :
"Installing ms-van3t under chroot jail"

It may be useful for others who try to install ms-van3t under chroot based virtualization.


The Issues that may be considered:

  1. In case, if you wish to provide support for 32Bit Systems, then you may consider the error "Assertion `lb <= ub' failed" that I got while running the simulation on a 32 bit OS. (It seems to be a problem related with "max size of the integer" under 32Bit OS )

  2. In case, if you wish to provide support for "chroot jail" based installation, then you may modify the script 'sandbox_builder.sh' or provide another script like "rootusr_builder.sh" and make the installation work on chroot jail.

Once again, thank you for the good software you provided to the community.

Charles Pandian,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant