Received windows console close event shutting log core down

@glvde. вот что 
 

———-
Loaded log file: «server_log.txt».
———-

SA-MP Dedicated Server
———————-
v0.3.7-R2, (C)2005-2015 SA-MP Team

[10:43:38] filterscripts = «»  (string)
[10:43:38] 
[10:43:38] Server Plugins
[10:43:38] —————
[10:43:38]  Loading plugin: streamer
[10:43:38] 

*** Streamer Plugin v2.8.2 by Incognito loaded ***

[10:43:38]   Loaded.
[10:43:38]  Loading plugin: sscanf
[10:43:38] 

[10:43:38]  ===============================

[10:43:38]       sscanf plugin loaded.     

[10:43:38]          Version:  2.8.1        

[10:43:38]    (c) 2012 Alex «Y_Less» Cole  

[10:43:38]  ===============================

[10:43:38] 
[10:43:38] Filterscripts
[10:43:38] —————
[10:43:38]   Loaded 0 filterscripts.

[10:43:38] Script[gamemodes/new.amx]: Run time error 19: «File or function is not found»
[10:43:38] Number of vehicle models: 0
 

• ← Предыдущая тема
• Вопросы по скриптингу
• Следующая тема →

---

1. 
   13.09.2016, 23:51
   
   
   #191
   

   

   Пользователь

   

   ---

   Доброго времени суток, ошибку никак не могу исправить подскажите как действовать и что неправильно. Делал как вы показывали, R39.
   Еще никак не появляется окно регистрации в игре.
   [21:45:30] Script[gamemodes/Crim.amx]: Run time error 19: «File or function is not found»
   [21:45:30] Number of vehicle models: 0

   ---

2. 
   14.09.2016, 21:25
   
   
   #192
   

   Сообщение от xxlex
   

   Доброго времени суток, ошибку никак не могу исправить подскажите как действовать и что неправильно. Делал как вы показывали, R39.
   Еще никак не появляется окно регистрации в игре.
   [21:45:30] Script[gamemodes/Crim.amx]: Run time error 19: «File or function is not found»
   [21:45:30] Number of vehicle models: 0

   Полный лог предоставьте

   Связаться со мной в VK можно через личные сообщения этой группы
   Заказы не принимаю

   
   

   Широко известно, что идеи стоят 0.8333 цента каждая (исходя из рыночной цены 10 центов за дюжину).
   Великих идей полно, на них нет спроса.
   Воплощение идеи в законченную игру требует долгой работы,
   таланта, терпения и креативности, не говоря уж о затратах денег, времени и ресурсов.
   Предложить идею просто, воплотить – вот в чём проблема

   
   

   Steve Pavlina

   ---

3. 
   18.09.2016, 17:48
   
   
   #193
   

   

   Пользователь

   

   ---

   Решил по про бывать 41 версию(так как с 40 версию он не запускал, а с этой запустил)
   все заработало только вот
   в log-core.log

   Код:

   [INFO] received Windows console close event; shutting log-core down

   и warnings.log

   Код:

   [plugins/mysql] mysql_connect: no password specified (E:\0gamemodestest.pwn:30832)

   строка с варнингом

   Код:

   mysql_connect_ID = mysql_connect(MYSQL_HOST, MYSQL_USER, MYSQL_PASSWORD, MYSQL_DATABASE);

   в define

   Код:

   #define MYSQL_HOST                "localhost"
   #define MYSQL_USER                "root"
   #define MYSQL_DATABASE            "test"
   #define MYSQL_PASSWORD            ""

   ---

4. 
   18.09.2016, 17:55
   
   
   #194
   

   Видимо теперь MySQL пользователи без пароля не поддерживаются.

   ---

5. 
   18.09.2016, 17:56
   
   
   #195
   

   По поводу первого — не знаю даже. Как сам мог заметить, проблема в плагине для логов (новой системе логирования). Разбираться надо, но пока нет времени. Можешь попробовать поискать ответ тут или же там же спросить о том, в чём проблема.

   По поводу второго — ничего страшного. Это просто плагин предупреждает, что пароль не установлен. Как это отключить, я, если честно, не разбирался, но если тебя это сильно напрягает, просто в phpMyAdmin поставь пароль на БД и укажи его в моде.
   Если переживаешь по поводу качества подключения, то не переживай — всё нормально подключится и будет работать.

   Связаться со мной в VK можно через личные сообщения этой группы
   Заказы не принимаю

   
   

   Широко известно, что идеи стоят 0.8333 цента каждая (исходя из рыночной цены 10 центов за дюжину).
   Великих идей полно, на них нет спроса.
   Воплощение идеи в законченную игру требует долгой работы,
   таланта, терпения и креативности, не говоря уж о затратах денег, времени и ресурсов.
   Предложить идею просто, воплотить – вот в чём проблема

   
   

   Steve Pavlina

   ---

6. 
   19.09.2016, 18:31
   
   
   #196
   

   

   Пользователь

   

   ---

   Скинешь код мода с регой на r41?

   ---

7. 
   19.09.2016, 18:57
   
   
   #197
   

   Сообщение от JeLLy
   

   Скинешь код мода с регой на r41?

   Код для R40 подойдёт для R41.

   Связаться со мной в VK можно через личные сообщения этой группы
   Заказы не принимаю

   
   

   Широко известно, что идеи стоят 0.8333 цента каждая (исходя из рыночной цены 10 центов за дюжину).
   Великих идей полно, на них нет спроса.
   Воплощение идеи в законченную игру требует долгой работы,
   таланта, терпения и креативности, не говоря уж о затратах денег, времени и ресурсов.
   Предложить идею просто, воплотить – вот в чём проблема

   
   

   Steve Pavlina

   ---

8. 
   19.09.2016, 19:13
   
   
   #198
   

   

   Пользователь

   

   ---

   why?
   Script[gamemodes/grandlarc.amx]: Run time error 19: «File or function is not found»
   Number of vehicle models: 0

   ---

9. 
   19.09.2016, 19:49
   
   
   #199
   

   Сообщение от JeLLy
   

   why?
   Script[gamemodes/grandlarc.amx]: Run time error 19: «File or function is not found»
   Number of vehicle models: 0

   Значит что-то сделал не так/не хватает каких-либо библиотек. Скачай crashdetect, подключи его самым первым и запусти сервер, а после логи сюда

   Связаться со мной в VK можно через личные сообщения этой группы
   Заказы не принимаю

   
   

   Широко известно, что идеи стоят 0.8333 цента каждая (исходя из рыночной цены 10 центов за дюжину).
   Великих идей полно, на них нет спроса.
   Воплощение идеи в законченную игру требует долгой работы,
   таланта, терпения и креативности, не говоря уж о затратах денег, времени и ресурсов.
   Предложить идею просто, воплотить – вот в чём проблема

   
   

   Steve Pavlina

   ---

10. 
    19.09.2016, 22:14
    
    
    #200
    

    

    Пользователь

    

    ---

    [debug] Run time error 19: «File or function is not found»
    [debug] mysql_connect
    [debug] mysql_errno
    [debug] mysql_tquery
    [debug] mysql_close
    [debug] cache_get_row_count
    [debug] cache_get_value_name
    [debug] cache_insert_id
    [debug] cache_get_value_name_int
    [debug] Run time error 19: «File or function is not found»
    [debug] mysql_connect
    [debug] mysql_errno
    [debug] mysql_tquery
    [debug] mysql_close
    [debug] cache_get_row_count
    [debug] cache_get_value_name
    [debug] cache_insert_id
    [debug] cache_get_value_name_int
    Script[gamemodes/grandlarc.amx]: Run time error 19: «File or function is not found»
    Number of vehicle models: 0

    ---

