Upgrade to latest version WebUI not working - legacy {ALLSKY_HOME} pointer #2604
-
|
Hello I installed the latest git last night and after running through the installation, I cannot load the WebUI any more. I am getting:
This must be because the previous version I had was in /home/allsky and the new one was installed in /home/pi/allsky. Before I installed the new version, I deleted the old allsky installation but there must be some legacy system link pointing the WebUI request to it. There were no errors in the new installation and my config.sh shows CAMERA_TYPE = "ZWO" in it (towards bottom in new version). Running scripts/check_allsky.sh results in "No issues found." But I cannot even access the WebUI. Any suggestions? Roberto |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 24 replies
-
|
And just to add to this - as it may seem obvious - re-installing the new version at /home/allsky rather than /home/pi/allsky does not solve the issue. Same message appears when the WebUI is invoked. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Eric Thanks for your help. Both previous version and current installed as pi. |
Beta Was this translation helpful? Give feedback.
-
|
And here's the config.sh file from the /home/pi/allsky/config folder of v2023.05.01: |
Beta Was this translation helpful? Give feedback.
-
When I go to allsky.local or my Raspberry's IP address, I get the red CAMERA type not defined...message I first posted. |
Beta Was this translation helpful? Give feedback.
-
|
When you first installed, did you first mv ~/allsky to ~/allsky-OLD and if so, did the installation ask you if you wanted to use it? It appears like the answer is "yes", but it couldn't find your camera. Do you have the old, original config/config.sh file? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Eric Since I knew I had installed the previous version at /home/allsky, I moved it to /home/pi/allsky-OLD and then used git to replicate to /home/pi/allsky. Attached is config.sh from previous version (which I had saved in a network folder just in case). Roberto |
Beta Was this translation helpful? Give feedback.
-
|
It also couldn't find the "images" directory in your old version, which is very unusual. It's as if the old version was corrupt. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe that's the source of my problems? I tried uninstalling and removing all folders but was having serious difficulty getting rid of the /allsky/tmp folder in the new installation. I wouldn't allow itself to be deleted. Was always reporting as being busy. Roberto |
Beta Was this translation helpful? Give feedback.
-
|
@rbotero1976 The problems could have been due to trying to move Allsky (from /home/allsky to /home/pi/allsky) while at the same time installing the new version. Probably would have been better to simply install the new version, then manually copy the "images" and "darks" folder, but that would have required knowing how to do that. We don't have any commands or documentation on how to move Allsky. Are you still getting the red error? If so, I suggest moving the current /home/pi/allsky to /home/pi/allsky-SAVED, then re-installing the new release. After that you can move the old "images" directory to the new location (and "darks" if you were using them). Then manually copy the settings from the old to new (don't copy the actual files). After you do that, I can help you with other stuff. |
Beta Was this translation helpful? Give feedback.
-
|
I may have to edit all the configuration files manually and just keep on using scripts/check_allsky.sh which at the moment is reporting no errors:
But no images are being uploaded (maybe it's my daytime settings). |
Beta Was this translation helpful? Give feedback.
-
|
After editing config.sh and settings.json, I have my website up and running again: Eric, is there a way of running the gui installer again separately? Like in the previous version to see if I can get WebUI back? Roberto |
Beta Was this translation helpful? Give feedback.
-
|
I reinstalled Apache2 just to make sure there was nothing corrupted and this created /var/www/html again. I did a
And I can now see the WebUI but none of the settings I have created through editing the config.sh, settings.sh, etc are reflected. |
Beta Was this translation helpful? Give feedback.
-
|
We don't support Allsky running under Apache, just under lighttpd. Other than that, I suggest uninstalling Apache. |
Beta Was this translation helpful? Give feedback.
-
|
That was it Eric! I don't know why Apache2 was installed...removing it, restarting lighttpd gets me this:
Now I need to update/replicate the settings I had got running but I think I'm there! Roberto |
Beta Was this translation helpful? Give feedback.
-
|
Roberto, phew, I am glad you got it working. The rest should be easy. |
Beta Was this translation helpful? Give feedback.
We don't support Allsky running under Apache, just under lighttpd.
Your Apache isn't configured to know where Allsky is so it's looking in /var/www/html which Allsky no longer uses. Does Apache support symbolic links? I could never get them to work with lighttpd, so that could be causing problems.
You might be able to get things to work by configuring Apache to mimic lighttpd - see the allsky/config_repo/lighttpd.config.repo file.
Other than that, I suggest uninstalling Apache.