[opensuse] 13.2 configuration questions

newer
[opensuse] using SNAPPER with EXT4...

Mark Goldstein

7 Dec 2014 7 Dec '14

19:02

Hi, I did clean install of 13.2 / x86-64. Most of the things are working (I have not completed it yet), but I've noticed some strange things: 1) I disabled ipv6 (and actually wicked show-xml all shows it disabled), but I see dbus-org.opensuse.Network.DHCP6 is enabled (inacive) wickedd-dhcp6.service is enabled and running ip6tables are loaded and active, during shutdown I see the system waiting on IPV6 I had to disable these services manually. Why? 2) I do not use LVM, but I see lvm2-lvmetad.service running 3) When I check in Yast what happens to services, I see a number of services "disabled" but "active"... (e.g. upowerd). What does it mean? TIA -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Andrei Borzenkov

7 Dec 7 Dec

19:21

В Sun, 7 Dec 2014 20:02:53 +0200 Mark Goldstein пишет:

...

2) I do not use LVM, but I see lvm2-lvmetad.service running

lvmetad is started on demand, when anything tries to contact it. Quite a few of tools may want to know about LVM devices, triggering startup. if you are absolutely sure you will never ever need it, you can disable both services and socket systemctl disable lvm2-lvmetad.service lvm2-lvmetad.socket systemctl stop lvm2-lvmetad.service lvm2-lvmetad.socket But then you need to edit /etc/lvm/lvm.conf and set use_lvmetad=0 to avoid warnings every time any lvm command is run.

...

3) When I check in Yast what happens to services, I see a number of services "disabled" but "active"... (e.g. upowerd). What does it mean?

"disabled" means service was not configured for autostart. This is similar to /etc/rc?.d links in previous versions. "active" means service is currently running. E.g. someone manually run /etc/init.d/foo start. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mark Goldstein

19:43

On Sun, Dec 7, 2014 at 8:21 PM, Andrei Borzenkov wrote:

...

В Sun, 7 Dec 2014 20:02:53 +0200 Mark Goldstein пишет:

Andrei, thanks for you response.

...

...
2) I do not use LVM, but I see lvm2-lvmetad.service running

lvmetad is started on demand, when anything tries to contact it. Quite a few of tools may want to know about LVM devices, triggering startup.

That's what I'm trying to understand - what tool did it?

...

if you are absolutely sure you will never ever need it, you can disable both services and socket

systemctl disable lvm2-lvmetad.service lvm2-lvmetad.socket systemctl stop lvm2-lvmetad.service lvm2-lvmetad.socket

Well, I'll do it. I do not expect I'll need LVM. I suspected that maybe virtual box needs this service, but on other systems (12.3 and 13.1) I do have virtual box and do not have this LVM service.

...

But then you need to edit /etc/lvm/lvm.conf and set use_lvmetad=0 to avoid warnings every time any lvm command is run.

use_lvmetad is set to 0 already...

...

...
3) When I check in Yast what happens to services, I see a number of services "disabled" but "active"... (e.g. upowerd). What does it mean?

"disabled" means service was not configured for autostart. This is similar to /etc/rc?.d links in previous versions. "active" means service is currently running. E.g. someone manually run /etc/init.d/foo start.

That was what I thought, so who could it be? I'm the only user and I definitely did not run them. I do not like when disabled services run by "miracle". Thanks again and regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

19:59

В Sun, 7 Dec 2014 20:43:32 +0200 Mark Goldstein пишет:

...

On Sun, Dec 7, 2014 at 8:21 PM, Andrei Borzenkov wrote:

...
В Sun, 7 Dec 2014 20:02:53 +0200 Mark Goldstein пишет:

Andrei, thanks for you response.

...
...
2) I do not use LVM, but I see lvm2-lvmetad.service running

lvmetad is started on demand, when anything tries to contact it. Quite a few of tools may want to know about LVM devices, triggering startup.

