Mailinglist Archive: opensuse-support (176 mails)

< Previous Next >
Re: [opensuse-support] Re: Unresponsive desktop
On 05/02/2019 10.54, Jiri Slaby wrote:
On 03. 02. 19, 14:33, Carlos E. R. wrote:
After several days running, this morning it locked as soon as I changed
workspaces. I noticed kswapd0 was busy long time, and that firefox had
about 10 gigs of virtual memory. The disk activity led was solid blue. I
couldn't find out more, the machine froze and had to be hard rebooted.

Sometimes, this gets logged as OOM. Have you checked logs from the boot
right before the reboot?

Yes, nothing. The word "OOM" is nowhere in the logs from 2019-01-28 to
2019-02-05.


/var/log/messages during the event:


<3.6> 2019-02-03 13:00:01 Telcontar dbus-daemon 1537 - - [system] Activating
service name='org.opensuse.Snapper' requested by ':1.10447' (ui
d=0 pid=29269 comm="/usr/lib/snapper/systemd-helper --timeline ") (using
servicehelper)
<3.6> 2019-02-03 13:00:01 Telcontar dbus-daemon 1537 - - [system] Successfully
activated service 'org.opensuse.Snapper'
<10.6> 2019-02-03 13:00:01 Telcontar cron 29258 - - pam_unix(crond:session):
session opened for user cer by (uid=0)
<10.6> 2019-02-03 13:00:01 Telcontar cron 29257 - - pam_unix(crond:session):
session opened for user cer by (uid=0)
<9.6> 2019-02-03 13:00:01 Telcontar CRON 29292 - - (cer) CMD
(/home/cer/bin/dar_la_hora_en_cron hora)
<10.6> 2019-02-03 13:00:01 Telcontar CRON 29257 - - pam_unix(crond:session):
session closed for user cer
<10.6> 2019-02-03 13:00:05 Telcontar CRON 29258 - - pam_unix(crond:session):
session closed for user cer
<3.6> 2019-02-03 13:06:46 Telcontar smartd 1473 - - Device: /dev/sdc [SAT],
SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 7
8 to 79
<3.6> 2019-02-03 13:06:46 Telcontar smartd 1473 - - Device: /dev/sdc [SAT],
SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 7
8 to 79
<3.6> 2019-02-03 13:09:28 Telcontar systemd 1 - - Started Leafnode NNTP server
(127.0.0.1:35362).
<3.6> 2019-02-03 13:09:28 Telcontar systemd 1 - - Started Leafnode NNTP server
(127.0.0.1:35360).
<10.6> 2019-02-03 13:20:01 Telcontar cron 30074 - - pam_unix(crond:session):
session opened for user cer by (uid=0)
<10.6> 2019-02-03 13:20:01 Telcontar CRON 30074 - - pam_unix(crond:session):
session closed for user cer
<10.6> 2019-02-03 13:24:05 Telcontar unix2_chkpwd - - - gkr-pam: unlocked
login keyring
<3.6> 2019-02-03 13:24:11 Telcontar systemd 1 - - Started Leafnode NNTP server
(127.0.0.1:35744).
<3.6> 2019-02-03 13:24:11 Telcontar systemd 1 - - Started Leafnode NNTP server
(127.0.0.1:35742).
<10.3> 2019-02-03 13:28:54 Telcontar cron 30378 - -
pam_systemd(crond:session): Failed to create session: Connection timed out
2019-02-03 13:34:47+01:00 - Booting the system now
================================================================================
Linux T



"Started Leafnode NNTP server" is probably when I successful sent one nntp
(news) post on Thunderbird on workspace 2, instants before it hanged.


Going to the "/var/log/allmessages-20190204.xz" log, I can see some more
details:


