Page 1 of 1
Incomplete web update?
Posted: 29 Dec 2013, 14:55
by macke
Just tried to update my B2 via the web gui update function. My previous version was 2.5.?.?. All went well until I got to 42%, then the progress bar seemed stuck. When I tried to access the web gui the B2 did not respond. I thought ok, I leave it like this for half an hour and try again later. Well, an hour later I could still not get any responses from the web gui. I then logged in via ssh and everything seemed to be ok. I rebooted my B2 with the "reboot" command and waited for it to come alive again. The LED started to flash as it normally does when booting but it never stopped... I left it in this state for an hour just to make sure. Hmmm.... I then performed a cold boot (pulling the plug). Now the B2 came alive again! When I now look at the web gui most modules seems to be updated except for the bubba-backend. Is this correct or should I try to update it once again?
Code: Select all
2.6.0.1
Detailed information
Package name Package version
bubba 2.6.0.1
bubba-album 2.6
bubba-backend 2.5.1.5
bubba-frontend 2.6.0.1+security1
bubba3-kernel 1:2.6.39.4-13
filetransferdaemon 0.55
logitechmediaserver 7.7.2.dfsg1-1
Re: Incomplete web update?
Posted: 29 Dec 2013, 17:28
by Ubi
The linux reboot command does not work on the bubbae for technical reasons. The update looks good, but you can always run
Code: Select all
apt-get update
Apt-get dist-upgrade
to be sure
Re: Incomplete web update?
Posted: 29 Dec 2013, 17:49
by johannes
Yes, I am almost sure that bubba-backend should have a more recent version (can't double-check from here right now), but my B3 bubba-backend is on 2.6, should be the same on B2. Try either a manual or a web update again, something did go wrong. (If you can a manual is better since you can se what's happening more in detail).
Re: Incomplete web update?
Posted: 30 Dec 2013, 05:41
by macke
Tried to do apt-get dist-upgrade and got the following output:
Code: Select all
root@b2:/# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
tor-geoipdb
The following packages will be upgraded:
bubba-backend
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
14 not fully installed or removed.
Need to get 0 B/588 kB of archives.
After this operation, 21.5 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
(Reading database ... 40081 files and directories currently installed.)
Preparing to replace bubba-backend 2.5.1.5 (using .../bubba-backend_2.6_all.deb) ...
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'wd_stop_unload_daemon' missing LSB tags and overrides
insserv: There is a loop between service led_blink and wd_stop_unload_daemon if stopped
insserv: loop involving service wd_stop_unload_daemon at depth 2
insserv: loop involving service led_blink at depth 1
insserv: Stopping wd_stop_unload_daemon depends on led_blink and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing /var/cache/apt/archives/bubba-backend_2.6_all.deb (--unpack):
subprocess new pre-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
/var/cache/apt/archives/bubba-backend_2.6_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Seems to be the wd_stop_unload_daemon that I added that is causing the trouble... However, I thought I had remove that service earlier but that must not be the case. So I tried to do the following:
Code: Select all
root@b2:/# update-rc.d -f wd_stop_unload_daemon remove
update-rc.d: using dependency based boot sequencing
insserv: warning: script 'wd_stop_unload_daemon' missing LSB tags and overrides
insserv: There is a loop between service led_blink and wd_stop_unload_daemon if stopped
insserv: loop involving service wd_stop_unload_daemon at depth 2
insserv: loop involving service led_blink at depth 1
insserv: Stopping wd_stop_unload_daemon depends on led_blink and therefore on system facility `$all' which can not be true!
Unfortunately I'm no Linux expert
Could someone please help me how to get rid of the wd_stop_unload_daemon? I have already moved the execution of the wd_stop_unload.sh to rc.local so the service should not be there.
Re: Incomplete web update?
Posted: 30 Dec 2013, 06:09
by macke
I forgot to actually remove the init script from init.d. Did that and tried the following:
Code: Select all
root@b2:/etc# update-rc.d wd_stop_unload_daemon remove
update-rc.d: using dependency based boot sequencing
Now the apt-get dist-upgrade seem to start. However, I encounter some problems when the bubba-album needs to be updated.
Code: Select all
Setting up bubba-album (2.6) ...
dbconfig-common: writing config to /etc/dbconfig-common/bubba-album.conf
creating database backup in /var/cache/dbconfig-common/backups/bubba-album_2.5.1.3.mysql.
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: ???).
unable to connect to mysql server.
error encountered backing up the old database:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: ???)
dbconfig-common: bubba-album configure: retrying.
The error lead to an on-screen dialog for package configuration:
Code: Select all
────────────────────────────────────────────────────────────────────┤ Configuring bubba-album ├────────────────────────────────────────────────────────────────────┐
│ │
│ The bubba-album package must have a database installed and configured before it can be used. This can be optionally handled with dbconfig-common. │
│ │
│ If you are an advanced database administrator and know that you want to perform this configuration manually, or if your database has already been installed and │
│ configured, you should refuse this option. Details on what needs to be done should most likely be provided in /usr/share/doc/bubba-album. │
│ │
│ Otherwise, you should probably choose this option. │
│ │
│ Configure database for bubba-album with dbconfig-common? │
│ │
│ <Yes> <No> │
│ │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
If I choose Yes I will be promped for a password I do not have... If I choose No the configuration fails...
When choosing Abort the installation proceeds and I eventually get:
Code: Select all
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
configured to not write apport reports
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
configured to not write apport reports
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
Setting up dbus (1.2.24-4+squeeze2) ...
Reloading system message bus config...done.
system message bus already started; not starting..
Errors were encountered while processing:
bubba-album
bubba-frontend
bubba
bubba-backend
E: Sub-process /usr/bin/dpkg returned an error code (1)
After this I tried the apt-get dist-upgrade again and got the following. When the bubba-album configuration dialog showed up I choosed the 'No' option.
Code: Select all
root@b2:/# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
tor-geoipdb
0 upgraded, 0 newly installed, 0 to remove and 1 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
Replacing config file /etc/album/debian-db.php with new version
Replacing config file /etc/album/debian-db.perl with new version
Reloading web server config: apache2apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.10.1 for ServerName
.
DBD::mysql::db selectall_hashref failed: No database selected at /usr/share/bubba-album/flush_thumbs.pl line 25.
DBD::mysql::db selectall_hashref failed: No database selected at /usr/share/bubba-album/flush_thumbs.pl line 25.
Setting up bubba (2.6.0.1) ...
Setting up bubba-backend (2.6) ...
Installing new version of config file /etc/bubba/AppleVolumes.default ...
Adding 'diversion of /etc/davfs2/davfs2.conf to /etc/davfs2/davfs2.conf.bubba-distrib by bubba-backend'
Reloading services for Avahi mDNS/DNS-SD Daemon: avahi-daemon failed!
Setting up firewall...done.
update-rc.d: warning: smbrestart stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (none)
Another twistd server is running, PID 1801
This could either be a previously started instance of your application or a
different application entirely. To start a new one, either run it in some other
directory, or use the --pidfile and --logfile parameters to avoid clashes.
Another twistd server is running, PID 1763
This could either be a previously started instance of your application or a
different application entirely. To start a new one, either run it in some other
directory, or use the --pidfile and --logfile parameters to avoid clashes.
Setting up bubba-frontend (2.6.0.1+security1) ...
Restarting web server: apache2apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.10.1 for ServerName
... waiting .apache2: Could not reliably determine the server's fully qualified domain name, using 192.168.10.1 for ServerName
.
Restarting fcgi for admin functions: adminphpspawn-fcgi.c.197: child spawned successfully: PID: 27747
.
Re: Incomplete web update?
Posted: 30 Dec 2013, 07:27
by johannes
The mysql root password is empty, if that is of any help. Always - when you are asked questions during a manual update, choose the default answer, this is what the web auto-updater does.
Re: Incomplete web update?
Posted: 30 Dec 2013, 09:25
by macke
Thanks for the answer. I will keep that in mind when doing future updates.
What exactly is bubba-album? In the web interface I see a camera icon with the description "Album". If I select it I get a blank page. I guess the bubba-album function is not setup correctly? Is there anything I can do to get it work again?