[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [DONATE]

Update issue

user@host:~$ whonixcheck
INFO] [whonixcheck] Tor Bootstrap Result: Connected to Tor.
[INFO] [whonixcheck] Whonix is produced independently of, with no guarantee from, The Tor Project. Whonix is experimental software. Do not rely on it for strong anonymity. https://www.whonix.org
[INFO] [whonixcheck] SocksPort Test: Testing Tor’s SocksPort…
[INFO] [whonixcheck] SocksPort Test Result: Connected to Tor. IP:
[INFO] [whonixcheck] TransPort Test: Testing Tor’s TransPort…
[INFO] [whonixcheck] TransPort Test Result: Connected to Tor. IP:
[INFO] [whonixcheck] Stream Isolation Test Result: Functional.
[INFO] [whonixcheck] Whonix News Download: Checking for Whonix news and updates…
[WARNING] [whonixcheck] Whonix News Result:
✘ Outdated: Installed whonix-workstation-packages-dependencies 1.9-1 is outdated!
You should update. You can automatically update using Whonix’s internal updater. Please update using:
sudo apt-get update && sudo apt-get dist-upgrade
√ Up to date: Whonix Build Version 10.0.0.5.5
[INFO] [whonixcheck] Debian Package Update Check: Checking for software updates via apt-get…
[INFO] [whonixcheck] Debian Package Update Check Result: No updates found via apt-get.
[INFO] [whonixcheck] Whonix APT Repository: Enabled.
When the Whonix team releases WHEEZY updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please
read https://www.whonix.org/wiki/Trust to understand the risk.
If you want to change this, use:
sudo whonix_repository
[INFO] [whonixcheck] Tor Browser Update Check: Checking version…
[INFO] [whonixcheck] Tor Browser Update Check Result: Up to date.

[WARNING] [whonixcheck] Whonix News Result: ✘ Outdated: Installed whonix-workstation-packages-dependencies 1.9-1 is outdated! You should update. You can automatically update using Whonix's internal updater. Please update using: sudo apt-get update && sudo apt-get dist-upgrade

when i run sudo apt-get update && sudo apt-get dist-upgrade

user@host:~$ sudo apt-get update && sudo apt-get dist-upgrade
Hit http://mirror.whonix.de wheezy Release.gpg
Hit http://ftp.us.debian.org wheezy Release.gpg
Hit http://mirror.whonix.de wheezy Release
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://ftp.us.debian.org wheezy-backports Release.gpg
Hit http://mirror.whonix.de wheezy/main i386 Packages
Hit http://security.debian.org wheezy/updates Release
Hit http://ftp.us.debian.org wheezy Release
Hit http://security.debian.org wheezy/updates/main i386 Packages
Hit http://ftp.us.debian.org wheezy-backports Release
Hit http://security.debian.org wheezy/updates/contrib i386 Packages
Hit http://ftp.us.debian.org wheezy/main i386 Packages
Hit http://security.debian.org wheezy/updates/non-free i386 Packages
Hit http://deb.torproject.org wheezy Release.gpg
Hit http://ftp.us.debian.org wheezy/contrib i386 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://deb.torproject.org wheezy Release
Hit http://ftp.us.debian.org wheezy/non-free i386 Packages
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://deb.torproject.org wheezy/main i386 Packages
Hit http://ftp.us.debian.org wheezy/contrib Translation-en
Hit http://security.debian.org wheezy/updates/non-free Translation-en
Hit http://ftp.us.debian.org wheezy/main Translation-en
Hit http://ftp.us.debian.org wheezy/non-free Translation-en
Hit http://ftp.us.debian.org wheezy-backports/main i386 Packages/DiffIndex
Ign http://mirror.whonix.de wheezy/main Translation-en_US
Hit http://ftp.us.debian.org wheezy-backports/contrib i386 Packages/DiffIndex
Ign http://mirror.whonix.de wheezy/main Translation-en
Hit http://ftp.us.debian.org wheezy-backports/non-free i386 Packages/DiffIndex
Hit http://ftp.us.debian.org wheezy-backports/contrib Translation-en/DiffIndex
Hit http://ftp.us.debian.org wheezy-backports/main Translation-en/DiffIndex
Hit http://ftp.us.debian.org wheezy-backports/non-free Translation-en/DiffIndex
Ign http://deb.torproject.org wheezy/main Translation-en_US
Ign http://deb.torproject.org wheezy/main Translation-en
Reading package lists… Done
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.

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Now how to update packages-dependencies ?

