Topic: Boot problems caused by httpd.conf

[loejf]

Hi.
After trying to resolve problems caused by 19. april update, I did run the command
 yum update --enablerepo=smecontribs
But it failed on doing it, and now my server is not able to boot up correctly.

It fails on booting telling that some misspellings in httpd.conf is causing this, and it just loops this message.

Can anyone please help.

Best regards Loejf.

[cactus]

After trying to resolve problems caused by 19. april update, I did run the command
 yum update --enablerepo=smecontribs
But it failed on doing it, and now my server is not able to boot up correctly.

Updates should not cause this, it is most likely a (custom) template fragment that is causing this issue to you.

It fails on booting telling that some misspellings in httpd.conf is causing this, and it just loops this message.

Are you able to login with SSH or at the console directly? If not you should probably reboot and press the I at the prompted moment you should then be able to activate services one by one, just hit return to accept defaults only not for httpd-e-smith, do not load that one.

After that you should be able to login again, please do so as root. Now we can start trying to fix things.

First test your configuration file:

Code: [Select]

httpd -t
This should tell you what the problem is with the configuration file, if nothing is wrong it should output:

Code: [Select]

Syntax OK
Please post the lines that are displayed by testing your configuration, perhaps we can help you spot and solve the error.

[loejf]

Hi.
By booting interactively, I can get to the console.
Typing httpd -t gives the output:

syntax error on line 607 of /etc/httpd/conf/httpd.conf:
invalid command 'php_flags', perhaps mis-spelled or defined by a module not included in the server configuration.

Best regards.

[loejf]

Hi.

I can see in httpd.conf that this line belongs to "sysinfo" contribs, I did comment it out and rebooted.
Now the problem moved to line 684, which belongs to "gallery2" contribs. I then commented this out.

Now the server boot up, but it looks very strange, it no longer has its hostname, at no connection on eth1 interface.
It looks like it is in some intermediate installation state !!

Best regards Loejf.

[cactus]

I can see in httpd.conf that this line belongs to "sysinfo" contribs, I did comment it out and rebooted.
Now the problem moved to line 684, which belongs to "gallery2" contribs. I then commented this out.

Do not start hacking at your configuration files, they are templates and problems will come back as they most likely are in template fragments.

Now the server boot up, but it looks very strange, it no longer has its hostname, at no connection on eth1 interface.
It looks like it is in some intermediate installation state !!

That is most likely because of the actions you took before.

Just bare with me and take it step by step... do not start off on your own.

Do you still have the gallery2 and the sysinfo contrib installed?

Check by:

Code: [Select]

rpm -q smeserver-gallery2
rpm -q smeserver-sysinfo
They both should output a version number when installed. If they do please run the following commands:

Code: [Select]

expand-template /etc/httpd/conf/httpd.conf
httpd -t
If the output of the last command is

Code: [Select]

Syntax OK then your problems might be solved. If so you'd be wise to run:

Code: [Select]

signal-event post-upgrade
signal-event reboot
If not we have to digg something further.

Please post the output of the commands using the code-tags (to improve readability) as well as the output of this command:

Could you please also run this command to see what repositories you have enabled:

Code: [Select]

for r in `db yum_repositories show |\
grep repository |\
grep -vi name | \
sed -e 's/=repository//g'`; \
do echo $r: `db yum_repositories getprop $r status`; \
done

[loejf]

Hi Cactus.

Thank you very much for your help.
But I don't even have network access on the server, and there seems to be too many things wrong.
I haven't got the patience to recover this installation.
I have changed the harddrive, and are making a fresh installation of 7.3, since the server MUST be up and running today.

Best regards Loejf.