Jolla 1 with outstanding uptime

Question

11

Jolla 1 with outstanding uptime

asked 2019-02-28 18:16:31 +0200

Self-Perfection

2496 ●37 ●53 ●49

updated 2019-02-28 18:37:57 +0200

Well not a question, but just wanting to share.

I noticed that my Jolla 1 has whopping uptime:

$ uptime
 18:53:11 up 474 days,  4:45,  2 users,  load average: 0.12, 0.16, 0.36
$ grep PRETTY /etc/os-release
PRETTY_NAME="SailfishOS 2.0.5.6 (Haapajoki) (armv7hl)"

Yup, I have not updated it for very long time. I currently use it just as sound recorder.

The interesting thing I found it that timed stopped responding between 2018-11-03 and 2018-11-06. That is suspiciously close to 1 year since it was started:

$ ps -o lstart -C timed-qt5
                 STARTED
Sat Nov 11 14:08:12 2017

timedclient-qt5 -l freezes and clock shows empty list of timers and alarms.

This might be a peculiar bug, but again it might have been already fixed in subsequent releases.

Any ideas what might be fun to check before I reboot this device?

edit retag flag offensive close delete

Comments

2

Would be nice to know if timed is actually stuck or not ...

systemctl --user status timed-qt5

"active (running)" -> ok
anything else -> not ok
dbus-send --system --type=method_call --print-reply --dest=com.nokia.time / org.freedesktop.DBus.Peer.Ping
practically immediate reply message -> ok
nothing happens for 25 seconds (default dbus timeout), then "org.freedesktop.DBus.Error.NoReply" -> the timed process is stuck and is not handling dbus requests
something else -> also interesting

If it is stuck and you are familiar with gdb: Installing timed debug packages, attaching gdb to running timed process + getting backtrace would be nice.

Since the process is likely to have been stuck for ages, there probably is nothing interesting in the logs, but might be worthwhile to try anyway - something like:

devel-su journalctl -a | grep timed

And perhaps check if restarting timed succeeds (process id changes) and restores functionality (the timedclient things that were not working)?

[nemo@Sailfish ~]$ /sbin/pidof timed-qt5
3514
[nemo@Sailfish ~]$ systemctl --user restart timed-qt5
[nemo@Sailfish ~]$ /sbin/pidof timed-qt5
6777

spiiroin ( 2019-03-01 10:42:05 +0200 )edit

Would be nice to know if timed is actually stuck or not ...
systemctl --user status timed-qt5
"active (running)" -> ok
anything else -> not ok
dbus-send --system --type=method_call --print-reply --dest=com.nokia.time / org.freedesktop.DBus.Peer.Ping
practically immediate reply message -> ok
nothing happens for 25 seconds (default dbus timeout), then "org.freedesktop.DBus.Error.NoReply" -> the timed process is stuck and is not handling dbus requests
something else -> also interesting
If it is stuck and you are familiar with gdb: Installing timed debug packages, attaching gdb to running timed process + getting backtrace would be nice.
Since the process is likely to have been stuck for ages, there probably is nothing interesting in the logs, but might be worthwhile to try anyway - something like:
devel-su journalctl -a | grep timed
And perhaps check if restarting timed succeeds (process id changes) and restores functionality (the timedclient things that were not working)?
[nemo@Sailfish ~]$ /sbin/pidof timed-qt5 3514 [nemo@Sailfish ~]$ systemctl --user restart timed-qt5 [nemo@Sailfish ~]$ /sbin/pidof timed-qt5 6777
spiiroin ( 2019-03-01 10:42:05 +0200 )edit

Answer 1

5

answered 2019-03-01 19:49:28 +0200

juiceme
4027 ●54 ●78 ●89

Pretty good start, that is.

I managed to get 1266 days of uptime on my last N9 before the infamous battery bloating killed the device. (that's 3 years and 171 days, huh)

edit flag offensive delete publish link

Comments

1

Really?!!!

addydon ( 2019-03-01 20:08:41 +0200 )edit

Truly.

After getting my Jolla sbj1 I retired the N9 and used it as media server (constantly on, plugged to a wall charger)

juiceme ( 2019-03-02 01:33:04 +0200 )edit

Answer 2

1

answered 2019-02-28 21:15:11 +0200

Pohli

188 ●5 ●13 ●19

updated 2019-02-28 21:20:09 +0200

Try to add events before and after 2038-01-19 in the calendar app and access them after. (Year 2038 problem)

Nothing to do with uptime though, but maybe you're going to update OS and I don't experience this bug in current version.

edit flag offensive delete publish link

Jolla 1 with outstanding uptime

Comments

2 Answers

Comments

Question tools

Stats

Jolla 1 with outstanding uptime

Comments

2 Answers

Comments

Question tools

Public thread

Stats