1Тема от Max_Damage

Wialon Pro перестал запускаться

  • Откуда: Пермь
  • Зарегистрирован: 19/04/2012
  • Сообщений: 13
  • Продукты: Wialon Pro
  • Карма: 0

Тема: Wialon Pro перестал запускаться

Добрый день. Сегодня с утра виалон завис. После остановки службы он попытался создать файл *.core и скушал остатки места на диске. Т.к. эти файлы создавались практически после каждого зависания и занимали более Гб каждый, а так же в содержимом была явно отладочная информация типа дампов, то файлы посчитались ненужными и пришлось почистить эти файлы, чтобы освободить место. При последующем запуске виалона он честно описал ошибки в логах и отказался запускаться. Собственно прошу помощи в этой проблеме.

error.log

2015/05/12 12:14:13:826: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/227270, past end of log at 1254/177449
2015/05/12 12:14:14:512: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:512: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:512: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/206002, past end of log at 1254/177711
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/218659, past end of log at 1254/177711
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/196144, past end of log at 1254/177711
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/224192, past end of log at 1254/177711
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/179623, past end of log at 1254/177711
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/204428, past end of log at 1254/177711
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:649: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/221306, past end of log at 1254/177711
2015/05/12 12:14:14:649: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:649: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:649: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:666: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/229330, past end of log at 1254/177711
2015/05/12 12:14:14:666: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:666: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:666: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:690: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/226138, past end of log at 1254/177711
2015/05/12 12:14:14:690: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:690: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:690: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:693: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/205014, past end of log at 1254/177711
2015/05/12 12:14:14:693: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:693: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:693: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:696: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/230985, past end of log at 1254/177711
2015/05/12 12:14:14:696: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:696: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:696: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:711: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/200741, past end of log at 1254/177711
2015/05/12 12:14:14:711: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:711: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:711: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:742: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/185675, past end of log at 1254/177711
2015/05/12 12:14:14:742: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:742: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:742: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment

trace.log

2015/05/12 12:14:03:139: Loading ADF plugin: 'storage_server'...
2015/05/12 12:14:03:140: core::load_library(adf_storage)
2015/05/12 12:14:03:140: storage_service::initialize(/var/lib/wialonb3/storage)
2015/05/12 12:14:03:214: storage_service::open_environment: initializing properties environment (cache: size: 16 MB, chunks: 1)...
2015/05/12 12:14:03:228: storage_service::open_environment: preloading databases...
2015/05/12 12:14:05:225: storage_service::open_environment: opening database environment...
2015/05/12 12:14:06:772: storage_service::open_environment: opening databases...
2015/05/12 12:14:06:773: storage_messages_env::open_environment: opening database environment (cache: size: 64 MB, chunks: 1)...
2015/05/12 12:14:07:989: storage_messages_env::open_environment: opening databases...
2015/05/12 12:14:07:990: storage_messages_env::open_environment: registered v2 1 database: left: 0, right: 0, count: 103878585, new-count: 5061504
2015/05/12 12:14:07:991: storage_messages_env::open_environment: registered v2 2 database: left: 0, right: 0, count: 105284051, new-count: 5464261
2015/05/12 12:14:07:991: storage_messages_env::open_environment: registered v2 3 database: left: 0, right: 0, count: 88524643, new-count: 16069246
2015/05/12 12:14:07:992: storage_messages_env::open_environment: registered v2 4 database: left: 0, right: 0, count: 54404233, new-count: 8230179
2015/05/12 12:14:07:992: storage_messages_env::open_environment: registered v2 5 database: left: 0, right: 0, count: 53140378, new-count: 2770024
2015/05/12 12:14:07:993: storage_messages_env::open_environment: registered v2 6 database: left: 0, right: 0, count: 23408467, new-count: 928927
2015/05/12 12:14:07:993: storage_messages_env::open_environment: registered v2 7 database: left: 0, right: 0, count: 2180168, new-count: 103000
2015/05/12 12:14:07:993: storage_messages_env::open_environment: opened 7 databases with 430820525 messages and 38627141 new messages, fragmentation level is 8%.
2015/05/12 12:14:08:004: storage_service::initialize: constructing service item...
2015/05/12 12:14:08:005: storage_service::initialize: next locid: 2309
2015/05/12 12:14:08:014: storage_service::initialize: service object constructed (guid='8ad12b639ef700670b4edad9dc841d38')
2015/05/12 12:14:08:091: storage_service::initialize: constructing other items with 4 threads...
2015/05/12 12:14:08:177: avl_server::init_prop_manager('f6ca8537eb154e6d5126bb1ca13d8594')
2015/05/12 12:14:08:682: storage_service::initialize: initialized 1896 objects in 620 ms
2015/05/12 12:14:08:682: storage_service::initialize: loading persistent items cache...
2015/05/12 12:14:08:703: storage_service::initialize: done loading persistent items cache of size 276.26 KB
2015/05/12 12:14:08:703: storage_messages_cache::msgs_thread('8ad12b639ef700670b4edad9dc841d38'): started
2015/05/12 12:14:08:760: Loading ADF plugin: 'webgis'...
2015/05/12 12:14:08:808: Loading ADF plugin: 'webavl'...
2015/05/12 12:14:08:863: core::load_library(adf_avl_web)
2015/05/12 12:14:08:863: Loaded 'adf_avl_web' version '5.5.0104'
2015/05/12 12:14:08:892: Loading ADF plugin: 'avl_comm_server'...
2015/05/12 12:14:09:168: adf_avl_init_comm('local', '0:0', 1)
2015/05/12 12:14:09:168: adf_avl_scan_hw_dir('8ad12b639ef700670b4edad9dc841d38')
2015/05/12 12:14:09:747: storage_messages_cache::msgs_thread('8ad12b639ef700670b4edad9dc841d38'): restored 9082 messages
2015/05/12 12:14:13:826: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/227270, past end of log at 1254/177449
2015/05/12 12:14:14:097: backtrace 1: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__db_errcall:??:0

