Upon creation of user apache freezes

Wunk

Verified User
Joined
Sep 25, 2003
Messages
110
Since today we have the issue that when creating a new user, apache suddenly freezes..

It looks like it's running fine, but it will not answer any socket calls, there's nothing in the error log for apache, all that I could find in the directadmin error.log is:

2005:10:14-17:10:10: Auth::passValid: unable to get user_info for Harro Lowie
2005:10:14-17:24:13: Unable to lstat /dev/null/mail : Not a directory
2005:10:14-17:29:07: Unable to lstat /dev/null/mail : Not a directory
2005:10:14-17:50:02: Unable to create ~/.shadow in
2005:10:14-17:52:12: Unable to create ~/.shadow in
2005:10:14-17:54:08: Unable to create ~/.shadow in
2005:10:14-18:09:03: Default Domain not found or else there were no domains for user harro.

Apache will not work again until we remove this user, we checked if we could find anything fishy, but it's just the average user on the shared IP..

Anyone got any idea what might be going wrong here ?
 
I had that on 4 servers - after endless
searching (was in a bit of a hurry), tried
rebuild everything using customapache
on one server. this worked and
back to normal.

quickly did this on the other three,
and all work fine. something updated,
I think, no idea what broke, but
sometimes just have to work quickly
and may never find the cause now ...

I did notice that the only items
missing in the ' new user's ' homedir
were .spamassassin and .shadow
which interestingly have group=mail
the others have group=username, of course...

(nb - one of the servers was new, had arrived
last week, and i'd only setup pf firewall on it,
had done nothing else till today.....)
 
Last edited:
There's already 800-sih customers on this server, I tried an apache rebuild, but that didn't work (i'll have to try a build update still)

ANd yeah, I noticed the .shadow (hence the error) missing, not the .spamassassin, it's reall odd, we had this with 3 accounts over and over, but 2 later not at all..
 
I finally found out what the problem was, it's odd that I haven't apache complain about it, but it ended up to be the maximum file descriptors apache is able/allowed to open..

I added fs.file-max=131072 to the /etc/sysctl.conf, increased it live with /sbin/sysctl -w fs.file-max=131072

Then I edited /usr/include/bits/typesizes.h and set
#define __FD_SETSIZE 32768

(this was set to 1024)

Then I recompiled customapache (build clean, build all) and the problem was solved..
 
Back
Top