|
2012-11-05
, 07:52
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#2
|
|
2012-11-05
, 07:55
|
Posts: 11 |
Thanked: 15 times |
Joined on Dec 2009
|
#3
|
|
2012-11-05
, 08:13
|
Posts: 11 |
Thanked: 15 times |
Joined on Dec 2009
|
#4
|
|
2012-11-05
, 08:34
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#5
|
|
2012-11-05
, 08:35
|
Posts: 280 |
Thanked: 136 times |
Joined on Dec 2011
@ Banyuwangi, Indonesia
|
#6
|
|
2012-11-05
, 08:48
|
Posts: 11 |
Thanked: 15 times |
Joined on Dec 2009
|
#7
|
tracker-sparql -q "select nie:plainTextContent(?d) where {?d a nmo:SMSMessage}"
|
2012-11-05
, 08:49
|
Posts: 11 |
Thanked: 15 times |
Joined on Dec 2009
|
#8
|
|
2012-11-05
, 08:55
|
Moderator |
Posts: 6,215 |
Thanked: 6,400 times |
Joined on Nov 2011
|
#9
|
|
2012-11-05
, 09:11
|
Posts: 11 |
Thanked: 15 times |
Joined on Dec 2009
|
#10
|
The Following User Says Thank You to csaavedra For This Useful Post: | ||
I suppose there is a corruption in the database storing messages, but I am not sure how to check it. Other applications are still working fine so it is less likely to be a general filesystem corruption.
This is pretty annoying as new incoming messages can only be read in their notifications.
Any ideas?