When I check syslog I see that indiserver is re-spawning a process repeatedly after encountering an error.
I have photo and telescope simulator devices activated.
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: restart #13223
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: 2016-01-19T12:00:14: Driver –vv: execlp: No such file or directory
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: stderr EOF
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: restart #13224
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: 2016-01-19T12:00:14: Driver –vv: execlp: No such file or directory
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: stderr EOF
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: restart #13225
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: 2016-01-19T12:00:14: Driver –vv: execlp: No such file or directory
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: stderr EOF
Jan 1913:00:14 Server-Pi indiserver[27149]: 2016-01-19T12:00:14: Driver –vv: restart #13226
Hmmm, command line looks good, the problem is probably related to how you are starting the service, -vv is used as the driver name not as the switch. Maybe some linux guru will help you with service configuration Peter