Re: [Evergreen] Continuing evergreen with Leap42.2
Ruediger Meier wrote: > On Tuesday 31 January 2017, Ruediger Meier wrote: >> On Monday 30 January 2017, Greg Freemyer wrote: >> > On Mon, Jan 30, 2017 at 11:28 AM, reinhard hennig >> > >> > <reinhard.hen...@freenet.de> wrote: >> > > my administration providing 12.000 Linux clients would appreciate >> > > continueing evergreen with Leap42.2, because it is planned >> > > to switch to leap 42.2 (13.2 at the moment) in a couple of >> > > months. >> > > >> > > That would be great. >> > >> > I don't know if it is working out, but the fundamental concept of >> > Leap is that the 42.x series is easy to upgrade between. In >> > theory, 42.2 is 42.1 with a major service pack. >> > >> > Major changes will be held back until 43.x. >> >> That's the theory. In practice seems that any packager/maintainer >> changes their packages however they want. >> >> For example one of my packages (sbcl) was even not building anymore >> for 42,2 although it was fine for 42.1. I've asked to revert the >> other incompatible change which broke my package but no chance ... >> I've had to change my package too otherwise they would have even >> removed my package from 42.2! Even this was a known issue, avoiding >> or reverting incompatible changes is obviously not important for >> Leap. > > ... and it happened again. They upgraded 42.3 to texlive-2016 and it > breaks again. Evergreen is still needed. Upgrading 42.1 the other day broke a customer system for me. -- Per Jessen, Zürich (7.2°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] what did you do / leap or tumbleweed or change to a other lts distro?
Simon Becherer wrote: > Hi there, > > i like to know, what did all the guys did, who has used evergreen here > since evergreen at all is eol? > > -> going to leap ? > -> going to tumbleweed ? > -> forget opensuse and go to another lts distro? We have remained on 13.1 and 13.2. Only test systems on Leap42x at the moment. -- Per Jessen, Zürich (4.3°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] new kernel for 11.4
Michal Kubecek wrote: > On Fri, Nov 04, 2016 at 06:14:49PM +0100, Simon Becherer wrote: >> >> i am surprised, today i recogniced that you have a kernel >> update for 11.4? is this correct? >> from 3.0.101-102.1 to 3.0.101-105.1 > > It was supposed to be just an update fixing recent serious > vulnerability known as "Dirty Cow" (CVE-2016-5195, bsc#1004418) but > then I realized I forgot to actually submit the previous kernel update > in May. That's why the changelog diff looks rather strange. > > Anyway, 11.4 is definitely missing lot of other important security > fixes so anyone still running it somewhere is strongly advised to > upgrade (Leap 42.2 seems to be the most reasonable choice at the > moment, at least for servers). Careful - a 'zypper dup' could render your HP Proliant unbootable due to lack of hardware support in 422. Leap421 is ok. -- Per Jessen, Zürich (4.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] lots of systemd log messages when starting up and stopping user sessions
Carlos E. R. wrote: > On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote: >> Per Jessen wrote: >> >>> I though I would be able to reduce this by adding "Loglevel=notify" >>> to /etc/systemd/user.conf, but: >>> >>> systemd[2034]: [/etc/systemd/user.conf:11] Invalid log >>> level'notify': Operation not permitted >> >> Loglevel=notice does the trick. > > It doesn't do much here. I was getting this block, many times: > It filtered out quite a few of them. All of these are gone: 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Paths. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Paths. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Timers. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Timers. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Sockets. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Sockets. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Basic System. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Basic System. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Default. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Default. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Startup finished in 36ms. Instead of some 40 messages, I see 8 or 9, an 80% reduction :-) 2016-05-19T22:17:01+02:00 sogo systemd[1]: Starting user-1000.slice. 2016-05-19T22:17:01+02:00 sogo systemd[1]: Created slice user-1000.slice. 2016-05-19T22:17:01+02:00 sogo systemd[1]: Starting User Manager for UID 1000... 2016-05-19T22:17:01+02:00 sogo systemd[1]: Started User Manager for UID 1000. 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopping User Manager for UID 1000... 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopped User Manager for UID 1000. 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopping user-1000.slice. 2016-05-20T02:08:15+02:00 sogo systemd[1]: Removed slice user-1000.slice. Anyway, Andrei Borzenkov suggested just masking user@.service, he doesn't think it's actually being used. -- Per Jessen, Zürich (8.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] lots of systemd log messages when starting up and stopping user sessions
Carlos E. R. wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote: >> Per Jessen wrote: >> >>> I though I would be able to reduce this by adding "Loglevel=notify" >>> to /etc/systemd/user.conf, but: >>> >>> systemd[2034]: [/etc/systemd/user.conf:11] Invalid log >>> level'notify': Operation not permitted >> >> Loglevel=notice does the trick. > > Not here. > > I get: > > # <3.4> 2016-05-19 06:10:01 Telcontar systemd 12279 - - > # [/etc/systemd/user.conf:12] Unknown lvalue 'Loglevel Hmm, weird. It might be case sensitive - LogLevel=notice works for me on 13.2. -- Per Jessen, Zürich (9.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] lots of systemd log messages when starting up and stopping user sessions
Per Jessen wrote: > I though I would be able to reduce this by adding "Loglevel=notify" > to /etc/systemd/user.conf, but: > > systemd[2034]: [/etc/systemd/user.conf:11] Invalid log level'notify': > Operation not permitted Loglevel=notice does the trick. -- Per Jessen, Zürich (18.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] apache systemd notify related log message
Patrick Schaaf wrote: > With the latest systemd etc. updates for 13.1 on my production > webservers, I started to get these messages, several times a day: > > 2016-05-12T13:13:01.494327+02:00 HOSTNAME systemd[1]: apache2.service: > Got notification message from PID 14342, but reception only permitted > for main PID 1621 > > Adding "NotifyAccess=all" to apache2.service [Service] section (done > locally through a dropin at the moment), seems to fix the symptom. > > Maybe that could be put into apache2.service in a future package > update? It might be a good idea to open a bugreport on that. -- Per Jessen, Zürich (11.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Something broken with systemd or udev after the last update
Carlos E. R. wrote: > On 2016-04-29 08:41, Per Jessen wrote: >> Carlos E. R. wrote: > > >> You need to look in the files and see what refers to 'udev.service'. >> >> do the same find: >> >> find /etc/systemd /lib/systemd /usr/lib/systemd -type f | xargs >> grep -i 'udev.service' > > On the desktop, none. On the laptop... none either. > Only the desktop has the error messages. >> >> On my 13.1 system, I only have hits on: >> >> office11:~ # find /etc/systemd /lib/systemd /usr/lib/systemd -type f >> | xargs grep -i 'udev.service' >> Binary file /usr/lib/systemd/systemd matches >> Binary file /usr/lib/systemd/systemd-logind matches >> Binary file /usr/lib/systemd/systemd-udevd matches > > Yes, same here. > >> >> Fyi, I have udev-210-43.1.x86_64. >> >> > > laptop: > > udev-210-43.1.x86_64 > systemd-210-43.1.x86_64 > > desktop: > > udev-210-46.1.x86_64 > systemd-210-46.1.x86_64 > > > It is version -46 which has the problem. Hmm, I've just patched my system, I'm also -46 now. Still can't find any such message. -- Per Jessen, Zürich (13.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Where's the last 3.12 kernel update for 13.1
Ruediger Meier wrote: > On Tuesday 26 April 2016, Marcus Meissner wrote: >> On Tue, Apr 26, 2016 at 03:12:57PM +0200, Michal Kubecek wrote: >> > On úterý 26. dubna 2016 15:02 Marcus Meissner wrote: >> > > We have a fresh 3.12 kernel in QA, at >> > > http://download.opensuse.org/repositories/openSUSE:/Maintenance:/ >> > >4989/openSUSE_Leap_42.1_Update/ >> > > >> > > Could people test it? >> > >> > Should be >> > >> > http://download.opensuse.org/repositories/openSUSE:/Maintenance:/49 >> >66/openSUSE_13.1_Update/ > > BTW one thing I was always wondering about. What is the most simple > way to install such non-offcial patch without adding that Maintenance > repo. Do we have something like > > zypper patch -r >http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4966/openSUSE_13.1_Update/ > For kernels, I find it easier to just download the RPM and install with rpm or zypper. -- Per Jessen, Zürich (3.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Something broken with systemd or udev after the last update
Carlos E. R. wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On Friday, 2016-04-22 at 13:54 +0200, Patrick Schaaf wrote: >> On Fri, Apr 22, 2016 at 1:17 PM, Carlos E. R. <> wrote: >>> <3.4> 2016-04-22 13:13:02 Telcontar systemd 1 - - Cannot add >>> dependency job for unit udev.service, ignoring: Unit udev.service >>> failed to load: No such file or directory. >> >> I'm seeing this, too. Seems to be benign. > > Somebody knows how can we silence the error? Sounds like you could look through all the systemd units and grep for udev. Something depends on udev.service, which probably should depend on udevd.service. I can't find it though. Oh, there might even be a systemctl incantation that'll tell you right away. Funny, I feel certain I have also seen that message, but I can't find it now. Where do you see it Carlos? -- Per Jessen, Zürich (2.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Where's the last 3.12 kernel update for 13.1
Bruno Friedmann wrote: > Stangely on mirrors and download.o.o in update/13.1 there's no more > kernel 3.12 The metadata were created April 20th. > I still have it on my local mirror, but that hasn't been updated since 14/4. -- Per Jessen, Zürich (14.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Per Jessen wrote: > Wolfgang Rosenauer wrote: > >> Hi, >> >> yes, you are basically on the right list. Just not sure if the right >> people are here to help directly. Therefore I would kindly ask you to >> open a bug in bugzilla still for 13.1. I'll try to involve the right >> people. It's not a guarantee for resolution though. > > Okay, willdo. > https://bugzilla.opensuse.org/show_bug.cgi?id=971331 -- Per Jessen, Zürich (3.0°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
Wolfgang Rosenauer wrote: > Hi, > > yes, you are basically on the right list. Just not sure if the right > people are here to help directly. Therefore I would kindly ask you to > open a bug in bugzilla still for 13.1. I'll try to involve the right > people. It's not a guarantee for resolution though. Okay, willdo. -- Per Jessen, Zürich (2.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
