Error [px4] Startup script returned with return value: 2

Hi,
I have been troubling with px4 firmware for a while with the below error.
It had been perfectly working in my pc (Ubuntu 20.04 ROS noetic)
But troubling to run with jetson nano 4gb ram (Ubuntu 18.04 ROS melodic)
I have been using the latest version v1.12.3 as well as stable version v1.11.0 . Both the versions gave same error. Can i find some help to solve this issue ?

 roslaunch px4 posix_sitl.launch 
... logging to /home/fly/.ros/log/4497a4d8-8fba-11ec-897f-7cdd90f5b1be/roslaunch-fly-desktop-24389.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://fly-desktop:46749/

SUMMARY
========

PARAMETERS
 * /gazebo/enable_ros_network: True
 * /rosdistro: melodic
 * /rosversion: 1.14.12
 * /use_sim_time: True

NODES
  /
    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)
    sitl (px4/px4)
    vehicle_spawn_fly_desktop_24389_7134471001525864433 (gazebo_ros/spawn_model)

auto-starting new master
process[master]: started with pid [24856]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 4497a4d8-8fba-11ec-897f-7cdd90f5b1be
process[rosout-1]: started with pid [24938]
started core service [/rosout]
process[sitl-2]: started with pid [25090]
Creating symlink /home/fly/PX4-Autopilot/build/px4_sitl_default/etc -> /home/fly/.ros/etc

______  __   __    ___ 
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [px4] Calling startup script: /bin/sh etc/init.d-posix/rcS 0
process[gazebo-3]: started with pid [25091]
INFO  [init] found model autostart file as SYS_AUTOSTART=10016
INFO  [param] selected parameter default file eeprom/parameters_10016
[param] parameter file not found, creating eeprom/parameters_10016
process[gazebo_gui-4]: started with pid [25110]
  SYS_AUTOCONFIG: curr: 0 -> new: 1
process[vehicle_spawn_fly_desktop_24389_7134471001525864433-5]: started with pid [25120]
  SYS_AUTOSTART: curr: 0 -> new: 10016
  CAL_ACC0_ID: curr: 0 -> new: 1310988
  CAL_GYRO0_ID: curr: 0 -> new: 1310988
  CAL_ACC1_ID: curr: 0 -> new: 1310996
  CAL_GYRO1_ID: curr: 0 -> new: 1310996
  CAL_ACC2_ID: curr: 0 -> new: 1311004
  CAL_GYRO2_ID: curr: 0 -> new: 1311004
* CAL_MAG0_ID: curr: 0 -> new: 197388
* CAL_MAG1_ID: curr: 0 -> new: 197644
* SENS_BOARD_X_OFF: curr: 0.0000 -> new: 0.0000
* SENS_DPRES_OFF: curr: 0.0000 -> new: 0.0010
* SYS_AUTOCONFIG: curr: 1 -> new: 0
* IMU_INTEG_RATE: curr: 200 -> new: 250
INFO  [simulator] Waiting for simulator to connect on UDP port 14560
[ INFO] [1645079080.309488242]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1645079080.339203602]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1645079080.516895699]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1645079080.525310213]: waitForService: Service [/gazebo_gui/set_physics_properties] has not been advertised, waiting...
[INFO] [1645079081.262275, 0.000000]: Loading model XML from file /home/fly/catkin_ws/src/sitl_gazebo/models/iris/iris.sdf
[INFO] [1645079081.325793, 0.000000]: Waiting for service /gazebo/spawn_sdf_model
[INFO] [1645079082.875505, 0.000000]: Calling service /gazebo/spawn_sdf_model
[ INFO] [1645079082.879125380]: waitForService: Service [/gazebo/set_physics_properties] is now available.
[INFO] [1645079083.495318, 0.004000]: Spawn status: SpawnModel: Successfully spawned entity
[ INFO] [1645079083.565835192, 0.004000000]: Physics dynamic reconfigure ready.
[vehicle_spawn_fly_desktop_24389_7134471001525864433-5] process has finished cleanly
log file: /home/fly/.ros/log/4497a4d8-8fba-11ec-897f-7cdd90f5b1be/vehicle_spawn_fly_desktop_24389_7134471001525864433-5*.log
^C[gazebo_gui-4] killing on exit
[sitl-2] killing on exit
[gazebo-3] killing on exit
ERROR [px4] Startup script returned with return value: 2
Segmentation fault (core dumped)
[gazebo_gui-4] escalating to SIGTERM
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done

Thanks in advance