Submitted by sgrayban on Mon, 07/27/2009 - 03:42
Enabling php to run as virtual server owner the php.ini is not being created at all.
Status:
Closed (fixed)
Web Hosting and Cloud Computing Control Panels
Comments
Submitted by sgrayban on Mon, 07/27/2009 - 04:04 Comment #1
neither is the cgi wrapper
Submitted by JamieCameron on Mon, 07/27/2009 - 10:28 Comment #2
Do you get any error message during domain creation?
Also, is the source php.ini file under /etc world-readable?
Submitted by sgrayban on Mon, 07/27/2009 - 13:43 Comment #3
Well this is a odd issue. I can't pin down what's causing this. I think what happened is from the bug about moving domains that had no home and the parent domain not importing correctly because of that and what seemed to happen was the new id and gid where not created correctly and well the old id/group numbers were being used which crossed up because some of those #'s were already setup for other domains. If you follow that.....
Submitted by JamieCameron on Mon, 07/27/2009 - 13:50 Comment #4
So is this consistently re-producable for new virtual servers?
Submitted by sgrayban on Mon, 07/27/2009 - 14:11 Comment #5
I think so until the new virtualmin-server package is released. After I got the pre-release version I didn't have the same problems with the domain moves.
Submitted by JamieCameron on Mon, 07/27/2009 - 14:43 Comment #6
Oh, so the 3.70-9 pre-release version I sent you fixes this? Or causes it? :-)
Submitted by sgrayban on Mon, 07/27/2009 - 14:51 Comment #7
Fixed it.
Before I installed that version a lot of things were not working right. The GID was one the other was apache suexec directive wasn't getting changed to the right UID/GID and the files for each domain under virtualmin-server/domains/ wasn't getting edited correctly either.
After I installed that pre-release it seemed to work fine from the point on with domain moves.
Submitted by JamieCameron on Mon, 07/27/2009 - 14:54 Comment #8
Cool .. in that case, I will close this bug.
Submitted by sgrayban on Mon, 07/27/2009 - 14:59 Comment #9
I hope that is the case at least. This one was a bit hard to follow because so much was wrong but I know it was the GID that wasn't being properly created when the domains were imported.
Submitted by Issues on Mon, 08/10/2009 - 16:18 Comment #10
Automatically closed -- issue fixed for 2 weeks with no activity.