Problems with amavisd-new: cannot start the service

[Gustavo A. Díaz]

Binary package hint: amavisd-new

Hi Guys!

Since a few (3 days? or less..) I have experiencing Mail server problems.. and I've notice that since people was telling that they sent emails to me.. and those never came. So, I've searched some logs and i found this:

Starting amavisd: Error in config file "/etc/amavis/conf.d/05-domain_id": Insecure directory in $ENV{PATH} while running with -T switch at /etc/amavis/conf.d/05-domain_id line 7.

This is when i try to start amavisd-new, and i noticed this since postfix cannot filter emails:

Jul 24 01:13:05 servidor postfix/smtp[469]: 24AB785C77B: to=<gdiaz@xxxxxxxx>, relay=none, delay=42728, delays=42728/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

What is wrong¿? I cant remember if this or related package was upgraded these days... And i really want to get my server running again. I didn't find anything in the web.

Thanks.

[Gustavo A. Díaz (gdiaz)]

Forgot to mention that in the line that amavisd-new error suggest i only have:

chomp($mydomain = `head -n 1 /etc/mailname`);

[dar-gdnet (dar-gdnet)]

I am having the same problem since updating ...

[Scott Kitterman (kitterman)]

What release are you running and what is in /etc/mailname?

[Gustavo A. Díaz (gdiaz)]

Hardy as well and my /etc/mailname is servidor.gdnet.com.ar as always was...
nothing was changed in my system by me, and suddenly this started to happen.
I know that i've upgraded some packages in this past days. So is why i
wonder and ask this...

2008/7/24 Scott Kitterman <email address hidden>:

> What release are you running and what is in /etc/mailname?
>
> --
> Problems with amavisd-new: cannot start the service
> https://bugs.launchpad.net/bugs/251377
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

[Gustavo A. Díaz (gdiaz)]

Any news about this Guys? since i am having many spams if i have amavisd-new disabled...
And since i didn't change anything, i suspect this is a bug from Ubuntu or that package itselft...

I've googled about this and i get nothing.

[Scott Kitterman (kitterman)]

What is at /etc/amavis/conf.d/05-domain_id line 7?

[Gustavo A. Díaz (gdiaz)]

This what says in that line:

chomp($mydomain = `head -n 1 /etc/mailname`);

[FransAlmere (t-root-flfinancieel-nl)]

Is this problem solved, since this morning out of the blue I have the same problem.

I do not understand the mesage

Error in config file "/etc/amavis/conf.d/05-domain_id": Insecure directory in $ENV{PATH} while running with -T switch at /etc/amavis/conf.d/05-domain_id line 7.

I am using intrepid amavis 2.6.1.

in mailname is only the name of my server

Like to hear

[FransAlmere (t-root-flfinancieel-nl)]

Oh and before I forget I do not understand running with -T switch. What is trying to run with -T switch

[markop123 (markop)]

See if any of these directories are world writable:
ls -ld /
ls -ld /usr
ls -ld /bin
ls -ld /sbin
ls -ld /usr/bin
ls -ld /usr/sbin
ls -ld /usr/local
ls -ld /usr/local/bin
ls -ld /usr/local/sbin

http://<email address hidden>/msg02464.html

My problem was /usr/local/bin permission 777

Have a nice day
Marko

[Alex Muntada (alex.muntada)]

It's been a while since the last comment on this issue, can anyone confirm that the problem is still present? Thanks a lot.

[Alex Muntada (alex.muntada)]

About the -T switch it refers to the perl -T option (Perl tainted mode), see man perlrun for details.

[Gustavo A. Díaz (gdiaz)]

I still have this blacklisted as it continue with the freezes if not.

2010/1/27 Alex Muntada <email address hidden>

> About the -T switch it refers to the perl -T option (Perl tainted mode),
> see man perlrun for details.
>
> --
> Problems with amavisd-new: cannot start the service
> https://bugs.launchpad.net/bugs/251377
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

[Alex Muntada (alex.muntada)]

