Jump to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

New Install Polyglot on Raspberry Pi - E: Package 'mongodb-server' has no installation candidate

Featured Replies

Posted

Following:  https://github.com/UniversalDevicesInc/polyglot-v2#installation-instructions

Running the installation script:

wget -qO - https://raw.githubusercontent.com/UniversalDevicesInc/polyglot-v2/master/scripts/install.sh | bash -e

Receiving:

E: Package 'mongodb-server' has no installation candidate

Simplified commands down to:  sudo apt install mongodb

Package mongodb is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Have tried researching and it seems that maybe mongo is no longer supported on the default Raspberry Pi OS 32-bit.

Is there an updated installation guide on how to install Polyglot on a Raspberry Pi?

Solved by randyth

Go to solution

If you are using Pi3 or Pi4 you can run 64 bit if that is possible you can download a 64 bit DEB at https://www.mongodb.com/try/download/community or if you need 32 bit you can compile it from source. The other option is to use Ubuntu Server for Pi and just install the version in their repo. 

On a side note, compiling isn't very hard in most cases you just navigate to the folder, issue the commands ./configure followed my make and then make install and you are done.

  • 2 weeks later...

The same is happening to me, someone has been able to find a solution to install polyglot v2?


Sent from my iPhone using Tapatalk

@jesusmr Just a thought. I recall something about having to use an older install of Raspbian to allow everything to work. You might try one of the older OS installs here. Maybe 2019?

Thank, I will check out


Sent from my iPhone using Tapatalk

  • Solution

If you use the Raspberry Pi Imager, choose Raspberry Pi OS (other) and then select Raspberry Pi OS Lite (Legacy).

image.png.042ba33d05b60d741f16279fae163823.png

After installing PG2, follow these instructions to fix the “ee key too small” error. Then you should be all set.

Thank!!! Now is running perfectly!!!!


Sent from my iPhone using Tapatalk

21 minutes ago, jesusmr said:

Thank!!! Now is running perfectly!!!!


Sent from my iPhone using Tapatalk

Yay! Glad I could help.

@Michel Kohanim, perhaps someone could update the readme to include the fact that the latest RPi OS won't work with PG2?

I never found any of the NOOBS o/ses worked with anything. They were always missing components of the O/Sytems and every bit of advice from others never worked for one reason or another.

I completely wrote my RPis off,  after a year or two of frustration, rebuilding them many, many times. About a year later, I downloaded a proper image of Debian, or whatever the latest O/S was at the time, and things just started to work properly. I don't touch the NOOBs installation any more.

My PG1 and PG2 worked just fine with all my RPis until I ported over to polisy.

Edited by larryllix

  • Author

@kzboray thank you for your insight on an older version of Pi Operating System might be required.

@randyth thank you for pointing me to the buster version of Pi OS.  That seems to have solved my problem with MongoDB.  I don't think I see any error "ee key too small" so I didn't take that step.

At the end of the installation, I received:

###################################################################################
DONE! Login to Polyglot v2 at https://192.168.0.89:3000
Username: admin
Password: admin
Be patient. It may take up to three minutes for the interface to be available while
MongoDB and Polyglot start up for the first time.
###################################################################################

Now, my problem is:

  • https://192.168.0.89:3000/
    This site can’t be reached
    192.168.0.89 refused to connect
    ERR_CONNECTION_REFUSED

Here's what info I've collected

  • sudo systemctl status polyglot-v2.service
    shows that we are active (running)
  • nano ~/.polyglot/log/debug.log
    shows that things started up (at least partially)
    12/27/2021, 15:47:58 [polyglot] info: Starting Polyglot....
    12/27/2021, 15:47:58 [polyglot] info: Settings: No config found in database, creating settings entries.
    12/27/2021, 15:47:58 [polyglot] info: Auto Discovering ISY on local network.....
    12/27/2021, 15:47:59 [polyglot] info: ISY discovered at address: 192.168.0.64:80
    12/27/2021, 15:48:02 [polyglot] info: Settings: Polyglot Version 2.2.11
    12/27/2021, 15:48:02 [polyglot] info: Settings: Retrieved config from database
    12/27/2021, 15:48:02 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
    12/27/2021, 15:48:02 [polyglot] info: SSL: No HTTPS Certificate or Key found. Generating...
    12/27/2021, 15:48:07 [polyglot] info: SSL: Certificate Generation completed successfully.
    12/27/2021, 15:48:07 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883
    
    12/27/2021, 15:48:17 [polyglot] info: Starting Polyglot....
    12/27/2021, 15:48:17 [polyglot] info: Settings: Polyglot Version 2.2.11
    12/27/2021, 15:48:17 [polyglot] info: Settings: Retrieved config from database
    12/27/2021, 15:48:17 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
    12/27/2021, 15:48:17 [polyglot] info: Aedes MQTT Broker Service: Started on port 1883
    
    repeat the 2nd block over and over and over

So it seem to be starting up... but whatever is supposed to happen after the MQTT Broker Service starts on port 1883, seems to be failing.

I went here and enabled debug logging:  https://github.com/UniversalDevicesInc/polyglot-v2#enable-debug-logging-for-polyglot

Now I'm seeing:

12/27/2021, 12:11:44 [polyglot] info: Starting Polyglot....
12/27/2021, 12:11:44 [polyglot] info: Settings: Polyglot Version 2.2.11
12/27/2021, 12:11:44 [polyglot] info: Settings: Retrieved config from database
12/27/2021, 12:11:44 [polyglot] info: Settings: Retrieved config overrides from .env and updated database
12/27/2021, 12:11:44 [polyglot] debug: TLS: Found Keys and Certificate data in database. Exporting to /home/pi/.polyglot/ssl/
12/27/2021, 12:11:44 [polyglot] debug: Checking for DB Maintenence needs...
12/27/2021, 12:11:48 [polyglot] debug: Created PID file: /home/pi/.polyglot/polyglot.pid
12/27/2021, 12:11:53 [polyglot] info: Starting Polyglot....
repeat prior lines

Now I have no idea what I'm really doing, but I tried this:

  • tail /home/pi/.polyglot/polyglot.pid
pi@RasPi-Polyglot:~ $ tail /home/pi/.polyglot/polyglot.pid
1767
pi@RasPi-Polyglot:~ $

and I tried

  • tail -f /home/pi/.polyglot/polyglot.pid
pi@RasPi-Polyglot:~ $ tail -f /home/pi/.polyglot/polyglot.pid
1937
tail: /home/pi/.polyglot/polyglot.pid: file truncated
1950
tail: /home/pi/.polyglot/polyglot.pid: file truncated
1964
tail: /home/pi/.polyglot/polyglot.pid: file truncated
1977

Wondering if the above information is sufficient for anyone to guide me further?

Thank you for your time and consideration.

BradS

18 minutes ago, BradS said:

@randyth thank you for pointing me to the buster version of Pi OS.  That seems to have solved my problem with MongoDB.  I don't think I see any error "ee key too small" so I didn't take that step.

I think you are having trouble because you skipped the "SSL Error 'ee key too small'" step mentioned above. So, please try following these instructions and see if that helps: https://github.com/UniversalDevicesInc/polyglot-v2#ssl-error-ee-key-too-small

  • Author

@randyth thanks for reading and responding.  That seems to be it!

+1 Thank you @randyth!  I was bored over the holiday and decided to upgrade all the node servers on my Pi.  Many hours of troubleshooting later I came across this post and am back up and running again.  

-Brian

Guest
This topic is now closed to further replies.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.