Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : httpd not starting

[fgraph]

When trying to start apache and /or httpd, I get the following message:
[warn] module frontpage_module is already loaded, skipping

The services give me a fail status. Any ideas on how i can fix this?

[blockcipher]

What control panel are you using if any? Check in your httpd.conf for double entry of this.

My Plesk server does it, but does not fail.

Thanks,

[fgraph]

plesk. I tried to upgrade mysql by getting the new rpms. Now the server no longer boots up unless via rescue mode (1and1's feature). Clearly I messed up. Trying to learn for the fun of it but this is getting fairly frustrating.

[blockcipher]

What does your logs say? Will show you the boot errors. Take a look in /var/log and post here if you like.

[fgraph]

something maybe wrong with apache as well. When i try to start it, I get this message also.

[fgraph]

I've posted everything of Jan 19th from boot.log:
Jan 19 02:01:27 xxxxxxxxx syslog: syslogd startup succeeded
Jan 19 02:01:27 xxxxxxxxx syslog: klogd startup succeeded
Jan 19 02:01:27 xxxxxxxxx keytable: Loading keymap:
Jan 19 02:01:28 xxxxxxxxx keytable: [
Jan 19 02:01:28 xxxxxxxxx keytable:
Jan 19 02:01:28 xxxxxxxxx keytable: Loading system font:
Jan 19 02:01:28 xxxxxxxxx keytable: Couldnt get a file descriptor referring to the console
Jan 19 02:01:28 xxxxxxxxx keytable: [
Jan 19 02:01:28 xxxxxxxxx keytable:
Jan 19 02:01:28 xxxxxxxxx rc: Starting keytable: succeeded
Jan 19 02:01:28 xxxxxxxxx random: Initializing random number generator: succeeded
Jan 19 02:01:29 xxxxxxxxx netfs: Mounting other filesystems: succeeded
Jan 19 02:01:29 xxxxxxxxx autofs: automount startup succeeded
Jan 19 02:01:26 xxxxxxxxx kudzu: succeeded
Jan 19 02:01:26 xxxxxxxxx kudzu: Updating /etc/fstab succeeded
Jan 19 02:01:26 xxxxxxxxx sysctl: net.ipv4.ip_forward = 0
Jan 19 02:01:26 xxxxxxxxx sysctl: net.ipv4.conf.default.rp_filter = 1
Jan 19 02:01:26 xxxxxxxxx sysctl: kernel.sysrq = 0
Jan 19 02:01:26 xxxxxxxxx sysctl: kernel.core_uses_pid = 1
Jan 19 02:01:26 xxxxxxxxx network: Setting network parameters: succeeded
Jan 19 02:01:30 xxxxxxxxx named: named startup succeeded
Jan 19 02:01:30 xxxxxxxxx sshd: succeeded
Jan 19 02:01:34 xxxxxxxxx xinetd: xinetd startup succeeded
Jan 19 02:01:34 xxxxxxxxx ntpd: failed
Jan 19 02:01:34 xxxxxxxxx ntpd: ntpd startup succeeded
Jan 19 02:01:35 xxxxxxxxx courier-imap: Starting imapd succeeded
Jan 19 02:01:35 xxxxxxxxx courier-imap: Starting imap-ssl succeeded
Jan 19 02:01:35 xxxxxxxxx courier-imap: Starting pop3 succeeded
Jan 19 02:01:35 xxxxxxxxx courier-imap: Starting pop3-ssl succeeded
Jan 19 02:01:36 xxxxxxxxx qmail: Starting qmail: succeeded
Jan 19 02:01:40 xxxxxxxxx spamassassin: spamd startup succeeded
Jan 19 02:01:41 xxxxxxxxx psa-spamassassin: Starting psa-spamassassin service: failed
Jan 19 02:01:42 xxxxxxxxx stunnel: Starting stunnel: succeeded
Jan 19 02:01:45 xxxxxxxxx httpd: [Wed Jan 19 02:01:45 2005] [warn] module frontpage_module is already loaded, skipping
Jan 19 02:01:47 xxxxxxxxx httpd: httpd startup succeeded
Jan 19 02:01:48 xxxxxxxxx psa-spamassassin: Starting psa-spamassassin service: failed
Jan 19 02:01:51 xxxxxxxxx psa: Starting Plesk: failed
Jan 19 02:01:53 xxxxxxxxx crond: crond startup succeeded
Jan 19 02:01:54 xxxxxxxxx xfs: xfs startup succeeded
Jan 19 02:01:54 xxxxxxxxx anacron: anacron startup succeeded
Jan 19 02:01:55 xxxxxxxxx atd: atd startup failed
Jan 19 02:01:55 xxxxxxxxx rhnsd: rhnsd startup succeeded
Jan 19 02:01:57 xxxxxxxxx rc: Starting mailman: succeeded
Jan 19 14:13:54 xxxxxxxxx syslog: syslogd startup succeeded
Jan 19 14:13:54 xxxxxxxxx syslog: klogd startup succeeded
Jan 19 14:13:54 xxxxxxxxx keytable: Loading keymap:
Jan 19 14:13:55 xxxxxxxxx keytable: [
Jan 19 14:13:55 xxxxxxxxx keytable:
Jan 19 14:13:55 xxxxxxxxx keytable: Loading system font:
Jan 19 14:13:55 xxxxxxxxx keytable: Couldnt get a file descriptor referring to the console
Jan 19 14:13:55 xxxxxxxxx keytable: [
Jan 19 14:13:55 xxxxxxxxx keytable:
Jan 19 14:13:55 xxxxxxxxx rc: Starting keytable: succeeded
Jan 19 14:13:55 xxxxxxxxx random: Initializing random number generator: succeeded
Jan 19 14:13:55 xxxxxxxxx netfs: Mounting other filesystems: succeeded
Jan 19 14:13:56 xxxxxxxxx autofs: automount startup succeeded
Jan 19 14:13:53 xxxxxxxxx kudzu: succeeded
Jan 19 14:13:53 xxxxxxxxx kudzu: Updating /etc/fstab succeeded
Jan 19 14:13:53 xxxxxxxxx sysctl: net.ipv4.ip_forward = 0
Jan 19 14:13:53 xxxxxxxxx sysctl: net.ipv4.conf.default.rp_filter = 1
Jan 19 14:13:53 xxxxxxxxx sysctl: kernel.sysrq = 0
Jan 19 14:13:53 xxxxxxxxx sysctl: kernel.core_uses_pid = 1
Jan 19 14:13:53 xxxxxxxxx network: Setting network parameters: succeeded
Jan 19 14:13:56 xxxxxxxxx named: named startup succeeded
Jan 19 14:13:57 xxxxxxxxx sshd: succeeded
Jan 19 14:14:00 xxxxxxxxx xinetd: xinetd startup succeeded
Jan 19 14:14:01 xxxxxxxxx ntpd: failed
Jan 19 14:14:01 xxxxxxxxx ntpd: ntpd startup succeeded
Jan 19 14:14:01 xxxxxxxxx courier-imap: Starting imapd succeeded
Jan 19 14:14:02 xxxxxxxxx courier-imap: Starting imap-ssl succeeded
Jan 19 14:14:02 xxxxxxxxx courier-imap: Starting pop3 succeeded
Jan 19 14:14:02 xxxxxxxxx courier-imap: Starting pop3-ssl succeeded
Jan 19 14:14:03 xxxxxxxxx qmail: Starting qmail: succeeded
Jan 19 14:14:07 xxxxxxxxx spamassassin: spamd startup succeeded
Jan 19 14:14:07 xxxxxxxxx psa-spamassassin: Starting psa-spamassassin service: failed
Jan 19 14:14:08 xxxxxxxxx stunnel: Starting stunnel: succeeded
Jan 19 14:14:11 xxxxxxxxx httpd: [Wed Jan 19 14:14:11 2005] [warn] module frontpage_module is already loaded, skipping
Jan 19 14:14:13 xxxxxxxxx httpd: httpd startup succeeded
Jan 19 14:14:13 xxxxxxxxx psa-spamassassin: Starting psa-spamassassin service: failed
Jan 19 14:14:15 xxxxxxxxx psa: Starting Plesk: failed
Jan 19 14:14:17 xxxxxxxxx crond: crond startup succeeded
Jan 19 14:14:19 xxxxxxxxx xfs: xfs startup succeeded
Jan 19 14:14:19 xxxxxxxxx anacron: anacron startup succeeded
Jan 19 14:14:19 xxxxxxxxx atd: atd startup failed
Jan 19 14:14:19 xxxxxxxxx rhnsd: rhnsd startup succeeded
Jan 19 14:14:21 xxxxxxxxx rc: Starting mailman: succeeded

[Criminal#58369]

Does apache work? It also shows that the starting of plesk has failed, i think u can force this, but i dont know the commands...

[fgraph]

Well the thing is that plesk won't run because mysql won't run. When I installed the mysql rpms, I think that may have caused segmentation failures? I suppose this means i have to fix up apache?

[fgraph]

is it true that after upgrading mysql that there can be segmentation faults. That this may be associated with my RAM? I did a fsck and got some errors that it tried to clear up too but seem to keep reoccuring.

[Criminal#58369]

I have seen people who have tryed to upgrade mysql, and have had errors with plesk, because plesk is so tightly integrated into the system. You may want to talk to plesk about this, or look on their forums.

[JTY]

What version of MySQL did you upgrade from? And, what are you running now?

[Steven]

Originally posted by fgraph
is it true that after upgrading mysql that there can be segmentation faults. That this may be associated with my RAM? I did a fsck and got some errors that it tried to clear up too but seem to keep reoccuring.

Yes that is true but its not due to ram. If you upgrade mysql and dont have the correct libs you can get seg faults in things like php etc

[youandme]

hi
i think that problem can fix easily if you remove plesk and reinstall plesk ! remove php apache mysql and all components of plesk ! reinstall them and it will work well ( remm backup before uninstall by using plesk utilities) . With some ver of Plesk run on some OS then u still have Mysql error ( cant start) but infact it work dont know why but with Linux Fedora core1.....always with Plesk 7.0.x didn't try with other ver of plesk

[JTY]

In my experience, if you don't recompile PHP after upgrading from MySQL 4.0 to 4.1, you'll get segfaults. Also, after upgrading be sure to update the "GRANTS" table.