Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: red hat *, fedora core *, gentoo, slackware, ubuntu
Posts: 27
Rep:
mailq gets "Segmentation fault" (fedora core 5)
Hi all,
Im on a postfix server running fedora core 5. I logged in because there are e-mail problems. So i wanted to check the mailq, but then i get the Segmentation fault error.
So i check out the status of the postfix deamon, it says Master stopped. Well ok thats fine with me, ill restart it.
I don't use postfix myself, but here are a few quick bits of information and some suggestions to get you started...
First off, a "Segmentation Fault" means that a program has accessed an area of memory it was not supposed to access. This is like a GPF in Windows, and it's a hard crash.
Based on the log segment you posted, it sounds like there might be a problem with your /etc/postfix/aliases file. I would take a look and see if the file is corrupted. Maybe there's a character in there it doesn't like, or maybe two lines got accidentally joined together. The fact that it's in /etc means it's probably a text file, so I would look at it with "less" and see if you see some suspicious characters.
If everything looks okay there (and in case I'm totally misreading this log segment, which I think I might be), there might be an email in the queue which is badly formed, and maybe that's causing the crash. You would have to find out where postfix has it's incoming mail queue and look through the emails and see if something looks amiss. Any character that isn't a normal printable character might cause a problem. Postfix might keep incoming emails as separate files, and if you see a message that looks wrong, try deleting that file or moving it somewhere else and try starting postfix again. Qmail, the mail system I use, can have multiple files in different places for one incoming email, so you might have to hunt around if that is the case in postfix.
Distribution: red hat *, fedora core *, gentoo, slackware, ubuntu
Posts: 27
Original Poster
Rep:
Thnx guys for the fast reply's and i did had some use from it.
But there was a surprise.
The error that postfix isnt correct, there are no problems with memory.
This server is deliverd and installed by me, but the customer has root access to. yea i know not great.
The customer changed the hostname, but he did not did this the right way. When i did a hostname -s or -f it sayd unknown hostname. Postfix does a hostname check and it gets the wrong info, there even are some spaces in the output. The space in the output gives postfix a reason to think that there is a segmentation error.
When i did a hostname -s or -f it sayd unknown hostname. Postfix does a hostname check and it gets the wrong info, there even are some spaces in the output. The space in the output gives postfix a reason to think that there is a segmentation error.
So i fixed it
But how? I've checked a couple of resources online, and I, too, get the same error and hostname -s gives me unknown hostname...
I tried hostname myname.domain.com
then edited /etc/sysconfig/network
Code:
NETWORKING=yes
HOSTNAME=myname.domain.com
/etc/hosts
Code:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 domain.com myname localhost.localdomain localhost
Still the hostname doesn't want to change. I'm running Fedora Core2... Please help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.