Okay, I took a closer look. I can remember once when I wanted to run something on the server, but there was no memory available. So I think that was on 13-10. That explains that error message. That leaves this message:
Code: Select all
2021-10-15 02:50:02 1mbBQA-0003aa-1q 1mbBQA-0003aa-1q bad addresses found in headers
I have not been able to find a clear explanation on the internet. I just then went to see what mail was sent at 02:50. That was this email:
It is true that there was no connection for a while at that time. I did a sudo apt update & upgrade. Then mysql dropped out for a while. I have vesta on two servers, and had also updated another server. That one also had the same error. I think it has already been explained in this one. I have therefore emptied paniclog now.
Is there perhaps something else that needs to be adjusted in VestaCP to avoid this error message? Otherwise, are the error messages in mainlog normal? I don't have all these error messages on another server (with myVesta). There I only have erros like this:
Code: Select all
2021-10-22 22:03:54 Start queue run: pid=23665
2021-10-22 22:03:54 1mdm73-0003Zw-99 Message is frozen
2021-10-22 22:03:54 1mdkmn-0002XX-VX Message is frozen
2021-10-22 22:03:54 1mdPdV-000365-CK Message is frozen
2021-10-22 22:03:54 1mdOJG-00023m-9V Message is frozen
2021-10-22 22:03:54 End queue run: pid=23665
2021-10-22 22:33:54 Start queue run: pid=24965
2021-10-22 22:33:54 1mdm73-0003Zw-99 Message is frozen
2021-10-22 22:33:54 1mdkmn-0002XX-VX Message is frozen
2021-10-22 22:33:54 1mdPdV-000365-CK Message is frozen
2021-10-22 22:33:54 1mdOJG-00023m-9V Message is frozen
2021-10-22 22:33:54 End queue run: pid=24965