[18:47:00] [INFO] received Windows console close event; shutting log-core down [18:47:31] [INFO] received Windows console close event; shutting log-core down [18:48:05] [INFO] received Windows console close event; shutting log-core down [18:49:01] [INFO] received Windows console close event; shutting log-core down [18:51:04] [INFO] received Windows console close event; shutting log-core down [19:47:22] [INFO] received Windows console close event; shutting log-core down [19:58:24] [INFO] received Windows console close event; shutting log-core down [20:24:54] [INFO] received Windows console close event; shutting log-core down [20:33:35] [INFO] received Windows console close event; shutting log-core down [20:35:16] [INFO] received Windows console close event; shutting log-core down [20:37:18] [INFO] received Windows console close event; shutting log-core down [20:39:46] [INFO] received Windows console close event; shutting log-core down [20:46:40] [INFO] received Windows console close event; shutting log-core down [20:49:40] [INFO] received Windows console close event; shutting log-core down [21:03:31] [INFO] received Windows console close event; shutting log-core down [21:13:48] [INFO] received Windows console close event; shutting log-core down [21:38:07] [INFO] received Windows console close event; shutting log-core down [21:47:06] [INFO] received Windows console close event; shutting log-core down [21:48:45] [INFO] received Windows console close event; shutting log-core down [21:51:13] [INFO] received Windows console close event; shutting log-core down [21:55:03] [INFO] received Windows console close event; shutting log-core down [22:07:32] [INFO] received Windows console close event; shutting log-core down [22:12:02] [INFO] received Windows console close event; shutting log-core down [22:17:04] [INFO] received Windows console close event; shutting log-core down [22:19:50] [INFO] received Windows console close event; shutting log-core down [22:20:51] [INFO] received Windows console close event; shutting log-core down [22:21:42] [INFO] received Windows console close event; shutting log-core down [22:22:36] [INFO] received Windows console close event; shutting log-core down [22:23:56] [INFO] received Windows console close event; shutting log-core down [22:25:07] [INFO] received Windows console close event; shutting log-core down [22:26:02] [INFO] received Windows console close event; shutting log-core down [22:28:02] [INFO] received Windows console close event; shutting log-core down [22:40:36] [INFO] received Windows console close event; shutting log-core down [22:43:05] [INFO] received Windows console close event; shutting log-core down [22:59:39] [INFO] received Windows console close event; shutting log-core down [23:06:30] [INFO] received Windows console close event; shutting log-core down [23:16:49] [INFO] received Windows console close event; shutting log-core down [23:18:25] [INFO] received Windows console close event; shutting log-core down [23:21:57] [INFO] received Windows console close event; shutting log-core down [23:25:21] [INFO] received Windows console close event; shutting log-core down [00:15:53] [INFO] received Windows console close event; shutting log-core down [02:12:15] [INFO] received Windows console close event; shutting log-core down [02:12:18] [INFO] received Windows console close event; shutting log-core down [02:14:08] [INFO] received Windows console close event; shutting log-core down [02:15:45] [INFO] received Windows console close event; shutting log-core down [17:34:52] [INFO] received Windows console close event; shutting log-core down [17:35:35] [INFO] received Windows console close event; shutting log-core down [17:36:50] [INFO] received Windows console close event; shutting log-core down [17:46:30] [INFO] received Windows console close event; shutting log-core down [19:34:52] [INFO] received Windows console close event; shutting log-core down [19:39:03] [INFO] received Windows console close event; shutting log-core down [20:26:34] [INFO] received Windows console close event; shutting log-core down [20:32:51] [INFO] received Windows console close event; shutting log-core down [20:41:33] [INFO] received Windows console close event; shutting log-core down [20:47:05] [INFO] received Windows console close event; shutting log-core down [20:53:53] [INFO] received Windows console close event; shutting log-core down [20:57:16] [INFO] received Windows console close event; shutting log-core down [21:00:21] [INFO] received Windows console close event; shutting log-core down [21:04:06] [INFO] received Windows console close event; shutting log-core down [21:11:18] [INFO] received Windows console close event; shutting log-core down [21:15:37] [INFO] received Windows console close event; shutting log-core down [21:17:49] [INFO] received Windows console close event; shutting log-core down [21:21:23] [INFO] received Windows console close event; shutting log-core down [21:54:49] [INFO] received Windows console close event; shutting log-core down [22:14:55] [INFO] received Windows console close event; shutting log-core down [22:16:00] [INFO] received Windows console close event; shutting log-core down [22:32:34] [INFO] received Windows console close event; shutting log-core down [22:47:13] [INFO] received Windows console close event; shutting log-core down [22:49:02] [INFO] received Windows console close event; shutting log-core down [22:57:29] [INFO] received Windows console close event; shutting log-core down [23:00:02] [INFO] received Windows console close event; shutting log-core down [23:32:49] [INFO] received Windows console close event; shutting log-core down [23:40:04] [INFO] received Windows console close event; shutting log-core down [23:48:31] [INFO] received Windows console close event; shutting log-core down [23:55:06] [INFO] received Windows console close event; shutting log-core down [23:59:05] [INFO] received Windows console close event; shutting log-core down [00:08:05] [INFO] received Windows console close event; shutting log-core down [00:41:58] [INFO] received Windows console close event; shutting log-core down [00:56:53] [INFO] received Windows console close event; shutting log-core down [02:08:45] [INFO] received Windows console close event; shutting log-core down [02:09:50] [INFO] received Windows console close event; shutting log-core down [02:10:49] [INFO] received Windows console close event; shutting log-core down [02:11:51] [INFO] received Windows console close event; shutting log-core down [02:20:54] [INFO] received Windows console close event; shutting log-core down [02:28:22] [INFO] received Windows console close event; shutting log-core down [02:33:51] [INFO] received Windows console close event; shutting log-core down [13:50:21] [INFO] received Windows console close event; shutting log-core down [14:08:18] [INFO] received Windows console close event; shutting log-core down [14:53:58] [INFO] received Windows console close event; shutting log-core down [15:16:31] [INFO] received Windows console close event; shutting log-core down [15:28:02] [INFO] received Windows console close event; shutting log-core down [16:19:13] [INFO] received Windows console close event; shutting log-core down [16:19:42] [INFO] received Windows console close event; shutting log-core down [16:21:08] [INFO] received Windows console close event; shutting log-core down [16:33:13] [INFO] received Windows console close event; shutting log-core down [19:50:59] [INFO] received Windows console close event; shutting log-core down [20:00:14] [INFO] received Windows console close event; shutting log-core down [20:20:03] [INFO] received Windows console close event; shutting log-core down [20:21:34] [INFO] received Windows console close event; shutting log-core down [20:26:09] [INFO] received Windows console close event; shutting log-core down [20:43:12] [INFO] received Windows console close event; shutting log-core down [20:47:48] [INFO] received Windows console close event; shutting log-core down [21:01:06] [INFO] received Windows console close event; shutting log-core down [21:04:48] [INFO] received Windows console close event; shutting log-core down [21:07:40] [INFO] received Windows console close event; shutting log-core down [21:11:34] [INFO] received Windows console close event; shutting log-core down [21:13:31] [INFO] received Windows console close event; shutting log-core down [21:17:38] [INFO] received Windows console close event; shutting log-core down [21:22:22] [INFO] received Windows console close event; shutting log-core down [21:29:25] [INFO] received Windows console close event; shutting log-core down [21:34:54] [INFO] received Windows console close event; shutting log-core down [21:42:53] [INFO] received Windows console close event; shutting log-core down [21:44:38] [INFO] received Windows console close event; shutting log-core down [21:46:06] [INFO] received Windows console close event; shutting log-core down [21:47:34] [INFO] received Windows console close event; shutting log-core down [21:51:40] [INFO] received Windows console close event; shutting log-core down [22:00:01] [INFO] received Windows console close event; shutting log-core down [22:04:14] [INFO] received Windows console close event; shutting log-core down [22:07:53] [INFO] received Windows console close event; shutting log-core down [22:09:55] [INFO] received Windows console close event; shutting log-core down [22:11:33] [INFO] received Windows console close event; shutting log-core down [22:12:55] [INFO] received Windows console close event; shutting log-core down [22:15:16] [INFO] received Windows console close event; shutting log-core down [22:16:16] [INFO] received Windows console close event; shutting log-core down [22:23:22] [INFO] received Windows console close event; shutting log-core down [22:28:19] [INFO] received Windows console close event; shutting log-core down [22:29:15] [INFO] received Windows console close event; shutting log-core down [22:32:32] [INFO] received Windows console close event; shutting log-core down [22:33:44] [INFO] received Windows console close event; shutting log-core down [22:42:06] [INFO] received Windows console close event; shutting log-core down [22:45:42] [INFO] received Windows console close event; shutting log-core down [22:47:27] [INFO] received Windows console close event; shutting log-core down [22:54:05] [INFO] received Windows console close event; shutting log-core down [22:57:35] [INFO] received Windows console close event; shutting log-core down [23:00:01] [INFO] received Windows console close event; shutting log-core down [23:05:09] [INFO] received Windows console close event; shutting log-core down [23:07:06] [INFO] received Windows console close event; shutting log-core down [23:08:24] [INFO] received Windows console close event; shutting log-core down [23:15:47] [INFO] received Windows console close event; shutting log-core down [23:18:34] [INFO] received Windows console close event; shutting log-core down [23:33:32] [INFO] received Windows console close event; shutting log-core down [23:41:55] [INFO] received Windows console close event; shutting log-core down [23:52:20] [INFO] received Windows console close event; shutting log-core down [00:03:40] [INFO] received Windows console close event; shutting log-core down [00:17:08] [INFO] received Windows console close event; shutting log-core down [00:21:59] [INFO] received Windows console close event; shutting log-core down [00:25:11] [INFO] received Windows console close event; shutting log-core down [00:47:48] [INFO] received Windows console close event; shutting log-core down [00:51:31] [INFO] received Windows console close event; shutting log-core down [00:54:11] [INFO] received Windows console close event; shutting log-core down [00:57:35] [INFO] received Windows console close event; shutting log-core down [00:59:37] [INFO] received Windows console close event; shutting log-core down [01:02:58] [INFO] received Windows console close event; shutting log-core down [01:05:42] [INFO] received Windows console close event; shutting log-core down [01:07:47] [INFO] received Windows console close event; shutting log-core down [01:20:48] [INFO] received Windows console close event; shutting log-core down [01:27:33] [INFO] received Windows console close event; shutting log-core down [01:34:49] [INFO] received Windows console close event; shutting log-core down [01:40:28] [INFO] received Windows console close event; shutting log-core down [01:41:30] [INFO] received Windows console close event; shutting log-core down [01:45:38] [INFO] received Windows console close event; shutting log-core down [01:47:39] [INFO] received Windows console close event; shutting log-core down [01:48:15] [INFO] received Windows console close event; shutting log-core down [02:00:43] [INFO] received Windows console close event; shutting log-core down [02:09:38] [INFO] received Windows console close event; shutting log-core down [02:12:16] [INFO] received Windows console close event; shutting log-core down [02:22:24] [INFO] received Windows console close event; shutting log-core down [02:43:50] [INFO] received Windows console close event; shutting log-core down [02:49:43] [INFO] received Windows console close event; shutting log-core down [02:55:54] [INFO] received Windows console close event; shutting log-core down [03:27:02] [INFO] received Windows console close event; shutting log-core down [03:29:25] [INFO] received Windows console close event; shutting log-core down [03:30:55] [INFO] received Windows console close event; shutting log-core down [03:43:03] [INFO] received Windows console close event; shutting log-core down [03:49:30] [INFO] received Windows console close event; shutting log-core down [03:54:06] [INFO] received Windows console close event; shutting log-core down [04:03:26] [INFO] received Windows console close event; shutting log-core down [18:58:02] [INFO] received Windows console close event; shutting log-core down [19:04:40] [INFO] received Windows console close event; shutting log-core down [19:15:35] [INFO] received Windows console close event; shutting log-core down [20:40:04] [INFO] received Windows console close event; shutting log-core down [20:52:28] [INFO] received Windows console close event; shutting log-core down [23:57:00] [INFO] received Windows console close event; shutting log-core down [00:06:29] [INFO] received Windows console close event; shutting log-core down [00:42:56] [INFO] received Windows console close event; shutting log-core down [01:49:05] [INFO] received Windows console close event; shutting log-core down [01:53:14] [INFO] received Windows console close event; shutting log-core down [02:40:17] [INFO] received Windows console close event; shutting log-core down [02:41:21] [INFO] received Windows console close event; shutting log-core down [02:50:40] [INFO] received Windows console close event; shutting log-core down [03:14:26] [INFO] received Windows console close event; shutting log-core down [04:06:44] [INFO] received Windows console close event; shutting log-core down [04:16:38] [ERROR] exception 0XC0000005 (ACCESS_VIOLATION) from Vectored Exception Handler catched; shutting log-core down [04:19:33] [ERROR] exception 0XC0000005 (ACCESS_VIOLATION) from Vectored Exception Handler catched; shutting log-core down [18:29:17] [INFO] received Windows console close event; shutting log-core down [17:36:01] [INFO] received Windows console close event; shutting log-core down [17:37:19] [INFO] received Windows console close event; shutting log-core down [17:48:26] [INFO] received Windows console close event; shutting log-core down [17:54:21] [INFO] received Windows console close event; shutting log-core down [18:28:47] [INFO] received Windows console close event; shutting log-core down [18:48:07] [INFO] received Windows console close event; shutting log-core down [19:09:21] [INFO] received Windows console close event; shutting log-core down [19:16:04] [INFO] received Windows console close event; shutting log-core down [21:41:45] [INFO] received Windows console close event; shutting log-core down [21:47:01] [INFO] received Windows console close event; shutting log-core down [22:30:49] [INFO] received Windows console close event; shutting log-core down [00:51:42] [INFO] received Windows console close event; shutting log-core down [00:52:53] [INFO] received Windows console close event; shutting log-core down [01:34:29] [INFO] received Windows console close event; shutting log-core down [01:43:49] [INFO] received Windows console close event; shutting log-core down [01:44:48] [INFO] received Windows console close event; shutting log-core down [01:47:50] [INFO] received Windows console close event; shutting log-core down [02:05:36] [INFO] received Windows console close event; shutting log-core down [02:08:11] [INFO] received Windows console close event; shutting log-core down [02:34:40] [INFO] received Windows console close event; shutting log-core down [03:12:13] [INFO] received Windows console close event; shutting log-core down [03:22:16] [INFO] received Windows console close event; shutting log-core down [03:26:35] [INFO] received Windows console close event; shutting log-core down [03:30:48] [INFO] received Windows console close event; shutting log-core down [03:31:49] [INFO] received Windows console close event; shutting log-core down [13:51:30] [INFO] received Windows console close event; shutting log-core down [13:51:47] [INFO] received Windows console close event; shutting log-core down [13:53:58] [INFO] received Windows console close event; shutting log-core down [14:30:34] [INFO] received Windows console close event; shutting log-core down [15:33:28] [INFO] received Windows console close event; shutting log-core down [17:20:36] [INFO] received Windows console close event; shutting log-core down [15:09:25] [INFO] received Windows console close event; shutting log-core down

