Thursday, October 20, 2011

"zypper up" error

Installation of _package_ failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: db3 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30987) getting "" records from Requireversion index
error: db3 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30987) getting "" records from Requireversion index
error: db3 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30987) getting "" records from Requireversion index
error: db3 error(-30987) from dbcursor->c_get: DB_PAGE_NOTFOUND: Requested page not found
error: error(-30987) getting "" records from Requireversion index


When I tried to run a rebuild of the rpm database as root:

# rpm -rebuilddb
rpm: arguments to --root (-r) must begin with a /

Try:
user@host:~> su -c 'rpm --rebuilddb'

Tuesday, September 27, 2011

VMware-Workstation no 32-bit CPU support anymore

grrr
just tried to install VMware-Workstation-Full-8.0.0-.i386.bundle on my 32bit workstation and got the error:

VMware Installer
"One or more of your processors does not have the necessary 64bit extensions to run VMware virtual machines."

A quick search is telling me why:

VMware communities forum:

Question:
"Is there any chance that support for 32bit CPUs (P4) will return in 8.x?"

Answer:
"No, 32-bit CPU support won't be coming back

We dropped 32-bit CPU support to make our code simpler and easier to maintain, to improve performance, and to remove constraints going forward. Continuing to support 32-bit CPUs also would have been a burden for development and for testing. Since it's no longer possible to buy 32-bit CPUs (aside from some old 32-bit Atoms), we don't believe that supporting them is worth the trouble.

Unfortunately, if you need to continue using a 32-bit CPU, you will need to use Workstation 7."

Here you have it, you need a 64-bit VT-capable CPU. Obviously this machine I'm trying to install it on doesn't have it :(

Monday, August 1, 2011

Dropbox uses port 17500

I just read at speedguide.net:

"Dropbox LanSync Protocol (db-lsp) also uses port 17500 (TCP/UDP). It is used to synchronize file catalogs between Dropbox clients on a local network."

So when you see something like this on your LAN:

22:30:04.224001 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: UDP (17), length: 156) _IP_.17500 > _IP_.255.17500: [udp sum ok] UDP, length 128

Wow they use the the same port Trojans are known to use.
Don't freak out and check your Dropbox settings. Under Preferences -> General uncheck the "Enable LAN sync" box.

Wednesday, July 27, 2011

(bogus) error messages

dedoimedo just posted some great advice I'd like to re-post, because it's very useful. Besides offering step by step instructions how to handle the
Natty & Nvidia driver not in use error he also advised: what to do, when greeted with an error message:

...
What's the lesson of this short howto? First, don't sheep-panic. Second, don't blindly follow online advice. Someone has a similar error message to yours, that does not mean they have the same problem, if at all. In this case, this is clearly a bogus error. But most importantly, you need to know how to approach and troubleshooting issues like this one.

This article teaches you how to follow the train of logic and fix your problems without going overboard with fear or despair or random copy & paste of online solutions. For example, we learned this was a bogus error message.
...

So true in so many ways.

Tuesday, April 19, 2011

time to replace Dropbox

Now that Dropbox changed it's term of use allowing US agencies access to data saved on dropbox server, it's time to check out replacements. Not that I save sensitive data on their server but I don't comply with such methods.

More information (in German) can be read at: neues-feature-bei-dropbox-backdoor-fur-us-behorden

One of the replacements I'm looking into is spideroak, aerofs and tahoe-lafs.

spideroak also released an iOS app, so I decided to install the application too.
There's also a openSUSE project page for it: en.opensuse.org/SpiderOak.

Unfortunately the version downloadable at the spideroak website is not compatible with openSUSE 11.2 anymore and the Factory link at the openSUSE page is empty too. Oh well, openSUSE will be out of support soon anyways and unless I'm going to stay and use the Evergreen version, I need to update soon.

I have an openSUSE 11.4 VM and downloaded the current openSUSE rpm from:
the spideroak download page and installed it with "rpm -ihv". It installed fine and now I only need to setup the service.

Wednesday, February 2, 2011

I/O usage per process

statistics of I/O usage per process can be found in /proc/pid/io.
There's also a great utility 'iotop' available on openSUSE collecting the data and displaying it in a nice table/graph like top does.