A little excited? - SSL Error on download

geoffrey.bolte · April 24, 2020, 11:29pm

From terminal when trying to install -

curl: (60) SSL certificate problem: certificate is not yet valid

More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not

establish a secure connection to it. To learn more about this situation and

how to fix it, please visit the web page mentioned above.

Guessing I’m a little too early to install??

geoffrey.bolte · April 25, 2020, 6:57pm

@Saeed @ensar

Would love to get this Power Management up and running! Can’t get the software to download and install. Either through the cloud management or the open source link you mentioned!

Chomping at the bit to give this a try!

ensar · April 25, 2020, 8:18pm

Hi @geoffrey.bolte,

Check system time. SSL(encrypted connections) will not work unless the correct time is set.

geoffrey.bolte · April 25, 2020, 8:28pm

Guess I was a little excited. In using an old install the system time was not updated. Good to go now!

geoffrey.bolte · April 25, 2020, 9:39pm

@ensar

On the install the raspberry shutdown after install is that normal? I noticed the agent ran on boot, but am unable to see the hat in the cloud monitor. Have wifi IP address and connected to Internet.

I do have the cellular IOT hat software installed.

ensar · April 25, 2020, 10:21pm

Could you please share the output once you type systemctl status pms_agent.service?

geoffrey.bolte · April 26, 2020, 1:07am

Thanks @ensar was wondering what the service name was.

It failed according to the output, I ended up -

sudo systemctl disable pms_agent.service
sudo systemctl enable pms_agent.service
sudo systemctl start pms_agent.service

It then worked.

After reboot it failed again.

● pms_agent.service - Sixfab PMS Agent
Loaded: loaded (/etc/systemd/system/pms_agent.service; enabled; vendor preset: enabled)
Active: **failed** (Result: exit-code) since Sat 2020-04-25 20:48:02 EDT; 2min 13s ago
Process: 561 ExecStart=/usr/bin/python3 -u agent.py **(code=exited, status=1/FAILURE)**
Main PID: 561 (code=exited, status=1/FAILURE)
Apr 25 20:48:02 raspilapse1 systemd[1]: pms_agent.service: Service RestartSec=100ms expired, scheduling restart.
Apr 25 20:48:02 raspilapse1 systemd[1]: pms_agent.service: Scheduled restart job, restart counter is at 5.
Apr 25 20:48:02 raspilapse1 systemd[1]: Stopped Sixfab PMS Agent.
Apr 25 20:48:02 raspilapse1 systemd[1]: **pms_agent.service: Start request repeated too quickly.**
Apr 25 20:48:02 raspilapse1 systemd[1]: **pms_agent.service: Failed with result 'exit-code'.**
Apr 25 20:48:02 raspilapse1 systemd[1]: **Failed to start Sixfab PMS Agent.**

Currently going through the journalctl -e to see if I can see what happened.

geoffrey.bolte · April 26, 2020, 1:41am

@ensar

Looking through the journalctl -e looks as though the service starts before the wifi connects so the python script cannot function I believe??

Apr 25 21:27:03 raspilapse1 systemd[1]: Started Sixfab PMS Agent.

Apr 25 21:27:03 raspilapse1 systemd[1]: Started Permit User Sessions.

Apr 25 21:27:03 raspilapse1 systemd[1]: Started /etc/rc.local Compatibility.

Apr 25 21:27:03 raspilapse1 systemd[1]: Starting Terminate Plymouth Boot Screen…

Apr 25 21:27:03 raspilapse1 systemd[1]: Starting Hold until boot process finishes up…

Apr 25 21:27:03 raspilapse1 dhcpcd-run-hooks[444]: wlan0: starting wpa_supplicant

Apr 25 21:27:03 raspilapse1 systemd[1]: Received SIGRTMIN+21 from PID 154 (plymouthd).

Apr 25 21:27:03 raspilapse1 systemd[1]: plymouth-quit.service: Succeeded.

Apr 25 21:27:03 raspilapse1 systemd[1]: Started Terminate Plymouth Boot Screen.

Apr 25 21:27:03 raspilapse1 systemd[1]: plymouth-start.service: Succeeded.

Apr 25 21:27:03 raspilapse1 systemd[1]: plymouth-quit-wait.service: Succeeded.

Apr 25 21:27:03 raspilapse1 systemd[1]: Started Hold until boot process finishes up.

Apr 25 21:27:03 raspilapse1 systemd[1]: Started Getty on tty1.

Apr 25 21:27:03 raspilapse1 systemd[1]: Reached target Login Prompts.

Apr 25 21:27:03 raspilapse1 kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Apr 25 21:27:03 raspilapse1 kernel: brcmfmac: power management disabled

Apr 25 21:27:04 raspilapse1 sshd[449]: Server listening on 0.0.0.0 port 22.

Apr 25 21:27:04 raspilapse1 sshd[449]: Server listening on :: port 22.

Apr 25 21:27:04 raspilapse1 systemd[1]: Started OpenBSD Secure Shell server.

Apr 25 21:27:04 raspilapse1 raspi-config[328]: Checking if shift key is held down: No. Switching to ondemand scaling governor.

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: connected to Access Point `’

Apr 25 21:27:04 raspilapse1 systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: eth0: waiting for carrier

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: waiting for carrier

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: carrier acquired

Apr 25 21:27:04 raspilapse1 kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup

Apr 25 21:27:04 raspilapse1 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: DUID 00:01:00:01:25:d8:36:06:b8:27:eb:94:78:8c

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: IAID eb:94:78:8c

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: adding address fe80::8298:95e8:ccff:50bf

Apr 25 21:27:04 raspilapse1 avahi-daemon[375]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::8298:95e8:ccff:50bf.

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: carrier lost

Apr 25 21:27:04 raspilapse1 avahi-daemon[375]: New relevant interface wlan0.IPv6 for mDNS.

Apr 25 21:27:04 raspilapse1 avahi-daemon[375]: Registering new address record for fe80::8298:95e8:ccff:50bf on wlan0.*.

Apr 25 21:27:04 raspilapse1 dhcpcd[412]: wlan0: deleting address fe80::8298:95e8:ccff:50bf

Apr 25 21:27:04 raspilapse1 avahi-daemon[375]: Withdrawing address record for fe80::8298:95e8:ccff:50bf on wlan0.

Apr 25 21:27:04 raspilapse1 avahi-daemon[375]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8298:95e8:ccff:50bf.

Apr 25 21:27:04 raspilapse1 avahi-daemon[375]: Interface wlan0.IPv6 no longer relevant for mDNS.

Apr 25 21:27:04 raspilapse1 vncserver-x11[446]: ServerManager: Server started

Apr 25 21:27:04 raspilapse1 vncserver-x11[446]: ConsoleDisplay: Cannot find a running X server on vt1

Apr 25 21:27:05 raspilapse1 dhcpcd[412]: wlan0: carrier acquired

Apr 25 21:27:05 raspilapse1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Apr 25 21:27:05 raspilapse1 dhcpcd[412]: wlan0: connected to Access Point `CSWifi’