INFO log level makes crash. #195

Hello there.
On my test & local server, I’ve set INFO log level since a long time and recently, for apparently no reason, it makes crash my server with the error bellow.
I’m using MySQL R41-4. I got no problem with that in the past.

The line of code:
mysql_log(ERROR | WARNING | INFO);

The text was updated successfully, but these errors were encountered:

Could you provide (upload it here or send me an email) your mysql.log file? Can you reliably reproduce the crash?

It doesn’t provide any useful informations. The error isn’t even written in the errors.log file, only on log-core.log It happens only with this gamemode. I tried with an another one enabling ALL logs and I don’t get any crash.
The crash occurs at the same time, everytime. removed

Edit:
I tried some configurations and only INFO log level makes crash.

This might be related to #189.
If I correctly understood, it also crashes with full logging enabled. Can you delete your log files, enable full logging, reproduce this again and provide the new mysql.log file again?

I took a look about «Crashes when using non existant callback» but, unfortunaly, every public functions exist and they are called correctly without INFO log level. Don’t mind me if I’m completly wrong.
Log file with ALL debug levels:
mysql.log

Seems like your OnWeaponsEquipementLoading callback has a negative index. Are you sure it exists in your gamemode?

Same problem here, crashing after I log in. It didn’t happen before, now happening all of a sudden.

@Sunehildeep Can you reliably reproduce this crash? If so, delete your MySQL plugin log file, enable full logging, reproduce this and provide me your mysql.log file.

That’s right. I’m so stupid lmao. I compiled with the «preprocessed» mode to check out and callback existed but the file where it was supposed existed wasn’t included for some reasons.
So it’s just exactly the same thing as #189. I’m so sorry for the wasted time.

Okay so, here it is, first of all the MySQL.log keeps logging the old data first of the loading of vehicles, business, etc from database for a while and I get stuck on the class request screen after logging in, then after around 2 minutes, it starts loading my data and starts calling the callback of the player load data, after loading it crashes.

And this is the crash error from log-core

@Dayrion No worries there. I’m glad we found the cause that quick!
@Sunehildeep Does your crash happen if you disable the INFO loglevel?

Happens even without logging
EDIT: I found the problem, it was a hooking problem, you can close it now

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

How to check the Shutdown and Startup Log in Windows 11/10

