Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday, 2016-02-26 at 14:47 +0100, Marcus Meissner wrote:
Hi,
The 3.12 kernel version upgrade prepared by Michal is ready for testing:
http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4624/openSUSE_13.1_Update/
We will wait for positive feedback.
Any suggestion for machines using the propietary nvida driver, installed
the "easy way" (the rpm)? Should it work, or would I have to use the
manual installer? :-?
- --
Cheers,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlbZdXMACgkQtTMYHG2NR9WetgCbBVT1KZcNMx3zoOQz6posCDL6
wr8Ani6fd39qtXxWKOIlOWwgwo/8RtNu
=zySo
-END PGP SIGNATURE-
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2016-03-04 13:21, Bruno Friedmann wrote: > On vendredi, 4 mars 2016 12.45:55 h CET Carlos E. R. wrote: >> Any suggestion for machines using the propietary nvida driver, >> installed the "easy way" (the rpm)? Should it work, or would I >> have to use the manual installer? :-? > > I'm personally using a local rebuild of the actual rpm and they > work nicely with. G04 . > > It could be possible for myself to share the result, but I will > only do it for G04 version, any oldies is out of my scope, as I > will not have hardware to test it. > > This reminder me to perhaps also have a special rebuild for fglrx. Mine is G03. nvidia-glG03-331.79-27.1.x86_64 I will probably have to use the .run - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlbZiCEACgkQtTMYHG2NR9X3GgCfXh2C/ZTGhILFnWux9FknwfKI PeAAnR/qo4AEZx4cOOTlRF7MVPGaHgJ4 =tpgS -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
On Friday, 2016-02-26 at 14:47 +0100, Marcus Meissner wrote: The 3.12 kernel version upgrade prepared by Michal is ready for testing: http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4624/openSUSE_13.1_Update/ We will wait for positive feedback. Ciao, Marcus On nvidia with propietary driver, easy method (rpm), I get a display, but not by nvidia (trying startx) Initializing built-in extension DRI2 Loading extension GLX FATAL: Module nvidia not found. FATAL: Module nvidia_uvm not found. sh: cat: command not found /usr/bin/mknod: missing operand after 0 Try '/usr/bin/mknod --help' for more information. sh: chown: command not found sh: chown: command not found FATAL: Error running install command for nvidia The XKEYBOARD keymap compiler (xkbcomp) reports: I guess that installing the driver the "hard way" would work, perhaps I'll try later. On text mode console, I get some weird effects with redrawing the screen with Alpine (it is what I'm using to compose this), but 'mc' seems fine. I have also tried a laptop with Intel video, seems to work better. Tried hibernation, no problem there. -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2016-03-04 14:05, Carlos E. R. wrote: > On 2016-03-04 13:21, Bruno Friedmann wrote: >> On vendredi, 4 mars 2016 12.45:55 h CET Carlos E. R. wrote: > > >>> Any suggestion for machines using the propietary nvida driver, >>> installed the "easy way" (the rpm)? Should it work, or would I >>> have to use the manual installer? :-? > >> I'm personally using a local rebuild of the actual rpm and they >> work nicely with. G04 . > >> It could be possible for myself to share the result, but I will >> only do it for G04 version, any oldies is out of my scope, as I >> will not have hardware to test it. > >> This reminder me to perhaps also have a special rebuild for >> fglrx. > > Mine is G03. > > nvidia-glG03-331.79-27.1.x86_64 > > I will probably have to use the .run That is so, I had to use "the hard way". https://en.opensuse.org/SDB:NVIDIA_the_hard_way I also had to manually blacklist nouveau, or it insisted in loading and caused nvidia to crash. And do not forget to run mkinitrd. Previous to that, I "prepared" the kernel sources: echo -e "\n-- cloneconfig --" && make cloneconfig && \ echo -e "\n-- scripts --" && make scripts && \ echo -e "\n-- prepare --" && make prepare && \ echo -e "\n-- Done good! --" After that, it seems to run alright. I have also tested vmware player. So far, looks good. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlbasa0ACgkQtTMYHG2NR9V+dACfXq5cwLdZIhhXXiEa04+rM7GU XxoAnihIpbfG1ZMiDxmC6IQMfLuKgb+/ =sqlP -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
On 2016-03-11 08:24, Patrick Schaaf wrote:
> Now, when updating (zypper dup) with the 3.12 update, zypper tells me
> that in addition to kernel-vanilla, kernel-pae needs to be installed.
> I don't even have kernel-pae in my repo mirrors, because I exclude all
> the non-x86_64 stuff there.
When the package manager wants to install a 32 bit package on a 64 bit
installation it typically is because it doesn't find a 64 bit solution.
Some wanted 64 bit rpm does not exist on the repos.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Every second: "reset full-speed USB device number 2 using uhci_hcd"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I see this activity in the log since I updated my 32b server machine (on 13.1): <0.6> 2016-03-15T22:16:00.928142+01:00 AmonLanc kernel - - - [39604.176042] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:03.620149+01:00 AmonLanc kernel - - - [39606.868059] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:03.904177+01:00 AmonLanc kernel - - - [39607.152036] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:04.188133+01:00 AmonLanc kernel - - - [39607.436027] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:04.468134+01:00 AmonLanc kernel - - - [39607.716025] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:04.748172+01:00 AmonLanc kernel - - - [39607.996030] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:05.028142+01:00 AmonLanc kernel - - - [39608.276028] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <4.6> 2016-03-15T22:16:06.499228+01:00 AmonLanc sshd 19184 - - Postponed keyboard-interactive for cer from 192.168.1.14 port 36885 ssh2 [preauth] <0.6> 2016-03-15T22:16:07.716135+01:00 AmonLanc kernel - - - [39610.964033] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:07.996185+01:00 AmonLanc kernel - - - [39611.244802] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:08.276194+01:00 AmonLanc kernel - - - [39611.524038] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:08.556139+01:00 AmonLanc kernel - - - [39611.804036] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:08.836141+01:00 AmonLanc kernel - - - [39612.084029] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:09.116140+01:00 AmonLanc kernel - - - [39612.364037] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <4.6> 2016-03-15T22:16:09.362115+01:00 AmonLanc sshd 19184 - - Postponed keyboard-interactive/pam for cer from 192.168.1.14 port 36885 ssh2 [preauth] <4.6> 2016-03-15T22:16:09.365062+01:00 AmonLanc sshd 19184 - - Accepted keyboard-interactive/pam for cer from 192.168.1.14 port 36885 ssh2 <3.6> 2016-03-15T22:16:11.188082+01:00 AmonLanc systemd 1 - - Starting Session 115 of user cer. <3.6> 2016-03-15T22:16:11.188801+01:00 AmonLanc systemd 1 - - Started Session 115 of user cer. <4.6> 2016-03-15T22:16:11.189238+01:00 AmonLanc systemd-logind 1709 - - New session 115 of user cer. <0.6> 2016-03-15T22:16:11.812003+01:00 AmonLanc kernel - - - [39615.060032] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:12.092136+01:00 AmonLanc kernel - - - [39615.340043] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:12.372149+01:00 AmonLanc kernel - - - [39615.620048] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:12.652159+01:00 AmonLanc kernel - - - [39615.900049] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:12.932161+01:00 AmonLanc kernel - - - [39616.180042] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:13.220134+01:00 AmonLanc kernel - - - [39616.468048] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:15.908494+01:00 AmonLanc kernel - - - [39619.156075] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:16.192156+01:00 AmonLanc kernel - - - [39619.440043] usb 4-2: reset full-speed USB device number 2 using uhci_hcd Previous to the update, this happened 3 times per month. Today, the log has rotated because of that and contains more than 6 entries. cer@AmonLanc:~> uname -a Linux AmonLanc 3.12.53-40-default #1 SMP Thu Feb 25 06:26:23 UTC 2016 (b2ce64e) i686 i686 i386 GNU/Linux cer@AmonLanc:~> What can I do to stop this? I know how to filter the syslog, but I would like to stop the problem. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlboho8ACgkQtTMYHG2NR9XWrQCgjnDufUZGmZOXaCCD4KD4Vlqj Uu0AoIluA8KHN01PaGPRRL2nWFlC69mh =Ja0J -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] systemd complains about some service permissions:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<3.4> 2016-03-16 00:00:05 Telcontar systemd 1 - - Configuration file
/usr/lib/systemd/system/mgetty@.service is marked executable. Please remove
executable permission bits. Proceeding anyway.
<3.4> 2016-03-16 00:00:05 Telcontar systemd 1 - - Configuration file
/usr/lib/systemd/system/vgetty@.service is marked executable. Please remove
executable permission bits. Proceeding anyway.
This is new, after the recent update to systemd.
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlbolmYACgkQtTMYHG2NR9WoTACgk4rQebqJAgeA5MasJKsV8kdB
jHoAnjU+yDNsWjTmID5lUtERYG24KlW4
=Dkuy
-END PGP SIGNATURE-
___
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).
On 2016-03-16 09:05, Per Jessen wrote:
> I updated my 13.1 office desktop last week, I saw somebody mention a
> new 3.12 kernel. On start-up, it now claims one of two NFS drives
> couldn't be mounted, although in fact they were both mounted. This
> caused postfix and X not to be started. I commented out of the mounts
> in /etc/fstab and rebooted, now it worked.
I have an nfs mount, but it is done manually, not on boot, and there is no
issue :-?
AmonLanc:~ # systemctl status nfs.service
nfs.service - LSB: NFS client services
Loaded: loaded (/etc/init.d/nfs)
Drop-In: /run/systemd/generator/nfs.service.d
└─50-insserv.conf-$remote_fs.conf
Active: active (running) since Tue 2016-03-15 23:36:17 CET; 10h ago
Process: 2487 ExecStart=/etc/init.d/nfs start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/nfs.service
└─2562 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs
Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR:
gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab
/etc/krb5.keytab ...r.valinor
Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for
connection to server Telcontar.valinor
Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR:
gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab
/etc/krb5.keytab ...r.valinor
Mar 16 10:12:07 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for
connection to server Telcontar.valinor
Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR:
gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab
/etc/krb5.keytab ...r.valinor
Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for
connection to server Telcontar.valinor
Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR:
gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab
/etc/krb5.keytab ...r.valinor
Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for
connection to server Telcontar.valinor
Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR:
gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab
/etc/krb5.keytab ...r.valinor
Mar 16 10:12:08 AmonLanc rpc.gssd[2562]: ERROR: No credentials found for
connection to server Telcontar.valinor
Hint: Some lines were ellipsized, use -l to show in full.
AmonLanc:~ # systemctl status var-cache-zypp-nfs_packages.mount
var-cache-zypp-nfs_packages.mount - /var/cache/zypp/nfs_packages
Loaded: loaded (/etc/fstab)
Active: active (mounted) since Wed 2016-03-16 10:12:08 CET; 1min 9s ago
Where: /var/cache/zypp/nfs_packages
What: telcontar.valinor:/data/storage_c/repositorios_zypp
AmonLanc:~ #
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Every second: "reset full-speed USB device number 2 using uhci_hcd"
On 2016-03-16 10:18, Michal Kubecek wrote: >> cer@AmonLanc:~> uname -a >> Linux AmonLanc 3.12.53-40-default #1 SMP Thu Feb 25 06:26:23 UTC 2016 >> (b2ce64e) i686 i686 i386 GNU/Linux >> cer@AmonLanc:~> > > Please open a bug in bugzilla, assign it to me and attach output of > > lsusb -v > lspci -v > lsmod > > and (if possible) the part of log from boot to first few of the messages > (there might be some clue preceding the first message). Ok, will do. Thanks. I did a "rmmod uhci_hcd" to stop the messages, so I will have to reboot to get a pristine log. The interface belongs to an empty pcmcia card slot. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ 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).
On 2016-03-16 12:40, Patrick Schaaf wrote: > I also ran into this issue, some weeks ago. See > > http://bugzilla.suse.com/show_bug.cgi?id=968042 > > It is pretty much analyzed. > > /etc/init.d/xdm > /etc/init.d/ntp > and > /usr/lib/systemd/system/postfix.service > > all have dependencies on remote-fs which they would better not have. > > Just updated that bug report with the workarounds I use to cope with the > issue. I just had an nfs client problem: when shutting down the machine, it hanged at umounting or stopping the nfs mount. I don't know if it is related. I had to press the power button hard. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Every second: "reset full-speed USB device number 2 using uhci_hcd"
On 2016-03-16 10:43, Carlos E. R. wrote: > On 2016-03-16 10:18, Michal Kubecek wrote: >> Please open a bug in bugzilla, assign it to me and attach output of >> >> lsusb -v >> lspci -v >> lsmod >> >> and (if possible) the part of log from boot to first few of the messages >> (there might be some clue preceding the first message). > > Ok, will do. Thanks. Done. https://bugzilla.opensuse.org/show_bug.cgi?id=971387 -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] after systemd 210 update, abandoned scope units, related to cron, bunch up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday, 2016-03-18 at 18:18 +0100, Patrick Schaaf wrote: Hi list, I'd like to bring https://bugzilla.novell.com/show_bug.cgi?id=968629 to somebodies attention :) Since the systemd-210 update, on pretty much all systems where I have somewhat high frequency cronjobs running, more and more "abandoned scope units" hang around, as can be easily seen by running "systemctl | fgrep abandon". Just a few: Telcontar:~ # systemctl | fgrep abandon session-1252.scope loaded active abandoned Session 1252 of user news session-1439.scope loaded active abandoned Session 1439 of user news session-1449.scope loaded active abandoned Session 1449 of user news session-1913.scope loaded active abandoned Session 1913 of user wwwrun session-2.scope loaded active abandoned Session 2 of user lightdm session-313.scope loaded active abandoned Session 313 of user news session-887.scope loaded active abandoned Session 887 of user news Telcontar:~ # Occasionally, but a lot more rarely, there is /var/log/warn logspam, too, with messages from pam_systemd(crond:session) regarding "Failed to create session". I have a bunch of them on 2015-02-24, then another two on 2016-03-04. I'd primarily like to ask whether somebody else here is seeing these symptoms. Of course, ideas regarding fixes are welcome, too :) There was another update to systemd to correct problems in the previous systemd update: Telcontar:~ # rpm -q systemd systemd-210-43.1.x86_64 Telcontar:~ # I skipped the previous update. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlbsUs0ACgkQtTMYHG2NR9Xm6QCfVQIzIsDA+iN73n8aBBkS9DnE k1MAn1yx04XZgTm0jc2Ai+dYIr6wg02L =KI9V -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Little bug in systemd.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I reported: "Bug 972770 - systemd 210 says some files have wrong permissions". I'm told that it has been solved for recent releases, and to "submit maintenance request yourself". I have no idea how to do that, I'm not a maintainer. :-( What I know is how to edit the problem files in my system and solve the issue for me, which I did. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlb33BwACgkQtTMYHG2NR9VmVACfYOiQb/cdYtlT/aHGYhO27VMP MXAAn3kV9Cm4nfZuzFIy7f6F1QJthnb5 =2mtz -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] haveged spins after kernel upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, 2016-03-30 at 12:53 +0200, Tom Eicher wrote: how come you have -w 1024 here ? I also have 1024. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlb7v5MACgkQtTMYHG2NR9XzggCeLklSaZnVWykxzdXYzi2Qg5r2 2rwAn3ECyU+D0kpCOptl0EN+2vibM/48 =jDjJ -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1: nscd consumes a lot of memory
entries 0% cache hit rate 9 current number of cached values 98 maximum number of cached values 3 maximum chain length searched 0 number of delays on rdlock 0 number of delays on wrlock 0 memory allocations failed yes check /etc/services for changes netgroup cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 0 used data pool size 28800 seconds time to live for positive entries 20 seconds time to live for negative entries 0 cache hits on positive entries 0 cache hits on negative entries 0 cache misses on positive entries 0 cache misses on negative entries 0% cache hit rate 0 current number of cached values 0 maximum number of cached values 0 maximum chain length searched 0 number of delays on rdlock 0 number of delays on wrlock 0 memory allocations failed yes check /etc/netgroup for changes No hits at all, all misses on all sections. :-? >> but I am still on kernel-desktop-3.11.10-29.1.x86_64 >>nscd-2.18-4.44.1.x86_64 > > I assume that it has something to do with recent updates (kernel, > systemd?). Mine is updated, I think. At least on those two. I have these pending (zypper patch): MozillaThunderbird bind-libs bind-utils libgif6 openssh timezone timezone-java > Maybe my NIS setup is also a bit unusual but this is the > reason why I run nscd at all. > > Anyways it's for sure a bug. It should never use much more than > (5 * 32M) = 160M: That would be a huge lot for me, in that machine: 0.5GiB RAM total. > $ grep max-db /etc/nscd.conf > # max-db-size > max-db-size passwd 33554432 > max-db-size group 33554432 > max-db-size hosts 33554432 > max-db-size services33554432 > max-db-size netgroup33554432 > > > I really hate that nscd. I've had also problems with it a few years ago > on 11.4. (crashs, 100% CPU, ...). I wonder why the glibc people do not > fix it. Instead they have added a "paranoia" mode to restart it > regularly: > http://serverfault.com/questions/463648/why-would-nscd-use-a-huge-amount-of-ram > > I'll try /etc/nscd.conf: > paranoiayes > restart-interval3600 Oh. I wondered what that was. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1: nscd consumes a lot of memory
On 2016-04-06 22:02, Ruediger Meier wrote: > On Wednesday 06 April 2016, Patrick Shanahan wrote: >> passwd cache: >> [...] >> 3 cache hits on positive entries >> 0% cache hit rate > >> group cache: >> [...] >> 13 cache hits on positive entries >> 0% cache hit rate >> >> hosts cache: >> [...] >> 692 cache hits on positive entries >> 5% cache hit rate > >> services cache: >> [...] >> 1 cache hits on positive entries >> 3 cache hits on negative entries >> 0% cache hit rate > >> >> netgroup cache: >> [...] >> 0 cache hits on positive entries >> 0% cache hit rate > > > Only the host cache has at least 5% cache hit rate. Better than nothing? > Absolute just 692 times within 42 days a minor speed-up to safe a few > milliseconds. I wonder if it's really worth to run that buggy nscd at > all. On my machines I've found none with a cache hit rate more than 0%, > like Carlos' machine. Yes, I wonder if it is worth it running nscd at all. > Other distros (Ubuntu) are using a real local DNS caching server on each > machine which respects the DNS protocol. If you have one caching DNS > server in your LAN (any usual router does that) then you probaly don't > need neither nscd nor local DNS server. That's my case, I use dnsmasq or bind on all my machines. Some years I remember to configure nscd to not cache host entries. Long ago I tried not starting nscd, I could not figure out if it was good or bad. In this laptop I have: enable-cachehosts no but the machine I posted previously has it to yes. I have now set it to no. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1: nscd consumes a lot of memory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, 2016-04-07 at 10:13 +0100, Ruediger Meier wrote: Hm, my interpretation was wrong. To get meaningful stats you need to set shared xyzno Let's try: AmonLanc:~ # grep shared /etc/nscd.conf # shared shared passwd no shared group no shared hosts yes shared servicesyes shared netgroupyes AmonLanc:~ # It can only count stats if accesssed via socket but not if other processes are reading directly in nscd's memory. I really wondered about the low hit rates because any process who needs to convert uids into user names (like ls -l) should use nscd's passwd table rather than parsing /etc/passwd again and again or even worse asking the ldap or NIS server. This is IMO the most notable speedup. host caching is less useful. Surely ls -l only needs to do this just once per different uid, not once per file? This is what I have after 10 minutes now $ nscd -g | grep "hit\|cache:" After doing two "ls -l": AmonLanc:~ # nscd -g | grep "hit\|cache:" passwd cache: 2 cache hits on positive entries 0 cache hits on negative entries 0% cache hit rate group cache: 3 cache hits on positive entries 0 cache hits on negative entries 0% cache hit rate hosts cache: 0 cache hits on positive entries 0 cache hits on negative entries 0% cache hit rate services cache: 0 cache hits on positive entries 0 cache hits on negative entries 0% cache hit rate netgroup cache: 0 cache hits on positive entries 0 cache hits on negative entries 0% cache hit rate AmonLanc:~ # What happens if shared=yes, does it still work, but report fais to say so? What other effects has shared=no? - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcGQvMACgkQtTMYHG2NR9V3AQCdHyoyiVeBmu2SkqDhM3jgSpfZ hi4AnjgnKCcT26442Oi+CGJF37E4F1Ou =EgWx -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] lockups exiting startx with nouveau
On 2016-04-08 15:26, Tobias Klausmann wrote:
> fixed. Do you really need to use evergreen on systems with nouveau/nvidia?
I do. But I use the proprietary nvidia.run package now.
I've not experienced problems, but I don't use startx, but init 5 -
except for testing.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Recent (aparmor) updates broke dovecot
: Fatal: setrlimit(RLIMIT_DATA, 268435456): Permission denied <2.3> 2016-04-22 12:23:04 Telcontar dovecot - - - master: Error: service(imap-login): command startup failed, throttling for 4 secs <2.2> 2016-04-22 12:23:04 Telcontar dovecot - - - imap-login: Fatal: master: service(imap-login): child 30263 returned error 89 (Fatal failure) <2.4> 2016-04-22 12:23:07 Telcontar dovecot - - - master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.4> 2016-04-22 12:23:07 Telcontar dovecot - - - imap: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.6> 2016-04-22 12:23:07 Telcontar dovecot - - - imap: Server shutting down. in=3389 out=711046 <2.4> 2016-04-22 12:23:07 Telcontar dovecot - - - imap-login: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.4> 2016-04-22 12:23:07 Telcontar dovecot - - - imap-login: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.4> 2016-04-22 12:23:07 Telcontar dovecot - - - log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.6> 2016-04-22 12:23:08 Telcontar dovecot - - - master: Dovecot v2.1.17 starting up (core dumps disabled) <2.6> 2016-04-22 12:23:50 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=192.168.1.14, lip=192.168.1.14, mpid=30317, TLS, session= <2.6> 2016-04-22 12:23:50 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=192.168.1.14, lip=192.168.1.14, mpid=30318, TLS, session= <2.4> 2016-04-22 12:24:23 Telcontar dovecot - - - log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.4> 2016-04-22 12:24:23 Telcontar dovecot - - - master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) <2.6> 2016-04-22 12:24:23 Telcontar dovecot - - - master: Dovecot v2.1.17 starting up (core dumps disabled) <2.6> 2016-04-22 12:24:38 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=30376, TLS, session= <2.6> 2016-04-22 12:24:49 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=192.168.1.14, lip=192.168.1.14, mpid=30390, TLS, session= <2.6> 2016-04-22 12:24:49 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=192.168.1.14, lip=192.168.1.14, mpid=30391, TLS, session= <2.6> 2016-04-22 12:24:54 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=30396, TLS, session= <2.6> 2016-04-22 12:24:56 Telcontar dovecot - - - imap-login: Login: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=30402, TLS, session= I had to do this: Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes: Profile:/usr/sbin/dovecot Capability: sys_resource Severity: 8 (A)llow / [(D)eny] / Audi(t) / Abo(r)t / (F)inish Adding capability sys_resource to profile. = Changed Local Profiles = The following local profiles were changed. Would you like to save them? [1 - /usr/sbin/dovecot] (S)ave Changes / [(V)iew Changes] / Abo(r)t Writing updated profile for /usr/sbin/dovecot. Telcontar:~ # - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcZ/KAACgkQtTMYHG2NR9V/ZgCgictB0IcmjXup7GbkZcH1CNnh my4An3pee48jMFT4q5a6bwmPOqa3lw73 =vY4z -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Something broken with systemd or udev after the last update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<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.
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlcaCF4ACgkQtTMYHG2NR9XZRwCdFGffVEa7I7nCNaIQM1olD7kK
mFgAn2cQyjyZnY4jCWgWIlNDF4iJGhYL
=FHTd
-END PGP SIGNATURE-
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Recent (aparmor) updates broke dovecot
On 2016-04-22 12:27, Carlos E. R. wrote: > Telcontar:~ # aa-logprof > Reading log entries from /var/log/audit/audit.log. > Updating AppArmor profiles in /etc/apparmor.d. > Enforce-mode changes: > > Profile:/usr/sbin/dovecot > Capability: sys_resource > Severity: 8 > > (A)llow / [(D)eny] / Audi(t) / Abo(r)t / (F)inish > Adding capability sys_resource to profile. > > = Changed Local Profiles = > > The following local profiles were changed. Would you like to save them? > > [1 - /usr/sbin/dovecot] > > (S)ave Changes / [(V)iew Changes] / Abo(r)t > Writing updated profile for /usr/sbin/dovecot. > Telcontar:~ # Something else is broken here, because everytime I run "aa-logprof" I see the same error, even though I save the changes. But dovecot is working. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Recent (aparmor) updates broke dovecot
On 2016-04-22 13:19, Carlos E. R. wrote: > On 2016-04-22 12:27, Carlos E. R. wrote: > >> Telcontar:~ # aa-logprof >> Reading log entries from /var/log/audit/audit.log. >> Updating AppArmor profiles in /etc/apparmor.d. >> Enforce-mode changes: >> >> Profile:/usr/sbin/dovecot >> Capability: sys_resource >> Severity: 8 >> >> (A)llow / [(D)eny] / Audi(t) / Abo(r)t / (F)inish >> Adding capability sys_resource to profile. >> >> = Changed Local Profiles = >> >> The following local profiles were changed. Would you like to save them? >> >> [1 - /usr/sbin/dovecot] >> >> (S)ave Changes / [(V)iew Changes] / Abo(r)t >> Writing updated profile for /usr/sbin/dovecot. >> Telcontar:~ # > > > Something else is broken here, because everytime I run "aa-logprof" I > see the same error, even though I save the changes. But dovecot is working. Not quite: <2.3> 2016-04-22 13:19:26 Telcontar dovecot - - - master: Error: service(auth): command startup failed, throttling for 2 secs <2.2> 2016-04-22 13:19:26 Telcontar dovecot - - - auth: Fatal: master: service(auth): child 9680 killed with signal 9 <2.6> 2016-04-22 13:19:26 Telcontar dovecot - - - imap-login: Disconnected: Auth process broken (disconnected before greeting, waited 0 secs): user=<>, rip=192.168.1.14, lip=192.168.1.14, secured, session In fact, the change has been applied to /etc/apparmor.d/usr.sbin.dovecot several times: capability setuid, capability sys_chroot, capability sys_resource, capability sys_resource, capability sys_resource, capabilitysys_resource, capability sys_resource, capability sys_resource, capability sys_resource, -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Recent (aparmor) updates broke dovecot
On 2016-04-22 13:32, Christian Boltz wrote:
> Hello,
>
> Am Freitag, 22. April 2016, 12:27:44 CEST schrieb Carlos E. R.:
>> <2.2> 2016-04-22 12:14:59 Telcontar dovecot - - - master: Fatal:
>> setrlimit(RLIMIT_DATA, 268435456): Permission denied
> ...
>> Telcontar:~ # aa-logprof
>> Reading log entries from /var/log/audit/audit.log.
>> Updating AppArmor profiles in /etc/apparmor.d.
>> Enforce-mode changes:
>>
>> Profile:/usr/sbin/dovecot
>> Capability: sys_resource
>> Severity: 8
>>
>> (A)llow / [(D)eny] / Audi(t) / Abo(r)t / (F)inish
>> Adding capability sys_resource to profile.
>
> That's surprising in more than one way ;-)
>
> First, the dovecot profile wasn't touched in this update. (Nevertheless,
> check for *.rpmnew or *.rpmsave files in /etc/apparmor.d just to be on
> the safe side.)
I already did, none there.
> Now the question is why dovecot wants to do this. Did you change any
> settings in dovecot or rlimit settings on your system? Do you set
> vsz_limit somewhere in your dovecot config?
Not in months. Time ago, yes, I had to do it, or some thing ate all the RAM - I
remember now asking about it some time ago, maybe a year:
/etc/dovecot/local.conf
default_vsz_limit = 256M
# It is ignored, not applied to services. The real limit applied is
18446744073709551615 B.
#login_trusted_networks = 192.168.1.0/24, 127.0.0.1/8
login_trusted_networks = 192.168.1.14/31, 127.0.0.1/8
# 192.168.1.129/31,
# Space separated list of wanted authentication mechanisms:
# plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi otp skey
# gss-spnego
# NOTE: See also disable_plaintext_auth setting.
auth_mechanisms = plain login
# <2.2> 2014-08-19 23:47:06 Telcontar dovecot - - - auth: Fatal: CRAM-MD5
mechanism can't be supported with given passdbs
# <2.2> 2014-08-19 23:49:37 Telcontar dovecot - - - auth: Fatal: DIGEST-MD5
mechanism can't be supported with given passdbs
disable_plaintext_auth = yes
ssl = yes
mail_location = mbox:~/Mail:INBOX=/var/mail/%u
mail_debug = yes
#verbose_ssl = no
#CER - testing - nope, unknown setting #verbose_lda = no
# For use with delivery agent, /usr/lib/dovecot/dovecot-lda
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
#mail_max_userip_connections = 15 en 20-imap.conf
#CER - el Thunderbird puede necesitar más (15 o 30).
#No se si esto funcionaría:
protocol imap {
mail_max_userip_connections = 20
}
service imap {
# Most of the memory goes to mmap()ing files. You may need to increase this
# limit if you have huge mailboxes.
#vsz_limit = $default_vsz_limit
# this results in vsz_limit = 18446744073709551615 B
vsz_limit = 512 M
# Max. number of IMAP processes (connections)
#process_limit = 1024
}
ssl_cert =
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Recent (aparmor) updates broke dovecot
if > I have ever seen this one. > Anyway, the profile clearly allows the sys_resource capability ;-)) > (having 10 similar lines for it doesn't hurt) The problem is that when I run aa-logprof, I always get: Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes: Profile:/usr/sbin/dovecot Capability: sys_resource Severity: 8 (A)llow / [(D)eny] / Audi(t) / Abo(r)t / (F)inish Maybe I have something set to "audit" and I forgot :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] problem with a 13.1 server
On 2016-04-25 15:53, jdd wrote:
> before I start an extensive bug search, is there something in the recent
> release that could have set this up?
After the last update (two week packages) I lost network. Had to restart
network, dns and postfix, at least. On one machine only.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Recent (aparmor) updates broke dovecot
On 2016-04-25 17:47, Christian Boltz wrote:
> aa-logprof will read the log again every time you run it, which means it
> sees the "old" event again.
I thought it used some kind of timestamp to only scan new events.
> I just checked the perl code. Besides being reminded why we wanted to
> get rid of that ;-) I can probably explain what happens.
>
> This is from the code that parses the profile in /etc/apparmor.d:
>
> } elsif
> (m/^\s*(audit\s+)?(deny\s+)?capability(\s+(\S+))?\s*,\s*(#.*)?$/) { #
> capability entry
> # [...]
> my $capability = $3 ? $3 : 'all';
>
> If you start counting parenthesis, you'll notice that $1 is audit, $2
> is deny and $3 is everything between the 'capability' keyword and the
> comma. __Including the spaces!__ ($4 would be without spaces.)
>
> So aa-logprof knows the profile already contains the " sys_resource"
> (including the spaces!) capability, but the log tells it about the
> "sys_resource" capability (without spaces), which is technically a
> different one ;-)
>
> And to make things even more funny, a space gets added every time the
> profile gets written, which explains why your profile looks like stairs ;-)
I see :-)
> To get rid of the repeated questions, rotate the old audit.log away:
> old /var/log/audit/audit.log # will rename it to audit.log-$date
> rcauditd restart
That's a new command for me, "old". However, the logfiles there have a
different rotate method:
Telcontar:/var/log/audit # ls
audit.log audit.log.1 audit.log.2 audit.log.3 audit.log.4
No date stamp, so I can't use "old".
Mmmm, "rcauditd" does not exist. auditd.service does.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 11.4 flashplayer update
On 2016-04-25 19:02, Simon Becherer wrote: > Hi wolfgang, > > is it possible to update the flashplayer for 11.4? > > or give me a short instruction (5-6 lines would be enaught) > where to find the source and the updates, It is a proprietary package, so there are no sources. You can probably get the package from adobe directly - I don't have the link handy, but we wrote the information on the opensuse wiki. Here: https://en.opensuse.org/Adobe_Flash_Player Section 2.2. > and how to merge it, that i could try to compile it myselfe at my local > systems here (sorry no knowledge how to use the build service) > if noboy exept me still use it on 11.4 > (last update was made by pacman (11.2.202.577-1.1), but they have had > updated it only one or two times at all after you stopped the "regular/ > updates for me" 11.4 updates) / what is better than nothing ;-))) Packman announced recently they would no longer produce new updates for 11.4. Really, if you are using your computer for browsing on internet, you should not use 11.4. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Recent (aparmor) updates broke dovecot
On 2016-04-25 19:53, Christian Boltz wrote: > Hello, > > Am Montag, 25. April 2016, 19:29:06 CEST schrieb Carlos E. R.: >> No date stamp, so I can't use "old". > > Right, you won't get audit.log-$date automatically deleted because that > doesn't match the .1 etc suffix., so I agree it's exactly not what the > normal audit.log rotation does. > > Nevertheless, 'old' is the easiest way to rename a logfile ;-) Well, I may just delete the files, or wait some days :-) >> Mmmm, "rcauditd" does not exist. auditd.service does. > > One of the funny bugs caused by switching to systemd. > > It only needed a bugreport to get rcaudit back in later releases. > Also, I manually re-added it on my 13.1 servers (as symlink to > /sbin/service), so for me it's always available ;-) Yes, sometimes I do that, too. But as it is not a service I restart often, I have neither reported the bug or wrote the link myself. Let me see, you mean: ln -s /sbin/service /sbin/rcauditd ? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ 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
-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? - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcf2VoACgkQtTMYHG2NR9XfKgCff1eHYKNhH4ilvp/ceQq8Lb4/ gWsAn2kng5crdoU1H9PJJ8ZVSXIOaIHw =hfrj -END PGP SIGNATURE- ___ 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
On 2016-04-27 07:57, Per Jessen wrote: > Carlos E. R. wrote: >> 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. > Me neither. I greped /etc/systemd and /lib/systemd, and nothing contains the string "udev". Nor in /run/systemd > 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? In syslog. /var/log/warn. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ 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
On 2016-04-28 08:36, Per Jessen wrote: > Carlos E. R. wrote: > >> On 2016-04-27 07:57, Per Jessen wrote: >>> Carlos E. R. wrote: >> >> >>>> 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. >>> >> >> Me neither. I greped /etc/systemd and /lib/systemd, and nothing >> contains the string "udev". Nor in /run/systemd > > How about /usr/lib/systemd - that's the key one. Mmm. Many are binaries, tons of hits. Interestingly, there is a text file: /usr/lib/systemd/system/udev.service Maybe it is this file the one it says it can not find? > >>> Funny, I feel certain I have also seen that message, but I can't find >>> it now. Where do you see it Carlos? >> >> In syslog. /var/log/warn. > > Hmm, don't see any such messages. Interestingly, there is none in the laptop that I'm using this morning. I'll have to check again this afternoon on the other machine. I also have to verify that both have the same updates. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) signature.asc Description: OpenPGP digital signature ___ 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
On 2016-04-28 12:09, I wrote: > On 2016-04-28 08:36, Per Jessen wrote: >> Carlos E. R. wrote: >>> On 2016-04-27 07:57, Per Jessen wrote: >>>> Carlos E. R. wrote: >> How about /usr/lib/systemd - that's the key one. > > Mmm. Many are binaries, tons of hits. Interestingly, there is a text file: > > /usr/lib/systemd/system/udev.service > > Maybe it is this file the one it says it can not find? > > >> >>>> Funny, I feel certain I have also seen that message, but I can't find >>>> it now. Where do you see it Carlos? >>> >>> In syslog. /var/log/warn. >> >> Hmm, don't see any such messages. > > Interestingly, there is none in the laptop that I'm using this morning. > I'll have to check again this afternoon on the other machine. > I also have to verify that both have the same updates. Now sitting at the desktop machine. There is a "/usr/lib/systemd/system/sysinit.target.wants/systemd-udevd.service" and a "/usr/lib/systemd/system/systemd-udevd.service". -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ 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
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. Maybe I should grep on udev. What dir? :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Can you help me with a bugzilla that was closed as invalid because it is about 13.1?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I reported it last november, against LibreOffice ir repo 4.3. It has
been closed now becasue they say that they don't keep that repo.
So I reopen it against repo 5.0, and again they close it as invalid
because 13.1 is out of maintenance.
Absurd! The bug is not present in any other distro, it is just a missing
pacakge from the repo and should be easy to solve.
https://bugzilla.novell.com/show_bug.cgi?id=950873
Bug 950873 - LibreOffice:4.4/libreoffice: Bug - myspell is missing, but is
required.
Maybe somebody here has some influence and can ask the maintainers to
please solve this bug nicely and not close bugs for bureaucratic
reasons. After all, they are indeed publishing LibreOffice repos for
13.1.
I'm starting to think that they will close any bug I report because its
me. I reported a few weeks back something else, it was refused
unpolitely (solve it yourself if you want), then I saw an update that
covered what I had reported :-(
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlcnYDMACgkQtTMYHG2NR9XopQCgkQ9Lp+k8NBQE551/Hg+GY/XK
WNUAn1YR5gmZM1fueIGe1mAWBTk7I5jO
=mavs
-END PGP SIGNATURE-
___
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
On 2016-05-18 08:38, Per Jessen wrote: > Patrick Schaaf wrote: >> I already have some other rsyslog filters for similar stuff, but the >> amount of different messages here, makes me reluctant to go down the >> fiter-it-away route further... >> >> Maybe somebody knows the root cause + could make it go away? :) > > It does seem excessive to log 41 messages for every cronjob. However, > it is not for every cronjob, possibly only for user cronjobs. Jobs for > root only log 8 lines. I think it might be the systemd "User Manager" > that is overly chatty. Yesterday I added more filters to rsyslog. Works wonderful, now I can read what is important in the log. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ 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
-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 I edited /etc/systemd/user.conf thus: [Manager] #CER Loglevel=notice # #LogLevel=info #LogTarget=console ... - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlc9PzUACgkQtTMYHG2NR9UrfACfRv67exW+IED/64bK7nbKATMI WHsAnjsEYJI5h0HIfg0xt6P7swp01vDQ =H0tU -END PGP SIGNATURE- ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, 2016-05-19 at 09:17 +0200, Per Jessen wrote: Carlos E. R. wrote: 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. That was it; I was getting an error message every five minutes. This other message remains, every five minutes, sometimes twice: <3.4> 2016-05-19 16:15:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.4> 2016-05-19 16:15:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.4> 2016-05-19 16:20:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.4> 2016-05-19 16:25:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.4> 2016-05-19 16:30:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.4> 2016-05-19 16:30:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.3> 2016-05-19 16:30:01 Telcontar systemd 3055 - - Trying to run as user instance, but $XDG_RUNTIME_DIR is not set. <3.4> 2016-05-19 16:35:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. This is after applying all pending updates and rebooting this morning. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlc91o4ACgkQtTMYHG2NR9W3TwCgliaiZGDTLDKrLfjfok9tguvO +EAAoI+B9eI5pYQTO1/y72A8Yb10rUYO =VJLP -END PGP SIGNATURE- ___ 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
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, 2016-05-19 at 17:06 +0200, Carlos E. R. wrote: This other message remains, every five minutes, sometimes twice: <3.4> 2016-05-19 16:15:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. This is after applying all pending updates and rebooting this morning. Grepping with 'mc' on the entire "/usr/, I found these entries: Left File Command Options Right ┌<─ /usr ──.[^]>┐┌<─ ~/Downloads ───.[^]>┐ │.n y time │ │/.. ┌─ Find File ──┐ 9 21:48│ │/X11R6 │ /usr/share/rear/skel/Fedora/16/lib/systemd/system │ 4 2014│ │/bin│ 14:udev-settle.service │ 0 2013│ │/gameda │ 3:udev-trigger.service │ 5 2014│ │/games │ /usr/share/rear/skel/default/usr/lib/systemd/system │ 5 10:17│ │/i586-s │ 6:udev-control.socket │ 1 2012│ │/includ │ 6:udev-kernel.socket │ 3 2013│ │/java │ 14:udev-settle.service │ 9 2013│ │/lib│ 3:udev-trigger.service │ 2 2013│ │/lib64 │ /usr/share/rear/skel/Fedora/17/usr/lib/systemd/system │ 5 2013│ │/local │ 14:udev-settle.service │ 9 2013│ │/man│ 3:udev-trigger.service │ 2 2013│ │/sbin │ /usr/share/rear/skel/default/usr/lib/systemd/system/sockets.target.wants ││ │/share │ 6:udev-control.socket ││ │/src│ 6:udev-kernel.socket ││ │~tmp│ ││ │/x86_64 │ ││ │ I don't think those are in use, being "skeletons", but there are entries like: Wants=udev.service or Service=udev.service :-? - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlc+KeoACgkQtTMYHG2NR9XE7QCbBNsxD1YwfZUgWDhSMyPOfDmP 82UAn28iXpwkAKjpfD82ukW6rcz8Puxl =72ug -END PGP SIGNATURE-___ 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
On 2016-05-19 23:02, Carlos E. R. wrote: > >> This other message remains, every five minutes, sometimes twice: > >> <3.4> 2016-05-19 16:15:01 Telcontar systemd 1 - - Cannot add dependency job >> for unit udev.service, ignoring: Unit udev.service failed to load: No such >> file or directory. > >> This is after applying all pending updates and rebooting this morning. > > Grepping with 'mc' on the entire "/usr/, I found these entries: ... > I don't think those are in use, being "skeletons", but there are entries > like: > > Wants=udev.service > > or > > Service=udev.service The directories and files in the skels might have been copied to the proposed destinations, but no: Telcontar:~ # l lib/systemd/system/udev* ls: cannot access lib/systemd/system/udev*: No such file or directory Telcontar:~ # l /lib/systemd/system/udev* ls: cannot access /lib/systemd/system/udev*: No such file or directory Telcontar:~ # l /usr/lib/systemd/system/udev* ls: cannot access /usr/lib/systemd/system/udev*: No such file or directory Telcontar:~ # l /usr/lib/systemd/system/udev* ls: cannot access /usr/lib/systemd/system/udev*: No such file or directory Telcontar:~ # l /usr/lib/systemd/system/sockets.target.wants/udev* ls: cannot access /usr/lib/systemd/system/sockets.target.wants/udev*: No such file or directory Telcontar:~ # They would be symlinks, though: Telcontar:~ # l /usr/lib/systemd/system/sockets.target.wants/* lrwxrwxrwx 1 root root 14 Feb 19 2015 /usr/lib/systemd/system/sockets.target.wants/dbus.socket -> ../dbus.socket lrwxrwxrwx 1 root root 25 Apr 22 12:06 /usr/lib/systemd/system/sockets.target.wants/systemd-initctl.socket -> ../systemd-initctl.socket lrwxrwxrwx 1 root root 26 Apr 22 12:06 /usr/lib/systemd/system/sockets.target.wants/systemd-journald.socket -> ../systemd-journald.socket lrwxrwxrwx 1 root root 27 Apr 22 12:06 /usr/lib/systemd/system/sockets.target.wants/systemd-shutdownd.socket -> ../systemd-shutdownd.socket lrwxrwxrwx 1 root root 31 Apr 22 12:06 /usr/lib/systemd/system/sockets.target.wants/systemd-udevd-control.socket -> ../systemd-udevd-control.socket lrwxrwxrwx 1 root root 30 Apr 22 12:06 /usr/lib/systemd/system/sockets.target.wants/systemd-udevd-kernel.socket -> ../systemd-udevd-kernel.socket Telcontar:~ # That "../systemd-udevd-control.socket" contains: [Unit] Description=udev Control Socket Documentation=man:systemd-udevd.service(8) man:udev(7) DefaultDependencies=no Before=sockets.target ConditionPathIsReadWrite=/sys [Socket] Service=systemd-udevd.service < ListenSequentialPacket=/run/udev/control SocketMode=0600 PassCredentials=yes Could be that one? The error message mentions udev.service, not ude.service, so I don't think so. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ 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
-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. It doesn't do much here. I was getting this block, many times: <3.6> 2016-05-19 22:10:03 Telcontar systemd 1 - - Stopping User Manager for UID 30... <3.6> 2016-05-19 22:10:03 Telcontar systemd 1 - - Stopped User Manager for UID 30. <3.6> 2016-05-19 22:10:03 Telcontar systemd 1 - - Stopping user-30.slice. <3.6> 2016-05-19 22:10:03 Telcontar systemd 1 - - Removed slice user-30.slice. <3.6> 2016-05-19 22:15:01 Telcontar systemd 1 - - Starting user-0.slice. <3.6> 2016-05-19 22:15:01 Telcontar systemd 1 - - Created slice user-0.slice. <3.4> 2016-05-19 22:15:01 Telcontar systemd 1 - - Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. <3.6> 2016-05-19 22:15:01 Telcontar systemd 1 - - Starting User Manager for UID 0... <3.6> 2016-05-19 22:15:01 Telcontar systemd 1 - - Starting user-30.slice. I added rules in rsyslog to filter them out. What a nuisance. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlc+MnoACgkQtTMYHG2NR9WHaQCfUvCERXXVnCLflnw9D3oiVJgE WpkAn3P0QJ5qj5lXU7MMaWIMtyyFVDUV =zMuT -END PGP SIGNATURE- ___ 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
On 2016-05-20 08:17, Per Jessen wrote: > 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. I have this in rsyslog if (($programname == 'systemd') and ( \ (($msg contains 'Started Session') and ($msg contains 'of user')) \ or ($msg contains 'Starting Session') and (($msg contains 'of user news.') or ($msg contains 'of user wwwrun.') or ($msg contains 'of user cer.') or ($msg contains 'of user root.')) \ )) \ then-/var/log/pruned & stop and if ( $programname == 'systemd' and (\ ( \ ( $msg contains 'Starting' or $msg contains 'Started' or $msg contains 'Stopping' or $msg contains 'Stopped' ) \ and ($msg contains 'User Manager for UID' and ($msg contains '30' or $msg contains '0') ) \ ) \ or ( \ ( $msg contains 'Stopping' or $msg contains 'Removed slice' or $msg contains 'Starting' or $msg contains 'Created slice' ) \ and ($msg contains 'user-30.slice' or $msg contains 'user-0.slice') \ ) \ )) \ then-/var/log/pruned & stop and if ($programname startswith 'org.gtk.' and $msg contains '### debug:') or ($programname startswith 'org.gtk.vfs.Daemon') or ($programname startswith 'org.freedesktop.Tracker or ($programname startswith 'org.gnome.evince.Daemon' and ($msg contains 'egisterDocument' or $msg contains 'Watch name')) \ or ($programname startswith 'org.gnome.zeitgeist.Engine') \ or ($programname startswith 'org.xfce.FileManager' and ($msg contains 'fixme:' )) \ or ($programname == 'systemd' and ($msg contains 'Failed to open private bus connection: Failed to connect to socket' ))\ or ($programname startswith 'org.freedesktop.thumbnails.Thumbnailer') \ or ($programname startswith 'org.gnome.zeitgeist.SimpleIndexer')\ or ($programname startswith 'org.a11y.Bus') \ or ($programname startswith 'org.a11y.atspi.Registry') \ or ($programname startswith 'org.freedesktop.Telepathy.AccountManager' and ($msg contains 'WARNING' )) \ or ($programname startswith 'org.freedesktop.Notifications')\ or ($programname == 'org.gnome
Re: [Evergreen] Can you help me with a bugzilla that was closed as invalid because it is about 13.1?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, 2016-05-02 at 16:24 +0200, Patrick Schaaf wrote: On Monday 02 May 2016 16:12:03 Carlos E. R. wrote: Hi, I reported it last november, against LibreOffice ir repo 4.3. It has been closed now becasue they say that they don't keep that repo. So I reopen it against repo 5.0, and again they close it as invalid because 13.1 is out of maintenance. Absurd! The bug is not present in any other distro, it is just a missing pacakge from the repo and should be easy to solve. Jup, experienced that too - we solved it locally by enabling both the 4.3 libreoffice repo, where these packages are still present, and the 5.0 repo. Well, now they have removed all the libreoffice repos for 13.1. :-( - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlc++UAACgkQtTMYHG2NR9WcRQCfXX1XoB537RnH/TkyEErWEXay LVMAn3qrPVVHp2xs8hVagtm3rlTk9S9N =J01C -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Can you help me with a bugzilla that was closed as invalid because it is about 13.1?
On 2016-05-20 13:56, Patrick Schaaf wrote: > On Fri, May 20, 2016 at 1:47 PM, Carlos E. R. wrote: >> Well, now they have removed all the libreoffice repos for 13.1. :-( > > Last update was late in January, anyway. I wouldn't blame anybody for > that, really. The evergreen "promise" never did cover all the various > extra repositories, AFAIK. The Evergreen people, as few as they are, do a lot. But the maintainers of many extra repos are very fast on removing repositories that "just work" and should be easy to keep, IMHO. > I've been running local mirrors of the repositories for some years > now, and use them for all installs and updates, so it's not a big > issue to me. Yes, I also have local copies of all the repos I use. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Still every second: "reset full-speed USB device number 2 using uhci_hcd", after update to 3.12.57-44-default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, 2016-03-16 at 10:18 +0100, Michal Kubecek wrote: On Tue, Mar 15, 2016 at 11:02:55PM +0100, Carlos E. R. wrote: I see this activity in the log since I updated my 32b server machine (on 13.1): <0.6> 2016-03-15T22:16:00.928142+01:00 AmonLanc kernel - - - [39604.176042] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:03.620149+01:00 AmonLanc kernel - - - [39606.868059] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:03.904177+01:00 AmonLanc kernel - - - [39607.152036] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-03-15T22:16:04.188133+01:00 AmonLanc kernel - - - [39607.436027] usb 4-2: reset full-speed USB device number 2 using uhci_hcd ... Previous to the update, this happened 3 times per month. Today, the log has rotated because of that and contains more than 6 entries. cer@AmonLanc:~> uname -a Linux AmonLanc 3.12.53-40-default #1 SMP Thu Feb 25 06:26:23 UTC 2016 (b2ce64e) i686 i686 i386 GNU/Linux cer@AmonLanc:~> Please open a bug in bugzilla, assign it to me and attach output of lsusb -v lspci -v lsmod and (if possible) the part of log from boot to first few of the messages (there might be some clue preceding the first message). (https://bugzilla.opensuse.org/show_bug.cgi?id=971387) After update to kernel 3.12.57-44-default, this is still happening. To stop them, I do "rmmod uhci_hcd" which was harmless before but now impedes the UPS being detected. <0.6> 2016-05-21T13:41:50.079256+02:00 AmonLanc kernel - - - [ 321.720022] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:50.359261+02:00 AmonLanc kernel - - - [ 322.000108] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:53.051256+02:00 AmonLanc kernel - - - [ 324.692023] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:53.331256+02:00 AmonLanc kernel - - - [ 324.972020] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:53.611258+02:00 AmonLanc kernel - - - [ 325.252021] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:53.891254+02:00 AmonLanc kernel - - - [ 325.532023] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:54.171253+02:00 AmonLanc kernel - - - [ 325.812020] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:54.451255+02:00 AmonLanc kernel - - - [ 326.092033] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:57.147257+02:00 AmonLanc kernel - - - [ 328.788023] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:57.427257+02:00 AmonLanc kernel - - - [ 329.068021] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:57.707257+02:00 AmonLanc kernel - - - [ 329.348023] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:57.987253+02:00 AmonLanc kernel - - - [ 329.628022] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:58.267254+02:00 AmonLanc kernel - - - [ 329.908021] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:41:58.547255+02:00 AmonLanc kernel - - - [ 330.188025] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:42:01.243256+02:00 AmonLanc kernel - - - [ 332.884027] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:42:01.523251+02:00 AmonLanc kernel - - - [ 333.164058] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:42:01.803253+02:00 AmonLanc kernel - - - [ 333.444021] usb 4-2: reset full-speed USB device number 2 using uhci_hcd <0.6> 2016-05-21T13:42:02.083269+02:00 AmonLanc kernel - - - [ 333.724020] usb 4-2: reset full-speed USB device number 2 using uhci_hcd It happens about three times per second, it would fill the logs fast. I could fiter out the messages in syslog, but filtering systemd journal write is impossible. Is there some other way to disable that USB interface? I want to monitor my UPS. The messages only happen after login in graphics mode, so XFCE must be triggering them, trying to mount that PCMCIA. It appears that doing a manual "modprobe uhci_hcd" after some minutes work. The UPS interface is detected, and the PCMCIA is not probed - so far. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAldAUGAACgkQtTMYHG2NR9VAzQCfbh9PLDh8vzR3hN9qeXFKz/Gu viIAn28iPPOz6KkUuXq8wPnSAtKFVxgo =A6v+
Re: [Evergreen] Logspam: Cannot ad dependency job for unit udev.service
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday, 2016-09-13 at 18:26 +0200, Patrick Schaaf wrote: Dear list, as already discussed in May, ever since the 13.1 systemd update then, we regularly get these in our system logs: systemd[1]: Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. As I'm finally looking at newer suse versions (tumbleweed), and still see these messages all over the place on my 13.1 systems, I had another look + compared with tumbleweed - and apparently the "solution" is very simple: ln -s systemd-udevd.service /usr/lib/systemd/system/udev.service systemctl daemon-reload Now I don't think we'll get further package updates for 13.1 - but maybe this helps somebody else with that annoyance. Thanks! I have applied this change now. Telcontar:~ # cd /etc/systemd/system/ Telcontar:/etc/systemd/system # ln -s /usr/lib/systemd/system/systemd-udevd.service udev.service Telcontar:/etc/systemd/system # systemctl daemon-reload Telcontar:/etc/systemd/system # However, looking at Leap 42.2 Beta, I don't see that file either, nor the logspam: linux-qyxj:~ # locate udev.service /usr/lib/dracut/modules.d/98dracut-systemd/dracut-pre-udev.service /usr/lib/dracut/modules.d/98dracut-systemd/dracut-pre-udev.service.8 /usr/lib/dracut/modules.d/98dracut-systemd/dracut-pre-udev.service.8.asc /usr/lib/systemd/system/dracut-pre-udev.service /usr/lib/systemd/system/initrd.target.wants/dracut-pre-udev.service /usr/share/man/man8/dracut-pre-udev.service.8.gz linux-qyxj:~ # linux-qyxj:~ # journalctl | grep udev.service linux-qyxj:~ # So the problem is solved diferrently there. :-? - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlfi7FsACgkQtTMYHG2NR9XHpQCeOdbdiikoLI90P84bncwgO+78 p/0An0ZxrKHANhWwP4PX3h9KUbA3BTyv =jj4+ -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] openSUSE 13.1 after 2016-11-01
On 2016-10-23 15:59, Sebastian Niemeyer wrote:
> Hallo together,
>
> how are the plans for openSUSE 13.1 after 2016-11-01. Is there a change for a
> longer support of the current evergreen release?
I'm daunted by the perspectives. Either I buy new 64 bit hardware to
replace my old 32 bit hardware, or jump distro to something else, for
the server.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] openSUSE 13.1 after 2016-11-01
On 2016-10-24 08:22, Axel Braun wrote: > Am Sonntag, 23. Oktober 2016, 22:49:26 schrieb Felix Miata: >>> Me, I think something else would be easier, perhaps ubuntu. >> >> Ubuntu *is* (a) Debian (derivative), just with a custom set of personality >> modifications designed for shielding its users from the underlying power of >> FOSS, e.g. Unity (aka only one way), and sudo (Ugh!). > > As long as you just use it from the CLI, it should be OK. Using Ubuntu with > Unity is clearly a no-go in terms of privacy. Well, a server is mostly used as services and via CLI for changing configurations. > But using TW from command line and not running behind each and every update > may be OK for a server as well. Depends on the needs. Security wise, kernel and services that connect to internet, I guess. The machine has a pentium processor, so anything intensive takes ages. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] openSUSE 13.1 after 2016-11-01
On 2016-10-24 09:11, Moser Helmut wrote:
> Hello all,
>
> Can anybody here please answer the original question (besides tips about
> distro change)?
> It's very important for me too to know what to do after November 1st as I
> have several 13.1 machines sitting there.
The more or less official wisdom was to upgrade to 42.2.
I have tested this under vmware player, and finished with a graphical
mode with XFCE that locks dead. ssh keeps working. I have to test again
with RC1.
I fear that the automated test bench does not test 13.1 -> 42.2 path.
All my machines are 13.1.
--
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 - latest update broke graphical login
On 2016-10-28 14:13, Patrick Shanahan wrote: > * Axel Braun <> [10-28-16 06:08]: >> Any idea what this could be ? > > when I have seen startx can access but other methods fail, the graphical > driver has not matched the kernel (nvidia in my experience) and/or perms > for /usr/bin/Xorg needs to be suid. When the nvidia driver fails it fails both in level 5 and via startx. Actually, starting via startx serves to read the diagnosis messages. Axel, I would look at "/var/log/Xorg.0.log*" files for clues. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Last kernel update wrote wrong line to grub, system unbootable.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 /boot/grub/menu.lst: title Desktop -- openSUSE - 3.12.62-55 root (hd1,4) when it is (looking at other entries): title Desktop -- openSUSE - 3.12.62-55 root (hd0,4) Maybe it was confused by the presence of another external disk, which the kernel names as sda instead of sdf. But I often have a disk there. I think this is an old bug. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlgaA28ACgkQtTMYHG2NR9UYGwCeI3L9wSpJ9FZt4swGAlOEoSBF cH0AoIarnW/xDF8PKL2uTiGH8i+8XqMr =gZ+B -END PGP SIGNATURE- ___ 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?
On 2017-01-27 18:37, 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?
I went from 13.1 to 42.2 in one operation, using the offline or cold
upgrade. At one point the procedure pops a warning about not supported
product, just ignore.
At the same time, I had to upgrade my little home server hardware: it
was 32 bit. I also added functions to it: act as media centre.
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
signature.asc
Description: OpenPGP digital signature
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Continuing evergreen with Leap42.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
El 2017-02-22 a las 11:37 +0100, Ruediger Meier escribió:
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.
That will be solved eventually, I hope.
What worries me is that we got 2 kernel updates in a month. Several
updates this month that require a reboot (systemd, apparmor...). Not
good for server uptime.
- --
Cheers
Carlos E. R.
(from 42.2 x86_64 "Malachite" (Minas Tirith))
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iF0EAREIAAYFAliu0vcACgkQja8UbcUWM1wn+AD4tdN/6mIY7UMfU8I8Gc5tHszx
uKqYgibOc3Ir5YXvQgEAgtxYru8q7QrctDHS7R3J91242m3q3wR7bcmRPxIAhY4=
=SkFr
-END PGP SIGNATURE-___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Continuing evergreen with Leap42.2
On 2017-02-23 13:46, Ruediger Meier wrote: > On Thursday 23 February 2017, Carlos E. R. wrote: >> El 2017-02-22 a las 11:37 +0100, Ruediger Meier escribió: >>> ... and it happened again. They upgraded 42.3 to texlive-2016 and >>> it breaks again. Evergreen is still needed. >> >> That will be solved eventually, I hope. >> >> What worries me is that we got 2 kernel updates in a month. Several >> updates this month that require a reboot (systemd, apparmor...). Not >> good for server uptime. > > > You DO NOT NEED to reboot after kernel update. Nowadays the old kernel > should be still installed in parallel so module loading still works > without reboot. If I do that, then I would simply not apply the update at all. Far easier and more stable. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Continuing evergreen with Leap42.2
On 2017-02-23 14:27, Ruediger Meier wrote: > On Thursday 23 February 2017, Carlos E. R. wrote: >> On 2017-02-23 13:46, Ruediger Meier wrote: >>> On Thursday 23 February 2017, Carlos E. R. wrote: >>>> El 2017-02-22 a las 11:37 +0100, Ruediger Meier escribió: >>>>> ... and it happened again. They upgraded 42.3 to texlive-2016 and >>>>> it breaks again. Evergreen is still needed. >>>> >>>> That will be solved eventually, I hope. >>>> >>>> What worries me is that we got 2 kernel updates in a month. >>>> Several updates this month that require a reboot (systemd, >>>> apparmor...). Not good for server uptime. >>> >>> You DO NOT NEED to reboot after kernel update. Nowadays the old >>> kernel should be still installed in parallel so module loading >>> still works without reboot. >> >> If I do that, then I would simply not apply the update at all. Far >> easier and more stable. > > > Hm, I never care about updates. I get them automatically everyday and > reboot whenever I want. I think that's more simple. Not something you can do in a server. The point is, one does not expect that many updates in a stable release. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) signature.asc Description: OpenPGP digital signature ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
