Greetings,

I suspect that the problem is caused by not having all of the required
packages selected during the installation of FC4 x86_64.  In my
experience, missing (or incorrect versions of) libraries are almost
always the cause of "Premature end of script headers" errors.  Either
that, or corrupted binaries, but since this is compiled from a source
RPM, that's unlikely.

I'd try this:

1) create a domain and a couple of users using CLI tools in
/home/vpopmail/bin/

   /home/vpopmail/bin/vadddomain -q 10000000 test.coop password12345
   /home/vpopmail/bin/vadduser -q 5000000 -c "The Test User"
[EMAIL PROTECTED] password12345
   /home/vpopmail/bin/vdominfo test.coop

This will show you that the domain has been created.  Check to see that
the "dir:" directory has actually been created, and that the directory
permissions are correct.


2) run  /usr/share/qmailadmin/qmailadmin  from the CLI.

   /usr/share/qmailadmin/qmailadmin

This can often produce more information about the nature of whatever the
error is.  Oftentimes, when programs attempt to run, and detects missing
libraries, they print errors to STDOUT that apache doesn't forward to
the html stream -- output that may be present when running qmailadmin
from the command line.

If the 'strace' utility is not installed, install it (yum, or your local
RPM repository).  Try running the following and watch for errors.

   strace /usr/share/qmailadmin/qmailadmin | grep open

You'll see things like:  

   open("/usr/lib/mysql/libmysqlclient.so.14", O_RDONLY) = 3

If the required libraries aren't installed, this line, or the one under
it, should tell you.  Install them (yum, or your local RPM repository),
and try again.


Sincerely,
 

--
Joseph Lundgren
Systems Engineer
Peak Internet, LLC
[EMAIL PROTECTED]

-----Original Message-----
From: Istvan Kope [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 19, 2005 7:04 AM
To: [email protected]
Subject: Re: [qmailtoaster] qmailadmin doesn't strart

One more thing which might be important, about qtms-svcs.sh.
I ran it once and it cut me off :( and as I said I connected remotely
on the server. The server doesn't have screen nor keyboard and is on
the other side of the city.
About the firewall I droped it with lokkit --> disabled

I was looking in firewall.sh and I don't really understand much, but
anyway till this server is finished I want the firewall disabled. Is
that lokkit thing enoungh? Or do I need some of those weird iptables
commands?

On 10/19/05, Istvan Kope <[EMAIL PROTECTED]> wrote:
> I modified /etc/selinux/config
>
> # This file controls the state of SELinux on the system.
> # SELINUX= can take one of these three values:
> #       enforcing - SELinux security policy is enforced.
> #       permissive - SELinux prints warnings instead of enforcing.
> #       disabled - SELinux is fully disabled.
> SELINUX=disabled
> # SELINUXTYPE= type of policy in use. Possible values are:
> #       targeted - Only targeted network daemons are protected.
> #       strict - Full SELinux protection.
> SELINUXTYPE=targeted
>
> I run chmod -R 755 /usr/share/qmailadmin/
>
> Still doesn't work. Same errors...
> After I modified the selinux config do I have to restart something?
>
> On 10/19/05, Michael Hicks <[EMAIL PROTECTED]> wrote:
> > I also think you can check /etc/selinux/config to see if
> > SELINUX=disabled, which is what you want for ease of use. May also
want
> > to make sure that you have chmod 755 on the cgi scripts run in
/qmailadmin
> >
> > -Mike
> >
> > Jake Vickers wrote:
> >
> > > Do a 'rpm -q selinux' to see if it's installed or not.  SELinux
would
> > > stop applications from running over the Internet, and would have
been
> > > turned on when you installed FC - somewhere with the firewall
section
> > > there was an option to turn SELinux to ON,OFF,WARN.
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
[EMAIL PROTECTED]
> > For additional commands, e-mail:
[EMAIL PROTECTED]
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to