Vhosts...conf not synced to changes

[crypted]

Yes, but ISPCONFIG in the /sv/ispconfig_wconf exports its own path anyway does it not? So when the script is executed, it ought to know the proper paths.

I'm using CentOS 5.4.

Any idea how to resolve this?

# ISPConfig writeconf
#     
###################################

export PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin

[crypted]

And, I'm using ISPCONFIG 2.2.35 I believe. The latest in the 2.x branch I know that much.

I changed from TCSH to BASH for path reasons.

[root@its ispconfig]# /root/ispconfig/php/php /root/ispconfig/scripts/writeconf.php
start
Segmentation fault
[root@its ispconfig]#

LOG

[root@its ispconfig]# /root/ispconfig/php/php /root/ispconfig/scripts/writeconf.php
start
Segmentation fault
[root@its ispconfig]#

I then executed the MYSQL command to reload the entire database for ISPCONFIG to update all files. I ran the writeconf.php again and got the following:

[root@its ispconfig]# rm -rf .ispconfig_lock 
[root@its ispconfig]# /root/ispconfig/php/php /root/ispconfig/scripts/writeconf.php
start
UPDATE: 1
UPDATE: 3
UPDATE: 4
UPDATE: 5
UPDATE: 6
UPDATE: 52
UPDATE: 117
UPDATE: 116
UPDATE: 51
UPDATE: 127
UPDATE: 125
UPDATE: 128
UPDATE: 25
UPDATE: 49
UPDATE: 113
UPDATE: 104
UPDATE: 115
UPDATE: 122
UPDATE: 59
UPDATE: 68
UPDATE: 107
UPDATE: 109
UPDATE: 100
UPDATE: 105
UPDATE: 108
UPDATE: 119

Warning: symlink(): File exists in /root/ispconfig/scripts/lib/config.lib.php on line 940
UPDATE USER: 184
UPDATE USER: 205
UPDATE USER: 209
UPDATE USER: 191
UPDATE USER: 212

Warning: symlink(): File exists in /root/ispconfig/scripts/lib/config.lib.php on line 940
UPDATE USER: 214
UPDATE USER: 38
UPDATE USER: 211
UPDATE USER: 41
UPDATE USER: 42
UPDATE USER: 43
UPDATE USER: 189
UPDATE USER: 188
UPDATE USER: 210
UPDATE USER: 94
UPDATE USER: 59
UPDATE USER: 202
UPDATE USER: 222
UPDATE USER: 63
UPDATE USER: 226
UPDATE USER: 182
UPDATE USER: 80
UPDATE USER: 83
UPDATE USER: 84
UPDATE USER: 192
UPDATE USER: 90
UPDATE USER: 204
UPDATE USER: 171
UPDATE USER: 101
UPDATE USER: 117

Warning: symlink(): File exists in /root/ispconfig/scripts/lib/config.lib.php on line 940
UPDATE USER: 193
UPDATE USER: 190

Warning: symlink(): File exists in /root/ispconfig/scripts/lib/config.lib.php on line 940
UPDATE USER: 169
UPDATE USER: 170
UPDATE USER: 219
UPDATE USER: 187
UPDATE USER: 185
UPDATE USER: 186
UPDATE USER: 218
UPDATE USER: 223
UPDATE USER: 225
UPDATE USER: 227
Segmentation fault

ISPCONFIG log file has same error as before:

02.04.2010 - 13:10:33 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 2669: WARNING: could not httpd -t  &> /dev/null    
02.04.2010 - 13:10:33 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 2681: httpd syntax seems to contain errors, reload$
02.04.2010 - 13:10:33 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 2682: mv -f /etc/httpd/conf/vhosts/Vhosts_ispconfi$
02.04.2010 - 13:10:33 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 2683: mv -f /etc/httpd/conf/vhosts/Vhosts_ispconfi$
02.04.2010 - 13:10:34 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_system.lib.php, Line 755: /etc/rc.d/init.d/httpd relo$

[falko]

Can you try this?

ln -s /usr/sbin/httpd /usr/bin/httpd

[crypted]

Didn't resolve it

[root@its dingle]# ln -s /usr/sbin/httpd /usr/bin/httpd
[root@its dingle]#
[root@its ispconfig]# /root/ispconfig/php/php /root/ispconfig/scripts/writeconf.php
start
Segmentation fault
[root@its ispconfig]#

