×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

New All Sky camera management software: indi-allsky

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic New All Sky camera management software: indi-allsky

I have encountered this issue. Can you please elaborate more on what path needs to be written into the script and where?
Thank you
="Gonzothegreat post=90239" ]Flask command issue.
 
./setup.sh: line 1848: flask: command not found
 
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$ pip3 list | grep -i flask
Flask                  2.2.2
Flask-Login            0.6.2
Flask-Migrate          4.0.4
Flask-SQLAlchemy       3.0.3
Flask-WTF              1.1.1
heidenrod@heidenrod-obs:~/GitHubstuff/indi-allsky$
 
 
RESOLVED:
I've added the direct path to flask in the setup.sh file
Last edit: 9 months 3 days ago by Andrew.
9 months 3 days ago #94233

Please Log in or Create an account to join the conversation.

  • Posts: 264
  • Thank you received: 66

Replied by Aaron Morris on topic New All Sky camera management software: indi-allsky

That is interesting and I am not sure why this would happen.

Within the setup.sh script, it instantiates the python virtualenv, this should prepend the bin/ folder of the virtualenv to the shell's PATH environment.

You did not happen to move the cloned indi-allsky git folder, did you?
9 months 3 days ago #94234

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226

Replied by Andrew on topic New All Sky camera management software: indi-allsky

I did not move it. But I was getting warnings about some things not belonging to PATH. I can look into adding them and try again.
9 months 3 days ago #94235

Please Log in or Create an account to join the conversation.

  • Posts: 264
  • Thank you received: 66

Replied by Aaron Morris on topic New All Sky camera management software: indi-allsky

I used one of my test systems and moved the git checkout and was able to basically recreate the issue. It does not have to be the git checkout directory itself, but also any parent directory.

Usually, virtualenvs are not relocatable. I know there are some options that have allowed it in the past, but I think --relocatable has been deprecated and removed.

Your best option in this case is just fully delete the virtualenv/indi-allsky/ folder and re-run setup again to have it recreated.

Edit: I have also discovered that when the folder gets moved, it causes modules and programs to be installed in /home/username/.local/bin (also lib/ share/ and include/). These probably need to be cleaned up, as well.
Last edit: 9 months 3 days ago by Aaron Morris.
9 months 3 days ago #94237

Please Log in or Create an account to join the conversation.

  • Posts: 201
  • Thank you received: 18

Replied by Thomas Mason on topic New All Sky camera management software: indi-allsky


Saving the config and reloading fixed the problem with images not processing.
The following user(s) said Thank You: Aaron Morris
Last edit: 9 months 2 days ago by Thomas Mason.
9 months 2 days ago #94245

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 0

Replied by Pete on topic New All Sky camera management software: indi-allsky

Hi,

I'm trying to setup sync api and I'm getting the following errors on the local allsky
Aug 23 21:47:31 allsky [INFO] MainProcess/MainThread allsky._fileUploadWorkerStart() #489: Starting Upload-8 worker
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception: 
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception: KeyError: 'asset_type'
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:     if metadata['asset_type'] == constants.ASSET_IMAGE:
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:   File "/home/pfleming/indi-allsky/indi_allsky/uploader.py", line 495, in _syncapi
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:     self._syncapi(entry, metadata)
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:   File "/home/pfleming/indi-allsky/indi_allsky/uploader.py", line 456, in processUpload
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:     self.processUpload(u_dict)
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:   File "/home/pfleming/indi-allsky/indi_allsky/uploader.py", line 127, in saferun
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:     self.saferun()
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception:   File "/home/pfleming/indi-allsky/indi_allsky/uploader.py", line 99, in run
Aug 23 21:47:31 allsky [ERROR] MainProcess/MainThread allsky._fileUploadWorkerStart() #482: Upload worker exception: Traceback (most recent call last):
Aug 23 21:47:30 allsky [INFO] MainProcess/Upload-7 uploader.processUpload() #439: Upload transaction completed in 0.6129 s
Aug 23 21:47:30 allsky [INFO] MainProcess/Upload-7 boto3_s3.put() #137: File transferred in 0.5921 s (2616.13 kB/s)
Aug 23 21:47:29 allsky [INFO] MainProcess/Upload-7 generic.put() #50: Uploading /var/www/html/allsky/images/ccd_41a4d35e-cd9c-4161-a41d-b3bbcef4de84/20230823/night/23_21/ccd1_20230823_214725.jpg
Aug 23 21:47:29 allsky [INFO] MainProcess/Upload-7 generic.connect() #40: Connecting to amazonaws.com (443) as * with boto3_s3
Aug 23 21:47:29 allsky [INFO] Image-1/MainThread miscUpload.s3_upload_image() #299: Uploading to S3 bucket
Aug 23 21:47:29 allsky [INFO] Image-1/MainThread miscDb.addImage() #177: Adding image /var/www/html/allsky/images/ccd_41a4d35e-cd9c-4161-a41d-

