Well through a combination of things the problem is solved. After deleting the 
domain, I verified the domain folder was deleted, the domain table was deleted, 
and all records for the domain were deleted from the dir_control table. I then 
ran qmail-newu and recreated the domain with vadddomain. That seemed to fix the 
problem for that domain.
 
I was able to recreate the problem by creating, then deleteing, recreating a 
domain in vqadmin. If I do that the problem is recreated. The only way to then 
recreate the domain, which can be managed by vqadmin and qmailadmin is by 
following the steps above.
 
Thank you everyone for all of your help. 


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Mon, 10 Dec 2007 02:15:19 
+0100Subject: Re: [qmailtoaster] VQADMIN Problem



Did you also check the table dir_control ?
 
JP

----- Original Message ----- 
From: James Ecker 
To: [email protected] 
Sent: Sunday, December 09, 2007 8:45 PM
Subject: RE: [qmailtoaster] VQADMIN Problem
I have looked through the two different mySQL tables, besides the obvious there 
is no difference between the tables. Because there is no difference between the 
two tables, I have to assume there is some other location vpopmail is keeping 
track of the domains. I have backed up the non working domain data and 
recreated the table manually then restored the data, but that did not help.


From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Sun, 9 Dec 2007 20:08:54 
+0100Subject: RE: [qmailtoaster] VQADMIN Problem





Ok this does not help much for now, but it seems something goes wrong right 
after the query to dir_control.
Guess you should check if there are differences in the entry for a domain that 
works and one that does not..
 
JP
 


From: James Ecker [mailto:[EMAIL PROTECTED] Sent: zondag 9 december 2007 
16:50To: [EMAIL PROTECTED]: RE: [qmailtoaster] VQADMIN Problem
 
Thank you for you reply. The strace out put from two different domains, one 
that works and one that does not work, are shown below. The only difference I 
can see is the --- SIGSEGV (Segmentation fault) @ 0 (0) ---+++ killed by 
SIGSEGV +++ Here is the last few lines of out put of the domain that does not 
have a problem. fstat(6, {st_mode=S_IFREG|0644, st_size=2468, ...}) = 
0mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x2aaaaaabf000read(6, "veggiesoft.com\00089\00089\0/home/vpopm"..., 4096) = 
150close(6)                                = 0munmap(0x2aaaaaabf000, 4096)      
      = 0fstat(5, {st_mode=S_IFREG|0644, st_size=311, ...}) = 0mmap(NULL, 4096, 
PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aaaaaabf000read(5, 
"+pdgproduce.com-:pdgproduce.com:"..., 4096) = 311fstat(1, 
{st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0mmap(NULL, 4096, 
PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x2aaaaaac0000write(1, "domain: test123.com\n", 23domain: test123.com) = 
23write(1, "uid:    89\n", 11uid:    89)            = 11write(1, "gid:    
89\n", 11gid:    89)            = 11write(1, "dir:    
/home/vpopmail/domains/t"..., 46dir:    /home/vpopmail/domains/test123.com) = 
46poll([{fd=4, events=POLLIN|POLLPRI}], 1, 0) = 0write(4, "\1\0\0\0\16", 5)     
         = 5read(4, "\7\0\0\1\0\0\0\2\0\0\0", 16384) = 11poll([{fd=4, 
events=POLLIN|POLLPRI}], 1, 0) = 0write(4, "\375\0\0\0\3select cur_users, 
level_cur"..., 257) = 257read(4, 
"\1\0\0\1\20F\0\0\2\3def\10vpopmail\vdir_contr"..., 16384) = 1289write(1, 
"users:  0\n", 10users:  0)             = 10poll([{fd=4, 
events=POLLIN|POLLPRI}], 1, 0) = 0write(4, "\1\0\0\0\16", 5)              = 
5read(4, "\7\0\0\1\0\0\0\2\0\0\0", 16384) = 11poll([{fd=4, 
events=POLLIN|POLLPRI}], 1, 0) = 0write(4, ":\1\0\0\3replace into dir_control ( 
"..., 318) = 318read(4, "\7\0\0\1\0\2\0\2\0\0\0", 16384) = 11read(5, "", 4096)  
                     = 0close(5)                                = 
0munmap(0x2aaaaaabf000, 4096)            = 0poll([{fd=4, 
events=POLLIN|POLLPRI}], 1, 0) = 0write(4, "\1\0\0\0\1", 5)               = 
5shutdown(4, 2 /* send and receive */)   = 0close(4)                            
    = 0exit_group(0)                           = ?  Here is the last few lines 
of out put of the domain that has a problem. fstat(6, {st_mode=S_IFREG|0644, 
st_size=2468, ...}) = 0mmap(NULL, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aaaaaabf000read(6, 
"pdgproduce.com\00089\00089\0/home/vpopm"..., 4096) = 396close(6)               
                 = 0munmap(0x2aaaaaabf000, 4096)            = 0fstat(5, 
{st_mode=S_IFREG|0644, st_size=311, ...}) = 0mmap(NULL, 4096, 
PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aaaaaabf000read(5, 
"+testing.com-:testing.com:"..., 4096) = 311fstat(1, {st_mode=S_IFCHR|0620, 
st_rdev=makedev(136, 0), ...}) = 0mmap(NULL, 4096, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aaaaaac0000write(1, "domain: 
testing.com\n", 23domain: testing.com) = 23write(1, "uid:    89\n", 11uid:    
89)            = 11write(1, "gid:    89\n", 11gid:    89)            = 
11write(1, "dir:    /home/vpopmail/domains/t"..., 46dir:    
/home/vpopmail/domains/testing.com) = 46poll([{fd=4, events=POLLIN|POLLPRI}], 
1, 0) = 0write(4, "\1\0\0\0\16", 5)              = 5read(4, 
"\7\0\0\1\0\0\0\2\0\0\0", 16384) = 11poll([{fd=4, events=POLLIN|POLLPRI}], 1, 
0) = 0write(4, "\375\0\0\0\3select cur_users, level_cur"..., 257) = 257read(4, 
"\1\0\0\1\20F\0\0\2\3def\10vpopmail\vdir_contr"..., 16384) = 1289--- SIGSEGV 
(Segmentation fault) @ 0 (0) ---+++ killed by SIGSEGV +++



From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Sun, 9 Dec 2007 12:37:54 
+0100Subject: Re: [qmailtoaster] VQADMIN Problem

You could try a strace vdominfo

It should bail out with some more info.

 

JP

 


----- Original Message ----- 

From: James Ecker 

To: [email protected] 

Sent: Sunday, December 09, 2007 6:40 AM

Subject: RE: [qmailtoaster] VQADMIN Problem

 
Thank you everyone for your help. I think I have gotten a little closer to 
fixing the problem. When I run a vdominfo I get the following problem: domain: 
test.comuid:    89gid:    89dir:    /home/vpopmail/domains/test.comSegmentation 
faultAfter looking this problem up on Google, the only solution I found was to 
review the vpasswd file. Are there any other suggestions? Does anyone know 
where the vpasswd file is located? James



Get the power of Windows + Web with the new Windows Live. Power up! 
 



Get the power of Windows + Web with the new Windows Live. Power up!

You keep typing, we keep giving. Download Messenger and join the i’m Initiative 
now. Join in! 
_________________________________________________________________
Your smile counts. The more smiles you share, the more we donate.  Join in.
www.windowslive.com/smile?ocid=TXT_TAGLM_Wave2_oprsmilewlhmtagline

Reply via email to