Hello,

At this point, NGINX is missing noVNC. The service noVNC is dependent on vncserver-x11-service. The service vncserve-x11-service is serving 192.168.200.26, 127.0.0.1, AstroBerry.local, and AstroBerry. RealVNC is servicing the same resources. Hence, a conflict exists.

I can run this dependent group sans the service. First Light works as advertised. As a service, the noVNC does not see its partner.

I have used Type=forking to assist with services being enabled but inactive. Using “ systemctl start service” does not load the service into memory as in terminate and stay ready.

Apparently, noVNC was working on December 7, 2019. This date is the last save date of its log file. After this date, First Light stopped working. The date on the log file tells me when noVNC is running. The vncserver-x11 logfile is filled with these messages:

<11> 2020-01-13T11:56:06.601Z astroberry vncserver-x11[963]: AgentInitCheck: no response from agent

The NGINX log file is filled with these messages:


2020/01/12 21:35:13 [error] 569#569: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.200.26, server: _, request: "GET /indiwebmanager/ HTTP/1.1", upstream: "http://127.0.0.1:8624/", host: "192.168.200.26", referrer: "http://192.168.200.26/desktop/"

This looks like NGINX is attempting to get its stuff from RealVNC. The service vncserver-x11 is running. I will investigate the user context of this trio.

Hello,

I am happy to report First Light is now operational.

The service noVNC.service was corrected. I changed the Type from forking to idle on all these service files

Nginx
Vncserver-x11-serviced
NoVNC
Astropanel
Gpspanel
Indiwebmanager
Indiwebmanagerapp
VirtualGPS

I also found an issue with noVNC.service. This was the problem all along. I was looking at another service and noticed the syntax around After=.

Before

After=multi-user.target vncserver-x11-serviced

After

After=vncserver-x11-serviced

Additional Critical Path services had this configuration issue. They are GPSPANEL, ASTROPANEL, and VIRTUALGPS. Starting any of these with the fix will cause an infinite search for a non existant service.

Now, everything works.

Findings:

Critical path items had

1. User=multiple names

I removed all User= entries. They are not necessary.

2. Syntax errors [UNIT] should be [Unit]

3. NGINX requires SUDO help to load.

4. Type= different levels.

I standardized on Type=idle.

5. After=Multi-user.target service.name
This should be After=service.name

6. Running the update under sudo or root masks the needs of systemctl enable and restart. Be ready to input the password before and after the &&.

7. The noVNC service bug hung up the POSTINST script from completing. The service Multi-user. Target Service Name did not exist.

8. Bypassing all systemctl commands allowed the script to be completed. Running dpgk —configure-a did not and could not fix syntax errors

9. A December 7 patch left the First Light process in limbo. Several service files were corrupted.

This study is completed. The system is working as advertised. Thank you for your time.

Hi Radek,

where did you hide the Ubuntu Date and Time-Setting ?

When I´m in the Field with no internet, I need to set the time manualy.

I´ve googled for this, but at astroberry I don´t find this :
Change the date and time
Open the Activities overview and start typing Settings.
Click on Settings.
Click Details in the sidebar.
Click Date & Time in the sidebar to open the panel.
If you have the Automatic Date & Time switch set to on, your date and time should update automatically if you have an internet connection.

CS
Reiner

Hello,

I guess it is rights issue. The problem I have is with GPS. With First Light and a GPS connected, GPSPANEL map bounces between the default Poland and the current GPS coordinates. It looks like a hardwired coordinate is not allowing the system to change it. Where is the question? Deep dive coming.

Unfortunatelly Raspbian Desktop Environment (LXDE) does not include a standard tool to set the date and time. The easiest way is to issue a command on the command line, the following are some examples...
It's actually good change request... I will need to add it to the system in a future release.

You need to disable virtualgps, which is part of the system, for users that don't have GPS but want some of the system functionalities work for them.

Hello Radek,

Thank you. Oops... I think indiWeb is dependent on VirtualGPS running. Indiwebmanager stopped running after I disabled VirtualGPS.

It can't be. There is no dependence between the two. This is just coincidence

Hello,

I reconnected. Faulty chrome session. We are back in the saddle.

Wow, looks like AradoSKYindi has been on a roll and found a few issues and offered solutions!

Any chance these could be incorporated into next releases of Astroberry?

Hi Radek,

that did not work. I investigated via google and found this orders. And they work.

First Stop automatic time update
timedatectl set-ntp 0

sudo timedatectl set-time 2020-01-14
sudo timedatectl set-time 20:15


If you want to restart automatic time update:

timedatectl set-ntp 1

Reiner

Would it be possible to get the time from a connected mount with GPS? For example iOptron ?