Removed
Moderator: crythias
-
crythias
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Postmaster-Errors after upgrading
> Message: POP3: Can't process mail, email no 14 is empty!
means you're competing for emails. (multiple attempts to POP/Delete)
>Incorrect string value:
May be collation (not utf-8) problem.
means you're competing for emails. (multiple attempts to POP/Delete)
>Incorrect string value:
May be collation (not utf-8) problem.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
crythias
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Postmaster-Errors after upgrading
but another machine may be also using POP. When it says email no 14 is empty!, it means it is empty and the only way it is empty is if your repository is bad or it's already been deleted.akcom_ag wrote:Concerning the Postmaster-thing, I am almost sure there is only one postmaster process (scheduler) running at a time...I took a brief look at the crontab of user otrs and everything looks fine.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
crythias
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Postmaster-Errors after upgrading
probably would be better if you got procmail to work and then you'd get tickets instantly.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
bminnix
- Znuny newbie
- Posts: 4
- Joined: 16 Sep 2013, 22:44
- Znuny Version: 3.1.11
- Real Name: Brandon
- Company: NetWolves
Re: Postmaster-Errors after upgrading
Was this ever resolved? I have a similar scenario though I'm not as informed on our update history etc, but I am getting similar error messages ever since enabling the Postmaster account so that we could Automatically create tickets off of emails.
This is the error:
About the only troubleshooting that I've done is to try changing between IMAPS and POPS for the mail account as the first messages showed IMAPS in place of the above POPS entries. So it doesn't matter whether I'm fetching from POPS or IMAPS I get the error. Aside from this, I do not know where to begin on continuing to troubleshoot this.
This is the error:
Code: Select all
ERROR: OTRS-otrs.PostMasterMailbox.pl-10 Perl: 5.10.1 OS: linux Time: Fri Sep 20 13:40:05 2013
Message: POP3S: Can't process mail, email no 2 is empty!
Traceback (2512):
Module: Kernel::System::MailAccount::POP3S::_Fetch (v1.13) Line: 224
Module: Kernel::System::MailAccount::POP3S::Fetch (v1.13) Line: 106
Module: Kernel::System::MailAccount::MailAccountFetch (v1.17) Line: 424
Module: main::Fetch (v1.4) Line: 180
Module: /opt/otrs/bin/otrs.PostMasterMailbox.pl (v1.4) Line: 93About the only troubleshooting that I've done is to try changing between IMAPS and POPS for the mail account as the first messages showed IMAPS in place of the above POPS entries. So it doesn't matter whether I'm fetching from POPS or IMAPS I get the error. Aside from this, I do not know where to begin on continuing to troubleshoot this.
-
bminnix
- Znuny newbie
- Posts: 4
- Joined: 16 Sep 2013, 22:44
- Znuny Version: 3.1.11
- Real Name: Brandon
- Company: NetWolves
Re: Postmaster-Errors after upgrading
Okay, thanks akcom_ag for the response on this.
We found our issue and resolved it.
We have 3 OTRS environments.
1. Production
2. Backup
3. Development
I had placed the postmaster account on the development environment first and tested w/out issues. This started about a day or two after I placed the postmaster account on the production environment. I checked that I had removed it from the development environment, however the backup had ran and placed the postmaster account on the backup environment along with the crontab that performs the 'fetch' function.
We have set up our backup process to replace the crontab with the original after the backup process completes and believe this will resolve the issue for us.
Thanks for all of your help.
We found our issue and resolved it.
We have 3 OTRS environments.
1. Production
2. Backup
3. Development
I had placed the postmaster account on the development environment first and tested w/out issues. This started about a day or two after I placed the postmaster account on the production environment. I checked that I had removed it from the development environment, however the backup had ran and placed the postmaster account on the backup environment along with the crontab that performs the 'fetch' function.
We have set up our backup process to replace the crontab with the original after the backup process completes and believe this will resolve the issue for us.
Thanks for all of your help.