Error Amavis Failed To Stop
Contents |
Importance Assigned to Milestone amavisd-new (Debian) Edit Fix Released Unknown debbugs #652026 You need to log in to change restart amavisd-new this bug's status. Affecting: amavisd-new (Debian) Filed here by: Serge Hallyn
Barracuda Deferred: Connect To 127.0.0.1[127.0.0.1]:10024: Connection Refused
When: 2012-02-22 Target Distribution Baltix BOSS Juju Charms Collection Debian Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu amavisd dead but subsys locked PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Fix Released Unknown Assigned to unknown Remote Watch None, the
Connect To 127.0.0.1[127.0.0.1]:10025: Connection Refused
status of the bug is updated manually. None, the status of the bug is updated manually. Debian Bug tracker #652026 URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. This information was last pulled on 2016-10-05. Comment on this change (optional) Email me about changes to this status=deferred (connect to 127.0.0.1[127.0.0.1]:10026: connection refused) bug report amavisd-new (Ubuntu) Edit Fix Released High James Page Edit You need to log in to change this bug's status. Affecting: amavisd-new (Ubuntu) Filed here by: albatros When: 2012-02-12 Confirmed: 2012-02-22 Assigned: 2012-03-13 Started work: 2012-05-22 Completed: 2012-05-22 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Fix Released High Assigned to Me James Page (james-page) Comment on this change (optional) Email me about changes to this bug report Precise Fix Released High James Page Edit Ubuntu ubuntu-12.04.1 You need to log in to change this bug's status. Affecting: amavisd-new (Ubuntu Precise) Filed here by: James Page When: 2012-05-22 Confirmed: 2012-05-22 Assigned: 2012-05-22 Started work: 2012-05-22 Completed: 2012-06-01 Package (Find…) Status Importance Milestone Fix Released High Ubuntu ubuntu-12.04.1 Assigned to Me James Page (james-page) Comment on this change (optional) Email me about changes to this bug repo
Post #1 of 3 (719 views) Permalink amavisd: running or not running??? Hi Gentoo-users, I have this strange problem: I can not start amavisd because it is running, and
(delivery Temporarily Suspended: Connect To 127.0.0.1[127.0.0.1]:10024: Connection Refused)
at the same time I can not stop amavisd because it is not
Starting Amavisd Failed
running. How's that possible? vs4 ~ # /etc/init.d/amavisd start * WARNING: amavisd has already been started vs4 ~ # /etc/init.d/amavisd stop job for amavis.service failed * Stopping amavisd-new ... The amavisd daemon is not running [ !! ] * ERROR: amavisd failed to stop vs4 ~ # /etc/init.d/amavisd start * WARNING: amavisd has already been started vs4 ~ # https://bugs.launchpad.net/bugs/930916 ps -e | grep amavis vs4 ~ # How can I fix this mess? Jarry -- _______________________________________________________________ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted. u.schutz at bluewin Apr5,2015,11:09AM Post #2 of 3 (706 views) Permalink Re: amavisd: running or not running??? [In reply to] On 04/05/15 14:57, Jarry wrote: > Hi Gentoo-users, > > I have this strange problem: http://www.gossamer-threads.com/lists/gentoo/user/300308 I can not start amavisd because > it is running, and at the same time I can not stop amavisd > because it is not running. How's that possible? > > vs4 ~ # /etc/init.d/amavisd start > * WARNING: amavisd has already been started > vs4 ~ # /etc/init.d/amavisd stop > * Stopping amavisd-new ... > The amavisd daemon is not running [ !! ] > * ERROR: amavisd failed to stop > vs4 ~ # /etc/init.d/amavisd start > * WARNING: amavisd has already been started > vs4 ~ # ps -e | grep amavis > vs4 ~ # > > How can I fix this mess? > > Jarry > /etc/init.d/amavisd zap Urs dan at redchops Apr6,2015,2:00PM Post #3 of 3 (696 views) Permalink Re: amavisd: running or not running??? [In reply to] On 4/5/2015 1:57 PM, Jarry wrote: > Hi Gentoo-users, > > I have this strange problem: I can not start amavisd because > it is running, and at the same time I can not stop amavisd > because it is not running. How's that possible? > > vs4 ~ # /etc/init.d/amavisd start > * WARNING: amavisd has already been started > vs4 ~ # /etc/init.d/amavisd stop > * Stopping amavisd-new
New Member Hello, I am using FC15 and following the tutorial for setting up Postfix. I have run into a bit of a dilemma and I have been searching all over the place to try to find an answer. Sorry for the lengthy post, but I figured I'd tell my https://www.howtoforge.com/community/threads/issues-with-amavisd-new-wont-start.54393/ tale so that everyone can see where I've been; this way I won't be told to go http://serverfault.com/questions/599405/disable-clamav-for-amavis there again. I installed amavisd-new and clamav as per Page 4 of the tutorial. I changed the settings in amavisd.conf as instructed (entering my correct server information, of course). When I entered the command to start amavisd, I was presented with the following error: Code: Starting amavisd (via systemctl): Job failed. See system logs and 'systemctl status' for details. [FAILED] I noticed it did not give connect to me a log to check. So I went to /var/log and looked at the messages log, where I got this Code: Oct 2 00:35:14 server systemd[1]: amavisd.service: control process exited, code=exited status=255 Oct 2 00:35:14 server systemd[1]: Unit amavisd.service entered failed state. I searched for the above error string, only to be sent to articles about what status 255 means and not answering my question. The Force guided me to run Code: # cd /etc/init.d # amavisd (note the absence of 'start') At connect to 127.0.0.1[127.0.0.1]:10024: first it told me that the file /etc/amavisd.conf did not exist and that the script was failing at line 1795 in /usr/bin/amavisd. So, I went to edit said script file, only to find that the variable was set by another file (or at least it appeared to be. Searching for $config_file only sent me on an endless circle with nowhere to set the file path to the conf file). So, I created a symbolic link to point to /etc/amavisd/amavisd.conf; I then ran the amavisd command above again. Apparently $myhostname needed to be a FQDN and did not like my machine's name, which was simply 'server.' Funny, I don't remember that being in the tutorial. I should probably add that I've followed similar tutorials for the previous versions of Fedora and never had amavisd give me this problem. Anyway, I did as requested by amavis: I uncommented the line and entered a FQDN in $myhostname and commanded Fedora to start the flippin' program: Code: # /etc/rc.d/init.d/amavisd start I about threw the screen out the window when the error message about it failing came up again, but this time the code was 102. However, I remembered my Jedi training and did not give in to the Dark Side. So, I went and looked in the messages log... No new error entry there... I looked in maillog, and behold! Amavis created the BDB in /var/spool/amavisd, and all other kinds of activities (PERL modules loading)... But wait, Fedora told me the proce
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Disable ClamAV for Amavis up vote 2 down vote favorite I have a Postfix mail server, using Amavis and Spamassassin to check for unwanted e-mails. I have removed ClamAV because it'd basically freeze the whole server every time someone received an e-mail, and server-side virus-scanning does not seem to important for my use case. Spamassassin is still triggered by Amavis, and I'd like to keep it that way. Basically what I want is for Amavis to stop trying to trigger a virusscan for each e-mail. May 29 07:49:14 robinj amavis[19859]: (19859-01) (!)connect to /tmp/clamd.socket failed, attempt #1: Can't connect to UNIX socket /tmp/clamd.socket: No such file or directory May 29 07:49:15 robinj amavis[19859]: (19859-01) (!)connect to /tmp/clamd.socket failed, attempt #1: Can't connect to UNIX socket /tmp/clamd.socket: No such file or directory May 29 07:49:15 robinj amavis[19859]: (19859-01) (!)ClamAV-clamd: All attempts (1) failed connecting to /tmp/clamd.socket, retrying (2) May 29 07:49:21 robinj amavis[19859]: (19859-01) (!)connect to /tmp/clamd.socket failed, attempt #1: Can't connect to UNIX socket /tmp/clamd.socket: No such file or directory May 29 07:49:21 robinj amavis[19859]: (19859-01) (!)ClamAV-clamd av-scanner FAILED: run_