Finding out the last time the PC was correctly turned off or booted up is the way to start for troubleshooting many Windows issues. Another scenario is a public system. Thanks to the Event Viewer, administrators can view and monitor unauthorized use of the computer.

Whatever reason it is, you can find out when last your PC was put on and shut down directly from Windows. You don’t need a third-party app for this; the Windows Event Viewer can handle it perfectly.

What is the Windows Event Viewer?

The Windows Event Viewer is a Microsoft Management Console (MCC) – a core service of Windows that cannot be stopped or disabled. It keeps track of every activity that takes place on your PC.

During every event, the Event Viewer logs entries. It also logs the start and stop times of the event log service (Windows), giving correct date, time, and user details of every shutdown process.

How to use the Event Viewer?

They are more than four events related to shutting down and restarting the Windows 10 operating system; we will list the important five. They are:

How to find the shutdown log in Windows 11/10

They are different ways to find out any of the events listed above. The traditional way is through the Event Viewer app itself. Most events can be accessed with the Command Prompt, as you will see below.

1] View shutdown and restart events from Event Viewer

Open the Run dialogue box, and input eventvwr.msc then hit Ok. In Event Viewer, select Windows Logs > System from the left pane. From the right, click on the Filter Current Log link.

Type in 41,1074,6006,6008 into the box below Includes/Exclude Event IDs. Hit Ok. Windows then displays all shutdown-related events.

The Event Viewer shows detailed information on every operation carried out on the system. Learn how to view full event viewer logs in this article.

2] See the last shutdown time using Command Prompt

Open the Command Prompt, copy and paste the following code in the window, and hit Enter:

To view the timestamp of the last shutdown without other details, copy and paste the code below then hit Enter:

As much as this method gets the job done, we often suggest you use method one, which is the Event Viewer. Not only is it more straightforward, but it also doesn’t involve copying and pasting commands.

Источник

Why does my Windows Console Close Event Handler time out?

I build the following program in VS2017/Windows 10. When I run it, I hit close and ctrl_handler() is called as expected, but after

three seconds the process is forcefully terminated anyway.

This is a problem because my real application writes large log files and three seconds is not long enough to get them onto disk.

Where is the documentation that describes this behaviour? Its not in those for the CTRL+CLOSE signal.

Where is the timeout set? Can it be modified at the application level? Or with a group policy?

1 Answer 1

I suppose this is the reference you were looking for:

Unfortunately, this is determined by the OS. There is documentation describing the behavior in the HandlerRoutine Callback docs:

» In this case, no other handler functions are called, and the system displays a pop-up dialog box that asks the user whether to terminate the process. The system also displays this dialog box if the process does not respond within a certain time-out period (5 seconds for CTRL_CLOSE_EVENT, and 20 seconds for CTRL_LOGOFF_EVENT or CTRL_SHUTDOWN_EVENT).»

There is no (at least public, documented) API to change this timeout.

A process can use the SetProcessShutdownParameters function to prevent the system from displaying a dialog box to the user during logoff or shutdown. In this case,the system terminates the process when HandlerRoutine returns TRUE or when the time-out period elapses.

The operating system intentionally forces termination if it considers handler is taking too much time to complete.

Important note pulled from comments below:

. Ctrl+C is not subject to the time-out (I’ve tested it, and that’s what I am using now).

Источник

Read the Event Logs on Windows Server Core

So, you installed Windows Server Core without the Desktop Experience. Everything has been going fine with Server 2016 without the GUI until suddenly you start encountering an error. Now, how do read the Event Log for more troubleshooting information? Event Viewer, where are you?

If you have a Windows desktop computer nearby and remote management enabled on the server, you can connect remotely through Computer Management and read the event logs like you are used to doing. Alternatively, when it comes to Server Core, it’s up to PowerShell.

After logging into the server, you arrive at the command prompt. Enter ‘PowerShell.exe’ to change the command prompt to PowerShell.

To see the event logs available, enter this command:

This will show you the event logs available such as Application, HardwareEvents, Internet Explorer, Security, System, and others depending on the roles and software you have installed. This command will also show you the event log policies for maximum size, retention, overwrite action, and the number of entries.

To open a particular event log, use the command:

Replace [log name] with the name of the log you are interested in viewing. For example:

This lists the entries in the table format in the default order (most recent events at the top).

You can also filter the list to just show a particular type of entry such as errors or warnings.

This would get entries from the System log that occurred within the last hour and were logged as errors.

Now that you have browsed the logs, you might have found a particular instance that you wanted to see the full details. Use this command with the number from the index column in the logs:

This allows you to see all of the details of the entries without them being truncated.

Since this is PowerShell, you can use all of the tricks you are familiar with to optimize your use of the event log such as sorting, filtering, or exporting to a file. It’s a pretty simple process and should be faster than the MMC snap-in for Event Viewer.

Источник

Extending the shutdown timeout setting to ensure graceful IHostedService shutdown

I was seeing an issue recently where our application wasn’t running the StopAsync method in our IHostedService implementations when the app was shutting down. It turns out that this was due to some services taking too long to respond to the shutdown signal. In this post I show an example of the problem, discuss why it happens, and how to avoid it.

Running background services with IHostedService

StartAsync is called when the application is starting up. In ASP.NET Core 2.x this occurs just after the application starts handling requests, while in ASP.NET Core 3.x the hosted services are started just before the application starts handling requests.

StopAsync is called when the application receives the shut down ( SIGTERM ) signal, for example when you push CTRL+C in the console window, or the app is stopped by the host system. This allows you to close any open connections, dispose resources, and generally clean up your class as required.

Problems shutting down an IHostedService implementation

The problem I saw recently was causing an OperationCanceledException to be thrown when the application was shutting down:

Part of the problem is the way the Kafka library (and underlying librdkafka library) uses synchronous, blocking Consume calls, instead of async, cancellable calls. There’s not a great way around that.

The easiest way to understand this issue is with an example.

Demonstrating the problem

The easiest way to understand the problem is to create an application containing two IHostedService implementations:

The implementations for these two classes are shown below. The NormalHostedService is very simple:

The SlowHostedService is almost identical, but it has a Task.Delay that takes 10s to simulate a slow shutdown

The IHostedService s I had in practice only took 1s to shutdown, but we had many of them, so the overall effect was the same as above!

When we run the application, you’ll see the starting logs as usual:

However, if you press CTRL+C to shut down the application, there’s a problem. The SlowHostedService completes shutting down, but then an OperationCanceledException is thrown:

So what’s going on here? Where’s that timeout coming from?

The reason: HostOptions.ShutDownTimeout

You can find the problematic code in the framework Host implementation that runs on application shutdown. A simplified version is shown below:

The solution: increase the shutdown timeout

HostOptions isn’t explicitly configured anywhere by default, so you will need to configure it manually in your ConfigureSerices method. For example, the following config increases the timeout to 15s:

Alternatively, you can also load the timeout from configuration. For example, if you add the following to appsettings.json:

You can then bind the HostOptions configuration section to the HostOptions object:

This binds the serialised TimeSpan value 00:00:15 to the HostOptions value and sets the timeout to 15s. With that configuration, now when we stop the application, the services all shutdown correctly:

Your application will now wait up to 15s for all the hosted services to finish shutting down before exiting!

Summary

In this post I discussed an issue recently where our application wasn’t running the StopAsync method in our IHostedService implementations when the app was shutting down. This was due to some background services taking too long to respond to the shutdown signal, and exceeding the shutdown timeout. I demonstrated the problem with a single service taking 10s to shutdown, but in practice it happens whenever the total shutdown time for all services exceeds the default 5s.

The solution to the problem was to extend the HostOptions.ShutdownTimeout configuration value to be longer than 5s, using the standard ASP.NET Core IOptions configuration system.

Источник

//-INCLUDES-//
#include <a_samp>
#include <a_mysql> // plugin mysql
#include <sscanf2> // plugin sscanf
//---------//

//-MYSQL SETTING's-//
#define MYSQL_HOST    "localhost"     // Õîñòèíã
#define MYSQL_USER    "root"          // Ïîëüçîâàòåëü
#define MYSQL_PASS    ""              // Ïàðîëü
#define MYSQL_DB    "diamond"         // Áàçà äàííûõ

new MySQL: dbHandle;
new query[256];
//-----------------//

//-ÌÀÊÐÎÑÛ-//

// Îñòàëüíîå
#define     SERVER_NAME "Delaware Role Play | Test"

