helmi/infoscreen
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
cccaa274f8f7e7aa9a57fa1d14a5aa5b224f79db
infoscreen/python/ystemctl status mariadb.service
root (ariane) cccaa274f8 init commit
2025-10-10 20:31:12 +02:00

3855 lines
218 KiB
Desktop File
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
-- Logs begin at Sat 2021-12-11 12:16:24 CET, end at Sat 2021-12-11 12:23:59 CET. --
Dec 11 12:16:26 proteus postfix/smtp[439]: 34BB31C01D: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=26485, delays=26483/1.2/0.06/0.24, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7749B797EE97)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 34BB31C01D: removed
Dec 11 12:16:26 proteus postfix/smtp[416]: 337631C019: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=35485, delays=35484/1.1/0.05/0.3, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 76794797EE90)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 337631C019: removed
Dec 11 12:16:26 proteus postfix/smtp[417]: 3E13D1BBFE: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=25885, delays=25884/1.2/0.05/0.21, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7CE6A7C09471)
Dec 11 12:16:26 proteus postfix/smtp[454]: 39B091BDDF: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=14785, delays=14784/1.2/0.06/0.21, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7C9B47B8B5A1)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 39B091BDDF: removed
Dec 11 12:16:26 proteus postfix/smtp[448]: 3C36C1BFA4: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=11486, delays=11484/1.2/0.05/0.21, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7FD7F7C2D3E0)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 3E13D1BBFE: removed
Dec 11 12:16:26 proteus postfix/qmgr[408]: 3C36C1BFA4: removed
Dec 11 12:16:26 proteus postfix/smtp[453]: 3B6C61BD59: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=39385, delays=39384/1.2/0.05/0.22, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7B4B6797EEBA)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 3B6C61BD59: removed
Dec 11 12:16:26 proteus postfix/smtp[444]: 368C21BBFD: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=515, delays=513/1.2/0.06/0.27, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 76F2A797EE96)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 368C21BBFD: removed
Dec 11 12:16:26 proteus postfix/smtp[445]: 370121C01E: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=3085, delays=3084/1.2/0.06/0.27, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 775FD797EE98)
Dec 11 12:16:26 proteus postfix/smtp[446]: 3DC4E1BFA9: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=30085, delays=30083/1.2/0.05/0.22, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7B52A7B8720F)
Dec 11 12:16:26 proteus postfix/smtp[450]: 325971BAA8: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=7885, delays=7883/1.1/0.06/0.34, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 765A9797EE88)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 370121C01E: removed
Dec 11 12:16:26 proteus postfix/smtp[451]: 315A71BD53: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=33385, delays=33384/1.1/0.06/0.34, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 764B0797EE85)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 3DC4E1BFA9: removed
Dec 11 12:16:26 proteus postfix/smtp[441]: 347AB1C01C: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=38185, delays=38183/1.2/0.06/0.29, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 769E6797EE91)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 325971BAA8: removed
Dec 11 12:16:26 proteus postfix/smtp[452]: 35CB81BBFB: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=170, delays=169/1.2/0.05/0.28, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 76CC9797EE95)
Dec 11 12:16:26 proteus postfix/smtp[442]: 31EED1C018: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=21085, delays=21084/1.1/0.06/0.34, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7663C797EE8A)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 315A71BD53: removed
Dec 11 12:16:26 proteus postfix/qmgr[408]: 347AB1C01C: removed
Dec 11 12:16:26 proteus postfix/smtp[435]: 3A6181BDE1: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=385, delays=384/1.2/0.06/0.22, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7CA297BD72B5)
Dec 11 12:16:26 proteus postfix/smtp[413]: 378D11C020: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=26785, delays=26783/1.2/0.05/0.25, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 77765797EEB1)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 35CB81BBFB: removed
Dec 11 12:16:26 proteus postfix/smtp[419]: 393AB1BDDE: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=18886, delays=18884/1.2/0.05/0.22, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 7AEB5797EEB5)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 31EED1C018: removed
Dec 11 12:16:26 proteus postfix/qmgr[408]: 3A6181BDE1: removed
Dec 11 12:16:26 proteus postfix/smtp[418]: 40B491BAAD: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=30630, delays=30628/1.4/0.05/0.05, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as A3E9F7C2D3E3)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 378D11C020: removed
Dec 11 12:16:26 proteus postfix/qmgr[408]: 393AB1BDDE: removed
Dec 11 12:16:26 proteus postfix/qmgr[408]: 40B491BAAD: removed
Dec 11 12:16:26 proteus postfix/smtp[440]: 403751C02C: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=29485, delays=29483/1.3/0.05/0.11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 9D7F57C2D3E2)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 403751C02C: removed
Dec 11 12:16:26 proteus postfix/smtp[449]: 4139F1BAAF: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=18985, delays=18984/1.4/0.05/0.07, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as AC9347C2D3E4)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 4139F1BAAF: removed
Dec 11 12:16:26 proteus postfix/smtp[439]: 41AE91BFAB: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=11785, delays=11783/1.4/0.05/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B57297C2D3E5)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 41AE91BFAB: removed
Dec 11 12:16:26 proteus postfix/smtp[417]: 42E421BDE4: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=26186, delays=26184/1.4/0.06/0.16, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BF0917C2D3E6)
Dec 11 12:16:26 proteus postfix/smtp[448]: 433541BDE5: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=40285, delays=40283/1.4/0.06/0.16, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BED9D5BEF58D)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 42E421BDE4: removed
Dec 11 12:16:26 proteus postfix/smtp[453]: 438F51BDE6: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=30986, delays=30984/1.4/0.06/0.16, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BF01D5BEF58E)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 433541BDE5: removed
Dec 11 12:16:26 proteus postfix/qmgr[408]: 438F51BDE6: removed
Dec 11 12:16:26 proteus postfix/smtp[451]: 482391BD5D: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=85, delays=84/1.4/0.06/0.19, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C2CF47C2D3E8)
Dec 11 12:16:26 proteus postfix/qmgr[408]: 482391BD5D: removed
Dec 11 12:16:27 proteus postfix/smtp[454]: 428961BDE3: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=25285, delays=25284/1.4/0.07/0.24, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C2F607C2D3EA)
Dec 11 12:16:27 proteus postfix/smtp[445]: 459EF1C091: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=32185, delays=32183/1.4/0.06/0.24, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C25156C86E7C)
Dec 11 12:16:27 proteus postfix/smtp[446]: 478BC1BD5B: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=31885, delays=31883/1.4/0.06/0.24, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C1D2F409FA4F)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 428961BDE3: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 478BC1BD5B: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 459EF1C091: removed
Dec 11 12:16:27 proteus postfix/smtp[439]: 4ED6B1BDF5: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=36085, delays=36083/1.5/0.06/0.22, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E0CA67C2D3F9)
Dec 11 12:16:27 proteus postfix/smtp[452]: 4B2311BDF0: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=36385, delays=36383/1.4/0.07/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E0A2F7C2D3F4)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4ED6B1BDF5: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4B2311BDF0: removed
Dec 11 12:16:27 proteus postfix/smtp[418]: 4D0EA1BFAF: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=29785, delays=29783/1.4/0.07/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E09B87C2D3F3)
Dec 11 12:16:27 proteus postfix/smtp[416]: 424551BDE2: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=41786, delays=41784/1.4/0.08/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E08967C2D3F1)
Dec 11 12:16:27 proteus postfix/smtp[435]: 4C20B1C102: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=260, delays=258/1.4/0.08/0.31, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E0B237C2D3F6)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4D0EA1BFAF: removed
Dec 11 12:16:27 proteus postfix/smtp[449]: 4E44E1BAB1: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=17486, delays=17484/1.5/0.06/0.29, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E0C2E7C2D3F8)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 424551BDE2: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4C20B1C102: removed
Dec 11 12:16:27 proteus postfix/smtp[419]: 4C7731C093: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=3985, delays=3983/1.4/0.07/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E06EA7C2D3EF)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4E44E1BAB1: removed
Dec 11 12:16:27 proteus postfix/smtp[413]: 4BD8D1BDF2: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=31286, delays=31284/1.4/0.07/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E093B7C2D3F2)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4C7731C093: removed
Dec 11 12:16:27 proteus postfix/smtp[441]: 4881F1BD5E: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=1885, delays=1884/1.4/0.07/0.33, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E057A7C2D3ED)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4BD8D1BDF2: removed
Dec 11 12:16:27 proteus postfix/smtp[442]: 4ACE31BDEF: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=38785, delays=38784/1.4/0.07/0.33, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E06227C2D3EE)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4881F1BD5E: removed
Dec 11 12:16:27 proteus postfix/smtp[444]: 450BA1C08F: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=22285, delays=22283/1.4/0.07/0.33, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E044A7C2D3EB)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4ACE31BDEF: removed
Dec 11 12:16:27 proteus postfix/smtp[450]: 47D9F1BD5C: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=35186, delays=35184/1.4/0.08/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E0AAA7C2D3F5)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 450BA1C08F: removed
Dec 11 12:16:27 proteus postfix/smtp[448]: 4F8621BA7D: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=38485, delays=38483/1.6/0.06/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 0295B7C2D3FB)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 47D9F1BD5C: removed
Dec 11 12:16:27 proteus postfix/smtp[440]: 4E0631BD67: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=15086, delays=15084/1.4/0.05/0.32, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E0BA27C2D3F7)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4F8621BA7D: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4E0631BD67: removed
Dec 11 12:16:27 proteus postfix/smtp[417]: 4F2561BDF6: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=37886, delays=37884/1.6/0.06/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 049DB7C2D3FD)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 4F2561BDF6: removed
Dec 11 12:16:27 proteus postfix/smtp[451]: 513291C096: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=13885, delays=13883/1.6/0.05/0.11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 071817C2D3FE)
Dec 11 12:16:27 proteus postfix/smtp[453]: 50BA41C105: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=9386, delays=9384/1.6/0.06/0.13, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 0331D7C2D3FC)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 513291C096: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 50BA41C105: removed
Dec 11 12:16:27 proteus postfix/smtp[454]: 518881C097: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=20185, delays=20183/1.7/0.05/0.11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 13C177C2D3FF)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 518881C097: removed
Dec 11 12:16:27 proteus postfix/smtp[445]: 531731BDF8: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=258, delays=256/1.7/0.05/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 14CD27C2D404)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 531731BDF8: removed
Dec 11 12:16:27 proteus postfix/smtp[446]: 52C051C09B: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=16886, delays=16884/1.7/0.05/0.15, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 1433D7C2D401)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 52C051C09B: removed
Dec 11 12:16:27 proteus postfix/smtp[452]: 53B3F1BD68: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=24986, delays=24984/1.8/0.07/0.2, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2D6E25BEF590)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 53B3F1BD68: removed
Dec 11 12:16:27 proteus postfix/smtp[416]: 545A81BD6A: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=44485, delays=44483/1.8/0.07/0.3, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2F2987C2D40C)
Dec 11 12:16:27 proteus postfix/smtp[418]: 53FE51BD69: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=35785, delays=35783/1.8/0.06/0.31, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2D5375BEF58F)
Dec 11 12:16:27 proteus postfix/smtp[413]: 58BF71BAB9: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=18386, delays=18383/1.8/0.07/0.31, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2EE736C86E7F)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 545A81BD6A: removed
Dec 11 12:16:27 proteus postfix/smtp[439]: 536B21BDF9: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=18792, delays=18790/1.8/0.07/0.31, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2EEED7C2D406)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 53FE51BD69: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 58BF71BAB9: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 536B21BDF9: removed
Dec 11 12:16:27 proteus postfix/smtp[449]: 56AF01C107: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=46286, delays=46284/1.8/0.07/0.38, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2F0C07C2D409)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 56AF01C107: removed
Dec 11 12:16:27 proteus postfix/smtp[440]: 5DDC91BAC5: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=30686, delays=30684/1.7/0.08/0.44, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4B3EB7C2D41D)
Dec 11 12:16:27 proteus postfix/smtp[444]: 5B39C1BABF: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=13586, delays=13584/1.7/0.07/0.45, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4A45C7C2D411)
Dec 11 12:16:27 proteus postfix/smtp[448]: 5D6321BAC4: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=12086, delays=12083/1.7/0.06/0.45, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 49EF67C2D40D)
Dec 11 12:16:27 proteus postfix/smtp[451]: 5F7151BD70: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=12686, delays=12684/1.7/0.06/0.45, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4A67A7C2D412)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5DDC91BAC5: removed
Dec 11 12:16:27 proteus postfix/smtp[419]: 57F0B1BAB7: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=42386, delays=42383/1.8/0.07/0.45, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4A3787C2D410)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5B39C1BABF: removed
Dec 11 12:16:27 proteus postfix/smtp[442]: 5A6F41BABD: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=15386, delays=15384/1.8/0.07/0.45, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4AF877C2D416)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5D6321BAC4: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5F7151BD70: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 57F0B1BAB7: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5A6F41BABD: removed
Dec 11 12:16:27 proteus postfix/smtp[454]: 61C991C10E: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=8786, delays=8784/1.8/0.07/0.43, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4B6C67C2D41F)
Dec 11 12:16:27 proteus postfix/smtp[453]: 6054D1C10D: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=20786, delays=20784/1.7/0.06/0.5, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4B2637C2D41B)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 61C991C10E: removed
Dec 11 12:16:27 proteus postfix/smtp[441]: 59FD41BABC: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=9686, delays=9683/1.8/0.07/0.5, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4A2E37C2D40E)
Dec 11 12:16:27 proteus postfix/smtp[450]: 5C9DE1BAC2: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=39686, delays=39684/1.7/0.07/0.5, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4B0D07C2D41A)
Dec 11 12:16:27 proteus postfix/smtp[445]: 622201C10F: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=1286, delays=1283/1.8/0.06/0.41, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4C8857C70A03)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 6054D1C10D: removed
Dec 11 12:16:27 proteus postfix/smtp[417]: 5E8311BAC7: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=25586, delays=25584/1.7/0.06/0.5, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4AE287C2D415)
Dec 11 12:16:27 proteus postfix/smtp[435]: 55E1C1BDFA: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=27386, delays=27383/1.8/0.08/0.5, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4AD937C2D413)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 59FD41BABC: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5C9DE1BAC2: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 622201C10F: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 5E8311BAC7: removed
Dec 11 12:16:27 proteus postfix/qmgr[408]: 55E1C1BDFA: removed
Dec 11 12:16:27 proteus postfix/smtp[473]: 615641C186: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=14486, delays=14484/1.8/0.07/0.54, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 4B5537C2D41E)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 615641C186: removed
Dec 11 12:16:27 proteus postfix/smtp[413]: 65CC81BD74: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=771, delays=769/2.1/0.05/0.4, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 863AB7C8DFE5)
Dec 11 12:16:27 proteus postfix/qmgr[408]: 65CC81BD74: removed
Dec 11 12:16:28 proteus postfix/smtp[452]: 6317A1C112: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=24386, delays=24383/2.1/0.06/0.47, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 877FE7C8DFFA)
Dec 11 12:16:28 proteus postfix/smtp[418]: 6513D1BD73: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=987, delays=984/2.1/0.05/0.47, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 862187C86CDE)
Dec 11 12:16:28 proteus postfix/smtp[416]: 636391C034: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=43887, delays=43884/2.1/0.06/0.47, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 8768E7C8DFF4)
Dec 11 12:16:28 proteus postfix/smtp[439]: 663671BFB5: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=42087, delays=42084/2.2/0.05/0.4, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 97A957C99902)
Dec 11 12:16:28 proteus postfix/smtp[446]: 627E91C110: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=7287, delays=7284/2/0.06/0.57, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 78B247C79683)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 6513D1BD73: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 6317A1C112: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 663671BFB5: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 636391C034: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 627E91C110: removed
Dec 11 12:16:28 proteus postfix/smtp[448]: 6E9661BDFE: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=39987, delays=39984/2.2/0.05/0.48, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as AB10E7C9E3D5)
Dec 11 12:16:28 proteus postfix/smtp[444]: 6B2581BFB7: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=34286, delays=34284/2.2/0.05/0.48, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as A98017C9BE7F)
Dec 11 12:16:28 proteus postfix/smtp[440]: 6BCE71C03A: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=28887, delays=28884/2.2/0.05/0.48, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as AB69B7CA51FB)
Dec 11 12:16:28 proteus postfix/smtp[451]: 709921C18A: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=30387, delays=30384/2.2/0.05/0.48, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as AB3EA7C9F3B6)
Dec 11 12:16:28 proteus postfix/smtp[450]: 7FC131BACC: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=27986, delays=27984/2.2/0.07/0.41, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BA3527CA7781)
Dec 11 12:16:28 proteus postfix/smtp[442]: 71A331C115: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=28587, delays=28584/2.2/0.05/0.48, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as AB35A7C9F3A2)
Dec 11 12:16:28 proteus postfix/smtp[453]: 7BFCF1BD7B: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=2487, delays=2484/2.2/0.07/0.41, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BAE147CA914E)
Dec 11 12:16:28 proteus postfix/smtp[419]: 760481BD78: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=10587, delays=10584/2.2/0.07/0.41, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BA18F5BEF591)
Dec 11 12:16:28 proteus postfix/smtp[449]: 677391C038: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=21987, delays=21984/2.2/0.05/0.48, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as AB87A7CA5201)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 6BCE71C03A: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 6B2581BFB7: removed
Dec 11 12:16:28 proteus postfix/smtp[417]: 865091BFBC: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=495, delays=492/2.1/0.08/0.4, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BCD7D7CB88D1)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 6E9661BDFE: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 709921C18A: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 7FC131BACC: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 7BFCF1BD7B: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 71A331C115: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 760481BD78: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 677391C038: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 865091BFBC: removed
Dec 11 12:16:28 proteus postfix/smtp[441]: 855FC1C18C: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=18086, delays=18083/2.1/0.08/0.63, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BBE1D7CAABAE)
Dec 11 12:16:28 proteus postfix/smtp[454]: 7A1F61BFB9: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=43587, delays=43584/2.2/0.07/0.64, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BA2427CA521F)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 855FC1C18C: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 7A1F61BFB9: removed
Dec 11 12:16:28 proteus postfix/smtp[445]: 829371C18B: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=12387, delays=12384/2.2/0.07/0.63, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as BBCEF7CAABA4)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 829371C18B: removed
Dec 11 12:16:28 proteus postfix/smtp[435]: 8B9B11C040: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=23187, delays=23184/2.2/0.07/0.61, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as E64D67CBCC62)
Dec 11 12:16:28 proteus postfix/smtp[473]: 8DCB81BFBD: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=401, delays=398/2.4/0.06/0.46, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 009977CBCC76)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 8B9B11C040: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 8DCB81BFBD: removed
Dec 11 12:16:28 proteus postfix/smtp[439]: 91CCD1C207: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=28287, delays=28284/2.4/0.05/0.45, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 121827CBF8AB)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 91CCD1C207: removed
Dec 11 12:16:28 proteus postfix/smtp[446]: 904B81C282: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=516, delays=513/2.4/0.06/0.54, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 12F707CBF8B9)
Dec 11 12:16:28 proteus postfix/smtp[452]: 8F4831C18D: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=33087, delays=33084/2.4/0.05/0.54, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 123477CBF8B6)
Dec 11 12:16:28 proteus postfix/smtp[413]: 8E7A21C0A6: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=12987, delays=12984/2.4/0.06/0.54, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 132907CC0C60)
Dec 11 12:16:28 proteus postfix/smtp[418]: 8FB461C044: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=13287, delays=13284/2.4/0.06/0.54, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 131457CBF8BE)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 904B81C282: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 8F4831C18D: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 8E7A21C0A6: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 8FB461C044: removed
Dec 11 12:16:28 proteus postfix/smtp[416]: 927EC1C285: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=19887, delays=19884/2.6/0.05/0.47, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3A08D7CC4DAD)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 927EC1C285: removed
Dec 11 12:16:28 proteus postfix/smtp[449]: 96E951C291: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=27687, delays=27684/2.6/0.06/0.56, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3C1067CCB2DB)
Dec 11 12:16:28 proteus postfix/smtp[450]: 939441C288: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=1587, delays=1584/2.6/0.06/0.56, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3B5797CC4DBE)
Dec 11 12:16:28 proteus postfix/smtp[448]: 968A71C290: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=23487, delays=23484/2.6/0.06/0.56, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3B74C7CC8081)
Dec 11 12:16:28 proteus postfix/smtp[417]: 942AF1C28A: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=23787, delays=23784/2.6/0.06/0.56, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3BC947CC8091)
Dec 11 12:16:28 proteus postfix/smtp[442]: 948541C28B: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=517, delays=514/2.6/0.05/0.57, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 39DD47CC4DA6)
Dec 11 12:16:28 proteus postfix/smtp[440]: 92F641C286: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=4587, delays=4584/2.6/0.05/0.57, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 396F57CC4D94)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 939441C288: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 96E951C291: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 968A71C290: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 942AF1C28A: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 948541C28B: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 92F641C286: removed
Dec 11 12:16:28 proteus postfix/smtp[451]: 961F91C28F: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=173, delays=170/2.6/0.06/0.67, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 715C77CDA03E)
Dec 11 12:16:28 proteus postfix/smtp[444]: 934661C287: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=34887, delays=34884/2.6/0.06/0.67, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 72E1A7CE87BC)
Dec 11 12:16:28 proteus postfix/smtp[453]: 93D6E1C289: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=10287, delays=10284/2.6/0.06/0.67, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 72BD57CE87B9)
Dec 11 12:16:28 proteus postfix/smtp[419]: 974261C0A9: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=45387, delays=45384/2.8/0.06/0.46, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 72F9B7CEAECD)
Dec 11 12:16:28 proteus postfix/qmgr[408]: 961F91C28F: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 934661C287: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 93D6E1C289: removed
Dec 11 12:16:28 proteus postfix/qmgr[408]: 974261C0A9: removed
Dec 11 12:16:29 proteus postfix/pickup[407]: 2FC361C0AA: uid=33 from=<www-data>
Dec 11 12:16:29 proteus postfix/cleanup[443]: 2FC361C0AA: message-id=<BYZceHw-lpEAY-AAAAAAAAAAAAAAAAP255eL82-@osTicketMailer>
Dec 11 12:16:29 proteus postfix/qmgr[408]: 2FC361C0AA: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=732, nrcpt=1 (queue active)
Dec 11 12:16:29 proteus postfix/smtp[441]: 2FC361C0AA: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=0.64, delays=0/0/0.05/0.58, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 3EF6C5BEF594)
Dec 11 12:16:29 proteus postfix/qmgr[408]: 2FC361C0AA: removed
Dec 11 12:16:31 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:16:31 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 1.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:16:31 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 124 and the job result is done.
Dec 11 12:16:31 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 124.
Dec 11 12:16:31 proteus postfix/pickup[407]: A420C1C0AB: uid=33 from=<www-data>
Dec 11 12:16:31 proteus postfix/cleanup[447]: A420C1C0AB: message-id=<BYZceHw-B0626-AAAAAAAAAAAAAAAAPwHGNwNv-@osTicketMailer>
Dec 11 12:16:31 proteus postfix/qmgr[408]: A420C1C0AB: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=732, nrcpt=1 (queue active)
Dec 11 12:16:31 proteus mysqld[528]: 2021-12-11 12:16:31 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 528 ...
Dec 11 12:16:31 proteus postfix/smtp[473]: A420C1C0AB: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=0.22, delays=0/0/0.05/0.16, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B22BF5BEF59B)
Dec 11 12:16:31 proteus postfix/qmgr[408]: A420C1C0AB: removed
Dec 11 12:16:32 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:16:32 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:16:32 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 124 and the job result is failed.
Dec 11 12:16:37 proteus postfix/pickup[407]: 1B2681C30C: uid=33 from=<www-data>
Dec 11 12:16:37 proteus postfix/cleanup[443]: 1B2681C30C: message-id=<BYZceHw-v69Nd-AAAAAAAAAAAAAAAAP31IaiEs-@osTicketMailer>
Dec 11 12:16:37 proteus postfix/qmgr[408]: 1B2681C30C: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=732, nrcpt=1 (queue active)
Dec 11 12:16:37 proteus postfix/smtp[439]: 1B2681C30C: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=0.32, delays=0.01/0/0.05/0.26, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 29C4D5CCAF05)
Dec 11 12:16:37 proteus postfix/qmgr[408]: 1B2681C30C: removed
Dec 11 12:16:37 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:16:37 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 2.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:16:37 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 160 and the job result is done.
Dec 11 12:16:37 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 160.
Dec 11 12:16:37 proteus postfix/pickup[407]: E48BB1BAD3: uid=33 from=<www-data>
Dec 11 12:16:37 proteus postfix/cleanup[447]: E48BB1BAD3: message-id=<BYZceHw-=gMmU-AAAAAAAAAAAAAAAAP7nR+JaZ-@osTicketMailer>
Dec 11 12:16:37 proteus postfix/qmgr[408]: E48BB1BAD3: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=732, nrcpt=1 (queue active)
Dec 11 12:16:38 proteus mysqld[617]: 2021-12-11 12:16:38 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 617 ...
Dec 11 12:16:38 proteus postfix/smtp[452]: E48BB1BAD3: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=0.24, delays=0.01/0/0.05/0.18, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as F2E3E7C2D3FA)
Dec 11 12:16:38 proteus postfix/qmgr[408]: E48BB1BAD3: removed
Dec 11 12:16:38 proteus postfix/pickup[407]: 9486E1C0AD: uid=33 from=<www-data>
Dec 11 12:16:38 proteus postfix/cleanup[443]: 9486E1C0AD: message-id=<BYZceHw-4tgnK-AAAAAAAAAAAAAAAAP+JwU4bN-@osTicketMailer>
Dec 11 12:16:38 proteus postfix/qmgr[408]: 9486E1C0AD: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=732, nrcpt=1 (queue active)
Dec 11 12:16:38 proteus postfix/smtp[454]: 9486E1C0AD: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=0.16, delays=0/0/0.05/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as A32097D0D38B)
Dec 11 12:16:38 proteus postfix/qmgr[408]: 9486E1C0AD: removed
Dec 11 12:16:38 proteus /etc/mysql/debian-start[659]: Upgrading MySQL tables if necessary.
Dec 11 12:16:38 proteus /etc/mysql/debian-start[663]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:16:38 proteus /etc/mysql/debian-start[663]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:16:38 proteus /etc/mysql/debian-start[663]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:16:38 proteus /etc/mysql/debian-start[663]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:16:38 proteus /etc/mysql/debian-start[676]: Checking for insecure root accounts.
Dec 11 12:16:38 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 160.
Dec 11 12:16:38 proteus debian-start[656]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:16:38 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:16:38 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:16:44 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:16:44 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 3.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:16:44 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 196 and the job result is done.
Dec 11 12:16:44 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 196.
Dec 11 12:16:44 proteus mysqld[731]: 2021-12-11 12:16:44 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 731 ...
Dec 11 12:16:45 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:16:45 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:16:45 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 196 and the job result is failed.
Dec 11 12:16:50 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:16:50 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 4.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:16:50 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 232 and the job result is done.
Dec 11 12:16:50 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 232.
Dec 11 12:16:51 proteus mysqld[814]: 2021-12-11 12:16:51 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 814 ...
Dec 11 12:16:51 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:16:52 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:16:52 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 232 and the job result is failed.
Dec 11 12:16:57 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:16:57 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:16:57 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 268 and the job result is done.
Dec 11 12:16:57 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 268.
Dec 11 12:16:57 proteus mysqld[897]: 2021-12-11 12:16:57 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 897 ...
Dec 11 12:16:58 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:16:58 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:16:58 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 268 and the job result is failed.
Dec 11 12:17:01 proteus CRON[929]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 11 12:17:01 proteus CRON[930]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 11 12:17:01 proteus CRON[929]: pam_unix(cron:session): session closed for user root
Dec 11 12:17:03 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:03 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 6.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:03 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 304 and the job result is done.
Dec 11 12:17:03 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 304.
Dec 11 12:17:04 proteus mysqld[983]: 2021-12-11 12:17:04 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 983 ...
Dec 11 12:17:04 proteus /etc/mysql/debian-start[1018]: Upgrading MySQL tables if necessary.
Dec 11 12:17:04 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 304.
Dec 11 12:17:04 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:04 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:10 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:10 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 7.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:10 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 340 and the job result is done.
Dec 11 12:17:10 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 340.
Dec 11 12:17:10 proteus mysqld[1087]: 2021-12-11 12:17:10 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1087 ...
Dec 11 12:17:11 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:11 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:11 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 340 and the job result is failed.
Dec 11 12:17:16 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:16 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 8.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:16 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 376 and the job result is done.
Dec 11 12:17:16 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 376.
Dec 11 12:17:17 proteus mysqld[1170]: 2021-12-11 12:17:17 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1170 ...
Dec 11 12:17:17 proteus /etc/mysql/debian-start[1206]: Upgrading MySQL tables if necessary.
Dec 11 12:17:17 proteus /etc/mysql/debian-start[1210]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:17:17 proteus /etc/mysql/debian-start[1210]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:17:17 proteus /etc/mysql/debian-start[1210]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:17:17 proteus /etc/mysql/debian-start[1210]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:17:17 proteus /etc/mysql/debian-start[1223]: Checking for insecure root accounts.
Dec 11 12:17:17 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 376.
Dec 11 12:17:18 proteus debian-start[1203]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:17:18 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:18 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:23 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:23 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 9.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:23 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 412 and the job result is done.
Dec 11 12:17:23 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 412.
Dec 11 12:17:23 proteus mysqld[1278]: 2021-12-11 12:17:23 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1278 ...
Dec 11 12:17:24 proteus /etc/mysql/debian-start[1314]: Upgrading MySQL tables if necessary.
Dec 11 12:17:24 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 412.
Dec 11 12:17:24 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:24 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:29 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:29 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 10.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:29 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 448 and the job result is done.
Dec 11 12:17:29 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 448.
Dec 11 12:17:30 proteus mysqld[1382]: 2021-12-11 12:17:30 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1382 ...
Dec 11 12:17:30 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:30 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:30 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 448 and the job result is failed.
Dec 11 12:17:36 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:36 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 11.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:36 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 484 and the job result is done.
Dec 11 12:17:36 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 484.
Dec 11 12:17:36 proteus mysqld[1465]: 2021-12-11 12:17:36 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1465 ...
Dec 11 12:17:37 proteus /etc/mysql/debian-start[1501]: Upgrading MySQL tables if necessary.
Dec 11 12:17:37 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 484.
Dec 11 12:17:37 proteus /etc/mysql/debian-start[1505]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:17:37 proteus /etc/mysql/debian-start[1505]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:17:37 proteus /etc/mysql/debian-start[1505]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:17:37 proteus /etc/mysql/debian-start[1505]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:17:37 proteus /etc/mysql/debian-start[1518]: Checking for insecure root accounts.
Dec 11 12:17:37 proteus debian-start[1498]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:17:37 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:37 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:42 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:42 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 12.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:42 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 520 and the job result is done.
Dec 11 12:17:42 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 520.
Dec 11 12:17:43 proteus mysqld[1573]: 2021-12-11 12:17:43 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1573 ...
Dec 11 12:17:43 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:43 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:43 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 520 and the job result is failed.
Dec 11 12:17:49 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:49 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 13.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:49 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 556 and the job result is done.
Dec 11 12:17:49 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 556.
Dec 11 12:17:49 proteus mysqld[1656]: 2021-12-11 12:17:49 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1656 ...
Dec 11 12:17:50 proteus /etc/mysql/debian-start[1691]: Upgrading MySQL tables if necessary.
Dec 11 12:17:50 proteus /etc/mysql/debian-start[1696]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:17:50 proteus /etc/mysql/debian-start[1696]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:17:50 proteus /etc/mysql/debian-start[1696]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:17:50 proteus /etc/mysql/debian-start[1696]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:17:50 proteus /etc/mysql/debian-start[1709]: Checking for insecure root accounts.
Dec 11 12:17:50 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 556.
Dec 11 12:17:50 proteus debian-start[1689]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:17:50 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:50 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:17:55 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:17:55 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 14.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:17:55 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 592 and the job result is done.
Dec 11 12:17:55 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 592.
Dec 11 12:17:56 proteus mysqld[1764]: 2021-12-11 12:17:56 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1764 ...
Dec 11 12:17:56 proteus /etc/mysql/debian-start[1801]: Upgrading MySQL tables if necessary.
Dec 11 12:17:56 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 592.
Dec 11 12:17:56 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:17:57 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:02 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:02 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 15.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:02 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 628 and the job result is done.
Dec 11 12:18:02 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 628.
Dec 11 12:18:02 proteus mysqld[1868]: 2021-12-11 12:18:02 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1868 ...
Dec 11 12:18:03 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:03 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:03 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 628 and the job result is failed.
Dec 11 12:18:08 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:08 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 16.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:08 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 664 and the job result is done.
Dec 11 12:18:08 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 664.
Dec 11 12:18:09 proteus mysqld[1951]: 2021-12-11 12:18:09 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 1951 ...
Dec 11 12:18:09 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:10 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:10 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 664 and the job result is failed.
Dec 11 12:18:15 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:15 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 17.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:15 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 700 and the job result is done.
Dec 11 12:18:15 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 700.
Dec 11 12:18:15 proteus mysqld[2034]: 2021-12-11 12:18:15 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2034 ...
Dec 11 12:18:16 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:16 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:16 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 700 and the job result is failed.
Dec 11 12:18:21 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:21 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 18.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:21 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 736 and the job result is done.
Dec 11 12:18:21 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 736.
Dec 11 12:18:22 proteus mysqld[2121]: 2021-12-11 12:18:22 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2121 ...
Dec 11 12:18:22 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:22 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:22 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 736 and the job result is failed.
Dec 11 12:18:28 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:28 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 19.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:28 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 772 and the job result is done.
Dec 11 12:18:28 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 772.
Dec 11 12:18:28 proteus mysqld[2204]: 2021-12-11 12:18:28 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2204 ...
Dec 11 12:18:29 proteus /etc/mysql/debian-start[2240]: Upgrading MySQL tables if necessary.
Dec 11 12:18:29 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 772.
Dec 11 12:18:29 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:29 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:34 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:34 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 20.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:34 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 808 and the job result is done.
Dec 11 12:18:34 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 808.
Dec 11 12:18:35 proteus mysqld[2308]: 2021-12-11 12:18:35 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2308 ...
Dec 11 12:18:35 proteus /etc/mysql/debian-start[2344]: Upgrading MySQL tables if necessary.
Dec 11 12:18:35 proteus /etc/mysql/debian-start[2348]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:18:35 proteus /etc/mysql/debian-start[2348]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:18:35 proteus /etc/mysql/debian-start[2348]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:18:35 proteus /etc/mysql/debian-start[2348]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:18:35 proteus /etc/mysql/debian-start[2361]: Checking for insecure root accounts.
Dec 11 12:18:35 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 808.
Dec 11 12:18:36 proteus debian-start[2341]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:18:36 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:36 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:41 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:41 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 21.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:41 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 844 and the job result is done.
Dec 11 12:18:41 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 844.
Dec 11 12:18:41 proteus mysqld[2416]: 2021-12-11 12:18:41 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2416 ...
Dec 11 12:18:42 proteus /etc/mysql/debian-start[2452]: Upgrading MySQL tables if necessary.
Dec 11 12:18:42 proteus /etc/mysql/debian-start[2456]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:18:42 proteus /etc/mysql/debian-start[2456]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:18:42 proteus /etc/mysql/debian-start[2456]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:18:42 proteus /etc/mysql/debian-start[2456]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:18:42 proteus /etc/mysql/debian-start[2469]: Checking for insecure root accounts.
Dec 11 12:18:42 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 844.
Dec 11 12:18:42 proteus debian-start[2449]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:18:42 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:42 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:47 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:47 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 22.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:47 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 880 and the job result is done.
Dec 11 12:18:47 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 880.
Dec 11 12:18:48 proteus mysqld[2524]: 2021-12-11 12:18:48 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2524 ...
Dec 11 12:18:48 proteus /etc/mysql/debian-start[2559]: Upgrading MySQL tables if necessary.
Dec 11 12:18:48 proteus /etc/mysql/debian-start[2563]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:18:48 proteus /etc/mysql/debian-start[2563]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:18:48 proteus /etc/mysql/debian-start[2563]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:18:48 proteus /etc/mysql/debian-start[2563]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:18:48 proteus /etc/mysql/debian-start[2577]: Checking for insecure root accounts.
Dec 11 12:18:48 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 880.
Dec 11 12:18:48 proteus debian-start[2557]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:18:48 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:48 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:18:54 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:18:54 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 23.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:18:54 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 916 and the job result is done.
Dec 11 12:18:54 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 916.
Dec 11 12:18:54 proteus mysqld[2632]: 2021-12-11 12:18:54 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2632 ...
Dec 11 12:18:55 proteus /etc/mysql/debian-start[2668]: Upgrading MySQL tables if necessary.
Dec 11 12:18:55 proteus /etc/mysql/debian-start[2672]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:18:55 proteus /etc/mysql/debian-start[2672]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:18:55 proteus /etc/mysql/debian-start[2672]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:18:55 proteus /etc/mysql/debian-start[2672]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:18:55 proteus /etc/mysql/debian-start[2685]: Checking for insecure root accounts.
Dec 11 12:18:55 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 916.
Dec 11 12:18:55 proteus debian-start[2665]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:18:55 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:18:55 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:00 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:00 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 24.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:00 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 952 and the job result is done.
Dec 11 12:19:00 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 952.
Dec 11 12:19:01 proteus mysqld[2740]: 2021-12-11 12:19:01 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2740 ...
Dec 11 12:19:01 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:01 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:01 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 952 and the job result is failed.
Dec 11 12:19:07 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:07 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 25.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:07 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 988 and the job result is done.
Dec 11 12:19:07 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 988.
Dec 11 12:19:07 proteus mysqld[2823]: 2021-12-11 12:19:07 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2823 ...
Dec 11 12:19:08 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:08 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:08 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 988 and the job result is failed.
Dec 11 12:19:13 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:13 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 26.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:13 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1024 and the job result is done.
Dec 11 12:19:13 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1024.
Dec 11 12:19:14 proteus mysqld[2906]: 2021-12-11 12:19:14 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 2906 ...
Dec 11 12:19:14 proteus /etc/mysql/debian-start[2942]: Upgrading MySQL tables if necessary.
Dec 11 12:19:14 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1024.
Dec 11 12:19:14 proteus /etc/mysql/debian-start[2946]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:19:14 proteus /etc/mysql/debian-start[2946]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:19:14 proteus /etc/mysql/debian-start[2946]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:19:14 proteus /etc/mysql/debian-start[2946]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:19:14 proteus /etc/mysql/debian-start[2959]: Checking for insecure root accounts.
Dec 11 12:19:14 proteus debian-start[2939]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:19:14 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:14 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:20 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:20 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 27.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:20 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1060 and the job result is done.
Dec 11 12:19:20 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1060.
Dec 11 12:19:20 proteus mysqld[3014]: 2021-12-11 12:19:20 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3014 ...
Dec 11 12:19:21 proteus /etc/mysql/debian-start[3050]: Upgrading MySQL tables if necessary.
Dec 11 12:19:21 proteus /etc/mysql/debian-start[3054]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:19:21 proteus /etc/mysql/debian-start[3054]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:19:21 proteus /etc/mysql/debian-start[3054]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:19:21 proteus /etc/mysql/debian-start[3054]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:19:21 proteus /etc/mysql/debian-start[3067]: Checking for insecure root accounts.
Dec 11 12:19:21 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1060.
Dec 11 12:19:21 proteus debian-start[3047]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:19:21 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:21 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:26 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:26 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 28.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:26 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1096 and the job result is done.
Dec 11 12:19:26 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1096.
Dec 11 12:19:27 proteus mysqld[3122]: 2021-12-11 12:19:27 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3122 ...
Dec 11 12:19:27 proteus /etc/mysql/debian-start[3158]: Upgrading MySQL tables if necessary.
Dec 11 12:19:27 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1096.
Dec 11 12:19:28 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:28 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:33 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:33 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 29.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:33 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1132 and the job result is done.
Dec 11 12:19:33 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1132.
Dec 11 12:19:33 proteus mysqld[3226]: 2021-12-11 12:19:33 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3226 ...
Dec 11 12:19:34 proteus /etc/mysql/debian-start[3261]: Upgrading MySQL tables if necessary.
Dec 11 12:19:34 proteus /etc/mysql/debian-start[3266]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:19:34 proteus /etc/mysql/debian-start[3266]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:19:34 proteus /etc/mysql/debian-start[3266]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:19:34 proteus /etc/mysql/debian-start[3266]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:19:34 proteus /etc/mysql/debian-start[3279]: Checking for insecure root accounts.
Dec 11 12:19:34 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1132.
Dec 11 12:19:34 proteus debian-start[3259]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:19:34 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:34 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:39 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:39 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 30.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:39 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1168 and the job result is done.
Dec 11 12:19:39 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1168.
Dec 11 12:19:40 proteus mysqld[3334]: 2021-12-11 12:19:40 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3334 ...
Dec 11 12:19:40 proteus /etc/mysql/debian-start[3370]: Upgrading MySQL tables if necessary.
Dec 11 12:19:40 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1168.
Dec 11 12:19:40 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:40 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:46 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:46 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 31.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:46 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1204 and the job result is done.
Dec 11 12:19:46 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1204.
Dec 11 12:19:46 proteus mysqld[3438]: 2021-12-11 12:19:46 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3438 ...
Dec 11 12:19:47 proteus /etc/mysql/debian-start[3474]: Upgrading MySQL tables if necessary.
Dec 11 12:19:47 proteus /etc/mysql/debian-start[3478]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:19:47 proteus /etc/mysql/debian-start[3478]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:19:47 proteus /etc/mysql/debian-start[3478]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:19:47 proteus /etc/mysql/debian-start[3478]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:19:47 proteus /etc/mysql/debian-start[3491]: Checking for insecure root accounts.
Dec 11 12:19:47 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1204.
Dec 11 12:19:47 proteus debian-start[3471]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:19:47 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:47 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:52 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:52 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 32.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:52 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1240 and the job result is done.
Dec 11 12:19:52 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1240.
Dec 11 12:19:53 proteus mysqld[3546]: 2021-12-11 12:19:53 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3546 ...
Dec 11 12:19:53 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:19:53 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:19:53 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1240 and the job result is failed.
Dec 11 12:19:58 proteus postfix/scache[436]: statistics: start interval Dec 11 12:16:25
Dec 11 12:19:58 proteus postfix/scache[436]: statistics: domain lookup hits=0 miss=168 success=0%
Dec 11 12:19:58 proteus postfix/scache[436]: statistics: address lookup hits=0 miss=168 success=0%
Dec 11 12:19:59 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:19:59 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 33.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:19:59 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1276 and the job result is done.
Dec 11 12:19:59 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1276.
Dec 11 12:19:59 proteus mysqld[3629]: 2021-12-11 12:19:59 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3629 ...
Dec 11 12:20:00 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:00 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:00 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1276 and the job result is failed.
Dec 11 12:20:01 proteus CRON[3661]: pam_unix(cron:session): session opened for user www-data by (uid=0)
Dec 11 12:20:01 proteus CRON[3662]: (www-data) CMD (php /var/www/ticket/api/cron.php)
Dec 11 12:20:01 proteus postfix/pickup[407]: B163C1CD8A: uid=33 from=<www-data>
Dec 11 12:20:01 proteus postfix/cleanup[3667]: B163C1CD8A: message-id=<BYZceHw-yGfNl-AAAAAAAAAAAAAAAAP5vqimyF-@osTicketMailer>
Dec 11 12:20:01 proteus postfix/qmgr[408]: B163C1CD8A: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=736, nrcpt=1 (queue active)
Dec 11 12:20:01 proteus postfix/pickup[407]: B3F8C1CD8B: uid=33 from=<www-data>
Dec 11 12:20:01 proteus postfix/cleanup[3667]: B3F8C1CD8B: message-id=<20211211112001.B3F8C1CD8B@proteus.fet.htu.tuwien.ac.at>
Dec 11 12:20:01 proteus CRON[3661]: pam_unix(cron:session): session closed for user www-data
Dec 11 12:20:01 proteus postfix/qmgr[408]: B3F8C1CD8B: from=<www-data@proteus.fet.htu.tuwien.ac.at>, size=991, nrcpt=1 (queue active)
Dec 11 12:20:01 proteus postfix/local[3672]: B3F8C1CD8B: to=<www-data@proteus.fet.htu.tuwien.ac.at>, orig_to=<www-data>, relay=local, delay=0.01, delays=0/0/0/0, dsn=2.0.0, status=sent (delivered to mailbox)
Dec 11 12:20:01 proteus postfix/qmgr[408]: B3F8C1CD8B: removed
Dec 11 12:20:01 proteus postfix/smtp[3671]: B163C1CD8A: to=<bofh@fet.at>, relay=buran.htu.tuwien.ac.at[128.130.95.211]:25, delay=0.17, delays=0.01/0.01/0.05/0.1, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as C271880F0CEA)
Dec 11 12:20:01 proteus postfix/qmgr[408]: B163C1CD8A: removed
Dec 11 12:20:05 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:05 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 34.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:05 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1312 and the job result is done.
Dec 11 12:20:05 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1312.
Dec 11 12:20:06 proteus mysqld[3724]: 2021-12-11 12:20:06 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3724 ...
Dec 11 12:20:06 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:06 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:06 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1312 and the job result is failed.
Dec 11 12:20:12 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:12 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 35.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:12 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1348 and the job result is done.
Dec 11 12:20:12 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1348.
Dec 11 12:20:12 proteus mysqld[3807]: 2021-12-11 12:20:12 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3807 ...
Dec 11 12:20:13 proteus /etc/mysql/debian-start[3843]: Upgrading MySQL tables if necessary.
Dec 11 12:20:13 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1348.
Dec 11 12:20:13 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:13 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:18 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:18 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 36.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:18 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1384 and the job result is done.
Dec 11 12:20:18 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1384.
Dec 11 12:20:19 proteus mysqld[3911]: 2021-12-11 12:20:19 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 3911 ...
Dec 11 12:20:19 proteus /etc/mysql/debian-start[3947]: Upgrading MySQL tables if necessary.
Dec 11 12:20:19 proteus /etc/mysql/debian-start[3951]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:20:19 proteus /etc/mysql/debian-start[3951]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:20:19 proteus /etc/mysql/debian-start[3951]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:20:19 proteus /etc/mysql/debian-start[3951]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:20:19 proteus /etc/mysql/debian-start[3964]: Checking for insecure root accounts.
Dec 11 12:20:19 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1384.
Dec 11 12:20:19 proteus debian-start[3944]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:20:19 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:19 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:25 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:25 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 37.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:25 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1420 and the job result is done.
Dec 11 12:20:25 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1420.
Dec 11 12:20:25 proteus mysqld[4019]: 2021-12-11 12:20:25 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4019 ...
Dec 11 12:20:26 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:26 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:26 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1420 and the job result is failed.
Dec 11 12:20:31 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:31 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 38.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:31 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1456 and the job result is done.
Dec 11 12:20:31 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1456.
Dec 11 12:20:32 proteus mysqld[4102]: 2021-12-11 12:20:32 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4102 ...
Dec 11 12:20:32 proteus /etc/mysql/debian-start[4138]: Upgrading MySQL tables if necessary.
Dec 11 12:20:32 proteus /etc/mysql/debian-start[4142]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:20:32 proteus /etc/mysql/debian-start[4142]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:20:32 proteus /etc/mysql/debian-start[4142]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:20:32 proteus /etc/mysql/debian-start[4142]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:20:32 proteus /etc/mysql/debian-start[4155]: Checking for insecure root accounts.
Dec 11 12:20:32 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1456.
Dec 11 12:20:32 proteus debian-start[4135]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:20:32 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:32 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:38 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:38 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 39.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:38 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1492 and the job result is done.
Dec 11 12:20:38 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1492.
Dec 11 12:20:38 proteus mysqld[4210]: 2021-12-11 12:20:38 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4210 ...
Dec 11 12:20:39 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:39 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:39 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1492 and the job result is failed.
Dec 11 12:20:44 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:44 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 40.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:44 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1528 and the job result is done.
Dec 11 12:20:44 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1528.
Dec 11 12:20:45 proteus mysqld[4293]: 2021-12-11 12:20:45 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4293 ...
Dec 11 12:20:45 proteus /etc/mysql/debian-start[4329]: Upgrading MySQL tables if necessary.
Dec 11 12:20:45 proteus /etc/mysql/debian-start[4334]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:20:45 proteus /etc/mysql/debian-start[4334]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:20:45 proteus /etc/mysql/debian-start[4334]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:20:45 proteus /etc/mysql/debian-start[4334]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:20:45 proteus /etc/mysql/debian-start[4346]: Checking for insecure root accounts.
Dec 11 12:20:45 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1528.
Dec 11 12:20:46 proteus debian-start[4326]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:20:46 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:46 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:51 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:51 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 41.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:51 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1564 and the job result is done.
Dec 11 12:20:51 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1564.
Dec 11 12:20:51 proteus mysqld[4401]: 2021-12-11 12:20:51 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4401 ...
Dec 11 12:20:52 proteus /etc/mysql/debian-start[4437]: Upgrading MySQL tables if necessary.
Dec 11 12:20:52 proteus /etc/mysql/debian-start[4442]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:20:52 proteus /etc/mysql/debian-start[4442]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:20:52 proteus /etc/mysql/debian-start[4442]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:20:52 proteus /etc/mysql/debian-start[4442]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:20:52 proteus /etc/mysql/debian-start[4454]: Checking for insecure root accounts.
Dec 11 12:20:52 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1564.
Dec 11 12:20:52 proteus debian-start[4434]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:20:52 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:52 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:20:57 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:20:57 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 42.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:20:57 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1600 and the job result is done.
Dec 11 12:20:57 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1600.
Dec 11 12:20:58 proteus mysqld[4509]: 2021-12-11 12:20:58 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4509 ...
Dec 11 12:20:58 proteus /etc/mysql/debian-start[4545]: Upgrading MySQL tables if necessary.
Dec 11 12:20:58 proteus /etc/mysql/debian-start[4550]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:20:58 proteus /etc/mysql/debian-start[4550]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:20:58 proteus /etc/mysql/debian-start[4550]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:20:58 proteus /etc/mysql/debian-start[4550]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:20:58 proteus /etc/mysql/debian-start[4562]: Checking for insecure root accounts.
Dec 11 12:20:58 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1600.
Dec 11 12:20:58 proteus debian-start[4542]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:20:58 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:20:59 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:04 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:04 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 43.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:04 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1636 and the job result is done.
Dec 11 12:21:04 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1636.
Dec 11 12:21:04 proteus mysqld[4617]: 2021-12-11 12:21:04 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4617 ...
Dec 11 12:21:05 proteus /etc/mysql/debian-start[4653]: Upgrading MySQL tables if necessary.
Dec 11 12:21:05 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1636.
Dec 11 12:21:05 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:05 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:10 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:10 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 44.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:10 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1672 and the job result is done.
Dec 11 12:21:10 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1672.
Dec 11 12:21:11 proteus mysqld[4721]: 2021-12-11 12:21:11 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4721 ...
Dec 11 12:21:11 proteus /etc/mysql/debian-start[4756]: Upgrading MySQL tables if necessary.
Dec 11 12:21:11 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1672.
Dec 11 12:21:11 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:11 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:17 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:17 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 45.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:17 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1708 and the job result is done.
Dec 11 12:21:17 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1708.
Dec 11 12:21:17 proteus mysqld[4825]: 2021-12-11 12:21:17 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4825 ...
Dec 11 12:21:18 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:18 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:18 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1708 and the job result is failed.
Dec 11 12:21:23 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:23 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 46.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:23 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1744 and the job result is done.
Dec 11 12:21:23 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1744.
Dec 11 12:21:24 proteus mysqld[4908]: 2021-12-11 12:21:24 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 4908 ...
Dec 11 12:21:24 proteus /etc/mysql/debian-start[4943]: Upgrading MySQL tables if necessary.
Dec 11 12:21:24 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1744.
Dec 11 12:21:24 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:24 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:30 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:30 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 47.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:30 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1780 and the job result is done.
Dec 11 12:21:30 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1780.
Dec 11 12:21:30 proteus mysqld[5012]: 2021-12-11 12:21:30 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5012 ...
Dec 11 12:21:31 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:31 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:31 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1780 and the job result is failed.
Dec 11 12:21:36 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:36 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 48.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:36 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1816 and the job result is done.
Dec 11 12:21:36 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1816.
Dec 11 12:21:37 proteus mysqld[5095]: 2021-12-11 12:21:37 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5095 ...
Dec 11 12:21:37 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:37 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:37 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1816 and the job result is failed.
Dec 11 12:21:43 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:43 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 49.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:43 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1852 and the job result is done.
Dec 11 12:21:43 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1852.
Dec 11 12:21:43 proteus mysqld[5178]: 2021-12-11 12:21:43 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5178 ...
Dec 11 12:21:44 proteus /etc/mysql/debian-start[5214]: Upgrading MySQL tables if necessary.
Dec 11 12:21:44 proteus /etc/mysql/debian-start[5218]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:21:44 proteus /etc/mysql/debian-start[5218]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:21:44 proteus /etc/mysql/debian-start[5218]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:21:44 proteus /etc/mysql/debian-start[5218]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:21:44 proteus /etc/mysql/debian-start[5231]: Checking for insecure root accounts.
Dec 11 12:21:44 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1852.
Dec 11 12:21:44 proteus debian-start[5211]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:21:44 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:44 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:49 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:49 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 50.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:49 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1888 and the job result is done.
Dec 11 12:21:49 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1888.
Dec 11 12:21:50 proteus mysqld[5286]: 2021-12-11 12:21:50 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5286 ...
Dec 11 12:21:50 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:50 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:21:50 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1888 and the job result is failed.
Dec 11 12:21:56 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:21:56 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 51.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:21:56 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1924 and the job result is done.
Dec 11 12:21:56 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1924.
Dec 11 12:21:56 proteus mysqld[5369]: 2021-12-11 12:21:56 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5369 ...
Dec 11 12:21:57 proteus /etc/mysql/debian-start[5405]: Upgrading MySQL tables if necessary.
Dec 11 12:21:57 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1924.
Dec 11 12:21:57 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:21:57 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:02 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:02 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 52.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:02 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1960 and the job result is done.
Dec 11 12:22:02 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1960.
Dec 11 12:22:03 proteus mysqld[5473]: 2021-12-11 12:22:03 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5473 ...
Dec 11 12:22:03 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:03 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:03 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 1960 and the job result is failed.
Dec 11 12:22:09 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:09 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 53.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:09 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 1996 and the job result is done.
Dec 11 12:22:09 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 1996.
Dec 11 12:22:09 proteus mysqld[5556]: 2021-12-11 12:22:09 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5556 ...
Dec 11 12:22:10 proteus /etc/mysql/debian-start[5592]: Upgrading MySQL tables if necessary.
Dec 11 12:22:10 proteus /etc/mysql/debian-start[5596]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:22:10 proteus /etc/mysql/debian-start[5596]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:22:10 proteus /etc/mysql/debian-start[5596]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:22:10 proteus /etc/mysql/debian-start[5596]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:22:10 proteus /etc/mysql/debian-start[5609]: Checking for insecure root accounts.
Dec 11 12:22:10 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 1996.
Dec 11 12:22:10 proteus debian-start[5589]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:22:10 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:10 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:15 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:15 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 54.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:15 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2032 and the job result is done.
Dec 11 12:22:15 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2032.
Dec 11 12:22:16 proteus mysqld[5664]: 2021-12-11 12:22:16 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5664 ...
Dec 11 12:22:17 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:17 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:17 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2032 and the job result is failed.
Dec 11 12:22:22 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:22 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 55.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:22 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2068 and the job result is done.
Dec 11 12:22:22 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2068.
Dec 11 12:22:22 proteus mysqld[5747]: 2021-12-11 12:22:22 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5747 ...
Dec 11 12:22:23 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:23 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:23 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2068 and the job result is failed.
Dec 11 12:22:28 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:28 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 56.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:28 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2104 and the job result is done.
Dec 11 12:22:28 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2104.
Dec 11 12:22:29 proteus mysqld[5830]: 2021-12-11 12:22:29 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5830 ...
Dec 11 12:22:30 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:30 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:30 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2104 and the job result is failed.
Dec 11 12:22:35 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:35 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 57.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:35 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2140 and the job result is done.
Dec 11 12:22:35 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2140.
Dec 11 12:22:35 proteus mysqld[5913]: 2021-12-11 12:22:35 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5913 ...
Dec 11 12:22:36 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:36 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:36 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2140 and the job result is failed.
Dec 11 12:22:41 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:41 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 58.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:41 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2176 and the job result is done.
Dec 11 12:22:41 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2176.
Dec 11 12:22:42 proteus mysqld[5996]: 2021-12-11 12:22:42 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 5996 ...
Dec 11 12:22:43 proteus /etc/mysql/debian-start[6031]: Upgrading MySQL tables if necessary.
Dec 11 12:22:43 proteus /etc/mysql/debian-start[6036]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:22:43 proteus /etc/mysql/debian-start[6036]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:22:43 proteus /etc/mysql/debian-start[6036]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:22:43 proteus /etc/mysql/debian-start[6036]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:22:43 proteus /etc/mysql/debian-start[6049]: Checking for insecure root accounts.
Dec 11 12:22:43 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 2176.
Dec 11 12:22:43 proteus debian-start[6029]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:22:43 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:43 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:48 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:48 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 59.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:48 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2212 and the job result is done.
Dec 11 12:22:48 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2212.
Dec 11 12:22:48 proteus mysqld[6104]: 2021-12-11 12:22:48 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6104 ...
Dec 11 12:22:49 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:49 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:49 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2212 and the job result is failed.
Dec 11 12:22:54 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:22:54 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 60.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:22:54 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2248 and the job result is done.
Dec 11 12:22:54 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2248.
Dec 11 12:22:55 proteus mysqld[6187]: 2021-12-11 12:22:55 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6187 ...
Dec 11 12:22:56 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:22:56 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:22:56 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2248 and the job result is failed.
Dec 11 12:23:01 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:01 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 61.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:01 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2284 and the job result is done.
Dec 11 12:23:01 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2284.
Dec 11 12:23:01 proteus mysqld[6270]: 2021-12-11 12:23:01 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6270 ...
Dec 11 12:23:02 proteus /etc/mysql/debian-start[6306]: Upgrading MySQL tables if necessary.
Dec 11 12:23:02 proteus /etc/mysql/debian-start[6310]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:23:02 proteus /etc/mysql/debian-start[6310]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:23:02 proteus /etc/mysql/debian-start[6310]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:23:02 proteus /etc/mysql/debian-start[6310]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:23:02 proteus /etc/mysql/debian-start[6323]: Checking for insecure root accounts.
Dec 11 12:23:02 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 2284.
Dec 11 12:23:02 proteus debian-start[6303]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:23:02 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:02 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:07 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:07 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 62.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:07 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2320 and the job result is done.
Dec 11 12:23:07 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2320.
Dec 11 12:23:08 proteus mysqld[6378]: 2021-12-11 12:23:08 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6378 ...
Dec 11 12:23:09 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:09 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:09 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2320 and the job result is failed.
Dec 11 12:23:14 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:14 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 63.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:14 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2356 and the job result is done.
Dec 11 12:23:14 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2356.
Dec 11 12:23:14 proteus mysqld[6461]: 2021-12-11 12:23:14 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6461 ...
Dec 11 12:23:15 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:15 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:15 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2356 and the job result is failed.
Dec 11 12:23:17 proteus sshd[6493]: Accepted publickey for root from 192.168.86.6 port 35650 ssh2: RSA SHA256:mDonqNkMuAzeet/GVB1OM2oZwoM4M52yTHy9hgvNbOo
Dec 11 12:23:17 proteus sshd[6493]: pam_unix(sshd:session): session opened for user root by (uid=0)
Dec 11 12:23:17 proteus systemd[1]: Created slice User Slice of UID 0.
-- Subject: A start job for unit user-0.slice has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user-0.slice has finished successfully.
--
-- The job identifier is 2429.
Dec 11 12:23:17 proteus systemd[1]: Starting User Runtime Directory /run/user/0...
-- Subject: A start job for unit user-runtime-dir@0.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user-runtime-dir@0.service has begun execution.
--
-- The job identifier is 2393.
Dec 11 12:23:17 proteus systemd-logind[87]: New session 4089 of user root.
-- Subject: A new session 4089 has been created for user root
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 4089 has been created for the user root.
--
-- The leading process of the session is 6493.
Dec 11 12:23:17 proteus systemd[1]: Started User Runtime Directory /run/user/0.
-- Subject: A start job for unit user-runtime-dir@0.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user-runtime-dir@0.service has finished successfully.
--
-- The job identifier is 2393.
Dec 11 12:23:17 proteus systemd[1]: Starting User Manager for UID 0...
-- Subject: A start job for unit user@0.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user@0.service has begun execution.
--
-- The job identifier is 2392.
Dec 11 12:23:17 proteus systemd[6496]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Dec 11 12:23:17 proteus systemd[6496]: Listening on GnuPG cryptographic agent and passphrase cache.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 8.
Dec 11 12:23:17 proteus systemd[6496]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 11.
Dec 11 12:23:17 proteus systemd[6496]: Listening on GnuPG network certificate management daemon.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 9.
Dec 11 12:23:17 proteus systemd[6496]: Reached target Paths.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 12.
Dec 11 12:23:17 proteus systemd[6496]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 6.
Dec 11 12:23:17 proteus systemd[6496]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 10.
Dec 11 12:23:17 proteus systemd[6496]: Reached target Sockets.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 5.
Dec 11 12:23:17 proteus systemd[6496]: Reached target Timers.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 3.
Dec 11 12:23:17 proteus systemd[6496]: Reached target Basic System.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 2.
Dec 11 12:23:17 proteus systemd[6496]: Reached target Default.
-- Subject: A start job for unit UNIT has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit UNIT has finished successfully.
--
-- The job identifier is 1.
Dec 11 12:23:17 proteus systemd[6496]: Startup finished in 24ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The user manager instance for user 0 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
--
-- Startup of the manager took 24825 microseconds.
Dec 11 12:23:17 proteus systemd[1]: Started User Manager for UID 0.
-- Subject: A start job for unit user@0.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit user@0.service has finished successfully.
--
-- The job identifier is 2392.
Dec 11 12:23:17 proteus systemd[1]: Started Session 4089 of user root.
-- Subject: A start job for unit session-4089.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-4089.scope has finished successfully.
--
-- The job identifier is 2431.
Dec 11 12:23:20 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:20 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 64.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:20 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2471 and the job result is done.
Dec 11 12:23:20 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2471.
Dec 11 12:23:21 proteus mysqld[6576]: 2021-12-11 12:23:21 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6576 ...
Dec 11 12:23:22 proteus /etc/mysql/debian-start[6612]: Upgrading MySQL tables if necessary.
Dec 11 12:23:22 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 2471.
Dec 11 12:23:22 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:22 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:27 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:27 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 65.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:27 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2507 and the job result is done.
Dec 11 12:23:27 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2507.
Dec 11 12:23:27 proteus mysqld[6680]: 2021-12-11 12:23:27 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6680 ...
Dec 11 12:23:28 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:28 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:28 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2507 and the job result is failed.
Dec 11 12:23:33 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:33 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 66.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:33 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2543 and the job result is done.
Dec 11 12:23:33 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2543.
Dec 11 12:23:34 proteus mysqld[6768]: 2021-12-11 12:23:34 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6768 ...
Dec 11 12:23:35 proteus /etc/mysql/debian-start[6803]: Upgrading MySQL tables if necessary.
Dec 11 12:23:35 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 2543.
Dec 11 12:23:35 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:35 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:40 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:40 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 67.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:40 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2579 and the job result is done.
Dec 11 12:23:40 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2579.
Dec 11 12:23:40 proteus mysqld[6884]: 2021-12-11 12:23:40 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6884 ...
Dec 11 12:23:41 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:41 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:41 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2579 and the job result is failed.
Dec 11 12:23:46 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:46 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 68.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:46 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2615 and the job result is done.
Dec 11 12:23:46 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2615.
Dec 11 12:23:47 proteus mysqld[6967]: 2021-12-11 12:23:47 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 6967 ...
Dec 11 12:23:48 proteus /etc/mysql/debian-start[7003]: Upgrading MySQL tables if necessary.
Dec 11 12:23:48 proteus /etc/mysql/debian-start[7007]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Dec 11 12:23:48 proteus /etc/mysql/debian-start[7007]: Looking for 'mysql' as: /usr/bin/mysql
Dec 11 12:23:48 proteus /etc/mysql/debian-start[7007]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Dec 11 12:23:48 proteus /etc/mysql/debian-start[7007]: This installation of MySQL is already upgraded to 10.3.18-MariaDB, use --force if you still need to run mysql_upgrade
Dec 11 12:23:48 proteus /etc/mysql/debian-start[7020]: Checking for insecure root accounts.
Dec 11 12:23:48 proteus systemd[1]: Started MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished successfully.
--
-- The job identifier is 2615.
Dec 11 12:23:48 proteus debian-start[7000]: ERROR 2013 (HY000): Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 104
Dec 11 12:23:48 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:48 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:53 proteus systemd[1]: mariadb.service: Service RestartSec=5s expired, scheduling restart.
Dec 11 12:23:53 proteus systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 69.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Dec 11 12:23:53 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2651 and the job result is done.
Dec 11 12:23:53 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2651.
Dec 11 12:23:53 proteus mysqld[7085]: 2021-12-11 12:23:53 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 7085 ...
Dec 11 12:23:54 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:54 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:54 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2651 and the job result is failed.
Dec 11 12:23:55 proteus systemd[1]: Stopped MariaDB 10.3.18 database server.
-- Subject: A stop job for unit mariadb.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit mariadb.service has finished.
--
-- The job identifier is 2687 and the job result is done.
Dec 11 12:23:58 proteus systemd[1]: Starting MariaDB 10.3.18 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has begun execution.
--
-- The job identifier is 2688.
Dec 11 12:23:58 proteus mysqld[7209]: 2021-12-11 12:23:58 0 [Note] /usr/sbin/mysqld (mysqld 10.3.18-MariaDB-0+deb10u1) starting as process 7209 ...
Dec 11 12:23:59 proteus systemd[1]: mariadb.service: Main process exited, code=killed, status=11/SEGV
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 11.
Dec 11 12:23:59 proteus systemd[1]: mariadb.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Dec 11 12:23:59 proteus systemd[1]: Failed to start MariaDB 10.3.18 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 2688 and the job result is failed.
Reference in New Issue View Git Blame Copy Permalink