Bug 156617 - y2base delaying installation
Summary: y2base delaying installation
Status: RESOLVED FIXED
: 158307 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Beta 7
Hardware: i586 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Klaus Kämpf
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 17:51 UTC by Rasmus Plewe
Modified: 2006-04-05 19:12 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
at least the last one (181.88 KB, application/x-gzip)
2006-03-15 12:45 UTC, Lukas Ocilka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rasmus Plewe 2006-03-09 17:51:37 UTC
Updating 10.0 to 10.1 beta7, i386
After the last package installation, installation didn't proceed. It turned out that y2base was taking 100% CPU. After ~15 minutes I saw a "y2base (defunct)" in top, then installation proceeded normally. After finishing, showing the "Installation Completed" screen, the same thing happened again - no progress, y2base taking 100% CPU.
Comment 1 Michael Gross 2006-03-13 16:18:18 UTC
Have you watched excessive memory consumption of the process? Please attach the Yast logfiles here.
Comment 2 Rasmus Plewe 2006-03-13 16:56:49 UTC
This was reproducable with a new installation. No excenssive memory consumption was observed, although that depends of course on your point of view ("640k ought to be enough for everybody!"). 

Since the y2logs.tgz is 5.1M, and bugzilla only allows 512kB (-> excessive memory consumption, wissenschon), I placed the file into ~rplewe/Export/y2logs.tgz rather than splitting it into 10 pieces. 
Comment 3 Michael Gross 2006-03-14 14:58:08 UTC
You can use bzip2 for compression which results in much higher compression rates.
For now I suppose this has nothing to do with the packager.
Comment 4 Lukas Ocilka 2006-03-15 12:42:37 UTC
y2log:

The very last package installed:
2006-03-13 15:25:19 <0> linux(4010) [zypp] ExternalProgram.cc(start_program):166 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--' '/var/adm/mount/AP_0x00000001/suse/x86_64/kdevelop3-3.3.1-8.x86_64.rpm'

Next step:
2006-03-13 15:31:19 ProductControl.ycp:880 Calling `inst_hostname ($["enable_back":false, "enable_next":true])

---

Between that you can see:

2006-03-13 15:26:53 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:27:11 <0> linux(4010) [rpm] librpmDb.cc(D):83 DBACCESS {0(/)/var/lib/rpm}

2006-03-13 15:27:34 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:27:58 <0> linux(4010) [store] XMLFilesBackend.cc(storedObjects):592

2006-03-13 15:27:59 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:28:27 <0> linux(4010) [store] XMLFilesBackend.cc(storedObjects):592

2006-03-13 15:28:28 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:29:02 <0> linux(4010) [store] XMLFilesBackend.cc(storedObjects):592

2006-03-13 15:29:03 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:29:42 <0> linux(4010) [store] XMLFilesBackend.cc(storedObjects):592

2006-03-13 15:29:42 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:30:28 <0> linux(4010) [store] XMLFilesBackend.cc(storedObjects):592

2006-03-13 15:30:28 <1> linux(4010) [target] TargetImpl.cc(commit):212 TargetImpl::commit(<list>)
2006-03-13 15:31:18 <0> linux(4010) [store] XMLFilesBackend.cc(storedObjects):592

So I'd still blame libzypp for that :)
Comment 5 Lukas Ocilka 2006-03-15 12:45:09 UTC
Created attachment 73004 [details]
at least the last one
Comment 6 Lukas Ocilka 2006-03-17 10:48:38 UTC
*** Bug 158307 has been marked as a duplicate of this bug. ***
Comment 7 Michael Calmer 2006-03-21 16:23:47 UTC
Somebody taking care of this Bug?
Comment 8 Andreas Jaeger 2006-04-05 19:12:54 UTC
I don't see this with current Builds.  If it still happens with Beta9 or newer, please reopen.