// Ñîîáùåíèÿ
#define     SCM         SendClientMessage
#define     SCMTA       SendClientMessageToAll
#define     SPD         ShowPlayerDialog

// Ñòèëè äèàëîãîâ
#define     DSM            DIALOG_STYLE_MSGBOX
#define     DSL         DIALOG_STYLE_LIST
#define     DSP            DIALOG_STYLE_PASSWORD
#define     DSI         DIALOG_STYLE_INPUT
#define     DSTIL       DIALOG_STYLE_TABLIST
#define     DSTH        DIALOG_STYLE_TABLIST_HEADERS
//---------//

//-ÖÂÅÒÀ-//
#define COLOR_WHITE                     0xFFFFFFFF
#define COLOR_VALIK                     0x73B461FF
#define COLOR_SHBAR_BG                  0x000000FF
#define COLOR_SHBAR_BG2                 0xB8CEF6FF
#define COLOR_ORANGE                    0xFAAC58FF
#define COLOR_GREEN                     0x42B02CFF
#define COLOR_GOLD                      0xFFD700FF
#define COLOR_RED                       0xBE2D2DFF
#define COLOR_LIGHTRED                  0xFF6347FF
#define COLOR_LIGHTBLUE                 0x6495EDFF
#define COLOR_LIGHTGREEN                0x9ACD32FF
#define COLOR_YELLOW                    0xFFFF00FF
#define COLOR_BLUENEW                   0xB8CEF6FF
#define COLOR_BLUE                      0x94B0C1FF
#define COLOR_PURPLE                    0xC2A2DAFF
#define COLOR_LIME                      0x10F441FF
#define COLOR_GREY                      0xAFAFAFFF
#define COLOR_CHAT                      0xCECECEFF
#define COLOR_SCHAT                     0xF0E68CFF
#define COLOR_DOCHAT                    0x4682B4FF
#define COLOR_RACIO                     0x2DB043FF
#define COLOR_DEPAR                     0x3399ffFF
#define COLOR_ACHAT                     0x99CC00FF
#define COLOR_ME                        0xFF99FFFF
#define COLOR_GOV                       0x045FB4FF
//-------//

//-ÍÅÍÓÆÍÀß ÕÓÉÍß-//
#define      pName(%0)   player_info[%0][NAME]
//----------------//

enum player
{
    ID,
    NAME[MAX_PLAYER_NAME],
    PASS[30],
    SEX,
    COLOR,
}
new player_info[MAX_PLAYERS][player];

enum temp
{
    LOGINTRIES,
}
new temp_info[MAX_PLAYERS][temp];

enum
{
    DLG_NONE,
    DLG_REG_CONFIRM,
    DLG_REG_PASS,
    DLG_REG_GENDER,
    DLG_REG_COLOR,
    DLG_REG_AGE,
    DLG_REG_FINISH,
    DLG_LOGIN,
}

main(){}

public OnGameModeInit()
{
    dbHandle = mysql_connect(MYSQL_HOST, MYSQL_USER, MYSQL_PASS, MYSQL_DB);
    if(mysql_errno() != 0)
    {
        print("[MYSQL] Íå óäàëîñü ïîäêëþ÷èòüñÿ ê áàçå äàííûõ");
        return SendRconCommand("exit");
    }
    else
    {
        print("[MYSQL] Ïîäêëþ÷åíèå ê áàçå äàííûõ óñïåøíî");
    }
    SetGameModeText("Delaware-rp Russian");
    AddPlayerClass(0, 1958.3783, 1343.1572, 15.3746, 269.1425, 0, 0, 0, 0, 0, 0);
    return 1;
}

public OnGameModeExit()
{
    mysql_close(dbHandle);
    return 1;
}

public OnPlayerRequestClass(playerid, classid)
{
    return 1;
}

public OnPlayerConnect(playerid)
{
    SetTimerEx("CheckAccountFromMysql", 1000, false, "i", playerid);
    GetPlayerName(playerid, player_info[playerid][NAME], MAX_PLAYER_NAME);
    temp_info[playerid][LOGINTRIES] = 3;
    return 1;
}

forward CheckAccountFromMysql(playerid);
public CheckAccountFromMysql(playerid)
{
    mysql_format(dbHandle, query, sizeof(query), "SELECT * FROM `accounts` WHERE `name` = '%e'", player_info[playerid][NAME]);
    mysql_tquery(dbHandle, query, "GetPlayerAccountFromMysql", "i", playerid);
}

forward GetPlayerAccountFromMysql(playerid);
public GetPlayerAccountFromMysql(playerid)
{
    new rows;
    cache_get_row_count(rows);
    if(rows)
    {
        // Åñëè åñòü ñîâïàäåíèÿ, ïîêàçûâàåì àâòîðèçàöèþ
        cache_get_value_name(0, "password", player_info[playerid][PASS], 31);
        new tempstring[403+(-2+MAX_PLAYER_NAME)];
        format(tempstring, sizeof(tempstring), "{ffffff}Äîáðî ïîæàëîâàòü íà {E88813}Delaware Role Play{FFFFFF}nnÂâåäèòå ñâîé ïàðîëünÏîïûòîê äëÿ ââîäà ïàðîëÿ: {28910B}%i", temp_info[playerid][LOGINTRIES]);
        SPD(playerid, DLG_LOGIN, DSP, "{E88813}Àâòîðèçàöèÿ", tempstring, "Ïðèíÿòü", "Âûõîä");
    }
    else
    {
        // Åñëè íåòó ñîâïàäåíèé, ïîêàçûâàåì ðåãèñòðàöèþ
        SPD(playerid, DLG_REG_CONFIRM, DSM, "{E88813}ß íå ðîáîò{FFFFFF}",
        "{FFFFFF}×òîáû ïðîéòè ïðîâåðêó íà {E88813}ðîáîòà{FFFFFF}, íàæìèòå 'Äàëåå'nnÇíàéòå, ÷òî åñëè âû áóäåòå çàïóñêàòü áîòîâ. Âû áóäåòå çàáåíåíû ïî àéïè.",
        "Äàëåå", "Âûõîä");
    }
}

public OnPlayerDisconnect(playerid, reason)
{
    return 1;
}

public OnPlayerSpawn(playerid)
{
    SetPlayerPos(playerid, 1255.4739,-1692.7408,19.7344);
    return 1;
}

public OnPlayerDeath(playerid, killerid, reason)
{
    return 1;
}

public OnVehicleSpawn(vehicleid)
{
    return 1;
}

public OnVehicleDeath(vehicleid, killerid)
{
    return 1;
}

public OnPlayerText(playerid, text[])
{
    return 1;
}

public OnPlayerCommandText(playerid, cmdtext[])
{
    return 0;
}

public OnPlayerEnterVehicle(playerid, vehicleid, ispassenger)
{
    return 1;
}

public OnPlayerExitVehicle(playerid, vehicleid)
{
    return 1;
}

public OnPlayerStateChange(playerid, newstate, oldstate)
{
    return 1;
}

public OnPlayerEnterCheckpoint(playerid)
{
    return 1;
}

public OnPlayerLeaveCheckpoint(playerid)
{
    return 1;
}

public OnPlayerEnterRaceCheckpoint(playerid)
{
    return 1;
}

public OnPlayerLeaveRaceCheckpoint(playerid)
{
    return 1;
}

public OnRconCommand(cmd[])
{
    return 1;
}

public OnPlayerRequestSpawn(playerid)
{
    return false;
}

public OnObjectMoved(objectid)
{
    return 1;
}

public OnPlayerObjectMoved(playerid, objectid)
{
    return 1;
}

public OnPlayerPickUpPickup(playerid, pickupid)
{
    return 1;
}

public OnVehicleMod(playerid, vehicleid, componentid)
{
    return 1;
}

public OnVehiclePaintjob(playerid, vehicleid, paintjobid)
{
    return 1;
}

public OnVehicleRespray(playerid, vehicleid, color1, color2)
{
    return 1;
}

public OnPlayerSelectedMenuRow(playerid, row)
{
    return 1;
}

public OnPlayerExitedMenu(playerid)
{
    return 1;
}

public OnPlayerInteriorChange(playerid, newinteriorid, oldinteriorid)
{
    return 1;
}

public OnPlayerKeyStateChange(playerid, newkeys, oldkeys)
{
    return 1;
}

public OnRconLoginAttempt(ip[], password[], success)
{
    return 1;
}

public OnPlayerUpdate(playerid)
{
    return 1;
}

public OnPlayerStreamIn(playerid, forplayerid)
{
    return 1;
}