That's what I'm trying to understand - what tool did it?

In your case they are likely statically enabled, see below.

...

...
if you are absolutely sure you will never ever need it, you can disable both services and socket

systemctl disable lvm2-lvmetad.service lvm2-lvmetad.socket systemctl stop lvm2-lvmetad.service lvm2-lvmetad.socket

Well, I'll do it. I do not expect I'll need LVM. I suspected that maybe virtual box needs this service, but on other systems (12.3 and 13.1) I do have virtual box and do not have this LVM service.

...
But then you need to edit /etc/lvm/lvm.conf and set use_lvmetad=0 to avoid warnings every time any lvm command is run.

use_lvmetad is set to 0 already...

Yes, apparently there is mismatch between services and LVM configuration. Can't really comment as I have them disabled since 13.1 and update would not change it. * Wed May 28 2014 lwang@suse.com - enable lvm2-lvmetad.socket (bnc#878473) enable lvm2-lvmetad.service but * Wed May 28 2014 lwang@suse.com - disable lvmetad in lvm.conf to fix it (bnc#862076)

...

...
...
3) When I check in Yast what happens to services, I see a number of services "disabled" but "active"... (e.g. upowerd). What does it mean?

"disabled" means service was not configured for autostart. This is similar to /etc/rc?.d links in previous versions. "active" means service is currently running. E.g. someone manually run /etc/init.d/foo start.

That was what I thought, so who could it be? I'm the only user and I definitely did not run them. I do not like when disabled services run by "miracle".

Start with "systemctl list-dependencies --reverse <your-service>" to see, if any other unit requires or wants it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mark Goldstein

20:08

On Sun, Dec 7, 2014 at 8:59 PM, Andrei Borzenkov wrote:

...

В Sun, 7 Dec 2014 20:43:32 +0200 Mark Goldstein пишет:

...
On Sun, Dec 7, 2014 at 8:21 PM, Andrei Borzenkov wrote:

...
В Sun, 7 Dec 2014 20:02:53 +0200 Mark Goldstein пишет:

...

Start with "systemctl list-dependencies --reverse <your-service>" to see, if any other unit requires or wants it.

#systemctl list-dependencies --reverse upowerd.service upowerd.service ... OK, I'll try to investigate it a bit further with other services tomorrow. Thanks for advice. Regards, -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

20:13

В Sun, 7 Dec 2014 21:08:53 +0200 Mark Goldstein пишет:

...

On Sun, Dec 7, 2014 at 8:59 PM, Andrei Borzenkov wrote:

...
В Sun, 7 Dec 2014 20:43:32 +0200 Mark Goldstein пишет:

...
On Sun, Dec 7, 2014 at 8:21 PM, Andrei Borzenkov wrote:

...
В Sun, 7 Dec 2014 20:02:53 +0200 Mark Goldstein пишет:

...
Start with "systemctl list-dependencies --reverse <your-service>" to see, if any other unit requires or wants it.

#systemctl list-dependencies --reverse upowerd.service upowerd.service

It is on-demand activated by D-Bus. Has been this way for quite some tie already.

...

...

OK, I'll try to investigate it a bit further with other services tomorrow. Thanks for advice.

Regards,

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mark Goldstein

8 Dec 8 Dec

05:52

On Sun, Dec 7, 2014 at 9:13 PM, Andrei Borzenkov wrote:

...

В Sun, 7 Dec 2014 21:08:53 +0200 Mark Goldstein пишет:

...
On Sun, Dec 7, 2014 at 8:59 PM, Andrei Borzenkov wrote:

...
В Sun, 7 Dec 2014 20:43:32 +0200 Mark Goldstein пишет:

...
On Sun, Dec 7, 2014 at 8:21 PM, Andrei Borzenkov wrote:

...
В Sun, 7 Dec 2014 20:02:53 +0200 Mark Goldstein пишет:

...
Start with "systemctl list-dependencies --reverse <your-service>" to see, if any other unit requires or wants it.

