17 Jun
2019
17 Jun
'19
2:46 p.m.
http://fm.no-ip.com/Tmp/SUSE/Factory/zypAbort-tw-fi965r-20190614.txt is log tails
from latest instance: zypper.log, history, dmesg & journal. I normally run
upgrades from vtty3, usually from multi-user.target, as today.
Have these spontaneous aborts been happening to everybody lately? Will it stop
once every installation has caught up with recent mass rebuilds?
--
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
17 Jun
17 Jun
9:44 p.m.
On 18/06/2019 05:16, Felix Miata wrote:
http://fm.no-ip.com/Tmp/SUSE/Factory/zypAbort-tw-fi965r-20190614.txt is log tails
from latest instance: zypper.log, history, dmesg & journal. I normally run
upgrades from vtty3, usually from multi-user.target, as today.
Have these spontaneous aborts been happening to everybody lately? Will it stop
once every installation has caught up with recent mass rebuilds?
This sounds like a bug report that should be in bugzilla rather then on
this list.
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek
SUSE Linux Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
9:52 p.m.
Simon Lees composed on 2019-06-17 22:44 (UTC-0400):
Felix Miata wrote:
>
http://fm.no-ip.com/Tmp/SUSE/Factory/zypAbort-tw-fi965r-20190614.txt is log tails
> from latest instance: zypper.log, history, dmesg & journal. I normally run
> upgrades from vtty3, usually from multi-user.target, as today.
> Have these spontaneous aborts been happening to
everybody lately? Will it stop
> once every installation has caught up with recent mass rebuilds?
This sounds like a bug report that should be in
bugzilla rather then on
this list.
It does, except for the issue of reproducibility/steps to reproduce. It's a random
thing. If it happens to others, then not likely it's something I do that others do
not. If it only happens to me, it would not likely be a fixable bug.
--
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
10:14 p.m.
On 18/06/2019 12:22, Felix Miata wrote:
Simon Lees composed on 2019-06-17 22:44 (UTC-0400):
If multiple people are hitting the issue they will find and reply on the
bug tracker this is not the place to ask if everyone has the same issue
as you. This is a place for discussing distribution wide development
changes, the people on this list that are here to do such are getting
annoyed with the amount of "offtopic" discussions.
--
Simon Lees (Simotek) http://simotek.net
Emergency Update Team keybase.io/simotek
SUSE Linux Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Felix Miata wrote:
>
http://fm.no-ip.com/Tmp/SUSE/Factory/zypAbort-tw-fi965r-20190614.txt is log tails
> from latest instance: zypper.log, history, dmesg & journal. I normally run
> upgrades from vtty3, usually from multi-user.target, as today.
> Have these spontaneous aborts been happening
to everybody lately? Will it stop
> once every installation has caught up with recent mass rebuilds?
This sounds like a bug report that should be in
bugzilla rather then on
this list.
It does, except for the issue of reproducibility/steps to reproduce. It's a random
thing. If it happens to others, then not likely it's something I do that others do
not. If it only happens to me, it would not likely be a fixable bug.
18 Jun
18 Jun
2:07 a.m.
From the log it seems zypper receives a SIGPIPE and
exists, any idea why
this
could happen in your setup?
On 6/17/19 9:46 PM, Felix Miata wrote:
http://fm.no-ip.com/Tmp/SUSE/Factory/zypAbort-tw-fi965r-20190614.txt is log tails
from latest instance: zypper.log, history, dmesg & journal. I normally run
upgrades from vtty3, usually from multi-user.target, as today.
Have these spontaneous aborts been happening to everybody lately? Will it stop
once every installation has caught up with recent mass rebuilds?
--
Benjamin Zeller <bzeller(a)suse.de>
Systems Programmer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
2:30 a.m.
Benjamin Zeller composed on 2019-06-18 09:07 (UTC+0200):
Felix Miata wrote:
>
http://fm.no-ip.com/Tmp/SUSE/Factory/zypAbort-tw-fi965r-20190614.txt is log tails
> from latest instance: zypper.log, history, dmesg & journal. I normally run
> upgrades from vtty3, usually from multi-user.target, as today.
> Have these spontaneous aborts been happening to
everybody lately? Will it stop
> once every installation has caught up with recent mass rebuilds?
From the log it seems zypper receives a SIGPIPE and
exists, any idea why this
could happen in your setup?
Absent looking at the logs, not a thing, but these two log entries 2 seconds
before the abort do bother me:
Jun 17 15:19:18 gb250 systemd[1]: Reloading.
Jun 17 15:19:19 gb250 systemd[1]: Reloading.
Just how much is expected to survive PID1 reloading?
--
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
620
days inactive
621
days old
5 comments
3 participants
participants (3)
-
Benjamin Zeller -
Felix Miata -
Simon Lees