README.md 1.22 KB
Newer Older
1
2
3
4
5
6
# HPP-corbaserver

[![Building Status](https://travis-ci.org/humanoid-path-planner/hpp-corbaserver.svg?branch=master)](https://travis-ci.org/humanoid-path-planner/hpp-corbaserver)
[![Pipeline status](https://gepgitlab.laas.fr/humanoid-path-planner/hpp-corbaserver/badges/master/pipeline.svg)](https://gepgitlab.laas.fr/humanoid-path-planner/hpp-corbaserver/commits/master)
[![Coverage report](https://gepgitlab.laas.fr/humanoid-path-planner/hpp-corbaserver/badges/master/coverage.svg?job=doc-coverage)](http://projects.laas.fr/gepetto/doc/humanoid-path-planner/hpp-corbaserver/master/coverage/)

Florent Lamiraux's avatar
Florent Lamiraux committed
7
Corba server for Humanoid Path Planner applications.
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

# Troubleshooting

## `CORBA::TRANSIENT` when launching a server

It very often happens that the OmniNames server failed to start properly at boot.

To check if the server is running, run:
```bash
ps -C omniNames -o pid,args
```

If the process is not running, delete omniNames related log and backup files in `/var/lib/omniorb`. They may have different names on your computer, but most likely, something like:
```bash
rm /var/lib/omniORB/omninames-<computer_name>.log
rm /var/lib/omniORB/omninames-<computer_name>.bak
```
then restart the server:
```bash
sudo service omniorb4-nameserver restart
```