tag:blogger.com,1999:blog-7072295959847306495.post2632390669915301497..comments2023-07-31T03:25:30.986-07:00Comments on Letrange's EvE Blog: More clues to the PI bug.Unknownnoreply@blogger.comBlogger5125tag:blogger.com,1999:blog-7072295959847306495.post-82551913629539856362010-06-22T01:27:27.645-07:002010-06-22T01:27:27.645-07:00I've seen these bugs as well both the time tra...I've seen these bugs as well both the time travel one, we have all got the max time run on our extractors since we initially set them up, and have yet to kick them off again (this is from the night of the CC release)<br /><br />also resources going missing I've confirmed it further down the production chain as I've been running 200 -> 60 batches of s2-s3 and they've been dropping out aswell. My current working theory has to do with submitting multiple processors off of the same storage facility at the same time as I believe there might be a conflict collecting resources from the storage.WH Industrialisthttps://www.blogger.com/profile/12659746034588494624noreply@blogger.comtag:blogger.com,1999:blog-7072295959847306495.post-43318845145519764092010-06-21T19:06:21.357-07:002010-06-21T19:06:21.357-07:00I noticed the "time travel" effect as we...I noticed the "time travel" effect as well this weekend. I log in to restart my extractors left on the 23 hour, and sure enough, they were still going for about 10 or so more hours. I didn't audit the amount as they are bulk extractors for export, so I don't know if the extractors just stopped along the way and restarted, or if they cycled with some weird time interval.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7072295959847306495.post-39603726812804927032010-06-21T17:02:09.769-07:002010-06-21T17:02:09.769-07:00Huh, that could very well be it... but wierd since...Huh, that could very well be it... but wierd since the others way to overload a route gives a msg saying that this operation "can not be done because of heavy congestion"Unknownhttps://www.blogger.com/profile/05774498705192859951noreply@blogger.comtag:blogger.com,1999:blog-7072295959847306495.post-8886487618300497722010-06-21T15:59:54.598-07:002010-06-21T15:59:54.598-07:00You may have lost the route when going from 23h to...You may have lost the route when going from 23h to 5h and not noticed it. It takes more m3 on your routes during the 5h runs.<br /><br />Very easy, and not really a bug so much as no good "warning" that it couldn't continue to route.<br /><br />IMarvUnknownhttps://www.blogger.com/profile/01039188121434931051noreply@blogger.comtag:blogger.com,1999:blog-7072295959847306495.post-19836690823562222622010-06-21T08:21:09.834-07:002010-06-21T08:21:09.834-07:00Be sure to recheck your extrator routes also. Yest...Be sure to recheck your extrator routes also. Yesterday evening when I was restarting my extractors with their good 23h cycles (after doing 5h Cycles during the day sunday), exactly 1/4 of my extractor had their routes "Lost". <br /><br />I don't know how it happened, but 1 out of 4 had their outgoing materials "unrounted" and I'm pretty sure i they were before that. <br /><br />So I don't know if changing from a 23h cycle -> 5h cycle -> 23h cycle has a small chanche of deleting the outgoing route, but something wierd is going onUnknownhttps://www.blogger.com/profile/05774498705192859951noreply@blogger.com