Sorry if it wasn't clear, the example output I wrote was from triggering just one of the servers that controls my mount and camera for the telescope. I can run one of two servers fine, but running the second one shows binding errors regardless of port
Read More...
I have a setup with a single linux computer where I try to run two indi servers at once, one for the telescope and one for indi-allsky. When running both, I get the following output regardless of what port I try to use
```
observatory@observatorymaster:~$ indiserver -v -p 1234 indi_eqmod_telescope -p 7626 indi_canon_ccd
2024-04-06T23:40:51: startup: indiserver -v -p 1234 indi_eqmod_telescope -p 7626 indi_canon_ccd
2024-04-06T23:40:51: Driver indi_eqmod_telescope: pid=6710 rfd=6 wfd=6 efd=7
2024-04-06T23:40:51: Driver -p: pid=6711 rfd=8 wfd=8 efd=9
2024-04-06T23:40:51: Driver 7626: pid=6712 rfd=10 wfd=10 efd=11
2024-04-06T23:40:51: Driver indi_canon_ccd: pid=6713 rfd=12 wfd=12 efd=13
2024-04-06T23:40:51: listening to port 1234 on fd 5
2024-04-06T23:40:51: Local server: bind: Address already in use
2024-04-06T23:40:51: good bye
```
I'm running
```
INDI Library: 2.0.7
Code 2.0.7-tgz. Protocol 1.7.
```
any ideas would be greatly appreciated!
Read More...