New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !

Unable to update my bubba

Got problems with your B2 or B3? Share and get helped!
Post Reply
rojter
Posts: 12
Joined: 28 Jul 2013, 11:31

Unable to update my bubba

Post by rojter »

Hi!

Just did a re-install of my bubba with the latest 2.4.1.1 install image. No problems there, but when trying to update to the latest 2.6.0.2 my bubba doesn't seem to be able to find the update server even though it has internet connection. I have tried a couple of times now. Any ideas why?
unable.PNG
unable.PNG (26.85 KiB) Viewed 8393 times
Last edited by rojter on 18 Aug 2015, 09:38, edited 2 times in total.
rojter
Posts: 12
Joined: 28 Jul 2013, 11:31

Re: Unable to update my bubba

Post by rojter »

Found a solution here which did the trick:
http://forum.mybubba.org/viewtopic.php? ... 232#p25068
rojter
Posts: 12
Joined: 28 Jul 2013, 11:31

Re: Unable to update my bubba

Post by rojter »

Actually am still having some issues with this on my b3. Now getting this error:
Capture.PNG
Capture.PNG (52.45 KiB) Viewed 8025 times
Last bit not showing for some reason, but it says "Cannot connect to the updater deamon; Please contact support"

Tried the solution in the above post, but unfortunately it didn't work this time and I got these errors:

Code: Select all

apt-get update
Hit http://b3.update.excito.org elvin Release.gpg
Ign http://b3.update.excito.org/ elvin/main Translation-en
Hit http://b3.update.excito.org upstream_squeeze Release.gpg
Ign http://b3.update.excito.org/ upstream_squeeze/main Translation-en
Hit http://b3.update.excito.org elvin Release
Hit http://b3.update.excito.org upstream_squeeze Release
Ign http://b3.update.excito.org elvin/main armel Packages
Ign http://b3.update.excito.org upstream_squeeze/main armel Packages
Hit http://b3.update.excito.org elvin/main armel Packages
Hit http://b3.update.excito.org upstream_squeeze/main armel Packages
Reading package lists... Done
root@b3:/etc/apt# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up bubba-album (2.6) ...
dbconfig-common: writing config to /etc/dbconfig-common/bubba-album.conf
Replacing config file /etc/dbconfig-common/bubba-album.conf with new version
debconf: Unable to load Debconf::Element::Dialog. Failed because: Can't locate Debconf/Element/Dialog.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at (eval 26) line 2, <GEN5> line 16.
BEGIN failed--compilation aborted at (eval 26) line 2, <GEN5> line 16.

Can't locate object method "new" via package "Debconf::Element::Dialog" (perhaps you forgot to load "Debconf::Element::Dialog"?) at /usr/share/perl5/Debconf/FrontEnd.pm line 68, <GEN5> line 16.
dpkg: error processing bubba-album (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of bubba-frontend:
 bubba-frontend depends on bubba-album (>= 0.99.1); however:
  Package bubba-album is not configured yet.
dpkg: error processing bubba-frontend (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bubba:
 bubba depends on bubba-frontend; however:
  Package bubba-frontend is not configured yet.
 bubba depends on bubba-album; however:
  Package bubba-album is not configured yet.
dpkg: error processing bubba (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bubba-backend:
 bubba-backend depends on bubba; however:
  Package bubba is not configured yet.
dpkg: error processing bubba-backend (--configure):
 dependency problems - leaving unconfigured
configured to not write apport reports
                                      configured to not write apport reports
                                                                            configured to not write apport reports
                                                                                                                  configured to not write apport reports
                                                                                                                                                        Errors were encountered while processing:
 bubba-album
 bubba-frontend
 bubba
 bubba-backend
E: Sub-process /usr/bin/dpkg returned an error code (1)
Also tried to install openvpn but it told me:

Code: Select all

apt-get install openvpn
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package openvpn
Looked at my /etc/apt/sources.list which only states:

Code: Select all

# General sources.list
#
# Generated by change_distribution elvin
#
# vim: ft=debsources
Isn't it a bit empty? Not sure what it should contain though.

The /etc/apt/sources.list.d/excito.list looks OK I think:

Code: Select all

# Excito sources.list
#
# Generated by change_distribution elvin
#
# vim: ft=debsources
deb http://b3.update.excito.org/ elvin main
deb http://b3.update.excito.org/ upstream_squeeze main
uname -a says the following:

Code: Select all

Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel GNU/Linux
Any ideas to get the updater to work and ideas for sources to install openvpn and other stuff?
Gordon
Posts: 1461
Joined: 10 Aug 2011, 03:18

Re: Unable to update my bubba

Post by Gordon »

Did you search Google for that Debconf::Element::Dialog error? There are some pages out there addressing similar issues with debconf and there could be a solution on one of them that works for you.

The message about the updater daemon is probably not something you need to worry about. The web interface runs the updates through a daemonized process which in your case ends with a failure that the web interface is not programmed to trap. As a result the web interface keeps polling the process' status to the point where it fails itself because the process is unloaded.
Post Reply