public OnPlayerStreamOut(playerid, forplayerid)
{
    return 1;
}

public OnVehicleStreamIn(vehicleid, forplayerid)
{
    return 1;
}

public OnVehicleStreamOut(vehicleid, forplayerid)
{
    return 1;
}

public OnDialogResponse(playerid, dialogid, response, listitem, inputtext[])
{
    switch(dialogid)
    {
        case DLG_REG_CONFIRM:
        {
            if(response)
            {
                PlayerPlaySound(playerid, 1185, 0.0, 0.0, 0.0); // BIKE_AWARD_TRACK_START
                new tempstring[403+(-2+MAX_PLAYER_NAME)];
                format(tempstring, sizeof(tempstring), "{ffffff}Äîáðî ïîæàëîâàòü, {205CA2} %s{ffffff}nÝòîò àêêàóíò {FF6347}íå çàðåãèñòðèðîâàí{ffffff} íà íàøåì ñåðâåðå.nÄëÿ ðåãèñòðàöèè ââåäèòå ïàðîëü.nÎí áóäåò èñïîëüçîâàòüñÿ äëÿ àâòîðèçàöèè íà íàø¸ì ñåðâåðå.", player_info[playerid][NAME]);
                SPD(playerid, DLG_REG_PASS, DSI, "{E88813}(1/4) Ïàðîëü", tempstring, "Ïðèíÿòü", "Âûõîä");
            }
            else
            {
                Kick(playerid);
            }
        }
        case DLG_REG_PASS:
        {
            if(response)
            {
                if(strlen(inputtext) < 6 || strlen(inputtext) > 30)
                {
                    new tempstring[403+(-2+MAX_PLAYER_NAME)];
                    format(tempstring, sizeof(tempstring), "{ffffff}Äîáðî ïîæàëîâàòü, {205CA2} %snÝòîò àêêàóíò {FF6347}íå çàðåãèñòðèðîâàí{ffffff} íà íàøåì ñåðâåðå.nÄëÿ ðåãèñòðàöèè ââåäèòå ïàðîëü.nÎí áóäåò èñïîëüçîâàòüñÿ äëÿ àâòîðèçàöèè íà íàø¸ì ñåðâåðå.", player_info[playerid][NAME]);
                    SPD(playerid, DLG_REG_PASS, DSI, "{E88813}(1/4) Ïàðîëü", tempstring, "Ïðèíÿòü", "Âûõîä");
                }
                else if(strlen(inputtext) < 6)
                {
                    new tempstring[403+(-2+MAX_PLAYER_NAME)];
                    format(tempstring, sizeof(tempstring), "{ffffff}Äîáðî ïîæàëîâàòü, íà{205CA2} %s{ffffff}nÝòîò àêêàóíò {FF6347}íå çàðåãèñòðèðîâàí{ffffff} íà íàøåì ñåðâåðå.nÄëÿ ðåãèñòðàöèè ââåäèòå ïàðîëü.nÎí áóäåò èñïîëüçîâàòüñÿ äëÿ àâòîðèçàöèè íà íàø¸ì ñåðâåðå.", player_info[playerid][NAME]);
                    SPD(playerid, DLG_REG_PASS, DSI, "{E88813}(1/4) Ïàðîëü", tempstring, "Ïðèíÿòü", "Âûõîä");
                }
                else
                {
                    format(player_info[playerid][PASS], 31, inputtext);
                    SPD(playerid, DLG_REG_GENDER, DSL, "{E88813}[2/4] Âûáåðèòå âàø ïîë", "ÌóæñêîénÆåíñêèé", "Äàëåå", " íà÷àëî");
                }
                return 1;
            }
            else
            {
                Kick(playerid);
            }
        }
        case DLG_REG_GENDER:
        {
            if(response)
            {
                if(listitem == 0)
                {
                    player_info[playerid][SEX] = 1;
                    return SPD(playerid, DLG_REG_COLOR, DSL, "{E88813}[3/4] Âûáåðèòå öâåò êîæè", "ÑâåòëûénÒ¸ìíûé", "Äàëåå", " íà÷àëî");
                }
                if(listitem == 1)
                {
                    player_info[playerid][SEX] = 2;
                      return SPD(playerid, DLG_REG_COLOR, DSL, "{E88813}[3/4] Âûáåðèòå öâåò êîæè", "ÑâåòëûénÒ¸ìíûé", "Äàëåå", " íà÷àëî");
                }
            }
            else
            {
                player_info[playerid][PASS][0] = EOS;
                player_info[playerid][SEX] = 0;
                player_info[playerid][COLOR] = 0;
            }
        }
        case DLG_REG_COLOR:
        {
            if(response)
            {
                if(listitem == 0)
                {
                    player_info[playerid][COLOR] = 1;
                    RegFinish(playerid);
                    return 1;
                }
                if(listitem == 1)
                {
                    player_info[playerid][COLOR] = 2;
                    RegFinish(playerid);
                    return 1;
                }
            }
            else
            {
                  player_info[playerid][PASS][0] = EOS;
                player_info[playerid][SEX] = 0;
                player_info[playerid][COLOR] = 0;
            }
        }
        case DLG_LOGIN:
        {
            if(response)
            {
                if(strcmp(player_info[playerid][PASS], inputtext) != 0)
                {
                    temp_info[playerid][LOGINTRIES] --;
                    if(temp_info[playerid][LOGINTRIES] <= 0) return Kick(playerid);
                    cache_get_value_name(0, "password", player_info[playerid][PASS], 31);
                    new tempstring[403+(-2+MAX_PLAYER_NAME)];
                    format(tempstring, sizeof(tempstring), "{ffffff}Äîáðî ïîæàëîâàòü íà {E88813}Delaware Role Play{FFFFFF}nnÂâåäèòå ñâîé ïàðîëünÏîïûòîê äëÿ ââîäà ïàðîëÿ: {28910B}%i", temp_info[playerid][LOGINTRIES]);
                    SPD(playerid, DLG_LOGIN, DSP, "{E88813}Àâòîðèçàöèÿ", tempstring, "Ïðèíÿòü", "Âûõîä");
                }
                return 1;
            }
            else
            {
                Kick(playerid);
            }
        }
    }
    return 1;
}

forward RegFinish(playerid);
public RegFinish(playerid)
{
    mysql_format(dbHandle, query, sizeof(query),
    "INSERT INTO `accounts` (`name`, `password`, `sex`, `color`) VALUES ('%e', '%e', '%d', '%d')",
    player_info[playerid][NAME], player_info[playerid][PASS], player_info[playerid][SEX], player_info[playerid][COLOR]);
    mysql_tquery(dbHandle, query);
    SCM(playerid, COLOR_VALIK, "[Ïîäñêàçêà] {FFFFFF}Ñïàñèáî âàì çà ðåãèñòðàöèþ íà íàøåì ñåðâåðå");
    SpawnPlayer(playerid);
}

public OnPlayerClickPlayer(playerid, clickedplayerid, source)
{
    return 1;
}

1. [14:50:59] [plugins/mysql] mysql_tquery: callback error: callback «zprod» does not exist

2. //2

3. [20:58:38] [INFO] received Windows console close event; shutting log-core down

4. [20:59:15] [INFO] received Windows console close event; shutting log-core down

5. [21:32:09] [INFO] received Windows console close event; shutting log-core down

6. [21:43:15] [INFO] received Windows console close event; shutting log-core down

7. [22:38:22] [INFO] received Windows console close event; shutting log-core down

8. [23:17:11] [INFO] received Windows console close event; shutting log-core down

9. [23:21:50] [INFO] received Windows console close event; shutting log-core down

10. [23:22:19] [INFO] received Windows console close event; shutting log-core down

11. [21:29:11] [INFO] received Windows console close event; shutting log-core down

12. [21:29:12] [INFO] received Windows console close event; shutting log-core down

13. [21:33:18] [INFO] received Windows console close event; shutting log-core down

14. [21:36:59] [INFO] received Windows console close event; shutting log-core down

15. [21:38:26] [INFO] received Windows console close event; shutting log-core down

16. [21:40:41] [INFO] received Windows console close event; shutting log-core down

17. [23:03:39] [INFO] received Windows console close event; shutting log-core down

18. [23:25:10] [INFO] received Windows console close event; shutting log-core down

19. [23:33:48] [INFO] received Windows console close event; shutting log-core down

20. [23:42:53] [INFO] received Windows console close event; shutting log-core down

