2.0.4 can't finalize the tweak

[Alexpasnichenko]

After the installation, using the GUI I didn't manage to finalize the installation, at the update-astroarch stage it was failing saying it didn't get the response code after 10 seconds from some sudoers command

I managed to fix that running the update-astroarch

Now, no matter what I'm doing, I get this -

It locks the pacman, so I have to remove the /var/lib/pacman/db.lck

After that, I get to the same situation

[sc74]

Did you install version astroarch-2.0.4-20251103.img.gz?

[Alexpasnichenko]

Yes, the image from this link https://drive.google.com/file/d/1CzN3f9_lNp2InT2PLvp_vflsW7gywFZB/view

Is there a way to bypass the update and install indi staff from script/command?

These give nothing

systemctl list-units --type=service | grep -i indi
systemctl list-units --type=service | grep web

Either I can't find anything indi related from the pacman

[sc74]

No, you cannot disable the update-astroarch command in the configuration software. There is no ‘indi’ service to launch at startup. You can use the indi server GUI software if you are not using kstars. Or install a service for this yourself. To see the indi packages installed, run pacman -Qs indi

Are you using an SD card? Could you run the sudo calamares -d command in a console and give us the log output when the error occurs?

[Alexpasnichenko]

Yes, I'm using the 32Gb Sd card

Sorry, mate, I'll drop the errors and output as images

[Alexpasnichenko]

If this could give you more details - I was able to run the update-astroarch command, it worked fine for me, took up to 1.5 hour

I meant if I can install these outside the gui?

[sc74]

Yes, you can do this in a console using the commands found herehttps://github.com/devDucks/astroarch?tab=readme-ov-file#useful-commands --> use-astro-bleeding-edge or use-astro-stable

For your issue, could you reinstall and wait a few minutes before launching the configuration to see if it is the partition enlargement that causes an error with the update-astroarch command launched by the configurator?

[Alexpasnichenko]

I can install it again, but I never succeeded at the update-astroarch stage, every time it failed due to sudoers something issue, sorry, I've missed the exact error

I'm not really familiar with the astro software, what I want is to connect my ZWO asi662mc camera and Gemini focuser and run something, which could adjust focus and make photos/images/, first of all planetary. Is this is what I'm looking for?

[sc74]

For planetary imaging, use Firecapture for acquisition, but a Raspberry Pi isn't really designed for that, as it requires a lot of processing power. With Kstars, you can do deep sky imaging and use all your equipment.

Please share the error message with us if you encounter it.

[sc74]

Your issue is identical to #217

It seems that the timeout for the process executing the astroarch-update command is too short for your type of SD card and/or network. Currently, it is set to 15 minutes, and your process takes 1 hour and 30 minutes. I need to test whether we can extend this time without penalizing other users

[Alexpasnichenko]

I've reburned the image, after the first startup waited about 30 mins
Then, I've ran update-astroarch, it worked fine

Then, I've ran use-astro-stable, no issues either

Next step

timedatecl list-timezones                                                                                                                                                                                                            
zsh: timedatecl: command not found...

The vnc doesn't work, I've tried all the options from the manual provided in the release description with no result.

On the other side - kstars works fine with all my hardware, this is a great news

[sc74]

There is a missing 't' in your timedatectl command.

Could you please provide us with the output of systemctl status x0vncserver?

[sc74]

Could you test something for us?

Reinstall AstroArch on your SD card. Then, in a terminal, open the file /usr/share/calamares/modules/shellprocess-update.conf with the command:

sudo nano /usr/share/calamares/modules/shellprocess-update.conf

Then scroll down and change the value from timeout: 999 to timeout: 9999.

Close and save with crt + x.

Finally, go to the configurator that is open and configure your settings to see if you still get the blocked database error and the pacman -Sy issue

[Alexpasnichenko]

Sure, will give it a try

[Alexpasnichenko]

Same packman -Sy issue
Update-Astroarch worked fine

[sc74]

If you have time, could you test what I have indicated here #217 (comment)?