"Use of uninitialized value $tag in string.." errors

RT Users
21

Can you check the inbox if there is an email hanging there, maybe RT is trying to receive/parse/process but fails? We had an issue with big emails failing to get processed by RT but it was sending out the confirmation emails with ticket numbers that never got created in the DB, long story short we had to increase FcgidIOTimeout (and the only thing pointing in that direction was a single line warning in apache logs, RT logs even on debug level had nothing), if the logs are referring to non-existent ticket IDs it is at least somewhat similar in that regard, maybe it is trying to process tickets that failed in the first place

22

I think I may be wrong about the log entries being ticket numbers. I took the “RT[xxxx]” to be a ticket number as it’s in the same format, but I think it may just be a log event number.

RT[92913]: [92913] Use of uninitialized value $tag in string eq at /usr/local/lib/perl5/site_perl/HTML/Element.pm line 2634.

23

Or possibly the process ID? I don’t know how BSD Unix does it’s logging.

24

Whelp, this is embarassing. I resolved the issue. Turns out there was an email in the inbox that RT was somehow failing to retrieve.

Fetchmail was still working fine, and the email question wasn’t blocking the mailbox for other emails. The email itself didn’t appear to be problematic or corrupt in anyway, and nothing in any of the logs pointed to it being an email issue. The only reason I found it was because I had decided to make a copy of the VM to mess with. I copied it, and edited the copy with a new IP address and name, and disabled fetchmail to avoid screwing with the production VM. In doing so, I discovered the copy didn’t have the issue.

I want to give a big thanks to both of you for continuing to help me with this issue.

Adam

25

Sounds very similar to an issue we had with wsgetmail getting stuck on an email (but still continued retrieving other mail). If I recall, adding the timeout option to the config file was the solution, as otherwise processes started stacking up.

Just figured I’d add this in case someone runs into a similar issue with wsgetmail & O365 mail retrieval. Anyways—glad you got it sorted.