21. [00:27:45] [INFO] received Windows console close event; shutting log-core down

22. [00:32:51] [INFO] received Windows console close event; shutting log-core down

23. [00:33:41] [INFO] received Windows console close event; shutting log-core down

24. [00:37:57] [INFO] received Windows console close event; shutting log-core down

25. [22:39:05] [INFO] received Windows console close event; shutting log-core down

26. [22:58:19] [INFO] received Windows console close event; shutting log-core down

27. [23:05:26] [INFO] received Windows console close event; shutting log-core down

28. [23:05:26] [INFO] received Windows console close event; shutting log-core down

29. [23:26:41] [INFO] received Windows console close event; shutting log-core down

30. [23:27:59] [INFO] received Windows console close event; shutting log-core down

31. [23:32:14] [INFO] received Windows console close event; shutting log-core down

32. [23:36:19] [INFO] received Windows console close event; shutting log-core down

33. [00:09:59] [INFO] received Windows console close event; shutting log-core down

34. [00:13:46] [INFO] received Windows console close event; shutting log-core down

35. [15:21:28] [INFO] received Windows console close event; shutting log-core down

36. [15:22:14] [INFO] received Windows console close event; shutting log-core down

37. [15:27:32] [INFO] received Windows console close event; shutting log-core down

38. [15:30:49] [INFO] received Windows console close event; shutting log-core down

39. [15:34:04] [INFO] received Windows console close event; shutting log-core down

40. [15:38:20] [INFO] received Windows console close event; shutting log-core down

41. [15:43:05] [INFO] received Windows console close event; shutting log-core down

42. [15:50:30] [INFO] received Windows console close event; shutting log-core down

43. [16:00:03] [INFO] received Windows console close event; shutting log-core down

44. [16:26:53] [INFO] received Windows console close event; shutting log-core down

45. [16:27:12] [INFO] received Windows console close event; shutting log-core down

46. [16:27:30] [INFO] received Windows console close event; shutting log-core down

47. [16:39:51] [INFO] received Windows console close event; shutting log-core down

48. [16:48:09] [INFO] received Windows console close event; shutting log-core down

49. [23:24:28] [INFO] received Windows console close event; shutting log-core down

50. [23:34:23] [INFO] received Windows console close event; shutting log-core down

51. [23:44:49] [INFO] received Windows console close event; shutting log-core down

52. [23:53:02] [INFO] received Windows console close event; shutting log-core down

53. [23:53:02] [INFO] received Windows console close event; shutting log-core down

54. [23:56:05] [INFO] received Windows console close event; shutting log-core down

55. [23:58:27] [INFO] received Windows console close event; shutting log-core down

56. [00:06:04] [INFO] received Windows console close event; shutting log-core down

57. [23:47:21] [INFO] received Windows console close event; shutting log-core down

58. [23:49:55] [INFO] received Windows console close event; shutting log-core down

59. [00:09:34] [INFO] received Windows console close event; shutting log-core down

60. [00:12:40] [INFO] received Windows console close event; shutting log-core down

61. [00:13:01] [INFO] received Windows console close event; shutting log-core down

62. [00:14:33] [INFO] received Windows console close event; shutting log-core down

63. [01:16:55] [INFO] received Windows console close event; shutting log-core down

64. [01:29:31] [INFO] received Windows console close event; shutting log-core down

65. [01:48:09] [INFO] received Windows console close event; shutting log-core down

66. [01:52:12] [INFO] received Windows console close event; shutting log-core down

67. [02:33:05] [INFO] received Windows console close event; shutting log-core down

68. [13:17:03] [INFO] received Windows console close event; shutting log-core down

69. [13:23:28] [INFO] received Windows console close event; shutting log-core down

70. [13:30:43] [INFO] received Windows console close event; shutting log-core down

71. [14:33:29] [INFO] received Windows console close event; shutting log-core down

72. [14:45:30] [INFO] received Windows console close event; shutting log-core down

73. [14:57:00] [INFO] received Windows console close event; shutting log-core down

74. [14:58:45] [INFO] received Windows console close event; shutting log-core down

75. [15:06:19] [INFO] received Windows console close event; shutting log-core down

76. [15:32:42] [INFO] received Windows console close event; shutting log-core down

77. [15:34:03] [INFO] received Windows console close event; shutting log-core down

78. [17:11:02] [INFO] received Windows console close event; shutting log-core down

79. [17:14:33] [INFO] received Windows console close event; shutting log-core down

80. [17:20:19] [INFO] received Windows console close event; shutting log-core down

81. [17:20:19] [INFO] received Windows console close event; shutting log-core down

82. [17:22:05] [INFO] received Windows console close event; shutting log-core down

83. [17:23:44] [INFO] received Windows console close event; shutting log-core down

84. [17:59:11] [INFO] received Windows console close event; shutting log-core down

85. [18:15:47] [INFO] received Windows console close event; shutting log-core down

86. [18:22:22] [INFO] received Windows console close event; shutting log-core down

87. [00:06:22] [INFO] received Windows console close event; shutting log-core down

88. [00:53:58] [INFO] received Windows console close event; shutting log-core down

89. [01:10:25] [INFO] received Windows console close event; shutting log-core down

90. [19:27:12] [INFO] received Windows console close event; shutting log-core down

91. [21:01:53] [INFO] received Windows console close event; shutting log-core down

92. [21:05:31] [INFO] received Windows console close event; shutting log-core down

93. [21:10:54] [INFO] received Windows console close event; shutting log-core down

94. [22:04:47] [INFO] received Windows console close event; shutting log-core down

95. [22:06:48] [INFO] received Windows console close event; shutting log-core down

96. [22:13:29] [INFO] received Windows console close event; shutting log-core down

97. [22:24:40] [INFO] received Windows console close event; shutting log-core down

98. [22:25:56] [INFO] received Windows console close event; shutting log-core down

99. [00:54:34] [INFO] received Windows console close event; shutting log-core down

100. [01:05:33] [INFO] received Windows console close event; shutting log-core down

101. [01:31:14] [INFO] received Windows console close event; shutting log-core down

102. [15:28:34] [INFO] received Windows console close event; shutting log-core down

103. [15:55:20] [INFO] received Windows console close event; shutting log-core down

104. [16:58:56] [INFO] received Windows console close event; shutting log-core down

105. [19:18:41] [INFO] received Windows console close event; shutting log-core down

106. [19:53:14] [INFO] received Windows console close event; shutting log-core down

107. [20:15:34] [INFO] received Windows console close event; shutting log-core down

108. [20:34:07] [INFO] received Windows console close event; shutting log-core down

109. [20:55:29] [INFO] received Windows console close event; shutting log-core down

110. [01:04:06] [INFO] received Windows console close event; shutting log-core down

111. [17:16:43] [INFO] received Windows console close event; shutting log-core down

112. [17:18:52] [INFO] received Windows console close event; shutting log-core down

113. [23:26:56] [INFO] received Windows console close event; shutting log-core down

114. [19:25:52] [INFO] received Windows console close event; shutting log-core down

115. [20:05:46] [INFO] received Windows console close event; shutting log-core down

116. [18:49:16] [INFO] received Windows console close event; shutting log-core down

117. [18:57:42] [INFO] received Windows console close event; shutting log-core down

118. [21:01:09] [INFO] received Windows console close event; shutting log-core down

119. [21:01:24] [INFO] received Windows console close event; shutting log-core down

120. [21:01:26] [INFO] received Windows console close event; shutting log-core down

121. [21:01:26] [INFO] received Windows console close event; shutting log-core down

122. [21:36:01] [INFO] received Windows console close event; shutting log-core down

123. [21:43:58] [INFO] received Windows console close event; shutting log-core down

124. [21:48:00] [INFO] received Windows console close event; shutting log-core down

125. [00:56:11] [INFO] received Windows console close event; shutting log-core down

126. [01:00:13] [INFO] received Windows console close event; shutting log-core down

127. [02:31:22] [INFO] received Windows console close event; shutting log-core down

128. [02:34:17] [INFO] received Windows console close event; shutting log-core down

129. [02:53:32] [INFO] received Windows console close event; shutting log-core down

130. [02:53:32] [INFO] received Windows console close event; shutting log-core down

131. [02:55:13] [INFO] received Windows console close event; shutting log-core down

132. [03:01:01] [INFO] received Windows console close event; shutting log-core down

133. [03:03:24] [INFO] received Windows console close event; shutting log-core down

134. [03:04:30] [INFO] received Windows console close event; shutting log-core down

