Pratik,
The 404 not found error happens if there is an error in the url or the server is not available.
check if you get anything on running 10.0.1.108:9090/ros/get_global_namespace. if not check the link(ip) or restart flytos. it works for me.

The api get global namespace is working fine getting the namespace, also the api position set is also working fine.
But I don’t understand where is the issue in velocity set api which gives response 404. I have also change the parameters as per your suggestion but still the issue remains the same.

I have restarted the simulator two to three times.
When api command is fire through the terminal the simulator gives successful response. So I don’t think the issue is regarding the server getting crash. As the get global namespace command gives the namespace in the terminal, but gives response 0 through the browser.

Pratik,
If the commands work through the terminal it means that flytos is working which will still work if the server has crashed. If server crashes sometimes the port remains occupied even after killing the flytos and you wont be allowed to use the port.
so for starters check if u get “welcome to flyt” page when you enter :9090 in address bar. if nothing then kill your flytos .
then open a new terminal and type . netstat -ap | grep :9090
You will get a list containing what is using your 9090 network port … you will need to kill those processes.

For that look something like /python in the list
the number denotes the process id.
sudo kill -9

I run the following command in the terminal when the flytsim was up, I got following response

pratik@pratik-VirtualBox:~$ netstat -ap |grep :9090(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
pratik@pratik-VirtualBox:~$

It seems that port 9090 is not assign to server, I try to check on which port the flytos is running by the following command
but does not get any idea. Following is the command and its result

I have start the flytsim simulator, its been up. Now when I run the command lsof -i :9090, it doesn’t show any information regarding the port 9090 is occupied by flytos or not.
When I call 10.0.1.108:9090 I am getting unable to connect message in the browser.
Does flytos is running on some other port than 9090?

SO now kill the flytos
open a new terminal
Start it again and when you press enter you will see a bunch of commands flowing .
In that if you see some red commands scroll up and see if it says “rostful died”

The flytos server is up, as I rstarted the flytos server its starts working. But there is an issue that I am facing now, when I call api from browser or from app its gives me successful response. But after it donen’t respond to any api.

i.e first I call the take off api it gives successful response , but then I call the land api it doesn’t response.

Takeoff is currently a synchronous call …so after pressing takeoff there would be no response till the take off is complete to the provided height… After the takeoff is complete flytos will receive and respond to all rest calls