(https://www.whonix.org/wiki/Qubes/Binary_Install#Stay_tuned)

The same big Problem! In the past (9->10) it was possible to upgrade via sudo apt-get. Works with no Problems. Now, my Updater don´t work here too. So what i have to do exactly to upgrade and i read the Link you gave before. Thank you for your Helping Hands Patrick.

Best Regards!

townsend

9 -> 10 upgrades were simpler. The derivative operating system stayed at the very same version, Debian wheezy.

Now, we have to do a Debian wheezy -> Debian jessie upgrade. It’s not that simple.

You need to read and apply https://www.whonix.org/wiki/Upgrading_Whonix_10_to_Whonix_11 from top to bottom. There is no easier way.

Other than installing a freshly downloaded images of course. Which is easier. For the gateway, I guess I personally would be too lazy and be inclined to just a get a fresh one even though that’s not the most safe option [not keeping Tor entry guards]. But then data migration is not non-trivial either. Take your pick.

Thank you Patrick for the fast answer. Main Problem for me is, how i copy my .onion Page and SQL Database to the new one???

townsend

You need to create a backup. As per https://www.whonix.org/wiki/About#Based_on_Debian. Once you have files that you want transfer, pick some method listed under https://www.whonix.org/wiki/File_Transfer for the actual file transfer. Shared folder seems easiest to me.

Ahhh, ok, thank you for the Links Patrick. I try to make a thinkover one Day, than i decide what i make. But, i will report you here.

Best Regards and thank you very much!

townsend

Ok, lets start. Decide to make the workaround.

  • Upgrading my Main OS from wheezy to jessie -> Only one Error (db5.1-util) -> fixed with (apt-get -f install) -> Done and works perfectly!

A good Tutorial who helps me. -> https://www.howtoforge.com/tutorial/how-to-upgrade-debian-wheezy-to-jessie-stable-release/

  • Starting with Sanity Test on Workstation. Done All OK!
  • Starting the Upgrade Routine on Workstation. Done ALL OK! Only a ApparMor Message.

/var/log/kern.log contains 5 denied messages in the last day. For more information, please see: https://wiki.ubuntu.com/DebuggingApparmor

Short Notice: Workstation runs very fast, faster as before.

  • Now Starting with Sanity Test on Gateway. Done All OK!
  • Starting the Upgrade Routine on Gateway. Done ALL OK!

Now, i controll the Logs to found any Errors and Bugs. I will report, when i checked.

townsend

Report Error on Gateway and Workstation.

“Failed to start LSB - Agent Damon for spice Guests”

on Gateway i get following ARM Warn

[ARM_WARN] The torrc differs from what tor's using. You can issue a sighup to reload the torrc values by pressing x. - configuration value is missing from the torrc: RunAsDaemon

The only two Errors i found! Does it give a Workaround for this Error? Other runs absolut perfectly!

Thank you in Advance for your helping Hands Patrick!

townsend

the documentation may be a little confusing at the moment, patrick. it’s reading like the steps are for qubes installs.

"Failed to start LSB - Agent Damon for spice Guests"
Unimportant. Unlesss you are using KVM (probably not) you can use:
[ARM_WARN] The torrc differs from what tor's using. You can issue a sighup to reload the torrc values by pressing x. - configuration value is missing from the torrc: RunAsDaemon
The short answer is: you can mostly ignore arm. It shows a lot bogus messages. Most are documented here: https://www.whonix.org/wiki/Tor_Controller#Arm_FAQ

Dear Patrick. Thank you very much for the fast Answer. So i use VB. Can i do

too?. I ask, before i am doing something wrong! Although thank you for the Arm Link. I will ignore this.

Unimportant. Unlesss you are using KVM (probably not) you can use:

[quote][ARM_WARN] The torrc differs from what tor’s using. You can issue a
sighup to reload the torrc values by pressing x.

Best Regards and thank you very much for your Help! Great!

townsend

Done!

Whats about the Workstation Notification? Can i ignore?

/var/log/kern.log contains 5 denied messages in the last day. For more information, please see: https://wiki.ubuntu.com/DebuggingApparmor

Best Regards!

townsend

That’s for the AppArmor sub forum.

Would there be a difference / would it be bad if instead of a reboot at the end of the upgrade process I had shut the system down ? That’s for the workstation.
That’d help me to know, in order to troubleshoot on my end, but I may elaborate more on my problem in a new thread later.

No problem.

Will follow the Thread!

https://www.whonix.org/forum/index.php/topic,1356.0.html

Best Regards!

townsend

Hi again. I just wanted to tell you about my upgrading from Whonix 9.4 to Whonix 11 (both VMs) and see if I didn’t mess anything up.

  1. I think everything went fine, but when I run whonixcheck I have “Up to date: Whonix Build Version 9.4”.
    9.4 was the version when I had installed Whonix from scratch the first time. I read somewhere in these forums that it doesn’t mean there is a problem, but I prefer to ask just to be sure.

  2. Somewhere in the upgrade process (for both VMs), I was told that kdm better be stopped so it could be fully updated. So I aborted the upgrade process, I started over again from my clean 9.4 backup files, and what I did before anything else is to run:
    sudo su
    invoke-rc.d kdm stop
    And then I followed the instructions from the start. The message about kdm didn’t show up.
    Everything okay ?

  3. After upgrading, the resolution of WorkStation was set back to what it was before I set it to 2640x1980 ( I have a 4K display ). In 9.4, I had used:
    sudo mkdir -p /etc/X11/xorg.conf.d
    kdesudo kwrite /etc/X11/xorg.conf.d/00-virtualbox-monitor.conf
    (and copied the right content in the text file).
    I had also used “xrandr --newmode”, “xrandr --addmode”, “xrandr --output”. And on the host, I had also run “vboxmanage setextradata”.
    So all had been done for the resolution to be set to 2640x1980, but upgrading to Whonix 11 set it back to what it was before.
    So I decided to go for the VB guest additions. I read that they are installed by default in Whonix 11, but the resolution couldn’t be changed. So after the upgrade, I ran:
    sudo apt-get install virtualbox-guest-x11
    and then the resolution became resizable.

Now the sanity tests give 0 as an outcome. When I start or shut down both machines, I get only green “OK”. Everything seems to run fine, but I post this just to be sure I didn’t mess anything up :slight_smile:
And by the way, thank you very much for what you do and for Whonix, I’m really enjoying it.

1) I think everything went fine, but when I run whonixcheck I have "Up to date: Whonix Build Version 9.4". 9.4 was the version when I had installed Whonix from scratch the first time. I read somewhere in these forums that it doesn't mean there is a problem, but I prefer to ask just to be sure.
https://www.whonix.org/wiki/Whonixcheck#Whonix_Build_Version
2) Somewhere in the upgrade process (for both VMs), I was told that kdm better be stopped so it could be fully updated. So I aborted the upgrade process, I started over again from my clean 9.4 backup files, and what I did before anything else is to run: sudo su invoke-rc.d kdm stop And then I followed the instructions from the start. The message about kdm didn't show up. Everything okay ?
If everything works, yes.
[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Investors] [Priority Support] [Professional Support]