Апарсер падает, в лог пишется следующее:
Что делать? в чем может быть причина?
Код:
Mar 5 18:30:08.17338 long parsing(37.613233089447): SE::Yandex::0, query: стойки +на гранту цена
Mar 5 18:30:08.17442 long parsing(37.6167149543762): SE::Yandex::0, query: лада равен концепт 2013
Mar 5 18:30:10.52809 long parsing(1.83095812797546): SE::Yandex::0, query: lada prior
Mar 5 18:32:48.0795 long parsing(155.791522026062): SE::Yandex::0, query: лада калина 2 универсал в нижнем новгороде
Mar 5 18:32:49.26703 long parsing(1.11870288848877): SE::Yandex::0, query: "ваз лада ларгус технические характеристики"
Mar 5 18:32:49.89555 long parsing(0.622828960418701): SE::Yandex::0, query: "лада гранта аварии фото"
pfae d52f died at core.to_build.pl line 52907.
Mar 5 18:32:49.89603 exit called
Mar 5 18:32:49.89674 end called
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
(in cleanup) Can't use string ("") as a subroutine ref while "strict refs" in use at core.to_build.pl line 44772 during global destruction.
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
Mar 5 18:32:50.01753 cannot commit database unique_5_iterator config/unique/5_iterator.db
Use of uninitialized value in subroutine entry at core.to_build.pl line 44772 during global destruction.
Mar 5 18:33:58.53938 parser started
Mar 5 18:33:58.54374 load task 1
Mar 5 18:33:58.55173 load task 2
Mar 5 18:33:58.56257 load task 3
Mar 5 18:33:58.57031 load task 4
Mar 5 18:33:58.57813 load task 5
Mar 5 18:33:58.5897 starting task 1
Mar 5 18:33:58.97754 starting task 2
Mar 5 18:33:59.32823 starting task 3
Mar 5 18:33:59.6829 starting task 4
Mar 5 18:34:00.01816 starting task 5
Mar 5 18:34:01.80315 using existing iterator
Mar 5 18:34:01.80331 loading before not loaded iterator
Mar 5 18:34:01.80384 resuming queries/85238411 at 1357 line
DBD::SQLite::db do failed: Safety level may not be changed inside a transaction at core.to_build.pl line 17735, <$__ANONIO__> line 1357.
Mar 5 18:34:01.00506 using existing iterator
Mar 5 18:34:01.00522 loading before not loaded iterator
Mar 5 18:34:01.00572 resuming queries/52452838 at 1364 line
DBD::SQLite::db do failed: Safety level may not be changed inside a transaction at core.to_build.pl line 17735, <$__ANONIO__> line 1364.
Mar 5 18:34:02.16896 using existing iterator
Mar 5 18:34:02.1691 loading before not loaded iterator
Mar 5 18:34:02.16948 resuming queries/46727181 at 7397 line
DBD::SQLite::db do failed: Safety level may not be changed inside a transaction at core.to_build.pl line 17735, <$__ANONIO__> line 7397.
Mar 5 18:34:02.31946 using existing iterator
Mar 5 18:34:02.31963 loading before not loaded iterator
Mar 5 18:34:02.32005 resuming queries/77130853 at 12735 line
Mar 5 18:34:02.54705 using existing iterator
Mar 5 18:34:02.54725 loading before not loaded iterator
Mar 5 18:34:02.54812 resuming queries/17839458 at 7739 line
DBD::SQLite::db do failed: Safety level may not be changed inside a transaction at core.to_build.pl line 17735, <> line 7739.
DBD::SQLite::db do failed: Safety level may not be changed inside a transaction at core.to_build.pl line 17735, <$__ANONIO__> line 12735.Что делать? в чем может быть причина?
