indiwebmanager icon indicating copy to clipboard operation
indiwebmanager copied to clipboard

--conf option for Indiserver does not load expected config

Open gnthibault opened this issue 4 years ago • 1 comments

Pretty self explanatory from the title. I tried the option with my profiles.db files + some xml config for my pegasus upb driver. The profiles.db is well loaded, but I noticed that the pegasus upb driver did loaded another (default ?) xml, until I restarted indiwebmanager with the driver xml located in ~/.indi

Same goes for Losmandy Gemini driver, and maybo some other as well. I am not sure who sets the driver config location for those.

I am not sure if this is related to indiwebmanager or the driver itself ? Is there a way to force config lookup for all drivers using the --conf option of indiwebmanager ?

Thank you for your help

gnthibault avatar Dec 29 '21 23:12 gnthibault

Trying to answer myself here with a bit of info The actual fifo communication documentation from https://indilib.org/developers/deveioper-manual/92-indi-server.html :

  • To start a driver: start driver_path_name -n ["driver_name"] -c ["driver_config_path_name"] -s ["skeleton_file_path_name"]
  • To stop a driver: stop driver_path_name -n ["driver_name"]

Now the relevant part of the code: https://github.com/knro/indiwebmanager/blob/ad69a0c83686fa812fd20375e6809c3399318748/indiweb/indi_server.py#L35 and https://github.com/knro/indiwebmanager/blob/ad69a0c83686fa812fd20375e6809c3399318748/indiweb/indi_server.py#L49

I see that, although the "-n ["driver_name"]" is used, it seems that -c ["driver_config_path_name"] and -s ["skeleton_file_path_name"] are not specified.

Maybe it is specified when starting the indiserver https://github.com/knro/indiwebmanager/blob/ad69a0c83686fa812fd20375e6809c3399318748/indiweb/indi_server.py#L29

After a quick check I think the problem is there ? the --xmldir and --conf options do not seems to be propagated up to the server launch or the driver load

gnthibault avatar Jan 04 '22 20:01 gnthibault

Issue fixed simply by using the following launch cmd in my service file: ExecStart=/home/user/.local/bin/indi-web -v --xmldir /home/user/projects/RemoteObservatory/conf_files/indi_driver_xml --conf /home/user/projects/RemoteObservatory/conf_files/indi_driver_conf

gnthibault avatar Sep 05 '23 05:09 gnthibault