VortexBox 2.0: Update your system regularly

[Ron Olsen]

If you're running VortexBox 2.0, I recommend updating your VB on a regular basis (at least once a week). I update my VB 2.0 VBA every day, but that's probably overkill for more casual users.

Here's why:

* To pick up Andrew's updates to the VB software.

* To pick up updates from Fedora and Atrpms.

Fedora 16 is a new release, and Fedora updates it quite often. While none of these updates may be essential to operating your VB as a music server, it's still a good idea to update, much as you would update your Windows PC when prompted to do so by Microsoft Update.

The update can be done from the VB GUI Upgrade page by clicking the "Start Upgrade" button, or from the command line by

yum clean all; yum update

Note that it is rarely necessary to reboot after an update, despite the prompt to do so in the VB GUI. This is Linux, not Windows. The only time a reboot after update is needed is if a new kernel has been installed. Look for a new install of the kernel-PAE package. If you see this, reboot to use the new kernel. If not, continue on without a reboot.

Of course, you can also operate on the policy "it works, don't change anything". But if you do, when you decide to update, you'll have hundreds of packages to download and install. Personally, I like to have an up-to-date system, so things like DVD ripping continue to work, without outdated MakeMKV packages causing problems.

YMMV, but this is my opinion.

[Dennis A]

Thanks Ron,

As I understand it, the upgrade icon or the Command Line methods of upgrading VortexBox do not upgrade the Linux operating system, just the VB and LMS code.

If that is correct, do you foresee any problem or have any advice for those of us who have upgraded to LMS 7.7.0, and not yet from Linux 14 to Linux 16?

[Ron Olsen]

The VB GUI "Start Upgrade" button does essentially the same thing as "yum clean all; yum update" from the command line. *Both pick up Fedora (aka Linux OS) updates if any are available.

However, VB 1.10 runs on Fedora 14, which is no longer being updated by Fedora. *So you will see no Fedora updates on VB 1.10.

Therefore, it's not that important to update VB 1.10 very often. Andrew occasionally provides VB updates to VB 1.10 for VB software and LMS. Atrpms may also be providing F14 updates, but I'm not sure if they are still doing this.

VB 2.0 on Fedora 16 is the supported system going forward. I suggest updating to this platform when it's convenient for you.

[dvmis]

Just updated my VB 2.0 all went well, no errors but WEB interface is not responding any more...else works including SSH login. Tried cold reboot etc. Suggestions? Using SGC box.

[dvmis]

After trying to update via SSH got this:

yum clean all; yum update
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

** libbz2.so.1: cannot open shared object file: No such file or directory

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.2 (default, Oct 27 2011, 01:36:46)
[GCC 4.6.1 20111003 (Red Hat 4.6.1-10)]

[Ron Olsen]

See http://vortexbox.org/forum/hel.....ng/#p19929 for the fix.

[dvmis]

All fixed...superb responce time Ron :-)

[cburbs]

I did an update but get the following -

Running Transaction Check
Please report this error in http://yum.baseurl.org/report
ERROR with transaction check vs depsolve:
java-1.6.0-openjdk = 1:1.6.0.0-55.1.9.10.fc14 is needed by (installed) java-1.6.0-openjdk-plugin-1:1.6.0.0-55.1.9.10.fc14.i686
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
1:java-1.6.0-openjdk-plugin-1.6.0.0-55.1.9.10.fc14.i686 has missing requires of java-1.6.0-openjdk = ('1', '1.6.0.0', '55.1.9.10.fc14')
Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx-2011-12-14-14-112XXBnt.yumtx
12/14/2011 14:17:05 - Error: yum update failed. Check error messages and try to fix problems.

[Ron Olsen]

Are you running VB 2.0? If so, how did you upgrade to VB 2.0?

These java packages are for F14, not F16, and should not be on a VB 2.0 system.

Try this:

1. Login to your VB.

2. Enter

yum erase java*

This should remove the F14 java packages.

3. Then enter

yum install java

This should install the F16 version of java and its dependencies.

4. Then enter

yum clean all; yum update

and see if the update completes successfully.

[cburbs]

Thanks that did the trick.