-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Raspberry PI 2/3 install compatibility #78
Comments
Hello, could you please attach the install.log and tb-edge.log files? Analyzing them will aid us in identifying the potential root cause of the issue. We plan to conduct some tests on PI 3, but we will first need to acquire the necessary equipment. |
Sure, Best Regards, SeungChan |
I haven’t identified any errors in the logs provided. Could you please attach either the install or tb-edge logs that contain error messages, especially those related to the DB schema or any other issues? Additionally, please ensure that the logs are complete, starting from the application's startup. Thank you in advance. |
Oh, I've made some mistakes. |
It appears that the Edge is unable to establish a connection with the cloud, as indicated by the following error: Could you please verify whether port 7070 on IP address 192.168.88.237 is accessible from this Edge instance, using telnet or another network tool? Additionally, could you provide the logs from your TB server instance? Are there any error messages present in those logs? |
You're right I didn't write correct cloud IP address to .conf file. Thank you |
If you have the opportunity, we recommend updating to the latest 3.6.0 version. We have expanded the Edge installation instructions, and Ubuntu OS is now supported as well. You can follow the steps in these updated instructions, which include all the prepared configuration parameters for your convenience: |
It worked fine, finally edge is successfully installed and executed in Raspberry PI 2 and 3 with appropriate DB data. Also, I want to share some trouble shooting case in Raspberry PI. If using Ubuntu in Raspberry PI 2 or 3, often I could see 'unattached upgrade' process spend almost 100% of CPU resource. Stuck resource seems affect installation process (jdk, postgresql and edge). After change setting on 'unattached upgrade' process, I could install edge file normally as expected and faster. Referenced link is below. Thank you |
Thank you for sharing this valuable information regarding the installation process of Edge for Raspberry Pi 2 or 3. |
Description
I followed edge installation guide in Ubuntu.
https://thingsboard.io/docs/user-guide/install/edge/deb-installation/
When I install edge in Mac mini desktop which with Ubuntu 20, everything is clear.
But when I tried it with Raspberry PI 2 and Raspberry PI 3, the result is below.
Raspberry PI 2 with Ubuntu 20 32bit -> successfully install but some sort of important table in DB is empty. ex) edge, user, user-credentials table ... so I couldn't login to edge.
Raspberry PI 3 with Ubuntu 20 64bit -> successfully install but some sort of important table in DB is empty. ex) edge, user, user-credentials table ... so I couldn't login to edge.
Raspberry PI 3 with Ubuntu 22 64bit -> installation failed neither progress is slower than Ubuntu 20.
Environment
Edge
Thingsboard
Question
I also viewed related topic, and it seems 3.4.3 would be solving these issue.
arm7 compatibility
And I also viewed someone successfully install edge in Raspberry PI 4.
Successfully Raspberry PI 4 install
Can I run edge in Raspberry PI 2/3 with low 1GB memory model? Or go to Raspberry PI 4?
Or is there any other suggestion about empty DB problem?
Best Regards, SeungChan
The text was updated successfully, but these errors were encountered: