[Solved] Husarion Cloud - is it currently offline?

Cloud software
1

Hi,

My ROSbot 2.0 has its blue LED blinking continously. It looks like it’s in “Connecting” state.
I can connect through SSH and have internet in ROSbot.

Is Husarion Cloud currently offline?
Also, where can we instantaneously check the status of Cloud?

Thanks,
Erinc

2

Hi erugo,

Please try connect your ROSbot to cloud one more time. If problem will be still occurred try to change your WiFi, it can be problem with you network security settings.

Status of LR1 and LR2 constantly inform you about status of Cloud.

Best regards,
Hubert

3

Hello Hubert,

Thanks for your answer. I have tried to connect my ROSbot to the cloud on various networks, but failed to do so.

I have also tried restarting the ROSbot, and also sudo systemctl restart husarnet-configurator, but with no luck.

Is there any other reinstallation that I can try out? Or would you suggest any specific network configuration that I need to check? The first time Cloud connection had already been done, and I can access the device through SSH and local network, and the device has access to the internet.

Thanks.

4

Here is something I did in order to fix the cloud connectivity problem:

husarion@husarion:~$ sudo systemctl restart husarion-init-board
Job for husarion-init-board.service failed because the control process exited with error code. See "systemctl status husarion-init-board.service" and "journalctl -xe" for details.
husarion@husarion:~$ systemctl status husarion-init-board
* husarion-init-board.service - Initialize board
   Loaded: loaded (/lib/systemd/system/husarion-init-board.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2019-08-16 15:13:58 +03; 7s ago
  Process: 12127 ExecStart=/usr/bin/husarion-init-board (code=exited, status=1/FAILURE)
 Main PID: 12127 (code=exited, status=1/FAILURE)

Aug 16 15:13:58 husarion husarion-init-board[12127]: Traceback (most recent call last):
Aug 16 15:13:58 husarion husarion-init-board[12127]:   File "/usr/bin/husarion-init-board", line 15, in <module>
Aug 16 15:13:58 husarion husarion-init-board[12127]:     subprocess.check_call(['ifconfig', 'eth0', 'hw', 'ether', newmac])
Aug 16 15:13:58 husarion husarion-init-board[12127]:   File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
Aug 16 15:13:58 husarion husarion-init-board[12127]:     raise CalledProcessError(retcode, cmd)
Aug 16 15:13:58 husarion husarion-init-board[12127]: subprocess.CalledProcessError: Command '['ifconfig', 'eth0', 'hw', 'ether', (OMITTED)]' returned non-zero exit status 1
Aug 16 15:13:58 husarion systemd[1]: husarion-init-board.service: Main process exited, code=exited, status=1/FAILURE
Aug 16 15:13:58 husarion systemd[1]: Failed to start Initialize board.
Aug 16 15:13:58 husarion systemd[1]: husarion-init-board.service: Unit entered failed state.
Aug 16 15:13:58 husarion systemd[1]: husarion-init-board.service: Failed with result 'exit-code'.
husarion@husarion:~$ sudo ifconfig eth0 down
husarion@husarion:~$ sudo systemctl restart husarion-init-board
husarion@husarion:~$ systemctl status husarion-init-board
* husarion-init-board.service - Initialize board
   Loaded: loaded (/lib/systemd/system/husarion-init-board.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Fri 2019-08-16 15:14:28 +03; 5s ago
  Process: 13013 ExecStart=/usr/bin/husarion-init-board (code=exited, status=0/SUCCESS)
 Main PID: 13013 (code=exited, status=0/SUCCESS)

Aug 16 15:14:28 husarion systemd[1]: Starting Initialize board...
Aug 16 15:14:28 husarion systemd[1]: Started Initialize board.
husarion@husarion:~$ sudo ifconfig eth0 up

It looks like the husarion-init-board fails due to eth0 being up, and not being able to change its MAC address.
Something that sounds relevant is that when I try to connect to Wired Connection 1 from the connections menu, the connectivity icon keeps spinning, as if the wired connection can never be established.

5

Here is the output for systemctl status husarnet-configurator, and an attempt to manually run husarion-cloudproxy:

* husarnet-configurator.service - Husarnet Configurator
   Loaded: loaded (/lib/systemd/system/husarnet-configurator.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2019-08-16 15:55:46 +03; 53s ago
  Process: 8195 ExecStop=/usr/bin/set-core2-state on (code=exited, status=0/SUCCESS)
 Main PID: 8240 (python3)
   CGroup: /system.slice/husarnet-configurator.service
           |-8240 /usr/bin/python3 -u main.py
           `-8251 husarion-cloudproxy

Aug 16 15:56:35 husarion python3[8240]: [48.836] read from local serial: 0
Aug 16 15:56:35 husarion python3[8240]: [48.836] reading from local serial...
Aug 16 15:56:36 husarion python3[8240]: [49.837] read from local serial: 0
Aug 16 15:56:36 husarion python3[8240]: [49.837] reading from local serial...
Aug 16 15:56:37 husarion python3[8240]: [50.782] wake up CORE2
Aug 16 15:56:37 husarion python3[8240]: [50.837] read from local serial: 0
Aug 16 15:56:37 husarion python3[8240]: [50.837] reading from local serial...
Aug 16 15:56:38 husarion python3[8240]: [51.839] read from local serial: 0
Aug 16 15:56:38 husarion python3[8240]: [51.839] reading from local serial...
Aug 16 15:56:39 husarion python3[8240]: [52.587] QueueClient is not connected to platform, ignoring packet
~
~
~
~
husarion@husarion:~$ husarion-cloudproxy
created pty /dev/pts/7

creating symlink /dev/ttyCORE2

config mode: 0
entering bootloader...
[0.516] triggering bootloader
[0.516] waiting for bootloader to respond
[1.518] STM32 protocol error: 1

entering bootloader...
[2.019] triggering bootloader
[2.019] waiting for bootloader to respond
[3.020] STM32 protocol error: 1

entering bootloader...
[3.521] triggering bootloader
[3.521] waiting for bootloader to respond
[4.522] STM32 protocol error: 1

entering bootloader...
[4.951] skipping byte 76
[4.951] skipping byte 28
[5.153] skipping byte 61
[5.254] triggering bootloader
[5.254] waiting for bootloader to respond
[5.353] invalid response 119
[5.454] triggering bootloader
[5.454] waiting for bootloader to respond
[6.455] STM32 protocol error: 1
6

Hi Erugo,

I’ve got the same problem than you today. Yesterday I was able to connect my Rosbot to the Husarion cloud but since this morning the blue led blink …
I tried with an other wifi but my rosbot still stamped offline on the Husarion cloud !

Is there a known solution ?

7

Hi Baptiste,

I’ve checked all functionality of Husarion Cloud and everything work fine. May I ask you to unlink your ROSbot and try to connect it one more time?

Best regards,
Hubert

8

I tried to reconnect the Rosbot and now it’s okay. It’s strange but I’m not stuck now.
Thanks for support

1 Like