2015/05/12 12:14:14:109: backtrace 2: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__db_errx:??:0

2015/05/12 12:14:14:122: backtrace 3: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__log_check_page_lsn:??:0

2015/05/12 12:14:14:135: backtrace 4: /var/lib/wialonb3/dep/lib/libdb-6.0.so:(null):log_put.c:0

2015/05/12 12:14:14:148: backtrace 5: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__log_put_record:??:0

2015/05/12 12:14:14:162: backtrace 6: /var/lib/wialonb3/dep/lib/libdb-6.0.so:(null):bt_put.c:0

2015/05/12 12:14:14:175: backtrace 7: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__bam_ritem:??:0

2015/05/12 12:14:14:187: backtrace 8: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__bam_iitem:??:0

2015/05/12 12:14:14:199: backtrace 9: /var/lib/wialonb3/dep/lib/libdb-6.0.so:(null):bt_cursor.c:0

2015/05/12 12:14:14:211: backtrace 10: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__dbc_iput:??:0

2015/05/12 12:14:14:223: backtrace 11: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__dbc_put:??:0
2015/05/12 12:14:14:234: backtrace 12: /var/lib/wialonb3/dep/lib/libdb-6.0.so:__dbc_put_pp:??:0

2015/05/12 12:14:14:285: backtrace 13: /var/lib/wialonb3/lib/libadf_storage.so:_ZN3adf27i_storage_prop_manager_impl23set_property_value_implEhPKchPKvjbxjPNS_21storage_property_dataE:??:0

2015/05/12 12:14:14:297: backtrace 14: /var/lib/wialonb3/lib/libadf_storage.so:_ZN3adf27i_storage_prop_manager_impl18set_property_valueEhPKchPKvjbb:??:0

2015/05/12 12:14:14:309: backtrace 15: /var/lib/wialonb3/lib/libadf_storage.so:_ZN3adf27i_storage_prop_manager_impl19set_property_stringEhPKcS2_b:??:0

2015/05/12 12:14:14:357: backtrace 16: /var/lib/wialonb3/lib/libadf_avl.so:_ZN3adf20avl_hw_driver_plugin12configure_hwEv:??:0

2015/05/12 12:14:14:370: backtrace 17: /var/lib/wialonb3/lib/libadf_avl.so:_ZN3adf20avl_hw_driver_plugin10begin_commEv:??:0

2015/05/12 12:14:14:383: backtrace 18: /var/lib/wialonb3/lib/libadf_avl.so:_ZN3adf20avl_hw_driver_plugin6bg_jobEv:??:0

2015/05/12 12:14:14:396: backtrace 19: /var/lib/wialonb3/lib/libadf_storage.so:_ZN3adf12storage_item6bg_jobEv:??:0

2015/05/12 12:14:14:409: backtrace 20: /var/lib/wialonb3/lib/libadf_storage.so:_ZN3adf15storage_service14bg_jobs_threadEPv:??:0

