These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for procmail log question on the new forum.
Hi,
I am hoping someone may know what the following logs mean, especially the excessive resource part and a fix? Thanks!
Subject: lfd on targetmyad.net: Excessive resource usage: postfix (3062)
Folder: /root/Maildir/new/1326479537.4795_0.targetmyad.net 662
Time:1326479537 From:root@targetmyad.net To:root@targetmyad.net User:root Size:714 Dest:/root/Maildir/new/1326479537.4795_0.targetmyad.net Mode:None
Subject: lfd on targetmyad.net: Excessive resource usage: apache (18677)
Folder: /root/Maildir/new/1326477798.3528_0.targetmyad.net 646
Time:1326477798 From:root@targetmyad.net To:root@targetmyad.net User:root Size:698 Dest:/root/Maildir/new/1326477798.3528_0.targetmyad.net Mode:None
Howdy,
Well, that's the subject of an email that was sent to the root user.
What does the message body look like for that email?
-Eric
I havent a clue unfortunately.. I thought there was a place in vmin to view users mail but i cant seem to find it!! argh!
Scott Kappler
You can view a users mail by going into Edit Users -> USERNAME -> Login to Usermin.
-Eric
ahhh...
Well, apparently its a cron error mssg... (a couple) I am used to cpanel so maybe i am calling the files incorrectly? The folder structure with vmin is completely different... but i would think these would be correct?
Scott Kappler
So i am looking at the files permissions as it isnt working due to this message: OR am i reading the last lines incorrectly? The perms are 755 for the cron.php file...
--2012-01-13 18:15:16-- http://targetmyad.com/marketer/admin/cron.php Resolving targetmyad.com... 98.142.218.10 Connecting to targetmyad.com|98.142.218.10|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 0 [text/html] cron.php: Permission denied
Cannot write to `cron.php' (Permission denied).
Scott Kappler
got it figured out - this was a migrated server - and was trying to run the cron job as "user" not "root"... changed to root and works. :)
Scott Kappler