Quote:
Originally Posted by bigwoof
Thanks! can't test this today. visiting relatives with the little one. Will try tomorrow after backing up everything.. :-)
|
okay. ran a test today.
with the metadata version and NiLuJe's kobo tools. interesting to say the least
1. started ku and ran htop in a telnet shell. started klogd as well
htop showed that the memory usage up to the point of connection (where ku is reading the book list before connecting) is okay. about 280M and the telnet shell and htop were snappy. CPU usage was 100% for a while and then dropped to 10-20%
2. ku connected to calibre
memory usage shot up to 430M with 100% CPU but telnet and htop are still very responsive. so far so good.
calibre task is reading book list
3. calibre finishing reading the book list and switches to converting books and sending them
memory usage on kobo shoots up to 471M and 100% CPU htop just hangs.. I thought the WiFi disconnected to be honest but I can control C out to the command line and telnet is just super slow.. I can restart htop but the display never shows up.
calibre shows the task as sending metadata
Kobo reboots
4. When reading the syslog, I can't replicate the reboot crash.
But this behavior is consistent. ku connects, calibre starts the tasks. right before the first book is transferred, ku disconnects with this error in the syslogs
Jan 3 10:18:33 nickel: ( 1079.309 @ 0x3541df0 / packetdump.warning) "http://127.0.0.1:8181/messages" => "Connection closed"
calibre then fails all the conversion tasks
not sure why monitoring the syslog stops the reboot but I'll keep trying. the syslog is not logging to disk and I'm not sure I want to tell it too.
also two additional things.
1. if the calibre metadata file on kobo is empty (0 bytes) which happens after ku crashes for me, next time I start ku, it will not connect to calibre. it will just pop up the finished message during the metadata reading portion. this seems like a bad chicken and egg problem.
2. the files that were transfered were just put into the top-level /mnt/onboard directory. how do I get it to use the default <author name as directory>/<filename> convention?
I'll keep trying to get a reboot crash monitored in syslog. exciting!! :-)