AllskyTeam / allsky

A Raspberry Pi operated Wireless Allsky Camera
MIT License
1.15k stars 180 forks source link

Camera setting in webportal blank #293

Closed ghost closed 3 years ago

ghost commented 3 years ago

Hi All

I've installed allsky multiple times and everytime the liveview shows a broken icon and the camera setting only show the save and set default buttons.

Setup Raspberry Pi 3b+ ZWO 120MC

What I've tried so far

below is the readout from the allsky status command.

allsky.service - All Sky Camera Loaded: loaded (/lib/systemd/system/allsky.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-11-28 16:37:55 EST; 2min 35s ago Main PID: 759 (allsky.sh) Tasks: 7 (limit: 2063) CGroup: /system.slice/allsky.service ├─759 /bin/bash /home/pi/allsky/allsky.sh └─870 /home/pi/allsky/capture -angle -6 -autoexposure 1 -autogain 0 -bin 1 -brightness 50 -coolerEnabled 0 -darkframe 0 -daytimeDelay 5000 -delay 10 -exposure 10000 -filename image

Nov 28 16:40:24 allsky allsky.sh[759]: cp: missing destination file operand after 'liveview-.' Nov 28 16:40:24 allsky allsky.sh[759]: Try 'cp --help' for more information. Nov 28 16:40:29 allsky allsky.sh[759]: /home/pi/allsky/config.sh: line 69: /etc/raspap/autocam.sh: No such file or directory Nov 28 16:40:29 allsky allsky.sh[759]: jq: error: Could not open file /etc/raspap/settings_auto.json: No such file or directory Nov 28 16:40:29 allsky allsky.sh[759]: jq: error: Could not open file /etc/raspap/settings_auto.json: No such file or directory Nov 28 16:40:29 allsky allsky.sh[759]: /home/pi/allsky/scripts/darkCapture.sh: line 16: [: =: unary operator expected Nov 28 16:40:29 allsky allsky.sh[759]: jq: error: Could not open file /etc/raspap/settings_auto.json: No such file or directory Nov 28 16:40:29 allsky allsky.sh[759]: scripts/saveImageDay.sh: line 12: [: =: unary operator expected Nov 28 16:40:29 allsky allsky.sh[759]: cp: missing destination file operand after 'liveview-.' Nov 28 16:40:29 allsky allsky.sh[759]: Try 'cp --help' for more information. ~ ~

thomasjacquin commented 3 years ago

@ctreptow65 The issue may have been caused by a recent change to the code. I will do a fresh install at home to see what is causing it. In the meantime, if you want to you can use this previous version of the code and follow the instructions as usual https://github.com/thomasjacquin/allsky/archive/ae0e792eb2cde3fd881f9b7e42c6930f89253d5f.zip

ghost commented 3 years ago

Thanks that version works, awesome program

vidma commented 3 years ago

that's weird/interesting. some of my guesses:

also why do we have path different prefixes:

ghost commented 3 years ago

Until I loaded the archived version I edited the config files in the terminal. I could not find the settings json so I edited the settings_ZWO.json file. I did edit the config.sh but only to set the upload the ftp to true. Once I loaded the archive I was editing within the GUI,

Checking the logs after the 1st night of operation I can see I'm getting the ftp cert error, added the ssl-cert option to the process scripts this morning, but I am getting the allsky.sh [716] sunwait: not found

thomasjacquin commented 3 years ago

@vidma I believe I have fixed the issue. See this commit https://github.com/thomasjacquin/allsky/commit/425c90716c4b9571c64c437f56023c0958ef9d63 and this commit on the GUI code https://github.com/thomasjacquin/allsky-portal/commit/d11ca1e43914c9e2786cace9413dce92e34ce528. The issues were caused by the use of the wrong environment variable in allsky.sh and it created a side effect on this line https://github.com/thomasjacquin/allsky/blob/master/gui/install.sh#L61

It seems to work on my home camera. Let me know if you see a problem with those changes.

vidma commented 3 years ago

yes, @thomasjacquin , makes sense.

ghost commented 3 years ago

Great job, re-installed via the instructions and now it works..