• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

qmail unable to read control

A

AlbertS

Guest
Hello,

I experiance the following problem, its a clean 8.1 box, with FC4..

Qmail does not run, when starting it shows no error though log file gives following...

Jan 1 05:06:06 )*\377 sendmail[1911]: alias database /etc/aliases rebuilt by root
Jan 1 05:06:06 )*\377 sendmail[1911]: /etc/aliases: 76 aliases, longest 10 bytes, 765 bytes total
Jan 1 05:06:06 )*\377 sendmail[1915]: starting daemon (8.13.7): SMTP+queueing@01:00:00
Jan 1 05:06:06 )*\377 sm-msp-queue[1922]: starting daemon (8.13.7): queueing@01:00:00
Jan 1 05:58:28 )*\377 qmail: 1041397108.789783 alert: cannot start: unable to read controls


I can't find out what it causes, plz any assistance..

Regards,
Alb
 
I checked premissions, they seem to be ok.... reinstalled Qmail with force... (no errors...) but it keeps not working...

I set-up the box at my home network, changed the IP numbers at data center... Can that caused this problem?

edit.
Can this be caused by the php 5.1.4 version from the art unstable channel?

The problem seems to be OLD by google I find this problem in year 2000 etc. but no prober solutions...
 
Do I have a problem just nobody know's about?

Reinstall the box with the hope it does not pop up another time?

Even a little hunch would do good.... :(
 
Back
Top