2015/05/12 12:14:14:436: backtrace 21: /var/lib/wialonb3/lib/libadf_core.so:_ZN3adf14thread_creator12start_threadEPNS0_11thread_infoE:??:0

2015/05/12 12:14:14:448: backtrace 22: /var/lib/wialonb3/lib/libadf_core.so:_Z20thread_creator_startPv:??:0

2015/05/12 12:14:14:460: backtrace 23: /lib64/libpthread.so.0:(null):pthread_create.c:0

2015/05/12 12:14:14:512: backtrace 24: /lib64/libc.so.6:clone:??:0

2015/05/12 12:14:14:512: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:512: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:512: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/206002, past end of log at 1254/177711
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:533: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/218659, past end of log at 1254/177711
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:538: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/196144, past end of log at 1254/177711
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:566: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/224192, past end of log at 1254/177711
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:579: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/179623, past end of log at 1254/177711
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:611: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2506 file props.db has LSN 1254/204428, past end of log at 1254/177711
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2507 Commonly caused by moving a database from one database environment
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2508 to another without clearing the database LSNs, or by removing all of
2015/05/12 12:14:14:643: adf_storage_db_error_call: archive: BDB2509 the log files from a database environment

service.log

2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB0060 PANIC: fata
l region error detected; run recovery
2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB3015 props.db: w
rite failed for page 1260
2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB3027 props.db: u
nable to flush page: 1260
2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB2516 DB_ENV->log
_flush: LSN of 1254/661121 past current end-of-log of 1254/179221
2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB2517 Database en
vironment corrupt; the wrong log files may have been removed or incompatible dat
abase files imported from another environment
2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB0061 PANIC: BDB0
087 DB_RUNRECOVERY: Fatal error, run database recovery
2015/05/12 12:14:22:129: adf_storage_db_error_call: archive: BDB3027 props.db: u
nable to flush page: 1261

0
2Ответ от bako

Wialon Pro перестал запускаться

  • bako
  • bako
  • Wialon fan club
  • Неактивен
  • Зарегистрирован: 01/09/2010
  • Сообщений: 514
  • Карма: 174

Re: Wialon Pro перестал запускаться

core вы зря удалили, надо было оставить хотя бы последний из созданных. Освобождать место лучше всего за счет ротации логов, или удаляйте их вручную из /var/lib/wialonb3/logs/ . Дальнейшие инструкции будут отправлены по почте.

WDC Administrator
Gurtam

Max_Damage

+1
3Ответ от Max_Damage

Wialon Pro перестал запускаться

  • Откуда: Пермь
  • Зарегистрирован: 19/04/2012
  • Сообщений: 13
  • Продукты: Wialon Pro
  • Карма: 0

Re: Wialon Pro перестал запускаться

В том то и дело, что последний был нулевой длинны. Я удалил за прошлые года, но виалон уже не запускался. Так что остальные были так же удалены. Спасибо за быстрый ответ. С нетерпением ждём инструкций.
P.s. Сейчас нашёл подобную проблему и там рекомендовали отвязать лог файлы, но лучше дождусь инструкций, чтоб не обвалить базу.

0
4Ответ от Max_Damage

Wialon Pro перестал запускаться

  • Откуда: Пермь
  • Зарегистрирован: 19/04/2012
  • Сообщений: 13
  • Продукты: Wialon Pro
  • Карма: 0

Re: Wialon Pro перестал запускаться

Спасибо большое. Помогло. Виалон заработал. Единственная проблема была, что база размером около 200Гб и это заняло время...

0
5Ответ от bako

Wialon Pro перестал запускаться

  • bako
  • bako
  • Wialon fan club
  • Неактивен
  • Зарегистрирован: 01/09/2010
  • Сообщений: 514
  • Карма: 174

Re: Wialon Pro перестал запускаться

200 Гб это не самая большая база, но и на нее уходит некоторое время. Главное, что всё хорошо закончилось

WDC Administrator
Gurtam

0
6Ответ от lexer

Wialon Pro перестал запускаться

  • lexer
  • lexer
  • Gurtam Partner
  • Неактивен
  • Откуда: Киев
  • Зарегистрирован: 23/05/2012
  • Сообщений: 278
  • Продукты: Wialon ProWialon Local
  • Карма: 36

Re: Wialon Pro перестал запускаться

200 гб это не много)
у нас у клиента Про уже около 2 лет - около 5к обьектов и данные накапливаются постоянно без удаления - на данный момент .../storage - почти 1Тб smile

Роман
www.uonline.com.ua

Сайт lexer

0