Skip to main content

autoresponder causing errors

anewell
Hi there, We started seeing bounce emails generated when someone emails an account with an autoresponder active today, though it is not the same error as in

Comments

19 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! Just for fun, could you try rebuilding CageFS on that system? The last line of that output makes me wonder if that is involved somehow. If that doesn't work, could you check and see if removing a particular user from CageFS stops the issue from happening?
    0
  • anewell
    Hey there, I followed the procedure
    0
  • cPRex Jurassic Moderator
    Thanks for trying that. Do you have any server updates available that show up with the "yum update" command?
    0
  • anewell
    I did find a kernel update (3.10.0-962.3.2.lve1.5.70.el7.x86_64) available and have installed it, we'll need to schedule a reboot for the server and see if that's made any difference next. I'll update next when I'm able to, thanks.
    0
  • cPRex Jurassic Moderator
    I'm wondering if it could because that last line of the output mentions "kmod-lve" which is a kernel module.
    0
  • dexus
    I did find a kernel update (3.10.0-962.3.2.lve1.5.70.el7.x86_64) available and have installed it, we'll need to schedule a reboot for the server and see if that's made any difference next. I'll update next when I'm able to, thanks.

    Did kernel update resolved the issue?
    0
  • Serra
    It doesn't appear that the kernel version makes this better. I'm running the current kernel and still get the message.
    0
  • mtindor
    I have friends who run a hosting business, and their CL 7 boxes were experiencing this. They opened a ticket with CL, and CL told them to install latest kernel/reboot. The kernel update DID fix the autoresponder issue for them. You must update the kernel and reboot.
    0
  • mtindor
    Just got a notification from CloudLinux https://ci4.googleusercontent.com/proxy/rfcYW8491p-DYinwZC5JSG4h1eRbxjC-2GfZwEa6HmKpRfReEzfu6gxeplqh-VrNZgQg5vNbPuGKZXvU5VWe6ZxbxFMHee6prDvJNB1ccuQ8Sz5TMU0RwzkGZMXH-WUOxyUDwj5m1drja7Ozy5HNNKa0GYtw1lhwKRAIkVvzOjZiitZwY_MkL-wbmmqvAWjDr9OeK0Q68ukxNb35b6-bZoSqDzyrnMkZRo-7JS_S31g=s0-d-e1-ft#https://dka575ofm4ao0.cloudfront.net/assets/pages/manage/font_awesome_icons/operational-bd56b9a77953a492054b9fac76372f877402640990002ec53d717aa59e1d2d80.png
    CloudLinux OS Components - CageFS
    0
  • Serra
    I have friends who run a hosting business, and their CL 7 boxes were experiencing this. They opened a ticket with CL, and CL told them to install latest kernel/reboot. The kernel update DID fix the autoresponder issue for them. You must update the kernel and reboot.

    I'll reboot again tonight, but I'm showing the current kernel in KernelCare: Effective Kernel Version 3.10.0-962.3.2.lve1.5.70.el7
    0
  • mtindor
    I'll reboot again tonight, but I'm showing the current kernel in KernelCare: Effective Kernel Version 3.10.0-962.3.2.lve1.5.70.el7

    Not necessarily the same thing. Even if you were not running the most recent, you may see that message in KernelCare indicating it has been live-patched to the latest. But a reboot is necessary in all cases after an actual kernel update to fix this issue. Just having kernelcare patching is not enough apparently.
    0
  • Serra
    Not necessarily the same thing. Even if you were not running the most recent, you may see that message in KernelCare indicating it has been live-patched to the latest. But a reboot is necessary in all cases after an actual kernel update to fix this issue. Just having kernelcare patching is not enough apparently.

    Thanks. I'll give it a shot tonight.
    0
  • mtindor
    0
  • anewell
    I finally had a chance to reboot the server last night and can confirm that updating the kernel and rebooting resolved the issue.
    0
  • ldxsant
    I finally had a chance to reboot the server last night and can confirm that updating the kernel and rebooting resolved the issue.

    @anewell, good morning! Can you inform the updated Kernel version, please. I'm same problem.
    0
  • anewell
    @anewell, good morning! Can you inform the updated Kernel version, please. I'm same problem.

    Kernel version on our server (output from uname -rv) is currently: 3.10.0-962.3.2.lve1.5.70.el7.x86_64
    0
  • ldxsant
    Kernel version on our server (output from uname -rv) is currently: 3.10.0-962.3.2.lve1.5.70.el7.x86_64

    @anewell Thanks!
    0
  • sparek-3
    Not sure if my issue is related - I'm not using CloudLinux. I've been meaning to study this a bit more and make a post here. But I saw this one and thought I'd chime in. The issue I'm seeing seems to involve email messages that have a [font="courier new">[ or [font="courier new">] character(s) in their [font="courier new">From or [font="courier new">Reply-To headers (or maybe there are other headers that the autoresponder looks for?) When run directly the error message given is: [font="courier new">Use of uninitialized value in pattern match (m//) at bin/autorespond.pl line 118, line 67. Use of uninitialized value in lc at bin/autorespond.pl line 123, line 67. Again, not sure if it's at all related to this thread's specific issue. Didn't really mean to hijack a thread. But was quickly scouring through this forum and saw this and thought I'd mention it. I'll do some studying on this later, if anybody from cPanel thinks this is a separate issue, let me know, I'll start a new thread.
    0
  • cPRex Jurassic Moderator
    @sparek-3 - the issue here is specifically related to CloudLinux. We're tracking that on our end with UPS-472, but that's an "upstream" case and the CloudLinux case number has already been mentioned here. They'll get that resolved and then things will work as intended.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post