135. [22:07:25] [INFO] received Windows console close event; shutting log-core down

136. [22:33:51] [INFO] received Windows console close event; shutting log-core down

137. [22:56:27] [INFO] received Windows console close event; shutting log-core down

138. [23:02:30] [INFO] received Windows console close event; shutting log-core down

139. [23:28:16] [INFO] received Windows console close event; shutting log-core down

140. [15:04:32] [INFO] received Windows console close event; shutting log-core down

141. [15:06:58] [INFO] received Windows console close event; shutting log-core down

142. [15:09:22] [INFO] received Windows console close event; shutting log-core down

143. [15:11:13] [INFO] received Windows console close event; shutting log-core down

144. [15:13:34] [INFO] received Windows console close event; shutting log-core down

145. [15:19:08] [INFO] received Windows console close event; shutting log-core down

146. [15:35:29] [INFO] received Windows console close event; shutting log-core down

147. [15:38:27] [INFO] received Windows console close event; shutting log-core down

148. [15:40:36] [INFO] received Windows console close event; shutting log-core down

149. [15:41:58] [INFO] received Windows console close event; shutting log-core down

150. [15:46:19] [INFO] received Windows console close event; shutting log-core down

151. [15:47:37] [INFO] received Windows console close event; shutting log-core down

152. [15:49:54] [INFO] received Windows console close event; shutting log-core down

153. [16:37:02] [INFO] received Windows console close event; shutting log-core down

154. [17:00:54] [INFO] received Windows console close event; shutting log-core down

155. [17:03:36] [INFO] received Windows console close event; shutting log-core down

156. [17:17:45] [INFO] received Windows console close event; shutting log-core down

157. [17:22:29] [INFO] received Windows console close event; shutting log-core down

158. [17:24:53] [INFO] received Windows console close event; shutting log-core down

159. [17:35:28] [INFO] received Windows console close event; shutting log-core down

160. [17:37:41] [INFO] received Windows console close event; shutting log-core down

161. [17:38:26] [INFO] received Windows console close event; shutting log-core down

162. [17:46:11] [INFO] received Windows console close event; shutting log-core down

163. [17:47:29] [INFO] received Windows console close event; shutting log-core down

164. [17:49:57] [INFO] received Windows console close event; shutting log-core down

165. [17:52:33] [INFO] received Windows console close event; shutting log-core down

166. [17:52:35] [INFO] received Windows console close event; shutting log-core down

167. [18:02:06] [INFO] received Windows console close event; shutting log-core down

168. [19:04:03] [INFO] received Windows console close event; shutting log-core down

169. [19:08:04] [INFO] received Windows console close event; shutting log-core down

170. [20:53:08] [INFO] received Windows console close event; shutting log-core down

171. [20:58:00] [INFO] received Windows console close event; shutting log-core down

172. [20:58:53] [INFO] received Windows console close event; shutting log-core down

173. [21:10:19] [INFO] received Windows console close event; shutting log-core down

174. [21:13:02] [INFO] received Windows console close event; shutting log-core down

175. [21:17:09] [INFO] received Windows console close event; shutting log-core down

176. [21:21:25] [INFO] received Windows console close event; shutting log-core down

177. [21:23:50] [INFO] received Windows console close event; shutting log-core down

178. [21:28:34] [INFO] received Windows console close event; shutting log-core down

179. [21:34:45] [INFO] received Windows console close event; shutting log-core down

180. [21:34:46] [INFO] received Windows console close event; shutting log-core down

181. [21:41:12] [INFO] received Windows console close event; shutting log-core down

182. [22:12:01] [INFO] received Windows console close event; shutting log-core down

183. [22:13:06] [INFO] received Windows console close event; shutting log-core down

184. [22:13:53] [INFO] received Windows console close event; shutting log-core down

185. [22:14:47] [INFO] received Windows console close event; shutting log-core down

186. [22:18:51] [INFO] received Windows console close event; shutting log-core down

187. [22:23:12] [INFO] received Windows console close event; shutting log-core down

188. [22:28:48] [INFO] received Windows console close event; shutting log-core down

189. [22:32:59] [INFO] received Windows console close event; shutting log-core down

190. [14:58:37] [INFO] received Windows console close event; shutting log-core down

191. [14:59:11] [INFO] received Windows console close event; shutting log-core down

192. [15:03:43] [INFO] received Windows console close event; shutting log-core down

193. [15:34:57] [INFO] received Windows console close event; shutting log-core down

194. [17:35:50] [INFO] received Windows console close event; shutting log-core down

195. [17:36:29] [INFO] received Windows console close event; shutting log-core down

196. [17:37:11] [INFO] received Windows console close event; shutting log-core down

197. [17:41:25] [INFO] received Windows console close event; shutting log-core down

198. [17:41:25] [INFO] received Windows console close event; shutting log-core down

199. [17:55:34] [INFO] received Windows console close event; shutting log-core down

200. [18:05:26] [INFO] received Windows console close event; shutting log-core down

201. [19:03:26] [INFO] received Windows console close event; shutting log-core down

202. [19:09:24] [INFO] received Windows console close event; shutting log-core down

203. [19:10:36] [INFO] received Windows console close event; shutting log-core down

204. [19:13:35] [INFO] received Windows console close event; shutting log-core down

205. [19:16:42] [INFO] received Windows console close event; shutting log-core down

206. [19:18:11] [INFO] received Windows console close event; shutting log-core down

207. [19:21:20] [INFO] received Windows console close event; shutting log-core down

208. [19:24:19] [INFO] received Windows console close event; shutting log-core down

209. [19:34:22] [INFO] received Windows console close event; shutting log-core down

210. [19:38:02] [INFO] received Windows console close event; shutting log-core down

211. [19:41:16] [INFO] received Windows console close event; shutting log-core down

212. [20:00:17] [INFO] received Windows console close event; shutting log-core down

213. [14:31:46] [INFO] received Windows console close event; shutting log-core down

214. [14:33:09] [INFO] received Windows console close event; shutting log-core down

215. [14:44:48] [INFO] received Windows console close event; shutting log-core down

216. [15:18:39] [INFO] received Windows console close event; shutting log-core down

217. [11:14:24] [INFO] received Windows console close event; shutting log-core down

218. [11:24:04] [INFO] received Windows console close event; shutting log-core down

219. [11:25:46] [INFO] received Windows console close event; shutting log-core down

220. [11:27:17] [INFO] received Windows console close event; shutting log-core down

221. [11:31:06] [INFO] received Windows console close event; shutting log-core down

222. [11:41:13] [INFO] received Windows console close event; shutting log-core down

223. [13:40:08] [INFO] received Windows console close event; shutting log-core down

224. [13:55:08] [INFO] received Windows console close event; shutting log-core down

225. [13:58:11] [INFO] received Windows console close event; shutting log-core down

226. [14:04:56] [INFO] received Windows console close event; shutting log-core down

227. [14:57:11] [INFO] received Windows console close event; shutting log-core down

228. [15:02:11] [INFO] received Windows console close event; shutting log-core down

229. [15:09:42] [INFO] received Windows console close event; shutting log-core down

230. [15:10:48] [INFO] received Windows console close event; shutting log-core down

231. [15:24:24] [INFO] received Windows console close event; shutting log-core down

232. [15:29:35] [INFO] received Windows console close event; shutting log-core down

233. [15:30:34] [INFO] received Windows console close event; shutting log-core down

234. [15:32:24] [INFO] received Windows console close event; shutting log-core down

235. [15:39:01] [INFO] received Windows console close event; shutting log-core down

236. [15:44:06] [INFO] received Windows console close event; shutting log-core down

237. [16:12:43] [INFO] received Windows console close event; shutting log-core down

238. [16:25:35] [INFO] received Windows console close event; shutting log-core down

239. [16:26:54] [INFO] received Windows console close event; shutting log-core down

240. [16:27:49] [INFO] received Windows console close event; shutting log-core down

241. [10:44:30] [INFO] received Windows console close event; shutting log-core down

242. [10:53:16] [INFO] received Windows console close event; shutting log-core down

243. [10:55:11] [INFO] received Windows console close event; shutting log-core down

244. [11:04:40] [INFO] received Windows console close event; shutting log-core down

245. [11:06:39] [INFO] received Windows console close event; shutting log-core down

246. [14:53:42] [INFO] received Windows console close event; shutting log-core down

247. //3

248. [14:50:55] [plugins/mysql] mysql_connect: no password specified