Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: brookes on December 31, 2005, 05:38:43 AM
-
Went away for a week and came back to a server that will not respond to http or https. Check the YUM logs and there was some fairly major installs this morning. Anyone else having the same problems? Can someone give me some advice on the best places to start looking to solve the problem?
Cheers
Stephan.
Log contents:::
Dec 31 05:34:41 Updated: e-smith-lib.noarch 1.15.3-28
Dec 31 05:34:42 Updated: e-smith.noarch 4.2.0-08
Dec 31 05:34:43 Updated: perl-CGI-FormMagick.noarch 0.92-04
Dec 31 05:34:58 Updated: horde.noarch 3.0.7-02sme01
Dec 31 05:35:00 Updated: e-smith-formmagick.noarch 1.3.2-03
Dec 31 05:35:01 Updated: e-smith-runit.noarch 0.0.1-06
Dec 31 05:35:04 Updated: qmail.i386 1.03-13
Dec 31 05:35:05 Updated: e-smith-test.noarch 1.0.1-07
Dec 31 05:35:07 Updated: smeserver-yum.noarch 1.1.2-13
Dec 31 05:35:11 Updated: turba-h3.noarch 2.0.4-02sme01
Dec 31 05:35:14 Updated: ingo-h3.noarch 1.0.2-02sme01
Dec 31 05:35:23 Updated: imp-h3.noarch 4.0.4-02sme01
Dec 31 05:35:25 Updated: e-smith-samba.noarch 1.13.2-07
Dec 31 05:35:25 Updated: e-smith-manager.noarch 1.11.0-12
Dec 31 05:35:26 Updated: e-smith-grub.noarch 0.0.1-21
Dec 31 05:35:27 Updated: e-smith-cvm-unix-local.noarch 1.1.0-03
Dec 31 05:35:29 Updated: e-smith-imap.noarch 1.3.1-15
Dec 31 05:35:29 Updated: smeserver-locale-it.noarch 1.0.1-05
Dec 31 05:35:30 Updated: qmailanalog.i386 0.70-05
Dec 31 05:35:43 Updated: kernel-module-ppp.i686 1.0.2-2_2.6.9_22.0.1.EL
Dec 31 05:35:45 Updated: smeserver-locale-es.noarch 1.0.1-05
Dec 31 05:35:54 Updated: kernel-smp-module-ppp.i686 1.0.2-2_2.6.9_22.0.1.EL
Dec 31 05:35:55 Updated: smeserver-locale-fr.noarch 1.0.1-05
Dec 31 05:35:57 Updated: smeserver-locale-de.noarch 1.0.1-05
Dec 31 05:35:57 Updated: smeserver-support.noarch 1.4.7-23
Dec 31 05:36:05 Updated: e-smith-base.noarch 4.15.8-21
Dec 31 05:36:06 Updated: e-smith-packetfilter.noarch 1.15.1-12
Dec 31 05:36:08 Updated: e-smith-apache.noarch 1.1.2-33
Dec 31 05:36:11 Updated: e-smith-ingo.noarch 0.5.1-02
Dec 31 05:36:12 Updated: e-smith-backup.noarch 1.13.4-06
Dec 31 05:36:15 Updated: e-smith-radiusd.noarch 1.0.0-12
Dec 31 05:36:17 Installed: php-mbstring.i386 4.3.9-3.9
Dec 31 05:36:19 Updated: e-smith-horde.noarch 1.11.1-24
Dec 31 05:36:20 Updated: e-smith-pptpd.noarch 1.11.0-19
Dec 31 05:36:20 Updated: e-smith-flexbackup.noarch 1.9.0-15
Dec 31 05:36:23 Updated: e-smith-imp.noarch 1.11.2-13
Dec 31 05:36:26 Updated: e-smith-portforwarding.noarch 1.1.2-02
Dec 31 05:36:26 Updated: e-smith-ipmasq.noarch 1.10.0-02
Dec 31 05:36:27 Updated: e-smith-mysql.noarch 1.11.1-13
Dec 31 05:36:28 Updated: e-smith-oidentd.noarch 1.1.0-10
Dec 31 05:36:29 Updated: e-smith-dynamicdns-dyndns.org.noarch 1.4.0-03
Dec 31 05:36:30 Updated: e-smith-netatalk.noarch 1.13.0-08
Dec 31 05:36:31 Updated: e-smith-LPRng.noarch 1.13.3-09
Dec 31 05:36:31 Updated: e-smith-viewlogfiles.noarch 1.7.2-03
Dec 31 05:36:40 Updated: e-smith-php.noarch 1.11.0-09
Dec 31 05:36:50 Updated: e-smith-ldap.noarch 4.11.3-03
Dec 31 05:36:52 Updated: e-smith-hosts.noarch 1.13.3-03
Dec 31 05:36:56 Updated: e-smith-domains.noarch 1.3.3-04
Dec 31 05:36:58 Updated: e-smith-ntp.noarch 1.15.2-02
Dec 31 05:36:58 Updated: e-smith-dynamicdns-dyndns.noarch 1.4.0-02
Dec 31 05:37:00 Updated: e-smith-proftpd.noarch 1.11.0-26
Dec 31 05:37:01 Updated: e-smith-qmailanalog.noarch 1.11.2-02
Dec 31 05:37:02 Updated: e-smith-tinydns.noarch 0.5.0-20
Dec 31 05:37:03 Updated: e-smith-dynamicdns-yi.noarch 1.4.0-02
Dec 31 05:37:03 Updated: e-smith-ibays.noarch 1.1.3-04
Dec 31 05:37:04 Updated: e-smith-dynamicdns-tzo.noarch 1.4.0-02
Dec 31 05:37:04 Updated: e-smith-quota.noarch 1.9.2-05
Dec 31 05:37:05 Updated: e-smith-turba.noarch 1.5.1-09
Dec 31 05:37:05 Updated: e-smith-starterwebsite.noarch 0.2.2-02
Dec 31 05:37:07 Updated: e-smith-proxy.noarch 4.13.2-05
Dec 31 05:37:08 Updated: e-smith-openssh.noarch 1.11.0-21
Dec 31 05:37:10 Updated: e-smith-dnscache.noarch 0.5.1-06
Dec 31 05:37:11 Updated: e-smith-nutUPS.noarch 1.1.0-07
Dec 31 05:37:11 Updated: e-smith-lib-compspec.noarch 0.3.0-05
Dec 31 05:37:13 Updated: ppp.i386 2.4.3-7.rhel4.1
Dec 31 05:37:14 Updated: smeserver-release.noarch 24:7.0beta9-02
Dec 31 05:37:18 Updated: libtool-libs.i386 1.5.6-4.EL4.1.c4
Dec 31 05:37:19 Updated: e-smith-devtools.noarch 1.13.1-06
Dec 31 05:37:19 Updated: e-smith-lib-Tai64n.noarch 1.15.3-28
Dec 31 05:37:21 Updated: e-smith-pop3.noarch 1.1.0-03
Dec 31 05:37:23 Updated: e-smith-email.noarch 4.15.4-02
Dec 31 05:37:27 Updated: e-smith-qmail.noarch 1.9.0-16
-
Can someone give me some advice on the best places to start looking to solve the problem?
Yes. Report your problem via the Bug Tracker. 7.0beta9 is a test release - the only reason it's out there is for you to test it and report problems so that they can be fixed.
-
"signal-event post-upgrade", followed by "signal-event reboot" should solve the problem.
-
Yes. Report your problem via the Bug Tracker. 7.0beta9 is a test release - the only reason it's out there is for you to test it and report problems so that they can be fixed.
Thanks Charlie and when I establish that it is actually a bug I will report it. At the moment I am not sure if it is something I have done when I modified YUM to get all the updates. I did restart the server but it may be that I need to do a "signal-event post-upgrade" as suggested by Robert. I will give that a go and I will try dredging through the logs to see where the problem is?
I don't want to create a bug record for a "User" problem so if there is anywhere people can think of that I should be looking please let me know. I checked through the YUM logs directory and the logs do not tell me the results of the actual update action and I assume that would be recorded in the RPM logs but I am yet to find those.
Cheers
Stephan.
-
Oddly enough, I may have had the same problem. So, we may have a bug here.
I installed 7b8. Then a few weeks later, I did an update through the server panel, restarted, and then no apache. Restarted again and started getting an error about a corrupted line 131 in httpd.conf (SSLCipherSuite). The server wouldn't even boot up.
To fix it I commented out that line, and then went into the templates and blanked out the code in the ciphersuite file. Sorry, I can't remember anymore than that.
I do know that it fixed the problem. I figured I just had a corrupted install, but maybe not?
-
Oddly enough, I may have had the same problem. So, we may have a bug here.
I installed 7b8. Then a few weeks later, I did an update through the server panel, restarted, and then no apache. Restarted again and started getting an error about a corrupted line 131 in httpd.conf (SSLCipherSuite). The server wouldn't even boot up.
To fix it I commented out that line, and then went into the templates and blanked out the code in the ciphersuite file. Sorry, I can't remember anymore than that.
I do know that it fixed the problem. I figured I just had a corrupted install, but maybe not?
Doing a signal-event console-save solved the httpd.conf line 131 problem for me.
-
Hmm, ok I'll give it a shot. Since I altered my 35SSL10SSLCipherSuite file, does anyone have the code that is supposed to be in that file? It was only about 3 lines in my original.
thanks
chris
-
"signal-event post-upgrade", followed by "signal-event reboot" should solve the problem.
Robert,
Exactly, This did solve the problem, many thanks. Do you think this is an isolated thing or needs to be tracked as a bug?
Cheers
Stephan.
-
I had the same issue on the morning of Jan 1.
"signal-event post-upgrade", followed by "signal-event reboot" fixed it.
-
"signal-event post-upgrade", followed by "signal-event reboot" should solve the problem.
Robert,
Exactly, This did solve the problem, many thanks. Do you think this is an isolated thing or needs to be tracked as a bug?
Cheers
Stephan.
It is already tracked as Bug: 378 http://bugs.contribs.org/show_bug.cgi?id=378
(SSLCipherSuite not set after yum upgrade)