Apache's failing because of FollowSymlinks in 2.4.48

Hmm.. after an upgrade of httpd the problem came back again. Looks like somehow a ./build rewrite_confs put the UNIT_PROXY thing back in all user's configs :(
 
Even after doing all of this and getting Apache back up and running.. .none of my sites will load. Working on it...

Can't ping any domains on the server from CL on the server... hmmmm

Can't ping the IP for the domains.. .I'm wondering if I didn't have a bad yum update earlier... working on it.

PROBLEM: All of my IP addresses were somehow blown out of the linux network config.. .how the hell this happened is beyond me. After 25 years of doing this stuff I've never seen that happen.

FIX: For some damn reason startips wasn't getting started at bootup. I'll post it elsewhere. The fix of course is service startips restart.
 
Last edited:
The problem persist for me on one server
I have: 2.0.0 (rev: 2737)
And after httpd update it wont start and i see error: Invalid command '|UNIT_PROXY|
After doing this => sed -i '/|UNIT_PROXY|/d' /usr/local/directadmin/data/users/*/httpd.conf
all is up and running... but i dont get it why it is not in last version of CB ?
 
TestUser said:
The problem persist for me on one server
I have: 2.0.0 (rev: 2737)
And after httpd update it wont start and i see error: Invalid command '|UNIT_PROXY|
After doing this => sed -i '/|UNIT_PROXY|/d' /usr/local/directadmin/data/users/*/httpd.conf
all is up and running... but i dont get it why it is not in last version of CB ?
Click to expand...
Have you done /usr/local/directadmin/directadmin p ?
 
stefantriep said:
Have you done /usr/local/directadmin/directadmin p ?
Click to expand...
I dont know what this command dose?
But there is an interesting thing
if i do
/usr/local/directadmin/directadmin v
i get 1.62.5
but in DA web CB i see 2.0.0 (rev: 2737)
!?
 
TestUser said:
But there is an interesting thing
if i do
/usr/local/directadmin/directadmin v
i get 1.62.5
but in DA web CB i see 2.0.0 (rev: 2737)
!?
Click to expand...
You have 2 things, you have DirectAdmin and you have CustomBuild (CB)

In DirectAdmin you could have CB 1.0 in the past, but new installs come with CB 2.0.
CustomBuild makes versions of included software able to update within DirectAdmin

DirectAdmin p sets the right file permissions so DirectAdmin can filter out the UNIT_PROXY thing

Usage: ./directadmin [c|s|d|v|p|i|r|o|b(#)][set name value (restart)]
c : shows the values in the config file to make sure they were read in correctly
s : prints out where the program is slowing without forking. For Debugging only.
d : run as a daemon (required for init.d scripts)
v : prints the current program version and quits
p : set file permissions
i : run the program installer
r : runs as Deamon, but saves requests to file (debugging)
o : Shows which OS this binary is compiled on, and when.
b(#) : Dumps some debug info to stdout. # is optional debug level,eg b5
 
Had to do the: sed -i '/|UNIT_PROXY|/d' /usr/local/directadmin/data/users/*/httpd.conf again today after server update..
Tried everything, rebuilding using info in this topic, but the problem came back. After this command systemctl restart httpd and all is good again.
Is there a real true permanent way to fix this? Or am i missing something?
 
Fresh install today due to file system corruption. Having this issue. Tried Centos 8 and 7, multiple installs, followed things posted in this thread to the best of my ability :-( No dice.
 
You must log in or register to reply here.
Back
Top