<63>1 2019-02-03T13:24:16.583416+01:00 Telcontar fetchnews 30228 - - <211 0
451 450 comp.os.linux.announce
<63>1 2019-02-03T13:24:16.583442+01:00 Telcontar fetchnews 30228 - - >GROUP
comp.os.linux.embedded
<63>1 2019-02-03T13:24:16.633080+01:00 Telcontar fetchnews 30228 - - <211 4
1842 1845 comp.os.linux.embedded
<62>1 2019-02-03T13:24:16.633109+01:00 Telcontar fetchnews 30228 - -
comp.os.linux.embedded: no new articles
<63>1 2019-02-03T13:24:16.633372+01:00 Telcontar fetchnews 30228 - - >QUIT
<62>1 2019-02-03T13:24:16.782370+01:00 Telcontar fetchnews 30228 - - wrote
active file with 46702 lines
<63>1 2019-02-03T13:24:16.782824+01:00 Telcontar fetchnews 30252 - - Process
forked.
<62>1 2019-02-03T13:24:16.823734+01:00 Telcontar fetchnews 30228 - - child has
process ID 30252
<86>1 2019-02-03T13:24:16.832408+01:00 Telcontar CRON 30219 - -
pam_unix(crond:session): session closed for user news
<30>1 2019-02-03T13:24:16.837939+01:00 Telcontar systemd 1 - - Stopping User
Manager for UID 9...
<86>1 2019-02-03T13:24:16.856877+01:00 Telcontar systemd - - -
pam_unix(systemd-user:session): session closed for user news
<30>1 2019-02-03T13:24:16.857733+01:00 Telcontar systemd 1 - - Stopped User
Manager for UID 9.
<30>1 2019-02-03T13:24:16.858306+01:00 Telcontar systemd 1 - - Removed slice
User Slice of news.
<63>1 2019-02-03T13:24:17.825814+01:00 Telcontar fetchnews 30252 - - Process
done.
<63>1 2019-02-03T13:25:40.081855+01:00 Telcontar leafnode 30240 - - <POST
<63>1 2019-02-03T13:25:40.081890+01:00 Telcontar leafnode 30240 - - rereading
/var/spool/news/leaf.node/groupinfo
<63>1 2019-02-03T13:25:40.443816+01:00 Telcontar leafnode 30240 - - >340 Go
ahead.
<63>1 2019-02-03T13:25:40.566794+01:00 Telcontar leafnode 30240 - - >240
Article posted, now be patient
<22>1 2019-02-03T13:26:23.993497+01:00 Telcontar dovecot - - -
imap(cer)<30193><dXLxcPyAnoF/AAAB>: Logged out in=3526 out=9193 deleted=0 exp
unged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0
<22>1 2019-02-03T13:26:25.188125+01:00 Telcontar dovecot - - - imap-login:
Login: user=<cer>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mp
id=30339, TLS, session=<rS8QfPyAPoJ/AAAB>
<30>1 2019-02-03T13:28:29.454128+01:00 Telcontar systemd 1 - - Created slice
User Slice of news.
<30>1 2019-02-03T13:28:29.964244+01:00 Telcontar systemd 1 - - Starting User
Manager for UID 9...
<30>1 2019-02-03T13:28:30.608901+01:00 Telcontar systemd 1 - - Started Session
4871 of user news.
<83>1 2019-02-03T13:28:54.199886+01:00 Telcontar cron 30378 - -
pam_systemd(crond:session): Failed to create session: Connection timed out
<86>1 2019-02-03T13:28:56.968197+01:00 Telcontar cron 30378 - -
pam_unix(crond:session): session opened for user news by (uid=0)
<63>1 2019-02-03T13:29:17.142305+01:00 Telcontar fetchnews 30386 - - config:
debugmode is 1
<63>1 2019-02-03T13:29:17.279998+01:00 Telcontar fetchnews 30386 - - config:
maxfetch is 5000
<63>1 2019-02-03T13:29:17.280033+01:00 Telcontar fetchnews 30386 - - config:
maxage is 0

You can see how it is working, then things start to fail at 13:28, yet
fetchnews is running correctly

<63>1 2019-02-03T13:29:17.280033+01:00 Telcontar fetchnews 30386 - - config:
maxage is 0
<63>1 2019-02-03T13:29:17.280053+01:00 Telcontar fetchnews 30386 - - config:
postings have max. 500000 bytes
<63>1 2019-02-03T13:29:17.280075+01:00 Telcontar fetchnews 30386 - - config:
timeout_long is 100 days
<63>1 2019-02-03T13:29:17.280097+01:00 Telcontar fetchnews 30386 - - config:
timeout_fetchnews is 90 seconds

... trimming

<63>1 2019-02-03T13:29:23.735856+01:00 Telcontar fetchnews 30386 - -
check_date: News.Individual.NET: server time 1549196963, our time 15491
96963

... trimming


... trimming

<62>1 2019-02-03T13:29:39.454094+01:00 Telcontar fetchnews 30386 - -
comp.os.linux.embedded: no new articles
<63>1 2019-02-03T13:29:39.581622+01:00 Telcontar fetchnews 30386 - - >QUIT
<62>1 2019-02-03T13:29:39.971244+01:00 Telcontar fetchnews 30386 - - wrote
active file with 46702 lines
<63>1 2019-02-03T13:29:40.107338+01:00 Telcontar fetchnews 30387 - - Process
forked.
<62>1 2019-02-03T13:29:40.107366+01:00 Telcontar fetchnews 30386 - - child has
process ID 30387
<30>1 2019-02-03T13:34:48.596658+01:00 Telcontar systemd 1 - - systemd 234
running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT
+UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS
+KMOD -IDN2 -IDN default-hierarchy=hybrid)
<30>1 2019-02-03T13:34:48.596706+01:00 Telcontar systemd 1 - - Detected
architecture x86-64.
<30>1 2019-02-03T13:34:48.596715+01:00 Telcontar systemd 1 - - Set hostname to
<Telcontar>.
<28>1 2019-02-03T13:34:48.596721+01:00 Telcontar systemd 1 - -
nss-lookup.target: Dependency Before=nss-lookup.target dropped
<30>1 2019-02-03T13:34:48.596727+01:00 Telcontar apparmor.systemd 632 - -
Restarting AppArmor
<30>1 2019-02-03T13:34:48.596737+01:00 Telcontar apparmor.systemd 632 - -
Reloading AppArmor profiles



And that's the reboot. Last entry 2019-02-03T13:29:40.107366+01:00.


What I could see in the top display (I should have made a photo with camera)
was similar to this, taken last December on the laptop, that also has that
problem:

PID USER PR NI VIRT RES SHR SWAP S %CPU %MEM TIME+
COMMAND
38 root 20 0 0 0 0 0 S 25.39 0.000 20:48.33
kswapd0 <===




--
Cheers / Saludos,

Carlos E. R.
(from 15.0 x86_64 at Telcontar)

< Previous Next >
List Navigation