I got this error on my TouchPad back in July, now it just happened on my Verizon Pre 2 running webOS 2.1.0.
After rebooting, my phone would not boot back up. I waited for hours with the flashing HP logo before I re-doctored the phone.
Shortly after vre-doctoring, it's warning me that my application database is now "almost" full. So I connected it to my PC and loaded up novaterm and did a "df -h" and saw this:
Code:
/dev/mapper/store-mojodb
139.5M 128.3M 11.1M 92% /var/db
So like others said before me, the issue is in /var/db. Looking at the contents of that folder:
Code:
# ls -lha /var/db
drwxr-xr-x 5 root root 4.0K Nov 25 07:35 .
drwxr-xr-x 28 root root 4.0K Nov 25 04:05 ..
-rw------- 1 root root 0 May 4 2011 _lock
-rw------- 1 root root 2.0M Nov 25 07:35 log.0000000392
drwx------ 2 root root 16.0K Nov 24 16:11 lost+found
drwx------ 2 root root 4.0K Nov 24 22:22 main
drwx------ 2 root root 4.0K Nov 25 00:16 temp
Also, like before, I'm seeing 2M log files being generated. Looking at these log files I see contents of *really* old emails from my comapny (Exchange) email.
Now the really big files are under /var/db/main:
Code:
# du -m /var/db
0 /var/db/lost+found
0 /var/db/temp
110 /var/db/main
112 /var/db
Of the 139.5 MB available on this partition, /var/db/main is using 110 MB.
Code:
# ls -lha /var/db/main
drwx------ 2 root root 4.0K Nov 24 22:22 .
drwxr-xr-x 5 root root 4.0K Nov 25 07:35 ..
-rw------- 1 root root 24.0K Nov 25 07:34 UsageDbName
-rw------- 1 root root 1 May 4 2011 _version
-rw------- 1 root root 48.0K Nov 25 04:37 indexIds.db
-rw------- 1 root root 19.1M Nov 25 07:39 indexes.db
-rw------- 1 root root 56.0K Nov 25 05:35 kinds.db
-rw------- 1 root root 90.4M Nov 25 07:34 objects.db
-rw------- 1 root root 16.0K Nov 25 07:34 sequences.db
So 'objects.db' and 'indexes.db' are the biggest files here. objects.db alone is using two thirds of the space for the entire partition. I suspect this is probably not normal or desirable.
Does anyone know what this file is for? Can it be safely deleted?
I also noticed the process:
Code:
/usr/bin/mojodb-luna -c /etc/palm/mojodb.conf /var/db
Seemed quite busy. So I decided to peek at /etc/palm/mojodb.conf:
Code:
{
"log" : {
"appender" : {
"type" : "syslog"
},
"levels" : {
/*"default" : "info"*/
}
},
"db" : {
"permissions" : [
{"type":"db.role","object":"admin","caller":"com.palm.configurator","operations":{"*":"allow"}},
{"type":"db.role","object":"admin","caller":"com.palm.service.backup","operations":{"*":"allow"}},
{"type":"db.role","object":"admin","caller":"com.palm.odd.service","operations":{"*":"allow"}},
{"type":"db.role","object":"admin","caller":"com.palm.service.migrationscript","operations":{"*":"allow"}},
{"type":"db.role","object":"admin","caller":"com.palm.spacecadet","operations":{"*":"allow"}}
],
"quotas" : [
{"owner":"*","size":20971520},
{"owner":"com.palm.*","size":78643200}
],
"loadStepSize" : 173,
},
"bdb" : {
"maxLocks" : 6000,
"maxLockers" : 1000,
"compactStepSize" : 25000
}
}
Could I perhaps alter these settings to help with the issue?
-Jeremy
Originally Posted by irwinr12