I've updated the local by doing a git pull and running the setup script again just to make sure they were in sync. I'm also using s3 object storage.

Thanks!
8 months 1 week ago #95116

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 0

Replied by Pete on topic New All Sky camera management software: indi-allsky

Just wanted to update. Aaron fixed this in the latest code. I did a git pull and ran the setup and now things are working as expected. Thanks Aaron!

Pete
8 months 5 days ago #95219

Please Log in or Create an account to join the conversation.

  • Posts: 264
  • Thank you received: 66

Replied by Aaron Morris on topic New All Sky camera management software: indi-allsky

Sorry, I did not see this post here. This was a very specific bug that would only occur if you used S3 Object Storage and SyncAPI.
8 months 5 days ago #95221

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 1

Replied by Terry on topic New All Sky camera management software: indi-allsky

Hi all,
I've been trying to install indi-allsky on an Odroid C2 with Ubuntu 20.04. Everything goes ok until the end when I get the following error:
Collecting bottleneck (from -r /home/terryb/indi-allsky/requirements/requirements_debian11.txt (line 15))
Using cached Bottleneck-1.3.7.tar.gz (103 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error

× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: -4
╰─> [7 lines of output]
running dist_info
creating /tmp/pip-modern-metadata-9p7_1zd6/Bottleneck.egg-info
writing /tmp/pip-modern-metadata-9p7_1zd6/Bottleneck.egg-info/PKG-INFO
writing dependency_links to /tmp/pip-modern-metadata-9p7_1zd6/Bottleneck.egg-info/dependency_links.txt
writing requirements to /tmp/pip-modern-metadata-9p7_1zd6/Bottleneck.egg-info/requires.txt
writing top-level names to /tmp/pip-modern-metadata-9p7_1zd6/Bottleneck.egg-info/top_level.txt
writing manifest file '/tmp/pip-modern-metadata-9p7_1zd6/Bottleneck.egg-info/SOURCES.txt'
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.


The script exited abnormally, please try to run again...

I've tried restarting the script, tried the update indi option ....still the same.
Any ideas?
cheers
Terry
8 months 3 days ago #95264

Please Log in or Create an account to join the conversation.

  • Posts: 264
  • Thank you received: 66

Replied by Aaron Morris on topic New All Sky camera management software: indi-allsky


I have tried to reproduce this error, but I cannot. You might try to fully upgrade all packages and see if that helps.

sudo apt-get update
sudo apt-get dist-upgrade

However, I believe the bottleneck module is technically optional, so you could just comment out/delete "bottleneck" from ./requirements/requirements_debian11.txt and re-run setup.sh . Bottleneck just accelerates certain numpy functions, but everything should run without it.
8 months 3 days ago #95280

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 1

Replied by Terry on topic New All Sky camera management software: indi-allsky

Hi Aaron,,
sorry for the delay getting back......I've reinstalled ubuntu 20.04, followed your guidance, and get the following:

Downloading astroscrappy-1.1.0.tar.gz (368 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 368.5/368.5 kB 4.4 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: -4
╰─> [0 lines of output]
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: -4
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.


The script exited abnormally, please try to run again...

Hopefully you've got an idea.......
cheers
Terry
8 months 2 days ago #95296

Please Log in or Create an account to join the conversation.

  • Posts: 264
  • Thank you received: 66

Replied by Aaron Morris on topic New All Sky camera management software: indi-allsky


I have a couple of leads, but I need a little more info about your system. If you could pull down the latest code, I have a new script "./misc/support_info.sh" that will streamline gathering useful information.

I also renamed the requirements files, so you may have to restore your files to the original state.
8 months 2 days ago #95308

Please Log in or Create an account to join the conversation.

Time to create page: 1.362 seconds