1. Этот сайт использует файлы cookie. Продолжая пользоваться данным сайтом, Вы соглашаетесь на использование нами Ваших файлов cookie. Узнать больше.
  2. Вступайте в наш Telegram чат: https://t.me/a_parser Нас уже 2600+ и мы растем!
    Скрыть объявление

Частое аварийное завершение работы

Тема в разделе "Техническая поддержка", создана пользователем vipuncle, 18 мар 2016.

  1. vipuncle

    vipuncle A-Parser Pro License
    A-Parser Pro

    Регистрация:
    7 апр 2015
    Сообщения:
    125
    Симпатии:
    42
    Сигнатура проблемы:
    Имя события проблемы: APPCRASH
    Имя приложения: aparser.exe
    Версия приложения: 1.1.434.0
    Отметка времени приложения: 56d5ae77
    Имя модуля с ошибкой: ntdll.dll
    Версия модуля с ошибкой: 6.1.7601.19135
    Отметка времени модуля с ошибкой: 56a1c6fa
    Код исключения: c0000028
    Смещение исключения: 00090fb9
    Версия ОС: 6.1.7601.2.1.0.272.7
    Код языка: 1049
    Дополнительные сведения 1: 5f9e
    Дополнительные сведения 2: 5f9e5a8639ee13cf358653ed72c14692
    Дополнительные сведения 3: cf13
    Дополнительные сведения 4: cf1397d0bd15644f40b3a58fd74a1de6


    [​IMG]
     
  2. Support

    Support Administrator
    Команда форума A-Parser Enterprise

    Регистрация:
    16 мар 2012
    Сообщения:
    4.372
    Симпатии:
    2.102
    Выложите лог aparser.log, а также сообщите, выполняются ли в моменты падений другие задания, если да, то какие и во сколько потоков.
     
  3. vipuncle

    vipuncle A-Parser Pro License
    A-Parser Pro

    Регистрация:
    7 апр 2015
    Сообщения:
    125
    Симпатии:
    42
    create template(main) at build/core.to_build.pl line 852.
    created template -3656 at build/core.to_build.pl line 861.
    Mar 16 14:24:36.95891 parser started
    Mar 16 14:24:38.33172 starting task 56
    Mar 16 14:24:40.31292 loading before not loaded iterator
    Mar 16 14:24:40.31576 resuming queries/subs/words.txt at 1 line
    Mar 16 14:25:30.57954 task 56 stopped
    DBI db handle 0x21caf094 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x21caf094, com 0x28a0d654, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x21373938)
    KIDS 0 (0 Active)
    Mar 16 14:27:58.71784 starting task 57
    Mar 16 14:33:09.49225 task 57 stopped
    DBI db handle 0x6d0e0784 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x6d0e0784, com 0x28a0d18c, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x21373938)
    KIDS 0 (0 Active)
    Mar 16 14:34:06.90964 starting task 58
    Mar 16 14:38:09.29663 task 58 stopped
    DBI db handle 0x296bf9b8 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x296bf9b8, com 0x30b7341c, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x21373938)
    KIDS 0 (0 Active)
    Mar 16 14:38:47.75685 starting task 59
    Mar 16 14:39:58.0066 task 59 stopped
    DBI db handle 0x2a76ff80 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x2a76ff80, com 0x6db99304, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x21373938)
    KIDS 0 (0 Active)
    Mar 16 14:40:38.18977 starting task 60
    Mar 16 15:02:42.84819 long parsing(0.127557992935181): SE::Bing::0, query: images mercurio wp-admin
    Mar 16 20:39:40.88928 long parsing(0.181586980819702): SE::Bing::0, query: images topic wp-content/themes
    Mar 16 20:39:45.42889 long parsing(0.260226011276245): SE::Bing::0, query: images topic wp-content/themes
    Mar 16 20:39:47.4569 long parsing(0.108770847320557): SE::Bing::0, query: images topic wp-admin
    Mar 16 20:39:59.68732 long parsing(0.146856069564819): SE::Bing::0, query: images topic wp-content/themes
    Mar 16 20:40:00.91972 long parsing(0.236052989959717): SE::Bing::0, query: images topic wp-admin
    Mar 16 20:40:04.15044 long parsing(0.165800094604492): SE::Bing::0, query: images topic wp-content/themes
    Mar 16 20:40:17.83015 long parsing(0.272686004638672): SE::Bing::0, query: images topic wp-admin
    Mar 16 20:43:34.6446 long parsing(0.206451892852783): SE::Bing::0, query: images ntopic wp-includes
    Mar 16 20:43:40.0533 long parsing(0.270148992538452): SE::Bing::0, query: images ntopic wp-includes
    Mar 16 20:43:45.06901 long parsing(0.166321039199829): SE::Bing::0, query: images ntopic wp-includes
    Mar 16 20:43:50.19332 long parsing(0.325075149536133): SE::Bing::0, query: images ntopic wp-includes
    Mar 16 20:43:54.96694 long parsing(0.29783296585083): SE::Bing::0, query: images ntopic wp-includes
    Mar 16 20:43:59.97923 long parsing(0.161598205566406): SE::Bing::0, query: images ntopic wp-includes
    Mar 16 20:44:05.12255 long parsing(0.448312997817993): SE::Bing::0, query: images ntopic wp-includes
    IO error: config/unique/global_global/611025.ldb Append: cannot write at build/core.to_build.pl line 20161.
    create template(main) at build/core.to_build.pl line 852.
    created template -984 at build/core.to_build.pl line 861.
    Mar 17 12:24:02.59117 parser started
    Mar 17 12:24:03.93277 starting task 60
    Mar 17 12:24:05.92957 loading before not loaded iterator
    Mar 17 12:24:06.03886 resuming queries/subs/words.txt at 2 line
    Mar 17 12:24:45.51253 task 60 stopped
    DBI db handle 0x20ca3840 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x20ca3840, com 0x289d2f0c, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x2036b460)
    KIDS 0 (0 Active)
    Mar 17 12:26:12.81014 starting task 61
    Mar 17 13:16:17.27689 task 61 stopped
    DBI db handle 0x6747f214 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x6747f214, com 0x70e702ec, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x2036b460)
    KIDS 0 (0 Active)
    Mar 17 13:18:53.81545 starting task 62
    Mar 17 13:19:43.34127 task 62 stopped
    DBI db handle 0x6c58f2fc has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x6c58f2fc, com 0x679c8b54, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x2036b460)
    KIDS 0 (0 Active)
    Mar 17 13:20:01.00379 starting task 63
    Mar 17 13:26:07.68433 task 63 stopped
    DBI db handle 0x69fb3928 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x69fb3928, com 0x372afc64, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x2036b460)
    KIDS 0 (0 Active)
    Mar 17 13:26:53.18832 starting task 64
    Mar 17 13:29:46.97915 task 64 stopped
    DBI db handle 0x1dfabaa0 has uncleared implementors data at build/core.to_build.pl line 33596.
    dbih_clearcom (dbh 0x1dfabaa0, com 0x679c50e4, imp DBD::SQLite::db):
    FLAGS 0x100113: COMSET IMPSET Warn PrintError PrintWarn
    PARENT DBI::dr=HASH(0x2036b460)
    KIDS 0 (0 Active)
    Mar 17 13:30:44.16168 starting task 65
    Mar 17 14:20:50.24707 long parsing(0.196130990982056): SE::Bing::0, query: and mentis wp-content
    Mar 17 14:20:55.94755 long parsing(0.212901830673218): SE::Bing::0, query: and mentis wp-content
    Mar 17 14:42:03.73076 long parsing(0.145998001098633): SE::Bing::0, query: and transitivo wp-content/uploads
    IO error: config/unique/global_global/616971.ldb Append: cannot write at build/core.to_build.pl line 20161, <$__ANONIO__> line 12.
    create template(main) at build/core.to_build.pl line 852.
    created template -2252 at build/core.to_build.pl line 861.
    Mar 17 23:09:07.79336 parser started
    Mar 17 23:09:09.18176 starting task 65
    Mar 17 23:09:11.11617 loading before not loaded iterator
    Mar 17 23:09:11.12105 resuming queries/subs/top1000.txt at 3 line
    Mar 18 00:23:03.21235 long parsing(0.241142988204956): SE::Bing::0, query: a mentis
    Mar 18 00:23:09.1381 long parsing(0.298619985580444): SE::Bing::0, query: a mentis
    IO error: config/unique/global_global/618581.ldb Append: cannot write at build/core.to_build.pl line 20161.
    create template(main) at build/core.to_build.pl line 852.
    created template -3492 at build/core.to_build.pl line 861.
    Mar 18 11:22:06.4871 parser started
    Mar 18 11:22:07.92231 starting task 65
    Mar 18 11:22:09.96591 loading before not loaded iterator
    Mar 18 11:22:10.02977 resuming queries/subs/top1000.txt at 6 line
    Mar 18 11:40:30.18238 long parsing(0.365749835968018): SE::Bing::0, query: in mentis wp-content
    Mar 18 11:40:35.79839 long parsing(0.408719062805176): SE::Bing::0, query: in mentis wp-content
    Mar 18 11:40:41.4612 long parsing(0.113198041915894): SE::Bing::0, query: in mentis wp-content
    Mar 18 14:11:01.17518 long parsing(0.348870992660522): SE::Bing::0, query: was mentis
    Mar 18 14:11:07.82977 long parsing(0.408279895782471): SE::Bing::0, query: was mentis
    Mar 18 14:11:14.29826 long parsing(0.412358999252319): SE::Bing::0, query: was mentis
    Mar 18 14:11:21.45867 long parsing(0.39890193939209): SE::Bing::0, query: was mentis
    Mar 18 14:11:33.15866 long parsing(0.416305065155029): SE::Bing::0, query: was mentis
    Mar 18 14:53:43.88876 long parsing(0.441123008728027): SE::Bing::0, query: was fo
    Mar 18 14:53:50.12875 long parsing(0.36525297164917): SE::Bing::0, query: was fo
    IO error: config/unique/global_global/619407.ldb Append: cannot write at build/core.to_build.pl line 20161, <$__ANONIO__> line 7.
    create template(main) at build/core.to_build.pl line 852.
    created template -4052 at build/core.to_build.pl line 861.
    поставил 1000 потоков, пока норм, но на других серверах такой же конфигурации и по 1500 норм отрабатывает, и задания по больше...
     
    #3 vipuncle, 18 мар 2016
    Последнее редактирование: 18 мар 2016
  4. Support

    Support Administrator
    Команда форума A-Parser Enterprise

    Регистрация:
    16 мар 2012
    Сообщения:
    4.372
    Симпатии:
    2.102
    Данные ошибки говорят о проблемах с жестким диском (закончилось место или битые сектора)
     

Поделиться этой страницей