Page 4 of 6
Re: Release notes for BUBBA|2 1.3.0
Posted: 16 Feb 2010, 15:37
by pcrene
Hello All,
I have 2 bubba-2 one is the backup unit because i use them for my work i cannot do without them.
The normal bubba-2 is a raidsystem with 2x 1T disk.
I updated the backup one first using SSH.
first: apt-get update and then a apt-get upgrade
result: 12 items not installed...after a reboot no apache and no samba
using SSH i did an apt-get install of the rest of the not installed units and now all seems to work.
Next week......the main bubba-2
Rene
Re: Release notes for BUBBA|2 1.3.0
Posted: 16 Feb 2010, 15:45
by ahoff
first: apt-get update and then a apt-get upgrade
Try apt-get dist-upgrade
Re: Release notes for BUBBA|2 1.3.0
Posted: 16 Feb 2010, 15:56
by pcrene
just to be curious...
what is the difference?
Rene
Re: Release notes for BUBBA|2 1.3.0
Posted: 16 Feb 2010, 16:29
by ahoff
From man apt-get
upgrade
upgrade is used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list. Packages currently installed with new
versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. New versions of
currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that
apt-get knows that new versions of packages are available.
dist-upgrade
dist-upgrade in addition to performing the function of upgrade, also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system,
and it will attempt to upgrade the most important packages at the expense of less important ones if necessary. So, dist-upgrade command may remove some packages. The /etc/apt/sources.list file
contains a list of locations from which to retrieve desired package files. See also apt_preferences(5) for a mechanism for overriding the general settings for individual packages.
Re: Release notes for BUBBA|2 1.3.0
Posted: 16 Feb 2010, 16:41
by pcrene
thank you very much...
Rene
Re: Release notes for BUBBA|2 1.3.0
Posted: 17 Feb 2010, 15:42
by urbaxe
pa wrote:The problem with the failed upgrades seems to be related to an earlier version of horde, the webmail client.
For those of you with shell access you can try the following from the command line as root:
Code: Select all
dpkg --purge --force-depends bubba-horde
apt-get -f install
These two commands will uninstall horde, thus removing all settings made in the webmail client such as identities, but not any user accounts or email, that is not related to the client itself.
The last command will then reinstall and upgrade the rest of the system.
Regarding samba, we are still working on this issue and we will try to get a fix for horde as well.
/PA
Hi,
This worked for me.
No i'm back in business again.
Thanks
Re: Release notes for BUBBA|2 1.3.0
Posted: 18 Feb 2010, 14:54
by soovizzy
Feb 18 20:35:07 HORDE [error] [horde] DB Error: connect failed: [nativecode=Access denied for user 'horde'@'localhost' (using password: YES)] ** Array [pid 4700 on line 138 of "/usr/share/horde3/lib/Horde/Prefs/sql.php"]
A fatal error has occurred
DB Error: connect failed
Details have been logged for the administrator.
Error after running reinstallation of Horde
Suggestions?
//Rolf
Re: Release notes for BUBBA|2 1.3.0
Posted: 18 Feb 2010, 15:44
by soovizzy
I have folder under /bubba2/storage/musci that do not work anymore......
But suddenly I realized that there us a /bubba2/home/storage/music that works..
So it seems new that the storage filer suddenaly appears under /home as well..
All folders works on both paths, except the /music one...
Any Clue?
//Rolf
Re: Release notes for BUBBA|2 1.3.0
Posted: 18 Feb 2010, 15:44
by soovizzy
soovizzy wrote:Feb 18 20:35:07 HORDE [error] [horde] DB Error: connect failed: [nativecode=Access denied for user 'horde'@'localhost' (using password: YES)] ** Array [pid 4700 on line 138 of "/usr/share/horde3/lib/Horde/Prefs/sql.php"]
A fatal error has occurred
DB Error: connect failed
Details have been logged for the administrator.
Error after running reinstallation of Horde
Suggestions?
//Rolf
Solved after total reinstallation of horde and removal of mysql.....sad...but working //Rolf
Re: Release notes for BUBBA|2 1.3.0
Posted: 21 Feb 2010, 08:10
by essence
Like urbaxe, the reinstall of horde worked fine for me. Everything seams to be back to normal, now with 1.3.0, and there is no need to restart samba after reboot anymore.
Thanks for the email support PA and keep up the good work.
Re: Release notes for BUBBA|2 1.3.0
Posted: 21 Feb 2010, 08:30
by RobV
I followed the instructions from PA.
Most seems fine now, except that I need to restart SAMBA manually after every reboot.
Looking forward to receiving a solution for this as well.
RobV
Re: Release notes for BUBBA|2 1.3.0
Posted: 23 Feb 2010, 17:26
by pcrene
Hello All
did the update reporting now: 1.31
all seems to be workiong, did however a few apt-get install commmands
rene
Re: Release notes for BUBBA|2 1.3.0
Posted: 23 Feb 2010, 17:57
by RobV
I tried to upgrade to 1.3.1 as well, so I repeated following commands many times:
Code: Select all
apt-get -f install
apt-get install
apt-get dist-upgrade
... but the overall version remained 1.3.0
However, after I performed the GUI upgrade once only, I immediately ended up with version 1.3.1
Code: Select all
Package name Package version
bubba-frontend 1.3.1
bubba-backend 1.3.3
bubba-album 1.3.0
filetransferdaemon 0.50.19+b3
squeezecenter 7.4.1.dfsg1-6
To be honest, I didn't expect the GUI upgrading to be more effective...
From now on I will try both methods.
RobV
Re: Release notes for BUBBA|2 1.3.0
Posted: 23 Feb 2010, 18:11
by RobV
After this upgrade to 1.3.1 Samba still does NOT start automatically after reboot.
RobV
Re: Release notes for BUBBA|2 1.3.0
Posted: 23 Feb 2010, 18:42
by asparak
If you do it using apt-get, run apt-get update then your apt-get dist-upgrade. This tells it to update its list of version etc, before trying to determine if there are new packages.