Mailinglist Archive: opensuse (3441 mails)

[Jan Kupec <jkupec@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Josef Wolf wrote:
> Hello,
>
> I am running "zypper -n -q refresh" regularly from a cron job.  This was 
> working fine in the last couple of weeks.  But yesterday, it just got
> stuck.  Today, I noticed that it was hanging for about 20 hours, eating
> all the available CPU.  It also filled all my /var partition with a
> 16GB logfile.  Then I killed it (twice).  The only output was:
>
>     Timeout exceed
>     
>     OK OK! Exiting immediately...
>
> Most of the logfile contains lines like this:
>
>     2009-01-15 20:49:10 <2> raven(29162) [zypper] 
> prompt.cc(read_action_ari_with_timeout):129 Unknown char 377
>
> (the 377 is actually the byte 0xff which less shows in octal format)
>
> This looks to me like zypper is ignoring the -n switch and trying to
> read from stdin.  It also looks like the end-of-file condition on stdin
> is not handled correctly.
>
> Here are the last couple of lines before the "Unknown char" lines:

> Any ideas?

I believe this has already been fixed, you are probably using an old
zypper(?). If not please open a bug report. It's much better to report
such problems via bugzilla, it will reach developers more easily.


- --
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)---
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkl11GwACgkQgEhGpmN+6QE/BACfWaW7b6tsOHDxfm7zLQVPA/Gg
yGAAn0M+hdxK9QO/9frTvcNRAlo016/k
=nYHA
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx