http://bugzilla.suse.com/show_bug.cgi?id=1031400
Chenzi Cao <chcao(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bnc-team-screening(a)forge.pr |os.gnome.maintainers@gmail.
|ovo.novell.com |com
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1031434
Chenzi Cao <chcao(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bnc-team-screening(a)forge.pr |jengelh(a)inai.de
|ovo.novell.com |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1031476
Chenzi Cao <chcao(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bnc-team-screening(a)forge.pr |sbrabec(a)suse.com
|ovo.novell.com |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1031892
Bug ID: 1031892
Summary: snapperd in connection with other process consumes
100% CPU
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: hehe_br-opensuse(a)yahoo.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 719527
--> http://bugzilla.suse.com/attachment.cgi?id=719527&action=edit
hwinfo
Hi, I have installed Tumbleweed for a month now, and almost twice a day these
process consumes 100% CPU, only the mouse responds for about 10 minutes or
more:
snapperd
brtfs_cleaner
brtfs_transacti
kworker/u8:x
file_baloo
It sometimes happens during the login, other times randomly. Even to connect to
the tty (CTRL SHIFT f1) to run the command "top" takes about three minutes.
Before I was using openSUSE Leap and I had never had a problem with snapper.
openSUSE Tumbleweed 20170328
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1026212
Bug ID: 1026212
Summary: Apache doesn't start correctly on boot (very often)
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.1
Hardware: x86-64
OS: openSUSE 42.1
Status: NEW
Severity: Major
Priority: P5 - None
Component: Apache
Assignee: bnc-team-apache(a)forge.provo.novell.com
Reporter: studio(a)anchev.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I have been experiencing this so many times and I can't find a pattern. The
system boots normally but the few sites which I have on the local machine don't
load (404). Running 'rcapache2 restart' makes everything work but I can't find
why it sometimes happens and based on what factors.
Looking at /var/log/apache2/error_log:
-------------------------------------
[Sun Feb 19 16:28:30.000427 2017] [:notice] [pid 1767] ModSecurity for
Apache/2.9.0 (http://www.modsecurity.org/) configured.
[Sun Feb 19 16:28:30.469773 2017] [:notice] [pid 1767] ModSecurity: APR
compiled version="1.5.1"; loaded version="1.5.1"
[Sun Feb 19 16:28:30.469792 2017] [:notice] [pid 1767] ModSecurity: PCRE
compiled version="8.33 "; loaded version="8.39 2016-06-14"
[Sun Feb 19 16:28:30.469798 2017] [:warn] [pid 1767] ModSecurity: Loaded PCRE
do not match with compiled!
[Sun Feb 19 16:28:30.469802 2017] [:notice] [pid 1767] ModSecurity: LUA
compiled version="Lua 5.2"
[Sun Feb 19 16:28:30.469807 2017] [:notice] [pid 1767] ModSecurity: LIBXML
compiled version="2.9.1"
[Sun Feb 19 16:28:30.469811 2017] [:notice] [pid 1767] ModSecurity: Status
engine is currently disabled, enable it by set SecStatusEngine to On.
[Sun Feb 19 16:28:30.495914 2017] [core:error] [pid 1767] (EAI 2)Name or
service not known: AH00547: Could not resolve host name site1.local --
ignoring!
[Sun Feb 19 16:28:30.495979 2017] [core:error] [pid 1767] (EAI 2)Name or
service not known: AH00547: Could not resolve host name site2.local --
ignoring!
[Sun Feb 19 16:28:30.496037 2017] [core:error] [pid 1767] (EAI 2)Name or
service not known: AH00547: Could not resolve host name site3.local --
ignoring!
[Sun Feb 19 16:28:31.018255 2017] [mpm_prefork:notice] [pid 1767] AH00163:
Apache/2.4.16 (Linux/SUSE) OpenSSL/1.0.1i-fips configured -- resuming normal
operations
[Sun Feb 19 16:28:31.018285 2017] [core:notice] [pid 1767] AH00094: Command
line: '/usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -D SYSCONFIG -D SSL
-C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -D SYSTEMD
-D FOREGROUND'
-------------------------------------
I ran 'rcapache2 restart' and in the same log I see:
-------------------------------------
[Sun Feb 19 16:33:38.465418 2017] [mpm_prefork:notice] [pid 1767] AH00170:
caught SIGWINCH, shutting down gracefully
[Sun Feb 19 16:33:39.000468 2017] [:notice] [pid 3473] ModSecurity for
Apache/2.9.0 (http://www.modsecurity.org/) configured.
[Sun Feb 19 16:33:39.000561 2017] [:notice] [pid 3473] ModSecurity: APR
compiled version="1.5.1"; loaded version="1.5.1"
[Sun Feb 19 16:33:39.000568 2017] [:notice] [pid 3473] ModSecurity: PCRE
compiled version="8.33 "; loaded version="8.39 2016-06-14"
[Sun Feb 19 16:33:39.000572 2017] [:warn] [pid 3473] ModSecurity: Loaded PCRE
do not match with compiled!
[Sun Feb 19 16:33:39.000575 2017] [:notice] [pid 3473] ModSecurity: LUA
compiled version="Lua 5.2"
[Sun Feb 19 16:33:39.000579 2017] [:notice] [pid 3473] ModSecurity: LIBXML
compiled version="2.9.1"
[Sun Feb 19 16:33:39.000582 2017] [:notice] [pid 3473] ModSecurity: Status
engine is currently disabled, enable it by set SecStatusEngine to On.
[Sun Feb 19 16:33:40.013885 2017] [mpm_prefork:notice] [pid 3473] AH00163:
Apache/2.4.16 (Linux/SUSE) OpenSSL/1.0.1i-fips configured -- resuming normal
operations
[Sun Feb 19 16:33:40.013934 2017] [core:notice] [pid 3473] AH00094: Command
line: '/usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -D SYSCONFIG -D SSL
-C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -D SYSTEMD
-D FOREGROUND'
[Sun Feb 19 16:33:45.022714 2017] [core:notice] [pid 3473] AH00052: child pid
3485 exit signal Segmentation fault (11)
[Sun Feb 19 16:33:47.024813 2017] [core:notice] [pid 3473] AH00052: child pid
3486 exit signal Segmentation fault (11)
[Sun Feb 19 16:33:52.029721 2017] [core:notice] [pid 3473] AH00052: child pid
3481 exit signal Segmentation fault (11)
[Sun Feb 19 16:34:16.054527 2017] [core:notice] [pid 3473] AH00052: child pid
3505 exit signal Segmentation fault (11)
[Sun Feb 19 16:34:17.056118 2017] [core:notice] [pid 3473] AH00052: child pid
3501 exit signal Segmentation fault (11)
[Sun Feb 19 16:34:17.056145 2017] [core:notice] [pid 3473] AH00052: child pid
3502 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:13.176170 2017] [core:notice] [pid 3473] AH00052: child pid
3508 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:28.191208 2017] [core:notice] [pid 3473] AH00052: child pid
3506 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:28.191241 2017] [core:notice] [pid 3473] AH00052: child pid
3507 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:38.201731 2017] [core:notice] [pid 3473] AH00052: child pid
3617 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:40.204770 2017] [core:notice] [pid 3473] AH00052: child pid
3620 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:41.207193 2017] [core:notice] [pid 3473] AH00052: child pid
3621 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:51.219528 2017] [core:notice] [pid 3473] AH00052: child pid
3555 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:54.222686 2017] [core:notice] [pid 3473] AH00052: child pid
3480 exit signal Segmentation fault (11)
[Sun Feb 19 16:36:54.222723 2017] [core:notice] [pid 3473] AH00052: child pid
3489 exit signal Segmentation fault (11)
[Sun Feb 19 16:37:13.241850 2017] [core:notice] [pid 3473] AH00052: child pid
3642 exit signal Segmentation fault (11)
-------------------------------------
and after that everything works as expected.
All the HDD and SSD drives on the system are healthy. site1.local, site2.local
and site3.local are properly configured in /etc/hosts and point to 127.0.0.1
When this happens I notice that Apache starts before wicked:
-------------------------------------
[~]: systemd-analyze blame
6.767s nut-driver.service
2.222s apache2.service
2.124s mysql.service
2.027s wicked.service
1.353s ModemManager.service
1.292s SuSEfirewall2_init.service
302ms php-fpm.service
275ms avahi-daemon.service
266ms libvirtd.service
242ms SuSEfirewall2.service
...
-------------------------------------
But this is strange considering that the service says the unit should start
after network.target:
-------------------------------------
cat /usr/lib/systemd/system/apache2*
[Unit]
Description=The Apache Webserver
After=network.target nss-lookup.target time-sync.target remote-fs.target
Before=getty(a)tty1.service plymouth-quit.service xdm.service
[Service]
Type=notify
PrivateTmp=true
ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start
ExecReload=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful
ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop
KillMode=mixed
[Install]
WantedBy=multi-user.target
Alias=httpd.service apache.service
[Unit]
Description=The Apache Webserver %I
After=network.target nss-lookup.target time-sync.target
Before=getty(a)tty1.service plymouth-quit.service xdm.service
[Service]
Type=notify
PrivateTmp=true
Environment="HTTPD_INSTANCE=%i"
ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start
ExecReload=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful
ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop
KillMode=mixed
[Install]
WantedBy=multi-user.target
Alias=httpd@.service apache@.service
-------------------------------------
BTW in /usr/lib/systemd/system I have 2 services: apache2.service and
apache2@.service - is that normal and why are they 2?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1032006
Bug ID: 1032006
Summary: VUL-0: CVE-2017-7374: kernel-source: denial of service
(NULL pointer dereference) or possibly gain privileges
by revoking keyring keys being used for ext4, f2fs, or
ubifs encryption
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Security
Assignee: security-team(a)suse.de
Reporter: mikhail.kasimov(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Ref: https://nvd.nist.gov/vuln/detail/CVE-2017-7374
====================================================
Description
Use-after-free vulnerability in fs/crypto/ in the Linux kernel before 4.10.7
allows local users to cause a denial of service (NULL pointer dereference) or
possibly gain privileges by revoking keyring keys being used for ext4, f2fs, or
ubifs encryption, causing cryptographic transform objects to be freed
prematurely.
Source: MITRE Last Modified: 03/31/2017
====================================================
Hyperlink:
[1]
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1…
[2]
https://github.com/torvalds/linux/commit/1b53cf9815bb4744958d41f3795d5d5a1d…
[3] https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.10.7
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=999818
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|ibs:running:4392:low |ibs:running:4392:low
|maint:planned:update |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1031025
Bug ID: 1031025
Summary: brtfs + grub2, save default produces error: sparse
file not allowed at boot
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: openSUSE 42.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: harald.achitz(a)gmail.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Firefox/52.0
Build Identifier:
default openSUSE installation with a brtfs root partition
setup grub2 to save and boot the last used entry
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT="true"
reboot
save default does not work, it will always boot the first in the list, and an
error messages is displayed
sparse file not allowed at boot
Reproducible: Always
Steps to Reproduce:
1. install btrfs root partition and dual boot, for example with windows
2. setup grub2 to save default and boot saved
3. reboot
Actual Results:
instead of booting the last selected boot menu, always the default is used and
an error
error: sparse file not allowed at boot
is displayed
Expected Results:
to boot the last selected boot entry without any problems
--
You are receiving this mail because:
You are on the CC list for the bug.