org.archive.crawler.framework.exceptions.FatalConfigurationException: IOException occured while writing new settings files for new job/profile Invalid argument

JIRA | Michael Stack | 10 years ago
  1. 0

    Igor sees this on crawling006. When I try to create a new job based on an existing job I get FatalConfigurationException. An error occured org.archive.crawler.framework.exceptions.FatalConfigurationException: IOException occured while writing new settings files for new job/profile Invalid argument org.archive.crawler.framework.exceptions.FatalConfigurationException: IOException occured while writing new settings files for new job/profile Invalid argument at org.archive.crawler.admin.CrawlJobHandler.makeNew(CrawlJobHandler.java:834) at org.archive.crawler.admin.CrawlJobHandler.newJob(CrawlJobHandler.java:706) at org.archive.crawler.jspc.admin.jobs.new_jsp._jspService(Unknown Source) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicati onHandler.java:342) at org.archive.crawler.admin.ui.RootFilter.doFilter(RootFilter.java:67) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicati onHandler.java:334) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHand ler.java:286) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContex t.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:300) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)

    JIRA | 10 years ago | Michael Stack
    org.archive.crawler.framework.exceptions.FatalConfigurationException: IOException occured while writing new settings files for new job/profile Invalid argument
  2. 0

    Reported on list (Hei; structurechart@y) ===================================================== I was trying my checkpoint, and so I clicked on Jobs->Based on a recovery->recover-log. Then, I got the following exception: org.archive.crawler.framework.exceptions.FatalConfigurationException: /home/hei/heritrix-1.12.0/jobs/myHost-20070408024241829/logs/recover.gz.gz does not exist or is unreadable org.archive.crawler.framework.exceptions.FatalConfigurationException: /home/hei/heritrix-1.12.0/jobs/myHost-20070408024241829/logs/recover.gz.gz does not exist or is unreadable at org.archive.crawler.admin.CrawlJobHandler.checkDirectory(CrawlJobHandler.java:765) at org.archive.crawler.admin.CrawlJobHandler.updateRecoveryPaths(CrawlJobHandler.java:952) at org.archive.crawler.admin.CrawlJobHandler.newJob(CrawlJobHandler.java:734) at org.archive.crawler.jspc.admin.jobs.new_jsp._jspService(Unknown Source) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342) at org.archive.crawler.admin.ui.RootFilter.doFilter(RootFilter.java:67) at org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:300) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511) I think that the problem is that Heritrix is trying to open /home/hei/heritrix-1.12.0/jobs/myHost-20070408024241829/logs/recover.gz.gz instead of /home/hei/heritrix-1.12.0/jobs/myHost-20070408024241829/logs/recover.gz. It could be a typo in Heritrix code. I haven't got a chance to look at the code yet. Any idea? Thanks in advance. =====================================================

    JIRA | 10 years ago | Gordon Mohr
    org.archive.crawler.framework.exceptions.FatalConfigurationException: /home/hei/heritrix-1.12.0/jobs/myHost-20070408024241829/logs/recover.gz.gz does not exist or is unreadable

    Root Cause Analysis

    1. org.archive.crawler.framework.exceptions.FatalConfigurationException

      IOException occured while writing new settings files for new job/profile Invalid argument

      at org.archive.crawler.admin.CrawlJobHandler.makeNew()
    2. org.archive.crawler
      new_jsp._jspService
      1. org.archive.crawler.admin.CrawlJobHandler.makeNew(CrawlJobHandler.java:834)
      2. org.archive.crawler.admin.CrawlJobHandler.newJob(CrawlJobHandler.java:706)
      3. org.archive.crawler.jspc.admin.jobs.new_jsp._jspService(UnknownSource)
      3 frames
    3. GWT dev
      HttpJspBase.service
      1. org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
      1 frame
    4. JavaServlet
      HttpServlet.service
      1. javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      1 frame
    5. Jetty Server
      WebApplicationHandler$Chain.doFilter
      1. org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
      2. org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:342)
      2 frames
    6. org.archive.crawler
      RootFilter.doFilter
      1. org.archive.crawler.admin.ui.RootFilter.doFilter(RootFilter.java:67)
      1 frame
    7. Jetty Server
      ServletHandler.handle
      1. org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicationHandler.java:334)
      2. org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:286)
      3. org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
      3 frames
    8. org.mortbay.http
      HttpContext.handle
      1. org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
      1 frame
    9. Jetty Server
      WebApplicationContext.handle
      1. org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
      1 frame
    10. org.mortbay.http
      SocketListener.handleConnection
      1. org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
      2. org.mortbay.http.HttpServer.service(HttpServer.java:879)
      3. org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
      4. org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
      5. org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
      6. org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218)
      6 frames
    11. Jetty Util
      ThreadPool$PoolThread.run
      1. org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:300)
      2. org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)
      2 frames