The log says:

03.04.2010 - 12:31:30 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 289: postmap hash:/etc/postfix/$
03.04.2010 - 12:31:30 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 1268: cp -fr /etc/httpd/conf/vhosts/Vhosts_ispconf$
03.04.2010 - 12:31:30 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 2669: WARNING: could not httpd -t  &> /dev/null    
03.04.2010 - 12:31:30 => WARN - /root/ispconfig/scripts/lib/config.lib.php, Line 2681: httpd syntax seems to contain errors, reload$
03.04.2010 - 12:31:30 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 2682: mv -f /etc/httpd/conf/vhosts/Vhosts_ispconfi$
03.04.2010 - 12:31:30 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 2683: mv -f /etc/httpd/conf/vhosts/Vhosts_ispconfi$
03.04.2010 - 12:31:31 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_system.lib.php, Line 755: /etc/rc.d/init.d/httpd relo

[crypted]

After deleting some old sites and all that, and forcing a rewrite from the DB to all files, I still get the Segmentation fault. However, no errors in the ispconfig.log file.

[root@its ispconfig]# rm -rf .ispconfig_lock 
[root@its ispconfig]# /root/ispconfig/php/php -q /root/ispconfig/scripts/writeconf.php
start
Segmentation fault
[root@its ispconfig]#

03.04.2010 - 14:33:04 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 137: cp -fr /etc/postfix/local-$
03.04.2010 - 14:33:04 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 284: cp -fr /etc/postfix/virtus$
03.04.2010 - 14:33:04 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 289: postmap hash:/etc/postfix/$
03.04.2010 - 14:33:04 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 1268: cp -fr /etc/httpd/conf/vhosts/Vhosts_ispconf$
03.04.2010 - 14:37:06 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 137: cp -fr /etc/postfix/local-$
03.04.2010 - 14:37:06 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 284: cp -fr /etc/postfix/virtus$
03.04.2010 - 14:37:06 => INFO - /root/ispconfig/scripts/lib/classes/ispconfig_postfix.lib.php, Line 289: postmap hash:/etc/postfix/$
03.04.2010 - 14:37:06 => INFO - /root/ispconfig/scripts/lib/config.lib.php, Line 1268: cp -fr /etc/httpd/conf/vhosts/Vhosts_ispconf$

So it's segfaulting somewhere else towards the end of its script I guess??? ....

[falko]

Hm, hard to say what could cause the segmentation fault - it could even be a hardware problem (RAM, etc.)...

[crypted]

Tested all hardware. No errors.

[createch]

If I were you, I will either

a) replace the RAM with a new/reliable one (e.g. Kingston RAM), and re-test.
[Segmentation fault are usually caused by bad RAM. A simple RAM check may not be able to reveal the fault];

or --- if you are 100% sure that there is no hardward fault, then

b) backup all your data, reinstall the Linux STRICTLY following the perfect server setup guide and then reinstall the ISPconfig -- latest version. Then
--- do not restore your data yet, try to create a few new sites, see whether the httpd, ftp, email, webmail are all fine, if so (of course it should be unless there is hardware problem) , then
--- restore your backup data, test whether the problem is gone.

[crypted]

1. I'll have them swap out the RAM tonight. Further, after installing the RAM, should I do a recompile/upgrade install of ISPCONFIG? Or, should I just let it go and see if it works without changing it?

2. If I redo the OS, I'm going to go x64 this time around. Also, I'll redo all of ISPCONFIG as I've been using the same DB on several upgrades of CentOS and ISPCONFIG for three years. Would it be worthwhile and advisable to just go with ISPCONFIG 3.x? I haven't seen screen shots or anything for it. All I can find is info on 2.x.

[createch]

For (1) -- after reinstalling a good and reliable RAM, no need to recompile and just let us know whether some (if not all) of the problems have been solved automatically.

For (2) --- I believe your server is running ISPconfig 2. There is up to the present moment no direct migration from ISPconfig 2 to ISPconfig 3. If you go for ISPConfig 3, then you need to manually reinstall everything (re-create user accounts, reset the password... lots of things to do). If your server supports many clients then you can expect the number of things you need to do, the number of users you need to notify, etc. [For me I cannot afford such a change, but it depends on your own situation]