Haraka release
-
@BrutalBirdie @joseph My point is with the change in Haraka container we still experience thesame corruption. This is the message i have been trying to send out.. I have been low key working on this and I have seen that the problem is within so i guess this problem should be escalated by your team..
-
You have fixed the file. Great
But you've not yet confirmed that you restarted the
box.service
.
Thus, no one can really confirm that you are really using the configured image.Please confirm that you have run
systemctl restart box.service
And provide the console output of the following command:
docker inspect --format='{{.Config.Image}}' mail
Without doing exactly that, no further assistence can be given.
-
@BrutalBirdie Sorry to make this case but can you simplify the last command line instruction for me so I can post the results
this '{{.Config.Image}}' is what i cannot decypher
-
@BrutalBirdie Sorry to make this case but can you simplify the last command line instruction for me so I can post the results
this '{{.Config.Image}}' is what i cannot decypher
@mmtrade
There is nothinig to decypher.
The instruction statesprovide the console output of the following command
.
Connect to your server:
ssh root@my.DOMAIN.TLD
- Copy the first command, and paste it into the terminal that is connected to your server and press enter.
systemctl restart box.service
- Copy the second command and paste it into the terminal that is connected to your server and press enter.
docker inspect --format='{{.Config.Image}}' mail
Copy the output of the second (2.) command and post it here in the forum.
-
-
I am losing my patiance.
Why are you runningdocker stop mail
anddocker start mail
.
I never stated you should do that.
WHY?! Why won't you just follow the instruction to the letter!Everytime you do not follow given instruction, you raise possibility for erros even further.
-
Everything seems okay at the moment... If i have any more queries I will surely come back again
-
@BrutalBirdie @joseph @necrevistonnezr
This Haraka crashing is still happenning over and over again
I built with another server to check if it was from the server and yet this issue is still there..
Even when i updated to the lastest version manually.. Any ideas on this????
-
Do I need to edit anything??? @BrutalBirdie @joseph @necrevistonnezr
-
@joseph @BrutalBirdie @necrevistonnezr
i have been battling with this issue now for sometime. At some point it is good to go then next it crashes. I also try to do a new installation and check with different servers just to troubleshoot this but the issue is persistent.
Can you check this out ?? I guess some people are experiencing thesame issue without knowing exactly what it is
-
@joseph @BrutalBirdie @necrevistonnezr
i have been battling with this issue now for sometime. At some point it is good to go then next it crashes. I also try to do a new installation and check with different servers just to troubleshoot this but the issue is persistent.
Can you check this out ?? I guess some people are experiencing thesame issue without knowing exactly what it is