#systemctl list-dependencies --reverse upowerd.service upowerd.service

It is on-demand activated by D-Bus. Has been this way for quite some tie already.

OK, thanks, probably missed it before (I mostly use 12.3, since 13.1 did not work well for me). I'll check others later. What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

07:05

On Mon, Dec 8, 2014 at 7:52 AM, Mark Goldstein wrote:

...

What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

NetworkManager or wicked? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mark Goldstein

07:17

On Mon, Dec 8, 2014 at 8:05 AM, Andrei Borzenkov wrote:

...

On Mon, Dec 8, 2014 at 7:52 AM, Mark Goldstein wrote:

...
What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

NetworkManager or wicked?

wicked (I haven't even had an option to choose NetworkManager in Yast, probably need to install package). I actually never used NetworkManager. Good old ifup/down were sufficient for my simple static network. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

15:29

On 12/07/2014 11:52 PM, Mark Goldstein wrote:

...

What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

Isn't there a way to disable it on the command line? IIR there's also a config file of equivents... I think that /etc/sysctl.conf where I have net.ipv6.conf.all.disable_ipv6 = 1 But RTFM at sysctl.conf(5), sysctl.d(5) and sysctl(8) for more information If I read that right, then you can set up a config file specific to a kernel in /boot. See also more /usr/lib/sysctl.d/50-default.conf -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mark Goldstein

16:58

On Mon, Dec 8, 2014 at 4:29 PM, Anton Aylward wrote:

...

On 12/07/2014 11:52 PM, Mark Goldstein wrote:

...
What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

Isn't there a way to disable it on the command line?

IIR there's also a config file of equivents... I think that /etc/sysctl.conf where I have

net.ipv6.conf.all.disable_ipv6 = 1

It is the same here, net.ipv6.conf.all.disable_ipv6 =1 wicked show-xml all produces <ipv6> <enabled>false</enabled> <forwarding>false</forwarding> <accept-ra>host</accept-ra> <autoconf>true</autoconf> <privacy>prefer-temporary</privacy> <accept-redirects>true</accept-redirects> </ipv6> for all interfaces. And still I see during powering up: [ 39.190148] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 40.813486] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready Why IPv6 is doing something? Should I re-build initramfs? More voodoo? Something smells bad here. If IPv6 was disabled in YaST, I would not expect any IPv6-related leftovers. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Anton Aylward

17:36

On 12/08/2014 10:58 AM, Mark Goldstein wrote:

...

On Mon, Dec 8, 2014 at 4:29 PM, Anton Aylward wrote:

...
On 12/07/2014 11:52 PM, Mark Goldstein wrote:

...
What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

Isn't there a way to disable it on the command line?

IIR there's also a config file of equivents... I think that /etc/sysctl.conf where I have

net.ipv6.conf.all.disable_ipv6 = 1

It is the same here, net.ipv6.conf.all.disable_ipv6 =1

wicked show-xml all produces <ipv6> <enabled>false</enabled> <forwarding>false</forwarding> <accept-ra>host</accept-ra> <autoconf>true</autoconf> <privacy>prefer-temporary</privacy> <accept-redirects>true</accept-redirects> </ipv6> for all interfaces.

Hmm. Can't you hand edit that?

...

And still I see during powering up:

[ 39.190148] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 40.813486] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready

Why IPv6 is doing something? Should I re-build initramfs? More voodoo? Something smells bad here. If IPv6 was disabled in YaST, I would not expect any IPv6-related leftovers.