@Gustavo I just installed a fresh 8.04.04 (still being tested, to be released tomorrow IIRC) and amavisd-new doesn't argue about perl -T switch. Moreover, file /etc/amavis/conf.d/05-node_id has changed and now uses hostname command instead of tailing /etc/mailname.

Can you try it out when 8.04.04 is released?

[Gustavo A. Díaz (gdiaz)]

Ups.. sorry... i've replied in the wrong bug report.

2010/1/27 Gustavo A. Díaz <email address hidden>

> I still have this blacklisted as it continue with the freezes if not.
>
> 2010/1/27 Alex Muntada <email address hidden>
>
> About the -T switch it refers to the perl -T option (Perl tainted mode),
>> see man perlrun for details.
>>
>> --
>> Problems with amavisd-new: cannot start the service
>> https://bugs.launchpad.net/bugs/251377
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Gustavo A. Díaz
> GDNet Projects
> www.gdnet.com.ar
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

[Alex Muntada (alex.muntada)]

@Gustavo, can you confirm that this bug can we closed then? AFAICS it's been solved, but I'd like your opinion.

[Gustavo A. Díaz (gdiaz)]

Nope, I dont have it anymore in my current Kubuntu 9.10 server.

Cheers.

2010/1/29 Alex Muntada <email address hidden>

> @Gustavo, can you confirm that this bug can we closed then? AFAICS it's
> been solved, but I'd like your opinion.
>
> --
> Problems with amavisd-new: cannot start the service
> https://bugs.launchpad.net/bugs/251377
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Gustavo A. Díaz
GDNet Projects
www.gdnet.com.ar

[Alex Muntada (alex.muntada)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Noway2 (matt-noway2)]

I would like to add a note of confirmation that this "bug" is still alive. I updated my server to 9.10 (Karmic) this last Sunday and upon doing so noticed that amavis was not starting upon reboot. I could successfully issue a command 'sudo /etc/init.d/amavis start' and it would start without error. I scoured the logs and could not find any sort of indication as to the trouble. Normally, I have amavis listening on port 10024 for output from postfix. Neither the amavis processes appeared in a ps list nor was any process listening on this port.

I was able to 'resolve' this issue by explicitly setting $mydomain=my.fqdn in the amavis configruation file 50-user. I confirmed that undoing this setting resulted in a return of the problem and restoring it corrects the situation.

Further investigation in the mail.warn log shows that there was a potential problem at least a week prior to my updating to 9.10, but the situation suddenly corrected itself. I assume that this was due to a cron task restarting amavis.

I also located this post on ubuntu forums.org that lead me to the 'fix'. Apparently this was an issue several years ago, became a non-issue as I successfully ran a server for almost a year without it, and then became an issue again. Re:http://ubuntuforums.org/showthread.php?t=277838

I also encountered threads suggesting a problem with Perl updates and missing libraries, but these did not provide resolution.

[Alex Muntada (alex.muntada)]

Norway2, I just build a new karmic server from scratch and amavis service doesn't start by default unless the hostname is a FQDN. But an error is displayed on the console when this is the case (e.g. hostname being "karmic"):

Starting amavisd: head: cannot open `/etc/mailname' for reading: No such file or directory
  The value of variable $myhostname is "karmic", but should have been
  a fully qualified domain name; perhaps uname(3) did not provide such.
  You must explicitly assign a FQDN of this host to variable $myhostname
  in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
  network name!
(failed).

Either having /etc/mailname or defining a FQDN for the host is mandatory and service amavis states so quite clearly, IMHO. Could have happened that you missed this message above? In any case, if you still experience issues starting amavis i think a new, different bug should be open.

[kkumax (kkuma)]

As a result of trial in the cut -and-try！

# cd /etc/amavis/conf.d
#cat cat 05-domain_id
...........................
#chomp($mydomain = `head -n 1 /etc/mailname`);
chomp($mydomain = "kkuma.mydns.jp");
...........................

#cat 05-node_id
...........................
#chomp($myhostname = `hostname --fqdn`);
chomp($myhostname = "ubuntu.kkuma.mydns.jp --fqdn");
...........................

It works when you change as described above .

# hostname
ubuntu