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!

You would need to do the following:
indiserver -p 1234 indi_eqmod_telescope && indiserver -p 7626 indi_canon_ccd

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

Your command "$ indiserver -v -p 1234 indi_eqmod_telescope -p 7626 indi_canon_ccd" is incorrect.

If you look at the output, it shows that it's trying to start a driver called '-p' and '7626'
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

Well, that's strange, I can't run 2 indiservers on different ports either.

:~/Documents/$ indiserver -p 7625 indi_simulator_focus &
[1] 25993
:~/Documents/$ 2024-04-07T04:00:22: startup: indiserver -p 7625 indi_simulator_focus

:~/Documents/$ netstat -anp | grep 7625
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:7625 0.0.0.0:* LISTEN 25993/indiserver
:~/Documents/$

:~/Documents/$ indiserver -p 7626 indi_simulator_gps &
[2] 26043
:~/Documents/$ 2024-04-07T04:00:44: startup: indiserver -p 7626 indi_simulator_gps
2024-04-07T04:00:44: Local server: bind: Address already in use
2024-04-07T04:00:44: good bye

[2]+ Exit 1 indiserver -p 7626 indi_simulator_gps
:~/Documents/$

This is version 2.0.7

:~/Documents/$ indiserver
2024-04-07T04:04:55: startup: indiserver
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 2.0.7
Code v2.0.7. Protocol 1.7.

Because you need a different socket path (-u) for the second one. You can try this:

Then you'll end up with two INDI servers on both 7624 & 8000

But are you sure you don't want chained INDI servers ?

That did the trick, thanks!

What are Chained INDI servers?