I agree with you on that last, but I rarely do things like that with yast. I like to see what I'm configuring. I might make a change with yast and then look to see what changed as part of a learning process, but I've found that yast can be a crutch. Other posters to this list beside yourself have shown me that yast isn't comprehensive enough. Perhaps it was great enough and something got dropped in the conversion process. IIR part of it was automated. Automation is only as good as its programmed to be. I don't know about 13.2 and Drakut, but the mkinitrd in 13.1 and previously looked at what the running systems was when building the new, so if you had a ipv6 module when you ran it, you got a new kernel with ipv6. So make sure you modules are disbaled and try booting with ipv6 disabled on the command line. Then and only then run the drakut/mkinitrd Again, pre-drakut you could configure the default GRUB2 command line for the initrd. See /etc/default/grub -- perhaps you still can. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrei Borzenkov

18:51

В Mon, 8 Dec 2014 17:58:03 +0200 Mark Goldstein пишет:

...

On Mon, Dec 8, 2014 at 4:29 PM, Anton Aylward wrote:

...
On 12/07/2014 11:52 PM, Mark Goldstein wrote:

...
What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

Isn't there a way to disable it on the command line?

IIR there's also a config file of equivents... I think that /etc/sysctl.conf where I have

net.ipv6.conf.all.disable_ipv6 = 1

It is the same here, net.ipv6.conf.all.disable_ipv6 =1

wicked show-xml all produces <ipv6> <enabled>false</enabled> <forwarding>false</forwarding> <accept-ra>host</accept-ra> <autoconf>true</autoconf> <privacy>prefer-temporary</privacy> <accept-redirects>true</accept-redirects> </ipv6> for all interfaces.

And still I see during powering up:

[ 39.190148] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 40.813486] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready

Why IPv6 is doing something? Should I re-build initramfs? More voodoo? Something smells bad here. If IPv6 was disabled in YaST, I would not expect any IPv6-related leftovers.

try adding ipv6.disable=1 to kernel command line. You can alternatively add ipv6.autoconf=0 to disable autoconf. As ipv6 is built in, the only way to set it early enough is to use kernel parameter. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Mark Goldstein

19:18

On Mon, Dec 8, 2014 at 7:51 PM, Andrei Borzenkov wrote:

...

В Mon, 8 Dec 2014 17:58:03 +0200 Mark Goldstein пишет:

...
On Mon, Dec 8, 2014 at 4:29 PM, Anton Aylward wrote:

...
On 12/07/2014 11:52 PM, Mark Goldstein wrote:

...
What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

...

...
And still I see during powering up:

[ 39.190148] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 40.813486] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready

Why IPv6 is doing something? Should I re-build initramfs? More voodoo? Something smells bad here. If IPv6 was disabled in YaST, I would not expect any IPv6-related leftovers.

try adding ipv6.disable=1 to kernel command line. You can alternatively add ipv6.autoconf=0 to disable autoconf. As ipv6 is built in, the only way to set it early enough is to use kernel parameter.

Thanks Anton and Andrei. I guess Andrei is right, I'll try kernel con\mmand line parameter. Re-building initramfs did not help. The funny thing is that I've checked it now in 12.3 and saw the same thing (ipv6 ADDRCONF and ip6_table modules loaded...). Probably I just did not pay attention before I noticed that some IPV6 services are active in 13.2 -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

21:00

Mark Goldstein wrote:

...

What bothers me more are some shreds of IPv6. As I said, I disabled it (in Yast), then I manually disabled services like ip6tables and dhcp6, and I still see during power up and down the messages about IPv6 addresses configuration for my NIC. It causes power down delay, between other things.

Mark, I won't tell you that you're wrong, but leaving IPv6 active should just not cause any problems. I have never disabled IPv6, and I have never (since SuSE Linux 6) had any issues. (with lots of servers, desktops, laptops, Nintendo, androids, iphones, VoIP phones and what have you). If there is a genuine issue, I suggest it would be easier and more helpful to pursue that rather than disabling IPv6. -- Per Jessen, Zürich (3.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

3431

Age (days ago)

3432

Last active (days ago)

List overview

Download

14 comments

4 participants

participants (4)

Andrei Borzenkov
Anton Aylward
Mark Goldstein
Per Jessen

[opensuse] 13.2 configuration questions

tags

participants (4)