Mailinglist Archive: zypp-devel (47 mails)

[Jano Kupec <jkupec@xxxxxxx>]

Günther J. Niederwimmer wrote:
> Hello,
>
> Am Donnerstag, 21. Mai 2009 14:08:41 schrieb Jano Kupec:
> > Günther J. Niederwimmer wrote:
> > > Hello,
> > >
> > >
> > > yesterday my zypper is broken (?), zypper up is working but zypper dup
> > > hang ?
> > >
> > > It is only possible to stop zypper with Strg+C
> > >
> > > This is a 11.1 zypper with all Updates ?
> > >
> > >
> > > The last in zypper.log is
> > The log does not provide any clue (it looks like a corretly finished
> > zypper, although i'm not sure why the satsolver log is the last thing
> > before cleanup).
>
>
> It is a  correct finish after 2x Strg-C ?
>
> > Can you please retry it and check what is in the log at the point when
> > it is still hanging? You could also try with
>
>
>
> > $ tail -f /var/log/zypper.log
>
> tail have not sufficient "Buffer" to find this Problem :(.
>  
> > to see if it is still writing to the log.
>
> the last entree before only the satsolver message is in the log,  is
>
> 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81 
> solving....
>
> then is only hundred and hundred......
>
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving job rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving update/feature rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving job rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving update/feature rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving job rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving update/feature rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving job rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving update/feature rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving job rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving update/feature rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving job rules
> > > 2009-05-21 10:42:27 <1> techz(10789) [satsolver] PoolImpl.cc(logSat):81
> > > resolving update/feature rules
>
>
> This is the status before Strg+C
>
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypper] Zypper.cc(cleanup):4039
> > > START 2009-05-21 11:35:23 <1> techz(10789) [zypp]
> > > PathInfo.cc(_Log_Result):292 recursive_rmdir /var/tmp/TmpDir.MYWJA1
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp++] TmpPath.cc(~Impl):78
> > > TmpPath cleaned up /var/tmp/TmpDir.MYWJA1{d 0700 0/0}
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp] PathInfo.cc(_Log_Result):292
> > > recursive_rmdir /var/tmp/zypp.t8Fijv
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp++] TmpPath.cc(~Impl):78
> > > TmpPath cleaned up /var/tmp/zypp.t8Fijv{d 0700 0/0}
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypper] Zypper.cc(~Zypper):85 Bye!
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp] PathInfo.cc(_Log_Result):292
> > > recursive_rmdir /var/tmp/TmpDir.sUxNkn
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp++] TmpPath.cc(~Impl):78
> > > TmpPath cleaned up /var/tmp/TmpDir.sUxNkn{d 0700 0/0}
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp]
> > > ZYppFactory.cc(unLockFile):148 unlocked
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp]
> > > ZYppFactory.cc(~ZYppGlobalLock):81 Cleaning lock file. (10789)
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp] PathInfo.cc(_Log_Result):292
> > > unlink /var/run/zypp.pid
> > > 2009-05-21 11:35:23 <1> techz(10789) [zypp]
> > > ZYppFactory.cc(~ZYppGlobalLock):83 Lockfile cleaned. (10789)

Thanx! Now it seems clear. So it is the computing of the upgrade by the
solver what is taking so long (or forever). We will need a solver
testcase to debug this, so i suggest to open a bug in bugzilla and
attach it there. Do

$ zypper dup --debug-solver

to generate the testcase.

-- 
cheers,
jano


 Ján Kupec
 YaST team
---------------------------------------------------------(PGP)---
 Key ID: 637EE901
 Fingerprint: 93B9 C79B 2D20 51C3 800B  E09B 8048 46A6 637E E901
---------------------------------------------------------(IRC)---
 Server: irc.freenode.net
 Nick: jniq
 Channels: #zypp #yast #suse #susecz
---------------------------------------------------------(EOF)---