retire orestis
It looks like the new Onionoo host orestis has too slow I/O for the background update process. That process is supposed to run once per hour but takes up to 1.5 hours on orestis:
2017-02-11 08:16:04,808 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 10:02:23,439 INFO o.t.o.cron.Main:230 Done.
2017-02-11 10:02:23,439 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 11:22:18,326 INFO o.t.o.cron.Main:230 Done.
2017-02-11 11:22:18,326 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 12:48:30,872 INFO o.t.o.cron.Main:230 Done.
2017-02-11 12:48:30,872 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 14:19:26,622 INFO o.t.o.cron.Main:230 Done.
2017-02-11 14:19:26,622 DEBUG o.t.o.cron.Main:147 Started update ...
The same background update process runs for about 25 minutes on omeiense:
2017-02-11 11:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 11:39:53,571 INFO o.t.o.cron.Main:230 Done.
2017-02-11 12:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 12:40:25,127 INFO o.t.o.cron.Main:230 Done.
2017-02-11 13:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 13:39:43,664 INFO o.t.o.cron.Main:230 Done.
2017-02-11 14:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
2017-02-11 14:41:59,334 INFO o.t.o.cron.Main:230 Done.
2017-02-11 15:15:11,391 DEBUG o.t.o.cron.Main:147 Started update ...
If you can, please confirm that I/O is really the issue here. And if so, can you move orestis to a host with faster I/O similar to that of omeiense? Thanks!