Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

dist-upgrade from wheezy (using systemd) to jessie hangs

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
schafdog
Posts: 9
Joined: 2014-11-19 22:46

dist-upgrade from wheezy (using systemd) to jessie hangs

#1 Post by schafdog »

I have done on previous releases, but this time it hangs on me.

It's "only" a Virtualbox, so I can reproduce it. Still haven't found a solution.

The wheezy already runs systemd, and is fully updated to to latest packages. Does not run any graphical.

Edits the source.list and does
$ apt-get update
$ apt-get upgrade # Did on one upgrade
$ apt-get dist-upgrade

It starts to upgrade (complains about missing version in libpgp-error), libc is installed, but at some point the systemd is running at high CPU and a dpkg seems to be stalled.

Any pointers? Should I disable systemd on wheezy before? This might not have been tested so much.

cheers,
:-Dennis

Bulkley
Posts: 6386
Joined: 2006-02-11 18:35
Has thanked: 2 times
Been thanked: 39 times

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#2 Post by Bulkley »

Interesting problem. I always break up dist-upgrades into manageable sections starting with the kernel, then Xorg, etc. This enables me to test as I go along. Systemd may make that impossible. However, it might be worth a try to upgrade the kernel and systemd first and then do other chunks.

I did read that systemd may require a lot of reboots a la' Windows.

Keep us posted; I'm going to watch this thread.

User avatar
dilberts_left_nut
Administrator
Administrator
Posts: 5346
Joined: 2009-10-05 07:54
Location: enzed
Has thanked: 13 times
Been thanked: 66 times

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#3 Post by dilberts_left_nut »

Also, the upgrade path as it relates to systemd in jessie, is still being refined, so you may have just tried it at the wrong time.
And a systemd init wheezy will be in the minority, and maybe not top of the to do list for the release team yet.
AdrianTM wrote:There's no hacker in my grandma...

schafdog
Posts: 9
Joined: 2014-11-19 22:46

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#4 Post by schafdog »

A small error. The package that is the problem was libgpg-error0. I got a bit further after seeing systemctl giving this error:

systemctl: /lib/x86_64-linux-gnu/libgpg-error.so.0: no version information available (required by /lib/x86_64-linux-gnu/libgcrypt.so.20)
Failed to parse message: No such device or address

and then hanging like this:
root 16805 16788 0 12:40 pts/1 00:00:00 /bin/systemctl restart auditd.service
root 16807 1 0 12:40 ? 00:00:00 /sbin/auditd -n
root 16842 15965 0 12:41 pts/2 00:00:00 grep auditd
bd:~# strace -p 16805
Process 16805 attached - interrupt to quit
ppoll([{fd=3, events=POLLIN}], 1, NULL, NULL, 8^C <unfinished ...>

By installing this before systemd.

But it now seems to hang later due to libc6 issues when a setting up systemd-sysv:

Setting up systemd-sysv (215-5+b1) ...
Selecting previously unselected package init.

with

/usr/bin/dpkg --status-fd 18 --unpack --auto-deconfigure /var/cache/apt/archives/init_1.21_amd64.deb

running at 100% CPU. gdb gives the following:
0x00007fc1813e6089 in _IO_default_xsputn () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) where
#0 0x00007fc1813e6089 in _IO_default_xsputn () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007fc1813b7ec2 in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007fc181463a35 in __vsnprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x0000000000425fde in ?? ()
#4 0x00000000004260c4 in ?? ()
#5 0x00000000004105db in ?? ()
#6 0x000000000041112b in ?? ()
#7 0x00000000004149e1 in ?? ()
#8 0x0000000000415561 in ?? ()
#9 0x00000000004068da in ?? ()
#10 0x0000000000403580 in ?? ()
#11 0x00007fc181391b45 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6

This does not look good.

schafdog
Posts: 9
Joined: 2014-11-19 22:46

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#5 Post by schafdog »

I got through, but not a clean solution.

# apt-get install linux-image-amd64
(rebooted, dont think this is needed)
# apt-get install systemd
(81 packages in all, hangs at restarting services)
I do believe there is a problem when upgrading wheezy with systemd to jessie. I think that the (newer) systemctl can't understand the older systemd, so when systemd is upgraded and not yet rebooted this hanging will happen. But you can get past hanging by killing systemctl (many times). the apt-get install systemd will now have failed with some service upgrades (and systemd).

Now I wasn't able to reboot clean at this point (shutdown -r now, halt, ACPI poweroff). Got a timeout on channel /run/initctl
Took the "power".

Did
# apt-get -f install
Now systemd was install in full.
Did
# apt-get upgrade
# apt-get dist-upgrade

with no further problems.

cheers,
:- Dennis

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#6 Post by Head_on_a_Stick »

Just for the record, I installed wheezy on a laptop yesterday from a 7.7 netinstall (with non-free firmware) then changed the sources.list to "jessie" and used `apt-get dist-upgrade`

This failed due to problems with fontconfig, so I had to force the upgrade using `aptitude full-upgrade` and selecting the first option offered.

This is not the recommended way to upgrade to jessie, but it worked.

I had no problems with systemd, but the wheezy install was completely fresh (standard full GNOME desktop installation) and was running SysVinit.
deadbang

schafdog
Posts: 9
Joined: 2014-11-19 22:46

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#7 Post by schafdog »

As the title goes, I only expect this problem if already running systemd in wheezy. So a work-around could be to switch to SysV init before upgrading.

I guess it would be valuable to try from from clean 7.7, switch to systemd to see if this will reproduce the problem. But I think I'll wait a bit. Have reached my limit of installs.

cheers,
:- Dennis

schafdog
Posts: 9
Joined: 2014-11-19 22:46

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#8 Post by schafdog »

Somebody else got hit by this and someone found a work-around:

https://www.mail-archive.com/debian-bug ... 93216.html

cheers,
Dennis


User avatar
Flemur
Posts: 25
Joined: 2015-01-22 16:52

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#10 Post by Flemur »

FWIW, I recently installed wheezy and upgraded to jessie and it worked great.

Updated /etc/apt/sources.list:

Code: Select all

# change wheezy -> jessie
#deb cdrom:[Debian GNU/Linux 7.8.0 _Wheezy_ - Official amd64 NETINST Binary-1 20150110-14:41]/ wheezy main
deb http://ftp.us.debian.org/debian/ jessie main
deb-src http://ftp.us.debian.org/debian/ jessie main

deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main

# wheezy-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ jessie-updates main
deb-src http://ftp.us.debian.org/debian/ jessie-updates main
#
# wheezy-backports
# for nvidia drivers...
#
deb http://http.debian.net/debian/ wheezy-backports main contrib non-free
#
# for flash plugin
#
deb ftp://ftp.debian.org/debian testing main contrib non-free
Method:
- edit sources.list to above (still one ref to wheezy in sources.list -?).
# apt-get update
# apt-get --download-only dist-upgrade
(accidentally rebooted here after downloads were complete...)
# apt-get dist-upgrade

"Desktop Environment" was a minimal fluxbox, starting from the 220MB wheezy installer (64bit).
Debian 8+fluxbox-pulseaudio

schafdog
Posts: 9
Joined: 2014-11-19 22:46

Re: dist-upgrade from wheezy (using systemd) to jessie hangs

#11 Post by schafdog »

You have to actively replace init with systemd to be running as PID 1 for this to happen.

Post Reply