ShantaMcBain (User)
Posts: 5
|
| Failed to query Postfix config command to get the current value of parameter home_mailbox: 2007/02/17 01:06 |
|
|
Anyone got a fix for this one?
Failed to query Postfix config command to get the current value of parameter home_mailbox:
I am running the current versions of all webmin and GPL virtualmin modules on a debian serge system that I keep updated daily.
Thanks
Shanta
|
|
|
|
The administrator has disabled public write access. |
Joe (Admin)
Posts: 4117
|
| Re: Failed to query Postfix config command to get the current value of parameter home_mailbox: 2007/02/17 11:57 |
|
|
Hey Shanta,
This error indicates that postconf failed.
Does postconf run from the command line?
If so, check to be sure the Webmin Postfix module knows where to find it (in the Module Config, the option is labeled "Full path to Postfix config command").
If both of those things are true, then something is going wrong with the postconf command intermittently--maybe memory issues. I've seen this exact problem happen several times on various types of vserver, virtuozzo, and xen virtual systems, and it's always due to memory issues with those platforms. The workaround is to reduce memory usage, or increase available memory. (It's a bug in those platforms...but if you stay well under the available memory, you can probably get a stable system, though postconf is not the only thing that will run into problems.)
|
|
|
|
The administrator has disabled public write access. |
ShantaMcBain (User)
Posts: 5
|
| Re: Failed to query Postfix config command to get the current value of parameter home_mailbox: 2007/02/17 13:35 |
|
|
Hi Joe
Thanks for the responce
This error indicates that postconf failed.
>Does postconf run from the command line?
Don't know! The error happens when attempting to enter virtualmin server module.
>If so, check to be sure the Webmin Postfix module knows]where to find it (in the Module Config, the option is]labeled "Full path to Postfix config command").
This seems to be setup right the entry matches the location of the file.
>If both of those things are true, then something is going]wrong with the postconf command intermittently--maybe]memory issues. I've seen this exact problem happen several]times on various types of vserver, virtuozzo, and xen]virtual
I am on Redwoodvirtual which is a Linux virtual host.
>systems, and it's always due to memory issues with those]platforms. The workaround is to reduce memory usage, or]increase available memory. (It's a bug in those]platforms...but if you stay well under the available]memory, you can probably get a stable system, though]postconf is not the only thing that will run into]problems.)
in the running process
It memory as 125164 kB total / 80752. There is no swap file used by this vserver.
Reducing memory usage by Postfix did not seem to help.
I just guest at what to do here though.
I also turned of postgres to free more memory. I would assume that you are right about memory though as things where working before I got MySQL running. I will stop it as well and test.
Any other sugestions?
Shanta
|
|
|
|
The administrator has disabled public write access. |
ShantaMcBain (User)
Posts: 5
|
| Re: Failed to query Postfix config command to get the current value of parameter home_mailbox: 2007/02/17 13:37 |
|
|
Just turned of MYSQL but it did not help. Same problem.
Shanta
|
|
|
|
The administrator has disabled public write access. |
DenisMonsieur (User)
Posts: 1
|
| Re: Failed to query Postfix config command to get the current value of parameter home_mailbox: 2007/03/12 08:34 |
|
|
I'm having the same problem on Debian with current webmin/virtualmin versions. postconf runs fine from command line though.
I guess it has something to to with memory, but how can I be sure of that?
|
|
|
|
The administrator has disabled public write access. |
|
